Internet Society Frontpage

Search/Site Map Membership
About the Internet Standards
Publications Public Policy
About ISOC Education

Publications 

Become an ISOC Member

Internet Documents

RFCs 3100 - 3199s

RFCs All DocumentsSTDs Internet Standards DocumentsBCPs Best Current Practice DocumentsFYIs Informational Documents
 

 
RFC 3101 The OSPF Not-So-Stubby Area (NSSA) Option
 
Authors:P. Murphy.
Date:January 2003
Formats:txt pdf
Obsoletes:RFC 1587
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3101
This memo documents an optional type of Open Shortest Path First(OSPF) area that is somewhat humorously referred to as a "not-so- stubby" area (or NSSA). NSSAs are similar to the existing OSPF stub area configuration option but have the additional capability of importing AS external routes in a limited fashion.

The OSPF NSSA Option was originally defined in RFC 1587. The functional differences between this memo and RFC 1587 are explained in Appendix F. All differences, while expanding capability, are backward-compatible in nature. Implementations of this memo and ofRFC 1587 will interoperate.

 
RFC 3102 Realm Specific IP: Framework
 
Authors:M. Borella, J. Lo, D. Grabelsky, G. Montenegro.
Date:October 2001
Formats:txt pdf
Status:EXPERIMENTAL
DOI:10.17487/RFC 3102
This document examines the general framework of Realm Specific IP(RSIP). RSIP is intended as a alternative to NAT in which the end- to-end integrity of packets is maintained. We focus on implementation issues, deployment scenarios, and interaction with other layer-three protocols.
 
RFC 3103 Realm Specific IP: Protocol Specification
 
Authors:M. Borella, D. Grabelsky, J. Lo, K. Taniguchi.
Date:October 2001
Formats:txt pdf
Status:EXPERIMENTAL
DOI:10.17487/RFC 3103
This document presents a protocol with which to implement RealmSpecific IP (RSIP). The protocol defined herein allows negotiation of resources between an RSIP host and gateway, so that the host can lease some of the gateway's addressing parameters in order to establish a global network presence. This protocol is designed to operate on the application layer and to use its own TCP or UDP port.In particular, the protocol allows a gateway to allocate addressing and control parameters to a host such that a flow policy can be enforced at the gateway.
 
RFC 3104 RSIP Support for End-to-end IPsec
 
Authors:G. Montenegro, M. Borella.
Date:October 2001
Formats:txt pdf
Status:EXPERIMENTAL
DOI:10.17487/RFC 3104
This document proposes mechanisms that enable Realm Specific IP(RSIP) to handle end-to-end IPsec (IP Security).
 
RFC 3105 Finding an RSIP Server with SLP
 
Authors:J. Kempf, G. Montenegro.
Date:October 2001
Formats:txt pdf
Status:EXPERIMENTAL
DOI:10.17487/RFC 3105
This document contains an SLP service type template that describes the advertisements made by RSIP servers for their services. ServiceLocation Protocol (SLP) is an IETF standards track protocol specifically designed to allow clients to find servers offering particular services. Since RSIP (Realm Specific IP) clients require a mechanism to discover RSIP servers, SLP is a natural match for a solution. The service type template is the basis for an InternetAssigned Numbers Authority (IANA) standard definition of the advertisements offered by RSIP servers, an important step toward interoperability.
 
RFC 3106 ECML v1.1: Field Specifications for E-Commerce
 
Authors:D. Eastlake 3rd, T. Goldstein.
Date:April 2001
Formats:txt pdf
Obsoletes:RFC 2706
Updated by:RFC 4112
Status:INFORMATIONAL
DOI:10.17487/RFC 3106
Customers are frequently required to enter substantial amounts of information at an Internet merchant site in order to complete a purchase or other transaction, especially the first time they go there. A standard set of information fields is defined as the first version of an Electronic Commerce Modeling Language (ECML) so that this task can be more easily automated, for example by wallet software that could fill in fields. Even for the manual data entry case, customers will be less confused by varying merchant sites if a substantial number adopt these standard fields. In addition, some fields are defined for merchant to consumer communication.
 
RFC 3107 Carrying Label Information in BGP-4
 
Authors:Y. Rekhter, E. Rosen.
Date:May 2001
Formats:txt pdf
Updated by:RFC 6790
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3107
This document specifies the way in which the label mapping information for a particular route is piggybacked in the same BorderGateway Protocol (BGP) Update message that is used to distribute the route itself. When BGP is used to distribute a particular route, it can be also be used to distribute a Multiprotocol Label Switching(MPLS) label which is mapped to that route.
 
RFC 3108 Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer Connections
 
Authors:R. Kumar, M. Mostafa.
Date:May 2001
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3108
This document describes conventions for using the Session DescriptionProtocol (SDP) described in RFC 2327 for controlling ATM BearerConnections, and any associated ATM Adaptation Layer (AAL). The AALs addressed are Type 1, Type 2 and Type 5. This list of conventions is meant to be exhaustive. Individual applications can use subsets of these conventions. Further, these conventions are meant to comply strictly with the SDP syntax as defined in RFC 2327.
 
RFC 3109 Request to Move STD 39 to Historic Status
 
Authors:R. Braden, R. Bush, J. Klensin.
Date:May 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3109
This memo changes the status of STD 39, BBN Report 1822,"Specification of the Interconnection of a Host and an IMP", fromStandard to Historic.
 
RFC 3110 RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)
 
Authors:D. Eastlake 3rd.
Date:May 2001
Formats:txt pdf
Obsoletes:RFC 2537
Updated by:RFC 6944
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3110
This document describes how to produce RSA/SHA1 SIG resource records(RRs) in Section 3 and, so as to completely replace RFC 2537, describes how to produce RSA KEY RRs in Section 2.

Since the adoption of a Proposed Standard for RSA signatures in theDNS (Domain Name Space), advances in hashing have been made. A newDNS signature algorithm is defined to make these advances available in SIG RRs. The use of the previously specified weaker mechanism is deprecated. The algorithm number of the RSA KEY RR is changed to correspond to this new SIG algorithm. No other changes are made toDNS security.

 
RFC 3111 Service Location Protocol Modifications for IPv6
 
Authors:E. Guttman.
Date:May 2001
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3111
This document defines the Service Location Protocol Version 2's(SLPv2) use over IPv6 networks. Since this protocol relies on UDP and TCP, the changes to support its use over IPv6 are minor.

This document does not describe how to use SLPv1 over IPv6 networks.There is at the time of this publication no implementation or deployment of SLPv1 over IPv6. It is RECOMMENDED that SLPv2 be used in general, and specifically on networks which support IPv6.

 
RFC 3112 LDAP Authentication Password Schema
 
Authors:K. Zeilenga.
Date:May 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3112
This document describes schema in support of user/password authentication in a LDAP (Lightweight Directory Access Protocol) directory including the authPassword attribute type. This attribute type holds values derived from the user's password(s) (commonly using cryptographic strength one-way hash). authPassword is intended to used instead of userPassword.
 
RFC 3113 3GPP-IETF Standardization Collaboration
 
Authors:K. Rosenbrock, R. Sanmugam, S. Bradner, J. Klensin.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3113
This document describes the standardization collaboration between3GPP and IETF.
 
RFC 3114 Implementing Company Classification Policy with the S/MIME Security Label
 
Authors:W. Nicolls.
Date:May 2002
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3114
This document discusses how company security policy for data classification can be mapped to the S/MIME security label. Actual policies from three companies provide worked examples.
 
RFC 3115 Mobile IP Vendor/Organization-Specific Extensions
 
Authors:G. Dommety, K. Leung.
Date:April 2001
Formats:txt pdf
Obsoletes:RFC 3025
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3115
This document defines two new extensions to Mobile IP. These extensions will facilitate equipment vendors and organizations to make specific use of these extensions as they see fit for research or deployment purposes.
 
RFC 3116 Methodology for ATM Benchmarking
 
Authors:J. Dunn, C. Martin.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3116
This document discusses and defines a number of tests that may be used to describe the performance characteristics of ATM (AsynchronousTransfer Mode) based switching devices. In addition to defining the tests this document also describes specific formats for reporting the results of the tests.

This memo is a product of the Benchmarking Methodology Working Group(BMWG) of the Internet Engineering Task Force (IETF).

 
RFC 3117 On the Design of Application Protocols
 
Authors:M. Rose.
Date:November 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3117
This memo describes the design principles for the Blocks eXtensible eXchange Protocol (BXXP). BXXP is a generic application protocol framework for connection-oriented, asynchronous interactions. The framework permits simultaneous and independent exchanges within the context of a single application user-identity, supporting both textual and binary messages.
 
RFC 3118 Authentication for DHCP Messages
 
Authors:R. Droms, Ed., W. Arbaugh, Ed..
Date:June 2001
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3118
This document defines a new Dynamic Host Configuration Protocol(DHCP) option through which authorization tickets can be easily generated and newly attached hosts with proper authorization can be automatically configured from an authenticated DHCP server. DHCP provides a framework for passing configuration information to hosts on a TCP/IP network. In some situations, network administrators may wish to constrain the allocation of addresses to authorized hosts.Additionally, some network administrators may wish to provide for authentication of the source and contents of DHCP messages.
 
RFC 3119 A More Loss-Tolerant RTP Payload Format for MP3 Audio
 
Authors:R. Finlayson.
Date:June 2001
Formats:txt pdf
Obsoleted by:RFC 5219
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3119
This document describes a RTP (Real-Time Protocol) payload format for transporting MPEG (Moving Picture Experts Group) 1 or 2, layer III audio (commonly known as "MP3"). This format is an alternative to that described in RFC 2250, and performs better if there is packet loss.
 
RFC 3120 A URN Namespace for XML.org
 
Authors:K. Best, N. Walsh.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3120
This document describes a URN (Uniform Resource Name) namespace that is engineered by the Organization for the Advancement of StructuredInformation Standards (OASIS) for naming persistent resources stored in the XML.org repository (such as XML (Extensible Markup Language)Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other documents).
 
RFC 3121 A URN Namespace for OASIS
 
Authors:K. Best, N. Walsh.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3121
This document describes a URN (Uniform Resource Name) namespace that is engineered by the Organization for the Advancement of StructuredInformation Standards (OASIS) for naming persistent resources published by OASIS (such as OASIS Standards, XML (Extensible MarkupLanguage) Document Type Definitions, XML Schemas, Namespaces,Stylesheets, and other documents).
 
RFC 3122 Extensions to IPv6 Neighbor Discovery for Inverse Discovery Specification
 
Authors:A. Conta.
Date:June 2001
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3122
This memo describes extensions to the IPv6 Neighbor Discovery that allow a node to determine and advertise an IPv6 address corresponding to a given link-layer address. These extensions are called InverseNeighbor Discovery. The Inverse Neighbor Discovery (IND) was originally developed for Frame Relay networks, but may also apply to other networks with similar behavior.
 
RFC 3123 A DNS RR Type for Lists of Address Prefixes (APL RR)
 
Authors:P. Koch.
Date:June 2001
Formats:txt pdf
Status:EXPERIMENTAL
DOI:10.17487/RFC 3123
The Domain Name System (DNS) is primarily used to translate domain names into IPv4 addresses using A RRs (Resource Records). Several approaches exist to describe networks or address ranges. This document specifies a new DNS RR type "APL" for address prefix lists.
 
RFC 3124 The Congestion Manager
 
Authors:H. Balakrishnan, S. Seshan.
Date:June 2001
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3124
This document describes the Congestion Manager (CM), an end-system module that:

(i) Enables an ensemble of multiple concurrent streams from a sender destined to the same receiver and sharing the same congestion properties to perform proper congestion avoidance and control, and

(ii) Allows applications to easily adapt to network congestion.

 
RFC 3125 Electronic Signature Policies
 
Authors:J. Ross, D. Pinkas, N. Pope.
Date:September 2001
Formats:txt pdf
Status:EXPERIMENTAL
DOI:10.17487/RFC 3125
This document defines signature policies for electronic signatures. A signature policy is a set of rules for the creation and validation of an electronic signature, under which the validity of signature can be determined. A given legal/contractual context may recognize a particular signature policy as meeting its requirements.

A signature policy has a globally unique reference, which is bound to an electronic signature by the signer as part of the signature calculation.

The signature policy needs to be available in human readable form so that it can be assessed to meet the requirements of the legal and contractual context in which it is being applied.

To allow for the automatic processing of an electronic signature another part of the signature policy specifies the electronic rules for the creation and validation of the electronic signature in a computer processable form. In the current document the format of the signature policy is defined using ASN.1.

The contents of this document is based on the signature policy defined in ETSI TS 101 733 V.1.2.2 (2000-12) Copyright (C).Individual copies of this ETSI deliverable can be downloaded from http://www.etsi.org.

 
RFC 3126 Electronic Signature Formats for long term electronic signatures
 
Authors:D. Pinkas, J. Ross, N. Pope.
Date:September 2001
Formats:txt pdf
Obsoleted by:RFC 5126
Status:INFORMATIONAL
DOI:10.17487/RFC 3126
This document defines the format of an electronic signature that can remain valid over long periods. This includes evidence as to its validity even if the signer or verifying party later attempts to deny(i.e., repudiates the validity of the signature).

The format can be considered as an extension to RFC 2630 and RFC2634, where, when appropriate additional signed and unsigned attributes have been defined.

The contents of this Informational RFC is technically equivalent toETSI TS 101 733 V.1.2.2. The ETSI TS is under the ETSI Copyright (C).Individual copies of this ETSI deliverable can be downloaded from http://www.etsi.org

 
RFC 3127 Authentication, Authorization, and Accounting: Protocol Evaluation
 
Authors:D. Mitton, M. St.Johns, S. Barkley, D. Nelson, B. Patil, M. Stevens, B. Wolff.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3127
This memo represents the process and findings of the Authentication,Authorization, and Accounting Working Group (AAA WG) panel evaluating protocols proposed against the AAA Network Access Requirements, RFC2989. Due to time constraints of this report, this document is not as fully polished as it might have been desired. But it remains mostly in this state to document the results as presented.
 
RFC 3128 Protection Against a Variant of the Tiny Fragment Attack (RFC 1858)
 
Authors:I. Miller.
Date:June 2001
Formats:txt pdf
Updates:RFC 1858
Status:INFORMATIONAL
DOI:10.17487/RFC 3128
This document discusses how RFC 1858 compliant filters can be vulnerable to a variant of the "Tiny Fragment Attack" described in section 3.1 of the RFC. This document describes the attack and recommends corrective action.
 
RFC 3129 Requirements for Kerberized Internet Negotiation of Keys
 
Authors:M. Thomas.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3129
The goal of this document is to produce a streamlined, fast, easily managed, and cryptographically sound protocol without requiring public key.
 
RFC 3130 Notes from the State-Of-The-Technology: DNSSEC
 
Authors:E. Lewis.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3130
This is a memo of a DNSSEC (Domain Name System Security Extensions) status meeting.
 
RFC 3131 3GPP2-IETF Standardization Collaboration
 
Authors:S. Bradner, P. Calhoun, H. Cuschieri, S. Dennett, G. Flynn, M. Lipford, M. McPheters.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3131
This document describes the standardization collaboration between3GPP2 and IETF.
 
RFC 3132 Dormant Mode Host Alerting ("IP Paging") Problem Statement
 
Authors:J. Kempf.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3132
This memo describes paging, assesses the need for IP paging, and presents a list of recommendations for Seamoby charter items regarding work on paging. The results are specifically directed toward the task undertaken by the design team, and are not meant to be the definitive word on paging for all time, nor to be binding onSeamoby or other working groups, should the situation with regard toIP mobility protocols or radio link support undergo a major change.
 
RFC 3133 Terminology for Frame Relay Benchmarking
 
Authors:J. Dunn, C. Martin.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3133
This memo discusses and defines terms associated with performance benchmarking tests and the results of these tests in the context of frame relay switching devices.
 
RFC 3134 Terminology for ATM ABR Benchmarking
 
Authors:J. Dunn, C. Martin.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3134
This memo discusses and defines terms associated with performance benchmarking tests and the results of these tests in the context ofAsynchronous Transfer Mode (ATM) based switching devices supportingABR (Available Bit Rate). The terms defined in this memo will be used in addition to terms defined in RFCs 1242, 2285, and 2544 and2761. This memo is a product of the Benchmarking Methodology WorkingGroup (BMWG) of the Internet Engineering Task Force (IETF).
 
RFC 3135 Performance Enhancing Proxies Intended to Mitigate Link-Related Degradations
 
Authors:J. Border, M. Kojo, J. Griner, G. Montenegro, Z. Shelby.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3135
This document is a survey of Performance Enhancing Proxies (PEPs) often employed to improve degraded TCP performance caused by characteristics of specific link environments, for example, in satellite, wireless WAN, and wireless LAN environments. Different types of Performance Enhancing Proxies are described as well as the mechanisms used to improve performance. Emphasis is put on proxies operating with TCP. In addition, motivations for their development and use are described along with some of the consequences of using them, especially in the context of the Internet.
 
RFC 3136 The SPIRITS Architecture
 
Authors:L. Slutsman, Ed., I. Faynberg, H. Lu, M. Weissman.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3136
This document describes the architecture for supporting SPIRITS services, which are those originating in the PSTN (Public SwitchedTelephone Network)and necessitating the interactions between the PSTN and the Internet. (Internet Call Waiting, Internet Caller-IDDelivery, and Internet Call Forwarding are examples of SPIRIT services.) Specifically, it defines the components constituting the architecture and the interfaces between the components.
 
RFC 3137 OSPF Stub Router Advertisement
 
Authors:A. Retana, L. Nguyen, R. White, A. Zinin, D. McPherson.
Date:June 2001
Formats:txt pdf
Obsoleted by:RFC 6987
Status:INFORMATIONAL
DOI:10.17487/RFC 3137
This memo describes a backward-compatible technique that may be used by OSPF (Open Shortest Path First) implementations to advertise unavailability to forward transit traffic or to lower the preference level for the paths through such a router. In some cases, it is desirable not to route transit traffic via a specific OSPF router.However, OSPF does not specify a standard way to accomplish this.
 
RFC 3138 Extended Assignments in 233/8
 
Authors:D. Meyer.
Date:June 2001
Formats:txt pdf
Obsoleted by:RFC 5771
Status:INFORMATIONAL
DOI:10.17487/RFC 3138
This memo provides describes the mapping of the GLOP addresses corresponding to the private AS space.
 
RFC 3139 Requirements for Configuration Management of IP-based Networks
 
Authors:L. Sanchez, K. McCloghrie, J. Saperia.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3139
This memo discusses different approaches to configure networks and identifies a set of configuration management requirements for IP- based networks.
 
RFC 3140 Per Hop Behavior Identification Codes
 
Authors:D. Black, S. Brim, B. Carpenter, F. Le Faucheur.
Date:June 2001
Formats:txt pdf
Obsoletes:RFC 2836
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3140
This document defines a 16 bit encoding mechanism for the identification of differentiated services Per Hop Behaviors in protocol messages. It replaces RFC 2836.
 
RFC 3141 CDMA2000 Wireless Data Requirements for AAA
 
Authors:T. Hiller, P. Walsh, X. Chen, M. Munson, G. Dommety, S. Sivalingham, B. Lim, P. McCann, H. Shiino, B. Hirschman, S. Manning, R. Hsu, H. Koo, M. Lipford, P. Calhoun, C. Lo, E. Jaques, E. Campbell, Y.Xu,S.Baba,T.Ayaki,T.Seki,A.Hameed.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3141
This memo specifies cdma2000 wireless data AAA (Authentication,Authorization, Accounting) requirements associated with third generation wireless architecture that supports roaming among service providers for traditional PPP and Mobile IP services.
 
RFC 3142 An IPv6-to-IPv4 Transport Relay Translator
 
Authors:J. Hagino, K. Yamamoto.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3142
The document describes an IPv6-to-IPv4 transport relay translator(TRT). It enables IPv6-only hosts to exchange {TCP,UDP} traffic withIPv4-only hosts. A TRT system, which locates in the middle, translates {TCP,UDP}/IPv6 to {TCP,UDP}/IPv4, or vice versa.

The memo talks about how to implement a TRT system using existing technologies. It does not define any new protocols.

 
RFC 3143 Known HTTP Proxy/Caching Problems
 
Authors:I. Cooper, J. Dilley.
Date:June 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3143
This document catalogs a number of known problems with World Wide Web(WWW) (caching) proxies and cache servers. The goal of the document is to provide a discussion of the problems and proposed workarounds, and ultimately to improve conditions by illustrating problems. The construction of this document is a joint effort of the Web caching community.
 
RFC 3144 Remote Monitoring MIB Extensions for Interface Parameters Monitoring
 
Authors:D. Romascanu.
Date:August 2001
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3144
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community.The document proposes an extension to the Remote Monitoring MIB with a method of sorting the interfaces of a monitored device according to values of parameters specific to this interface.
 
RFC 3145 L2TP Disconnect Cause Information
 
Authors:R. Verma, M. Verma, J. Carlson.
Date:July 2001
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3145
This document provides an extension to the Layer 2 Tunneling Protocol("L2TP"), a mechanism for tunneling Point-to-Point Protocol (PPP) sessions. L2TP lacks a mechanism for a host to provide PPP-related disconnect cause information to another host. This information, provided by the extension described in this document, can be useful for accounting and debugging purposes.
 
RFC 3146 Transmission of IPv6 Packets over IEEE 1394 Networks
 
Authors:K. Fujisawa, A. Onoe.
Date:October 2001
Formats:txt pdf
Updated by:RFC 8064
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3146
This document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE1394 networks.
 
RFC 3147 Generic Routing Encapsulation over CLNS Networks
 
Authors:P. Christian.
Date:July 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3147
This document proposes a method for transporting an arbitrary protocol over a CLNS (Connectionless Network Service) network usingGRE (Generic Routing Encapsulation). This may then be used as a method to tunnel IPv4 or IPv6 over CLNS.
 
RFC 3148 A Framework for Defining Empirical Bulk Transfer Capacity Metrics
 
Authors:M. Mathis, M. Allman.
Date:July 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3148
This document defines a framework for standardizing multiple BTC(Bulk Transport Capacity) metrics that parallel the permitted transport diversity.
 
RFC 3149 MGCP Business Phone Packages
 
Authors:A. Srinath, G. Levendel, K. Fritz, R. Kalyanaram.
Date:September 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3149
This document describes a collection of MGCP (Media Gateway ControlProtocol) packages that can be used to take advantage of the feature keys and displays on digital business phones and IP-Phones.
 
RFC 3150 End-to-end Performance Implications of Slow Links
 
Authors:S. Dawkins, G. Montenegro, M. Kojo, V. Magret.
Date:July 2001
Formats:txt pdf
Also:BCP 0048
Status:BEST CURRENT PRACTICE
DOI:10.17487/RFC 3150
This document makes performance-related recommendations for users of network paths that traverse "very low bit-rate" links.

"Very low bit-rate" implies "slower than we would like". This recommendation may be useful in any network where hosts can saturate available bandwidth, but the design space for this recommendation explicitly includes connections that traverse 56 Kb/second modem links or 4.8 Kb/second wireless access links - both of which are widely deployed.

This document discusses general-purpose mechanisms. Where application-specific mechanisms can outperform the relevant general- purpose mechanism, we point this out and explain why.

This document has some recommendations in common with RFC 2689,"Providing integrated services over low-bitrate links", especially in areas like header compression. This document focuses more on traditional data applications for which "best-effort delivery" is appropriate.

 
RFC 3151 A URN Namespace for Public Identifiers
 
Authors:N. Walsh, J. Cowan, P. Grosso.
Date:August 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3151
This document describes a URN (Uniform Resource Name) namespace that is designed to allow Public Identifiers to be expressed in URI(Uniform Resource Identifiers) syntax.
 
RFC 3152 Delegation of IP6.ARPA
 
Authors:R. Bush.
Date:August 2001
Formats:txt pdf
Obsoleted by:RFC 3596
Updates:RFC 2874, RFC 2772, RFC 2766, RFC 2553, RFC 1886
Also:BCP 0049
Status:BEST CURRENT PRACTICE
DOI:10.17487/RFC 3152
This document discusses the need for delegation of the IP6.ARPA DNS zone, and specifies a plan for the technical operation thereof.
 
RFC 3153 PPP Multiplexing
 
Authors:R. Pazhyannur, I. Ali, C. Fox.
Date:August 2001
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3153
This document describes a method to reduce the PPP (Point-to-PointProtocol) framing overhead used to transport small packets over slow links.
 
RFC 3154 Requirements and Functional Architecture for an IP Host Alerting Protocol
 
Authors:J. Kempf, C. Castelluccia, P. Mutaf, N. Nakajima, Y. Ohba, R. Ramjee, Y. Saifullah, B. Sarikaya, X. Xu.
Date:August 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3154
This document develops an architecture and a set of requirements needed to support alerting of hosts that are in dormant mode. The architecture and requirements are designed to guide development of anIP protocol for alerting dormant IP mobile hosts, commonly called paging.
 
RFC 3155 End-to-end Performance Implications of Links with Errors
 
Authors:S. Dawkins, G. Montenegro, M. Kojo, V. Magret, N. Vaidya.
Date:August 2001
Formats:txt pdf
Also:BCP 0050
Status:BEST CURRENT PRACTICE
DOI:10.17487/RFC 3155
This document discusses the specific TCP mechanisms that are problematic in environments with high uncorrected error rates, and discusses what can be done to mitigate the problems without introducing intermediate devices into the connection.
 
RFC 3156 MIME Security with OpenPGP
 
Authors:M. Elkins, D. Del Torto, R. Levien, T. Roessler.
Date:August 2001
Formats:txt pdf
Updates:RFC 2015
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3156
This document describes how the OpenPGP Message Format can be used to provide privacy and authentication using the Multipurpose InternetMail Extensions (MIME) security content types described in RFC 1847.
 
RFC 3157 Securely Available Credentials - Requirements
 
Authors:A. Arsenault, S. Farrell.
Date:August 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3157
This document describes requirements to be placed on SecurelyAvailable Credentials (SACRED) protocols.
 
RFC 3158 RTP Testing Strategies
 
Authors:C. Perkins, J. Rosenberg, H. Schulzrinne.
Date:August 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3158
This memo describes a possible testing strategy for RTP (real-time transport protocol) implementations.
 
RFC 3159 Structure of Policy Provisioning Information (SPPI)
 
Authors:K. McCloghrie, M. Fine, J. Seligson, K. Chan, S. Hahn, R. Sahita, A. Smith, F. Reichmeyer.
Date:August 2001
Formats:txt pdf
Status:HISTORIC
DOI:10.17487/RFC 3159
This document, the Structure of Policy Provisioning Information(SPPI), defines the adapted subset of SNMP's Structure of ManagementInformation (SMI) used to write Policy Information Base (PIB) modules.

RFC 2748 defines the COPS protocol, and RFC 2749 describes how theCOPS protocol is used to provide for the outsourcing of policy decisions for RSVP. Another usage of the COPS protocol, for the provisioning of policy, is introduced in RFC 3084. In this provisioning model, the policy information is viewed as a collection of Provisioning Classes (PRCs) and Provisioning Instances (PRIs) residing in a virtual information store, termed the PolicyInformation Base (PIB). Collections of related Provisioning Classes are defined in a PIB module.

 
RFC 3160 The Tao of IETF - A Novice's Guide to the Internet Engineering Task Force
 
Authors:S. Harris.
Date:August 2001
Formats:txt pdf
Obsoletes:RFC 1718
Obsoleted by:RFC 4677
Status:INFORMATIONAL
DOI:10.17487/RFC 3160
This document describes the inner workings of IETF meetings andWorking Groups, discusses organizations related to the IETF, and introduces the standards process.
 
RFC 3161 Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)
 
Authors:C. Adams, P. Cain, D. Pinkas, R. Zuccherato.
Date:August 2001
Formats:txt pdf
Updated by:RFC 5816
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3161
This document describes the format of a request sent to a TimeStamping Authority (TSA) and of the response that is returned. It also establishes several security-relevant requirements for TSA operation, with regards to processing requests to generate responses.
 
RFC 3162 RADIUS and IPv6
 
Authors:B. Aboba, G. Zorn, D. Mitton.
Date:August 2001
Formats:txt pdf
Updated by:RFC 8044
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3162
This document specifies the operation of RADIUS (RemoteAuthentication Dial In User Service) when run over IPv6 as well as the RADIUS attributes used to support IPv6 network access.
 
RFC 3163 ISO/IEC 9798-3 Authentication SASL Mechanism
 
Authors:R. Zuccherato, M. Nystrom.
Date:August 2001
Formats:txt pdf
Status:EXPERIMENTAL
DOI:10.17487/RFC 3163
This document defines a SASL (Simple Authentication and SecurityLayer) authentication mechanism based on ISO/IEC 9798-3 and FIPS PUB196 entity authentication.
 
RFC 3164 The BSD Syslog Protocol
 
Authors:C. Lonvick.
Date:August 2001
Formats:txt pdf
Obsoleted by:RFC 5424
Status:INFORMATIONAL
DOI:10.17487/RFC 3164
This document describes the observed behavior of the syslog protocol.This protocol has been used for the transmission of event notification messages across networks for many years. While this protocol was originally developed on the University of CaliforniaBerkeley Software Distribution (BSD) TCP/IP system implementations, its value to operations and management has led it to be ported to many other operating systems as well as being embedded into many other networked devices.
 
RFC 3165 Definitions of Managed Objects for the Delegation of Management Scripts
 
Authors:D. Levi, J. Schoenwaelder.
Date:August 2001
Formats:txt pdf
Obsoletes:RFC 2592
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3165
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community.In particular, it describes a set of managed objects that allow the delegation of management scripts to distributed managers.
 
RFC 3166 Request to Move RFC 1403 to Historic Status
 
Authors:D. Meyer, J. Scudder.
Date:August 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3166
RFC 1403, "BGP OSPF Interaction", describes technology which is no longer used. This document requests that RFC 1403 be moved toHistoric status.
 
RFC 3167 Request to Move RFC 1745 to Historic Status
 
Authors:D. Meyer, J. Scudder.
Date:August 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3167
RFC 1745, "BGP4/IDRP for IP---OSPF Interaction", describes technology which was never deployed in the public internet. This document requests that RFC 1745 be moved to Historic status.
 
RFC 3168 The Addition of Explicit Congestion Notification (ECN) to IP
 
Authors:K. Ramakrishnan, S. Floyd, D. Black.
Date:September 2001
Formats:txt pdf
Obsoletes:RFC 2481
Updates:RFC 2003, RFC 2474, RFC 2401, RFC 0793
Updated by:RFC 4301, RFC 6040
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3168
This memo specifies the incorporation of ECN (Explicit CongestionNotification) to TCP and IP, including ECN's use of two bits in theIP header.
 
RFC 3169 Criteria for Evaluating Network Access Server Protocols
 
Authors:M. Beadles, D. Mitton.
Date:September 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3169
This document defines requirements for protocols used by NetworkAccess Servers (NAS).
 
RFC 3170 IP Multicast Applications: Challenges and Solutions
 
Authors:B. Quinn, K. Almeroth.
Date:September 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3170
This document describes the challenges involved with designing and implementing multicast applications. It is an introductory guide for application developers that highlights the unique considerations of multicast applications as compared to unicast applications.

To this end, the document presents a taxonomy of multicast application I/O models and examples of the services they can support.It then describes the service requirements of these multicast applications, and the recent and ongoing efforts to build protocol solutions to support these services.

 
RFC 3171 IANA Guidelines for IPv4 Multicast Address Assignments
 
Authors:Z. Albanna, K. Almeroth, D. Meyer, M. Schipper.
Date:August 2001
Formats:txt pdf
Obsoleted by:RFC 5771
Status:BEST CURRENT PRACTICE
DOI:10.17487/RFC 3171
This memo provides guidance for the Internet Assigned NumbersAuthority (IANA) in assigning IPv4 multicast addresses.
 
RFC 3172 Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")
 
Authors:G. Huston, Ed..
Date:September 2001
Formats:txt pdf
Also:BCP 0052
Status:BEST CURRENT PRACTICE
DOI:10.17487/RFC 3172
This memo describes the management and operational requirements for the address and routing parameter area ("arpa") domain. The "arpa" domain is used to support a class of infrastructural identifier spaces, providing a distributed database that translates elements of a structured name space derived from a protocol family to service names. The efficient and reliable operation of this DNS space is essential to the integrity of operation of various services within the Internet. The Internet Architecture Board (IAB) has the responsibility, in cooperation with the Internet Corporation forAssigned Names and Numbers (ICANN), to manage the "arpa" domain.This document describes the principles used by the IAB in undertaking this role.
 
RFC 3173 IP Payload Compression Protocol (IPComp)
 
Authors:A. Shacham, B. Monsour, R. Pereira, M. Thomas.
Date:September 2001
Formats:txt pdf
Obsoletes:RFC 2393
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3173
This document describes a protocol intended to provide lossless compression for Internet Protocol datagrams in an Internet environment.
 
RFC 3174 US Secure Hash Algorithm 1 (SHA1)
 
Authors:D. Eastlake 3rd, P. Jones.
Date:September 2001
Formats:txt pdf
Updated by:RFC 4634, RFC 6234
Status:INFORMATIONAL
DOI:10.17487/RFC 3174
The purpose of this document is to make the SHA-1 (Secure HashAlgorithm 1) hash algorithm conveniently available to the Internet community. The United States of America has adopted the SHA-1 hash algorithm described herein as a Federal Information ProcessingStandard. Most of the text herein was taken by the authors from FIPS180-1. Only the C code implementation is "original".
 
RFC 3175 Aggregation of RSVP for IPv4 and IPv6 Reservations
 
Authors:F. Baker, C. Iturralde, F. Le Faucheur, B. Davie.
Date:September 2001
Formats:txt pdf
Updated by:RFC 5350
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3175
This document describes the use of a single RSVP (ResourceReSerVation Protocol) reservation to aggregate other RSVP reservations across a transit routing region, in a manner conceptually similar to the use of Virtual Paths in an ATM(Asynchronous Transfer Mode) network. It proposes a way to dynamically create the aggregate reservation, classify the traffic for which the aggregate reservation applies, determine how much bandwidth is needed to achieve the requirement, and recover the bandwidth when the sub-reservations are no longer required. It also contains recommendations concerning algorithms and policies for predictive reservations.
 
RFC 3176 InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks
 
Authors:P. Phaal, S. Panchen, N. McKee.
Date:September 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3176
This memo defines InMon Coporation's sFlow system. sFlow is a technology for monitoring traffic in data networks containing switches and routers. In particular, it defines the sampling mechanisms implemented in an sFlow Agent for monitoring traffic, the sFlow MIB for controlling the sFlow Agent, and the format of sample data used by the sFlow Agent when forwarding data to a central data collector.
 
RFC 3177 IAB/IESG Recommendations on IPv6 Address Allocations to Sites
 
Authors:IAB, IESG.
Date:September 2001
Formats:txt pdf
Obsoleted by:RFC 6177
Status:INFORMATIONAL
DOI:10.17487/RFC 3177
This document provides recommendations to the addressing registries(APNIC, ARIN and RIPE-NCC) on policies for assigning IPv6 address blocks to end sites. In particular, it recommends the assignment of/48 in the general case, /64 when it is known that one and only one subnet is needed and /128 when it is absolutely known that one and only one device is connecting.

The original recommendations were made in an IAB/IESG statement mailed to the registries on September 1, 2000. This document refines the original recommendation and documents it for the historical record.

 
RFC 3178 IPv6 Multihoming Support at Site Exit Routers
 
Authors:J. Hagino, H. Snyder.
Date:October 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3178
The document describes a mechanism for basic IPv6 multihoming support, and its operational requirements. Unlike currently- practiced IPv4 multihoming, the technique does not impact the worldwide routing table size, nor IGP (Interior Gateway Protocol) routing table size in upstream ISPs. The mechanism can be combined with more sophisticated (or complex) multihoming support mechanisms, and can be used as a foundation for other mechanisms. The document is largely based on RFC 2260 by Tony Bates.
 
RFC 3179 Script MIB Extensibility Protocol Version 1.1
 
Authors:J. Schoenwaelder, J. Quittek.
Date:October 2001
Formats:txt pdf
Obsoletes:RFC 2593
Status:EXPERIMENTAL
DOI:10.17487/RFC 3179
The Script MIB extensibility protocol (SMX) defined in this memo separates language specific runtime systems from language independentScript MIB implementations. The IETF Script MIB defines an interface for the delegation of management functions based on the Internet management framework. A management script is a set of instructions that are executed by a language specific runtime system.
 
RFC 3180 GLOP Addressing in 233/8
 
Authors:D. Meyer, P. Lothberg.
Date:September 2001
Formats:txt pdf
Obsoletes:RFC 2770
Also:BCP 0053
Status:BEST CURRENT PRACTICE
DOI:10.17487/RFC 3180
This document defines the policy for the use of 233/8 for statically assigned multicast addresses.
 
RFC 3181 Signaled Preemption Priority Policy Element
 
Authors:S. Herzog.
Date:October 2001
Formats:txt pdf
Obsoletes:RFC 2751
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3181
This document describes a preemption priority policy element for use by signaled policy based admission protocols (such as the ResourceReSerVation Protocol (RSVP) and Common Open Policy Service (COPS).

Preemption priority defines a relative importance (rank) within the set of flows competing to be admitted into the network. Rather than admitting flows by order of arrival (First Come First Admitted) network nodes may consider priorities to preempt some previously admitted low priority flows in order to make room for a newer, high- priority flow.

This memo corrects an RSVP POLICY_DATA P-Type codepoint assignment error in RFC 2751.

 
RFC 3182 Identity Representation for RSVP
 
Authors:S. Yadav, R. Yavatkar, R. Pabbati, P. Ford, T. Moore, S. Herzog, R. Hess.
Date:October 2001
Formats:txt pdf
Obsoletes:RFC 2752
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3182
This document describes the representation of identity information inPOLICY_DATA object for supporting policy based admission control in the Resource ReSerVation Protocol (RSVP). The goal of identity representation is to allow a process on a system to securely identify the owner and the application of the communicating process (e.g., user id) and convey this information in RSVP messages (PATH or RESV) in a secure manner. We describe the encoding of identities as RSVP policy element. We describe the processing rules to generate identity policy elements for multicast merged flows. Subsequently, we describe representations of user identities for Kerberos andPublic Key based user authentication mechanisms. In summary, we describe the use of this identity information in an operational setting.

This memo corrects an RSVP POLICY_DATA P-Type codepoint assignment error and a field size definition error in ErrorValue in RFC 2752.

 
RFC 3183 Domain Security Services using S/MIME
 
Authors:T. Dean, W. Ottaway.
Date:October 2001
Formats:txt pdf
Status:EXPERIMENTAL
DOI:10.17487/RFC 3183
This document describes how the S/MIME (Secure/Multipurpose InternetMail Extensions) protocol can be processed and generated by a number of components of a communication system, such as message transfer agents, guards and gateways to deliver security services. These services are collectively referred to as 'Domain Security Services'.
 
RFC 3184 IETF Guidelines for Conduct
 
Authors:S. Harris.
Date:October 2001
Formats:txt pdf
Obsoleted by:RFC 7154
Status:BEST CURRENT PRACTICE
DOI:10.17487/RFC 3184
This document provides a set of guidelines for personal interaction in the Internet Engineering Task Force. The Guidelines recognize the diversity of IETF participants, emphasize the value of mutual respect, and stress the broad applicability of our work.
 
RFC 3185 Reuse of CMS Content Encryption Keys
 
Authors:S. Farrell, S. Turner.
Date:October 2001
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3185
This document describes a way to include a key identifier in a CMS(Cryptographic Message Syntax) enveloped data structure, so that the content encryption key can be re-used for further enveloped data packets.
 
RFC 3186 MAPOS/PPP Tunneling mode
 
Authors:S. Shimizu, T. Kawano, K. Murakami, E. Beier.
Date:December 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3186
This document specifies tunneling configuration over MAPOS (MultipleAccess Protocol over SONET/SDH) networks. Using this mode, a MAPOS network can provide transparent point-to-point link for PPP overSONET/SDH (Packet over SONET/SDH, POS) without any additional overhead.
 
RFC 3187 Using International Standard Book Numbers as Uniform Resource Names
 
Authors:J. Hakala, H. Walravens.
Date:October 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3187
This document discusses how International Standard Book Numbers(ISBN) can be supported within the URN (Uniform Resource Names) framework and the syntax for URNs defined in RFC 2141. Much of the discussion below is based on the ideas expressed in RFC 2288.
 
RFC 3188 Using National Bibliography Numbers as Uniform Resource Names
 
Authors:J. Hakala.
Date:October 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3188
This document discusses how national bibliography numbers (persistent and unique identifiers assigned by the national libraries) can be supported within the URN (Uniform Resource Names) framework and the syntax for URNs defined in RFC 2141. Much of the discussion is based on the ideas expressed in RFC 2288.
 
RFC 3189 RTP Payload Format for DV (IEC 61834) Video
 
Authors:K. Kobayashi, A. Ogawa, S. Casner, C. Bormann.
Date:January 2002
Formats:txt pdf
Obsoleted by:RFC 6469
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3189
This document specifies the packetization scheme for encapsulating the compressed digital video data streams commonly known as "DV" into a payload format for the Real-Time Transport Protocol (RTP).
 
RFC 3190 RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled Audio
 
Authors:K. Kobayashi, A. Ogawa, S. Casner, C. Bormann.
Date:January 2002
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3190
This document specifies a packetization scheme for encapsulating12-bit nonlinear, 20-bit linear, and 24-bit linear audio data streams using the Real-time Transport Protocol (RTP). This document also specifies the format of a Session Description Protocol (SDP) parameter to indicate when audio data is preemphasized before sampling. The parameter may be used with other audio payload formats, in particular L16 (16-bit linear).
 
RFC 3191 Minimal GSTN address format in Internet Mail
 
Authors:C. Allocchio.
Date:October 2001
Formats:txt pdf
Obsoletes:RFC 2303
Updates:RFC 2846
Status:DRAFT STANDARD
DOI:10.17487/RFC 3191
This memo describes a simple method of encoding Global SwitchedTelephone Network (GSTN) addresses (commonly called "telephone numbers") in the local-part of Internet email addresses, along with an extension mechanism to allow encoding of additional standard attributes needed for email gateways to GSTN-based services.
 
RFC 3192 Minimal FAX address format in Internet Mail
 
Authors:C. Allocchio.
Date:October 2001
Formats:txt pdf
Obsoletes:RFC 2304
Updates:RFC 2846
Status:DRAFT STANDARD
DOI:10.17487/RFC 3192
This memo describes a simple method of encoding Global SwitchedTelephone Network (GSTN) addresses of facsimile devices in the local-part of Internet email addresses.
 
RFC 3193 Securing L2TP using IPsec
 
Authors:B. Patel, B. Aboba, W. Dixon, G. Zorn, S. Booth.
Date:November 2001
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3193
This document discusses how L2TP (Layer Two Tunneling Protocol) may utilize IPsec to provide for tunnel authentication, privacy protection, integrity checking and replay protection. Both the voluntary and compulsory tunneling cases are discussed.
 
RFC 3194 The H-Density Ratio for Address Assignment Efficiency An Update on the H ratio
 
Authors:A. Durand, C. Huitema.
Date:November 2001
Formats:txt pdf
Updates:RFC 1715
Status:INFORMATIONAL
DOI:10.17487/RFC 3194
This document provides an update on the "H ratio" defined in RFC1715. It defines a new ratio which the authors claim is easier to understand.
 
RFC 3195 Reliable Delivery for syslog
 
Authors:D. New, M. Rose.
Date:November 2001
Formats:txt pdf
Status:PROPOSED STANDARD
DOI:10.17487/RFC 3195
The BSD Syslog Protocol describes a number of service options related to propagating event messages. This memo describes two mappings of the syslog protocol to TCP connections, both useful for reliable delivery of event messages. The first provides a trivial mapping maximizing backward compatibility. The second provides a more complete mapping. Both provide a degree of robustness and security in message delivery that is unavailable to the usual UDP-based syslog protocol, by providing encryption and authentication over a connection-oriented protocol.
 
RFC 3196 Internet Printing Protocol/1.1: Implementor's Guide
 
Authors:T. Hastings, C. Manros, P. Zehler, C. Kugler, H. Holst.
Date:November 2001
Formats:txt pdf
Obsoletes:RFC 2639
Status:INFORMATIONAL
DOI:10.17487/RFC 3196
This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP).
 
RFC 3197 Applicability Statement for DNS MIB Extensions
 
Authors:R. Austein.
Date:November 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3197
This document explains why, after more than six years as proposed standards, the DNS Server and Resolver MIB extensions were never deployed, and recommends retiring these MIB extensions by moving them to Historical status.
 
RFC 3198 Terminology for Policy-Based Management
 
Authors:A. Westerinen, J. Schnizlein, J. Strassner, M. Scherling, B. Quinn, S. Herzog, A. Huynh, M. Carlson, J. Perry, S. Waldbusser.
Date:November 2001
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3198
This document is a glossary of policy-related terms. It provides abbreviations, explanations, and recommendations for use of these terms. The document takes the approach and format of RFC 2828, which defines an Internet Security Glossary. The intent is to improve the comprehensibility and consistency of writing that deals with network policy, particularly Internet Standards documents (ISDs).
 
RFC 3199 Request for Comments Summary RFC Numbers 3100-3199
 
Authors:S. Ginoza.
Date:February 2003
Formats:txt pdf
Status:INFORMATIONAL
DOI:10.17487/RFC 3199