RFC Abstracts
RFC2453 - RIP Version 2
This document specifies an extension of the Routing Information Protocol (RIP) to expand the amount of useful information carried in RIP messages and to add a measure of security. [STANDARDS-TRACK]
RFC2452 - IP Version 6 Management Information Base for the Transmission Control Protocol
This document is one in the series of documents that define various MIB objects for IPv6. Specifically, this document is the MIB module which defines managed objects for implementations of the Transmission Control Protocol (TCP) over IP Version 6 (IPv6). [STANDARDS-TRACK]
RFC2451 - The ESP CBC-Mode Cipher Algorithms
This document describes how to use CBC-mode cipher algorithms with the IPSec ESP (Encapsulating Security Payload) Protocol. It not only clearly states how to use certain cipher algorithms, but also how to use all CBC-mode cipher algorithms. [STANDARDS-TRACK]
RFC2450 - Proposed TLA and NLA Assignment Rule
This document proposes rules for Top-Level Aggregation Identifiers (TLA ID) and Next-Level Aggregation Identifiers (NLA ID). This memo provides information for the Internet community.
RFC2449 - POP3 Extension Mechanism
This memo updates RFC 1939 to define a mechanism to announce support for optional commands, extensions, and unconditional server behavior. [STANDARDS-TRACK]
RFC2448 - AT&T's Error Resilient Video Transmission Technique
This document describes a set of techniques for packet loss resilient transmission of compressed video bitstreams based on reliable delivery of their vital information-carrying segments. This memo provides information for the Internet community.
RFC2447 - iCalendar Message-Based Interoperability Protocol (iMIP)
This document specifies a binding from the iCalendar Transport- independent Interoperability Protocol (iTIP) to Internet email-based transports. [STANDARDS-TRACK]
RFC2446 - iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries
This document specifies how calendaring systems use iCalendar objects to interoperate with other calendar systems. It does so in a general way so as to allow multiple methods of communication between systems. [STANDARDS-TRACK]
RFC2445 - Internet Calendaring and Scheduling Core Object Specification (iCalendar)
This memo has been defined to provide the definition of a common format for openly exchanging calendaring and scheduling information across the Internet. [STANDARDS-TRACK]
RFC2444 - The One-Time-Password SASL Mechanism
OTP provides a useful authentication mechanism for situations where there is limited client or server trust. Currently, OTP is added to protocols in an ad-hoc fashion with heuristic parsing. This specification defines an OTP SASL mechanism so it can be easily and formally integrated into many application protocols. [STANDARDS-TRACK]
RFC2443 - A Distributed MARS Service Using SCSP
This document describes a method for distributing a MARS service within a LIS. This method uses the Server Cache Synchronization Protocol (SCSP) to synchronize the MARS Server databases within a LIS. When SCSP is used to synchronize the caches of MARS Servers in a LIS, the LIS defines the boundary of an SCSP Server Group (SG). [STANDARDS-TRACK]
RFC2442 - The Batch SMTP Media Type
This document defines a MIME content type suitable for tunneling an ESMTP transaction through any MIME-capable transport. This memo provides information for the Internet community
RFC2441 - Working with Jon, Tribute delivered at UCLA, October 30, 1998
This memo provides information for the Internet community.
RFC2440 - OpenPGP Message Format
This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. [STANDARDS-TRACK]
RFC2439 - BGP Route Flap Damping
A usage of the BGP routing protocol is described which is capable of reducing the routing traffic passed on to routing peers and therefore the load on these peers without adversely affecting route convergence time for relatively stable routes. [STANDARDS-TRACK]
RFC2438 - Advancement of MIB specifications on the IETF Standards Track
This document specifies the process which the IESG will use to determine if a MIB specification document meets these requirements. It also discusses the rationale for this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
RFC2437 - PKCS #1: RSA Cryptography Specifications Version 2.0
This memo is the successor to RFC 2313. This document provides recommendations for the implementation of public-key cryptography based on the RSA algorithm. This memo provides information for the Internet community.
RFC2436 - Collaboration between ISOC/IETF and ITU-T
This document describes the collaboration process between the ITU-T and ISOC/IETF. This memo provides information for the Internet community.
RFC2435 - RTP Payload Format for JPEG-compressed Video
This memo describes the RTP payload format for JPEG video streams. [STANDARDS-TRACK]
RFC2434 - Guidelines for Writing an IANA Considerations Section in RFCs
This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on the IANA. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
RFC2433 - Microsoft PPP CHAP Extensions
The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol and a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This memo provides information for the Internet community.
RFC2432 - Terminology for IP Multicast Benchmarking
The purpose of this document is to define terminology specific to the benchmarking of multicast IP forwarding devices. This memo provides information for the Internet community.
RFC2431 - RTP Payload Format for BT.656 Video Encoding
This document specifies the RTP payload format for encapsulating ITU Recommendation BT.656-3 video streams in the Real-Time Transport Protocol (RTP). [STANDARDS-TRACK]
RFC2430 - A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)
This document describes the Provider Architecture for Differentiated Services and Traffic Engineering (PASTE) for Internet Service Providers (ISPs). This memo provides information for the Internet community.
RFC2429 - RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+)
This document specifies an RTP payload header format applicable to the transmission of video streams generated based on the 1998 version of ITU-T Recommendation H.263. [STANDARDS-TRACK]
RFC2428 - FTP Extensions for IPv6 and NATs
This paper specifies extensions to FTP that will allow the protocol to work over IPv4 and IPv6. [STANDARDS-TRACK]
RFC2427 - Multiprotocol Interconnect over Frame Relay
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. [STANDARDS-TRACK]
RFC2426 - vCard MIME Directory Profile
This memo defines the profile of the MIME Content-Type for directory information for a white-pages person object, based on a vCard electronic business card. [STANDARDS-TRACK]
RFC2425 - A MIME Content-Type for Directory Information
This document defines a MIME Content-Type for holding directory information. [STANDARDS-TRACK]
RFC2424 - Content Duration MIME Header Definition
This document describes the MIME header Content-Duration that is intended for use with any timed media content (typically audio/* or video/*). [STANDARDS-TRACK]
RFC2423 - VPIM Voice Message MIME Sub-type Registration
This document describes the registration of the MIME sub-type multipart/voice-message for use with the Voice Profile for Internet Mail (VPIM). [STANDARDS-TRACK]
RFC2422 - Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type Registration
This document describes the registration of the MIME sub-type audio/32KADPCM for toll quality audio. [STANDARDS-TRACK]
RFC2421 - Voice Profile for Internet Mail - version 2
This document profiles Internet mail for voice messaging. [STANDARDS-TRACK]
RFC2420 - The PPP Triple-DES Encryption Protocol (3DESE)
This document provides specific details for the use of the Triple-DES standard (3DES) for encrypting PPP encapsulated packets. [STANDARDS-TRACK]
RFC2419 - The PPP DES Encryption Protocol, Version 2 (DESE-bis)
This document provides specific details for the use of the DES standard for encrypting PPP encapsulated packets. [STANDARDS-TRACK]
RFC2418 - IETF Working Group Guidelines and Procedures
This document describes the guidelines and procedures for formation and operation of IETF working groups. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
RFC2417 - Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks
This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. [STANDARDS-TRACK]
RFC2416 - When TCP Starts Up With Four Packets Into Only Three Buffers
This memo is to document a simple experiment. The experiment showed that in the case of a TCP receiver behind a 9600 bps modem link at the edge of a fast Internet where there are only 3 buffers before the modem (and the fourth packet of a four-packet start will surely be dropped), no significant degradation in performance is experienced by a TCP sending with a four-packet start when compared with a normal slow start (which starts with just one packet). This memo provides information for the Internet community.
RFC2415 - Simulation Studies of Increased Initial TCP Window Size
This document covers some simulation studies of the effects of increasing the initial window size of TCP. This memo provides information for the Internet community.
RFC2414 - Increasing TCP's Initial Window
This document specifies an increase in the permitted initial window for TCP from one segment to roughly 4K bytes. This memo defines an Experimental Protocol for the Internet community.
RFC2413 - Dublin Core Metadata for Resource Discovery
This is the first of a set of Informational RFCs describing the Dublin Core. Its purpose is to introduce the Dublin Core and to describe the consensus reached on the semantics of each of the 15 elements. This memo provides information for the Internet community.
RFC2412 - The OAKLEY Key Determination Protocol
This document describes a protocol, named OAKLEY, by which two authenticated parties can agree on secure and secret keying material. The basic mechanism is the Diffie-Hellman key exchange algorithm. This memo provides information for the Internet community.
RFC2411 - IP Security Document Roadmap
This document is intended to provide guidelines for the development of collateral specifications describing the use of new encryption and authentication algorithms with the ESP protocol, described in and new authentication algorithms used with the AH protocol. This memo provides information for the Internet community.
RFC2410 - The NULL Encryption Algorithm and Its Use With IPsec
This memo defines the NULL encryption algorithm and its use with the IPsec Encapsulating Security Payload (ESP). [STANDARDS-TRACK]
RFC2409 - The Internet Key Exchange (IKE)
This memo describes a hybrid protocol. The purpose is to negotiate, and provide authenticated keying material for, security associations in a protected manner. [STANDARDS-TRACK]
RFC2408 - Internet Security Association and Key Management Protocol (ISAKMP)
This memo describes a protocol utilizing security concepts necessary for establishing Security Associations (SA) and cryptographic keys in an Internet environment. [STANDARDS-TRACK]
RFC2407 - The Internet IP Security Domain of Interpretation for ISAKMP
This document defines the Internet IP Security DOI (IPSEC DOI), which instantiates ISAKMP for use with IP when IP uses ISAKMP to negotiate security associations. [STANDARDS-TRACK]
RFC2406 - IP Encapsulating Security Payload (ESP)
The Encapsulating Security Payload (ESP) header is designed to provide a mix of security services in IPv4 and IPv6. [STANDARDS-TRACK]
RFC2405 - The ESP DES-CBC Cipher Algorithm With Explicit IV
This document describes the use of the DES Cipher algorithm in Cipher Block Chaining Mode, with an explicit IV, as a confidentiality mechanism within the context of the IPSec Encapsulating Security Payload (ESP). [STANDARDS-TRACK]
RFC2404 - The Use of HMAC-SHA-1-96 within ESP and AH
This memo describes the use of the HMAC algorithm in conjunction with the SHA-1 algorithm as an authentication mechanism within the revised IPSEC Encapsulating Security Payload and the revised IPSEC Authentication Header. [STANDARDS-TRACK]
This document specifies an extension of the Routing Information Protocol (RIP) to expand the amount of useful information carried in RIP messages and to add a measure of security. [STANDARDS-TRACK]
RFC2452 - IP Version 6 Management Information Base for the Transmission Control Protocol
This document is one in the series of documents that define various MIB objects for IPv6. Specifically, this document is the MIB module which defines managed objects for implementations of the Transmission Control Protocol (TCP) over IP Version 6 (IPv6). [STANDARDS-TRACK]
RFC2451 - The ESP CBC-Mode Cipher Algorithms
This document describes how to use CBC-mode cipher algorithms with the IPSec ESP (Encapsulating Security Payload) Protocol. It not only clearly states how to use certain cipher algorithms, but also how to use all CBC-mode cipher algorithms. [STANDARDS-TRACK]
RFC2450 - Proposed TLA and NLA Assignment Rule
This document proposes rules for Top-Level Aggregation Identifiers (TLA ID) and Next-Level Aggregation Identifiers (NLA ID). This memo provides information for the Internet community.
RFC2449 - POP3 Extension Mechanism
This memo updates RFC 1939 to define a mechanism to announce support for optional commands, extensions, and unconditional server behavior. [STANDARDS-TRACK]
RFC2448 - AT&T's Error Resilient Video Transmission Technique
This document describes a set of techniques for packet loss resilient transmission of compressed video bitstreams based on reliable delivery of their vital information-carrying segments. This memo provides information for the Internet community.
RFC2447 - iCalendar Message-Based Interoperability Protocol (iMIP)
This document specifies a binding from the iCalendar Transport- independent Interoperability Protocol (iTIP) to Internet email-based transports. [STANDARDS-TRACK]
RFC2446 - iCalendar Transport-Independent Interoperability Protocol (iTIP) Scheduling Events, BusyTime, To-dos and Journal Entries
This document specifies how calendaring systems use iCalendar objects to interoperate with other calendar systems. It does so in a general way so as to allow multiple methods of communication between systems. [STANDARDS-TRACK]
RFC2445 - Internet Calendaring and Scheduling Core Object Specification (iCalendar)
This memo has been defined to provide the definition of a common format for openly exchanging calendaring and scheduling information across the Internet. [STANDARDS-TRACK]
RFC2444 - The One-Time-Password SASL Mechanism
OTP provides a useful authentication mechanism for situations where there is limited client or server trust. Currently, OTP is added to protocols in an ad-hoc fashion with heuristic parsing. This specification defines an OTP SASL mechanism so it can be easily and formally integrated into many application protocols. [STANDARDS-TRACK]
RFC2443 - A Distributed MARS Service Using SCSP
This document describes a method for distributing a MARS service within a LIS. This method uses the Server Cache Synchronization Protocol (SCSP) to synchronize the MARS Server databases within a LIS. When SCSP is used to synchronize the caches of MARS Servers in a LIS, the LIS defines the boundary of an SCSP Server Group (SG). [STANDARDS-TRACK]
RFC2442 - The Batch SMTP Media Type
This document defines a MIME content type suitable for tunneling an ESMTP transaction through any MIME-capable transport. This memo provides information for the Internet community
RFC2441 - Working with Jon, Tribute delivered at UCLA, October 30, 1998
This memo provides information for the Internet community.
RFC2440 - OpenPGP Message Format
This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. [STANDARDS-TRACK]
RFC2439 - BGP Route Flap Damping
A usage of the BGP routing protocol is described which is capable of reducing the routing traffic passed on to routing peers and therefore the load on these peers without adversely affecting route convergence time for relatively stable routes. [STANDARDS-TRACK]
RFC2438 - Advancement of MIB specifications on the IETF Standards Track
This document specifies the process which the IESG will use to determine if a MIB specification document meets these requirements. It also discusses the rationale for this process. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
RFC2437 - PKCS #1: RSA Cryptography Specifications Version 2.0
This memo is the successor to RFC 2313. This document provides recommendations for the implementation of public-key cryptography based on the RSA algorithm. This memo provides information for the Internet community.
RFC2436 - Collaboration between ISOC/IETF and ITU-T
This document describes the collaboration process between the ITU-T and ISOC/IETF. This memo provides information for the Internet community.
RFC2435 - RTP Payload Format for JPEG-compressed Video
This memo describes the RTP payload format for JPEG video streams. [STANDARDS-TRACK]
RFC2434 - Guidelines for Writing an IANA Considerations Section in RFCs
This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on the IANA. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
RFC2433 - Microsoft PPP CHAP Extensions
The Point-to-Point Protocol (PPP) provides a standard method for transporting multi-protocol datagrams over point-to-point links. PPP defines an extensible Link Control Protocol and a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. This memo provides information for the Internet community.
RFC2432 - Terminology for IP Multicast Benchmarking
The purpose of this document is to define terminology specific to the benchmarking of multicast IP forwarding devices. This memo provides information for the Internet community.
RFC2431 - RTP Payload Format for BT.656 Video Encoding
This document specifies the RTP payload format for encapsulating ITU Recommendation BT.656-3 video streams in the Real-Time Transport Protocol (RTP). [STANDARDS-TRACK]
RFC2430 - A Provider Architecture for Differentiated Services and Traffic Engineering (PASTE)
This document describes the Provider Architecture for Differentiated Services and Traffic Engineering (PASTE) for Internet Service Providers (ISPs). This memo provides information for the Internet community.
RFC2429 - RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video (H.263+)
This document specifies an RTP payload header format applicable to the transmission of video streams generated based on the 1998 version of ITU-T Recommendation H.263. [STANDARDS-TRACK]
RFC2428 - FTP Extensions for IPv6 and NATs
This paper specifies extensions to FTP that will allow the protocol to work over IPv4 and IPv6. [STANDARDS-TRACK]
RFC2427 - Multiprotocol Interconnect over Frame Relay
This memo describes an encapsulation method for carrying network interconnect traffic over a Frame Relay backbone. It covers aspects of both Bridging and Routing. [STANDARDS-TRACK]
RFC2426 - vCard MIME Directory Profile
This memo defines the profile of the MIME Content-Type for directory information for a white-pages person object, based on a vCard electronic business card. [STANDARDS-TRACK]
RFC2425 - A MIME Content-Type for Directory Information
This document defines a MIME Content-Type for holding directory information. [STANDARDS-TRACK]
RFC2424 - Content Duration MIME Header Definition
This document describes the MIME header Content-Duration that is intended for use with any timed media content (typically audio/* or video/*). [STANDARDS-TRACK]
RFC2423 - VPIM Voice Message MIME Sub-type Registration
This document describes the registration of the MIME sub-type multipart/voice-message for use with the Voice Profile for Internet Mail (VPIM). [STANDARDS-TRACK]
RFC2422 - Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type Registration
This document describes the registration of the MIME sub-type audio/32KADPCM for toll quality audio. [STANDARDS-TRACK]
RFC2421 - Voice Profile for Internet Mail - version 2
This document profiles Internet mail for voice messaging. [STANDARDS-TRACK]
RFC2420 - The PPP Triple-DES Encryption Protocol (3DESE)
This document provides specific details for the use of the Triple-DES standard (3DES) for encrypting PPP encapsulated packets. [STANDARDS-TRACK]
RFC2419 - The PPP DES Encryption Protocol, Version 2 (DESE-bis)
This document provides specific details for the use of the DES standard for encrypting PPP encapsulated packets. [STANDARDS-TRACK]
RFC2418 - IETF Working Group Guidelines and Procedures
This document describes the guidelines and procedures for formation and operation of IETF working groups. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
RFC2417 - Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM Networks
This memo specifies a MIB module in a manner that is both compliant to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 definitions. [STANDARDS-TRACK]
RFC2416 - When TCP Starts Up With Four Packets Into Only Three Buffers
This memo is to document a simple experiment. The experiment showed that in the case of a TCP receiver behind a 9600 bps modem link at the edge of a fast Internet where there are only 3 buffers before the modem (and the fourth packet of a four-packet start will surely be dropped), no significant degradation in performance is experienced by a TCP sending with a four-packet start when compared with a normal slow start (which starts with just one packet). This memo provides information for the Internet community.
RFC2415 - Simulation Studies of Increased Initial TCP Window Size
This document covers some simulation studies of the effects of increasing the initial window size of TCP. This memo provides information for the Internet community.
RFC2414 - Increasing TCP's Initial Window
This document specifies an increase in the permitted initial window for TCP from one segment to roughly 4K bytes. This memo defines an Experimental Protocol for the Internet community.
RFC2413 - Dublin Core Metadata for Resource Discovery
This is the first of a set of Informational RFCs describing the Dublin Core. Its purpose is to introduce the Dublin Core and to describe the consensus reached on the semantics of each of the 15 elements. This memo provides information for the Internet community.
RFC2412 - The OAKLEY Key Determination Protocol
This document describes a protocol, named OAKLEY, by which two authenticated parties can agree on secure and secret keying material. The basic mechanism is the Diffie-Hellman key exchange algorithm. This memo provides information for the Internet community.
RFC2411 - IP Security Document Roadmap
This document is intended to provide guidelines for the development of collateral specifications describing the use of new encryption and authentication algorithms with the ESP protocol, described in and new authentication algorithms used with the AH protocol. This memo provides information for the Internet community.
RFC2410 - The NULL Encryption Algorithm and Its Use With IPsec
This memo defines the NULL encryption algorithm and its use with the IPsec Encapsulating Security Payload (ESP). [STANDARDS-TRACK]
RFC2409 - The Internet Key Exchange (IKE)
This memo describes a hybrid protocol. The purpose is to negotiate, and provide authenticated keying material for, security associations in a protected manner. [STANDARDS-TRACK]
RFC2408 - Internet Security Association and Key Management Protocol (ISAKMP)
This memo describes a protocol utilizing security concepts necessary for establishing Security Associations (SA) and cryptographic keys in an Internet environment. [STANDARDS-TRACK]
RFC2407 - The Internet IP Security Domain of Interpretation for ISAKMP
This document defines the Internet IP Security DOI (IPSEC DOI), which instantiates ISAKMP for use with IP when IP uses ISAKMP to negotiate security associations. [STANDARDS-TRACK]
RFC2406 - IP Encapsulating Security Payload (ESP)
The Encapsulating Security Payload (ESP) header is designed to provide a mix of security services in IPv4 and IPv6. [STANDARDS-TRACK]
RFC2405 - The ESP DES-CBC Cipher Algorithm With Explicit IV
This document describes the use of the DES Cipher algorithm in Cipher Block Chaining Mode, with an explicit IV, as a confidentiality mechanism within the context of the IPSec Encapsulating Security Payload (ESP). [STANDARDS-TRACK]
RFC2404 - The Use of HMAC-SHA-1-96 within ESP and AH
This memo describes the use of the HMAC algorithm in conjunction with the SHA-1 algorithm as an authentication mechanism within the revised IPSEC Encapsulating Security Payload and the revised IPSEC Authentication Header. [STANDARDS-TRACK]