RFC Abstracts

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]
RFC2403 - The Use of HMAC-MD5-96 within ESP and AH
This memo describes the use of the HMAC algorithm in conjunction with the MD5 algorithm as an authentication mechanism within the revised IPSEC Encapsulating Security Payload and the revised IPSEC Authentication Header. [STANDARDS-TRACK]
RFC2402 - IP Authentication Header
The IP Authentication Header (AH) is used to provide connectionless integrity and data origin authentication for IP datagrams (hereafter referred to as just "authentication"), and to provide protection against replays. [STANDARDS-TRACK]
RFC2401 - Security Architecture for the Internet Protocol
This memo specifies the base architecture for IPsec compliant systems. [STANDARDS-TRACK]
RFC2400 - Internet Official Protocol Standards
This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Architecture Board (IAB). This memo is an Internet Standard. [STANDARDS-TRACK]
RFC2398 - Some Testing Tools for TCP Implementors
This document lists only tools which can evaluate one or more TCP implementations, or which can privde some specific results which describe or evaluate the TCP being tested. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC2397 - The "data" URL scheme
A new URL scheme, "data", is defined. It allows inclusion of small data items as "immediate" data, as if it had been included externally. [STANDARDS-TRACK]
RFC2396 - Uniform Resource Identifiers (URI): Generic Syntax
This document defines a grammar that is a superset of all valid URI, such that an implementation can parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier type. [STANDARDS-TRACK]
RFC2395 - IP Payload Compression Using LZS
This document describes a compression method based on the LZS compression algorithm. This document defines the application of the LZS algorithm to the IP Payload Compression Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC2394 - IP Payload Compression Using DEFLATE
This document describes a compression method based on the DEFLATE compression algorithm. This document defines the application of the DEFLATE algorithm to the IP Payload Compression Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC2393 - IP Payload Compression Protocol (IPComp)
This document describes a protocol intended to provide lossless compression for Internet Protocol datagrams in an Internet environment. [STANDARDS-TRACK]
RFC2392 - Content-ID and Message-ID Uniform Resource Locators
The Uniform Resource Locator (URL) schemes, "cid:" and "mid:" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message. [STANDARDS-TRACK]
RFC2391 - Load Sharing using IP Network Address Translation (LSNAT)
In this document, we extend the use of NATs to offer Load share feature, where session load can be distributed across a pool of servers, instead of directing to a single server. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC2390 - Inverse Address Resolution Protocol
This memo describes additions to ARP that will allow a station to request a protocol address corresponding to a given hardware address. [STANDARDS-TRACK]
RFC2389 - Feature negotiation mechanism for the File Transfer Protocol
This document provides a mechanism by which clients of the FTP protocol can discover which new features are supported by a particular FTP server. [STANDARDS-TRACK]
RFC2388 - Returning Values from Forms: multipart/form-data
This specification defines an Internet Media Type, multipart/form-data, which can be used by a wide variety of applications and transported by a wide variety of protocols as a way of returning a set of values as the result of a user filling out a form. [STANDARDS-TRACK]
RFC2387 - The MIME Multipart/Related Content-type
This document defines the Multipart/Related content-type and provides examples of its use. [STANDARDS-TRACK]
RFC2386 - A Framework for QoS-based Routing in the Internet
This document describes some of the QoS-based routing issues and requirements, and proposes a framework for QoS-based routing in the Internet. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC2385 - Protection of BGP Sessions via the TCP MD5 Signature Option
This memo describes a TCP extension to enhance security for BGP. [STANDARDS-TRACK]
RFC2384 - POP URL Scheme
This memo defines a URL scheme for referencing a POP mailbox. [STANDARDS-TRACK]
RFC2383 - ST2+ over ATM Protocol Specification - UNI 3.1 Version
This document specifies an ATM-based protocol for communication between ST2+ agents. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC2382 - A Framework for Integrated Services and RSVP over ATM
This document outlines the issues and framework related to providing IP Integrated Services with RSVP over ATM. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC2381 - Interoperation of Controlled-Load Service and Guaranteed Service with ATM
This document provides guidelines for mapping service classes, and traffic management features and parameters between Internet and ATM technologies. [STANDARDS-TRACK]
RFC2380 - RSVP over ATM Implementation Requirements
This memo presents specific implementation requirements for running RSVP over ATM switched virtual circuits (SVCs). It presents requirements that ensure interoperability between multiple implementations and conformance to the RSVP and Integrated Services specifications. [STANDARDS-TRACK]
RFC2379 - RSVP over ATM Implementation Guidelines
This memo presents specific implementation guidelines for running RSVP over ATM switched virtual circuits (SVCs). This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
RFC2378 - The CCSO Nameserver (Ph) Architecture
The Ph Nameserver from the Computing and Communications Services Office (CCSO), University of Illinois at Urbana-Champaign has for some time now been used by several organizations as their choice of publicly available database for information about people as well as other things. This document provides a formal definition of the client-server protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC2377 - Naming Plan for Internet Directory-Enabled Applications
Application of the conventional X.500 approach to naming has heretofore, in the experience of the authors, proven to be an obstacle to the wide deployment of directory-enabled applications on the Internet. We propose a new directory naming plan that leverages the strengths of the most popular and successful Internet naming schemes for naming objects in a hierarchical directory. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC2376 - XML Media Types
This document proposes two new media subtypes, text/xml and application/xml, for use in exchanging network entities which are conforming Extensible Markup Language (XML). This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC2375 - IPv6 Multicast Address Assignments
This document defines the initial assignment of IPv6 multicast addresses. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
RFC2374 - An IPv6 Aggregatable Global Unicast Address Format
This document defines an IPv6 aggregatable global unicast address format for use in the Internet. [STANDARDS-TRACK]
RFC2373 - IP Version 6 Addressing Architecture
This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. [STANDARDS-TRACK]
RFC2372 - Transaction Internet Protocol - Requirements and Supplemental Information
This document describes the purpose (usage scenarios), and requirements for the Transaction Internet Protocol. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.