RFC Abstracts
RFC2706 - ECML v1: Field Names for E-Commerce
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. This memo provides information for the Internet community.
RFC2705 - Media Gateway Control Protocol (MGCP) Version 1.0
This document describes an application programming interface and a corresponding protocol (MGCP) for controlling Voice over IP (VoIP) Gateways from external call control elements. MGCP assumes a call control architecture where the call control "intelligence" is outside the gateways and handled by external call control elements. This memo provides information for the Internet community.
RFC2704 - The KeyNote Trust-Management System Version 2
This memo describes version 2 of the KeyNote trust-management system.It specifies the syntax and semantics of KeyNote `assertions', describes `action attribute' processing, and outlines the application architecture into which a KeyNote implementation can be fit. This memo provides information for the Internet community.
RFC2703 - Protocol-independent Content Negotiation Framework
This memo sets out terminology, an abstract framework and goals for protocol-independent content negotiation, and identifies some technical issues which may need to be addressed. This memo provides information for the Internet community.
RFC2702 - Requirements for Traffic Engineering Over MPLS
This document presents a set of requirements for Traffic Engineering over Multiprotocol Label Switching (MPLS). It identifies the functional capabilities required to implement policies that facilitate efficient and reliable network operations in an MPLS domain. This memo provides information for the Internet community.
RFC2701 - Nortel Networks Multi-link Multi-node PPP Bundle Discovery Protocol
This document specifies a standard way for Multi-link PPP to operate across multiple nodes. This memo provides information for the Internet community.
RFC2700 - Internet Official Protocol Standards
This memo describes the current state of standardization of protocols used in the Internet as determined by the Internet Engineering Task Force (IETF). [STANDARDS-TRACK]
RFC2698 - A Two Rate Three Color Marker
This document defines a Two Rate Three Color Marker (trTCM), which can be used as a component in a Diffserv traffic conditioner. This memo provides information for the Internet community.
RFC2697 - A Single Rate Three Color Marker
This document defines a Single Rate Three Color Marker (srTCM), which can be used as component in a Diffserv traffic conditioner. This memo provides information for the Internet community.
RFC2696 - LDAP Control Extension for Simple Paged Results Manipulation
This document describes an LDAPv3 control extension for simple paging of search results. This memo provides information for the Internet community.
RFC2695 - Authentication Mechanisms for ONC RPC
This document describes two authentication mechanisms created by Sun Microsystems that are commonly used in conjunction with the ONC Remote Procedure Call (ONC RPC Version 2) protocol. This memo provides information for the Internet community.
RFC2694 - DNS extensions to Network Address Translators (DNS_ALG)
This document identifies the need for DNS extensions to NATs and outlines how a DNS Application Level Gateway (DNS_ALG) can meet the need. This memo provides information for the Internet community.
RFC2693 - SPKI Certificate Theory
This document gives the theory behind SPKI certificates and ACLs without going into technical detail about those structures or their uses. This memo defines an Experimental Protocol for the Internet community.
RFC2692 - SPKI Requirements
The SPKI Working Group first established a list of things one might want to do with certificates (attached at the end of this document), and then summarized that list of desires into requirements. This document presents that summary of requirements. This memo defines an Experimental Protocol for the Internet community.
RFC2691 - A Memorandum of Understanding for an ICANN Protocol Support Organization
This is the text of the Memorandum of Understanding (MoU) that was signed by ICANN, the IETF, the ITU-T, W3C and ETSI on July 14, 1999 in Oslo. This MoU creates the Protocol Support Organization (PSO) within the Internet Corporation for Assigned Names and Numbers (ICANN). This memo provides information for the Internet community.
RFC2690 - A Proposal for an MOU-Based ICANN Protocol Support Organization
This is a copy of the proposal for an MOU-based Protocol Supporting Organization that was submitted to ICANN on April 23, 1999. This memo provides information for the Internet community.
RFC2689 - Providing Integrated Services over Low-bitrate Links
This document describes an architecture for providing integrated services over low-bitrate links, such as modem lines, ISDN B-channels, and sub-T1 links. This memo provides information for the Internet community.
RFC2688 - Integrated Services Mappings for Low Speed Networks
This document defines the service mappings of the IETF Integrated Services for low-bitrate links, specifically the controlled load and guaranteed services. [STANDARDS-TRACK]
RFC2687 - PPP in a Real-time Oriented HDLC-like Framing
This document proposes the suspend/resume-oriented solution for the real-time encapsulation format part of the architecture. [STANDARDS-TRACK]
RFC2686 - The Multi-Class Extension to Multi-Link PPP
This document proposes the fragment-oriented solution for the real-time encapsulation format part of the architecture. [STANDARDS-TRACK]
RFC2685 - Virtual Private Networks Identifier
This document proposes a format for a globally unique VPN identifier. [STANDARDS-TRACK]
RFC2684 - Multiprotocol Encapsulation over ATM Adaptation Layer 5
This memo replaces RFC 1483. It describes two encapsulations methods for carrying network interconnect traffic over AAL type 5 over ATM. [STANDARDS-TRACK]
RFC2683 - IMAP4 Implementation Recommendations
The IMAP4 specification describes a rich protocol for use in building clients and servers for storage, retrieval, and manipulation of electronic mail. Because the protocol is so rich and has so many implementation choices, there are often trade-offs that must be made and issues that must be considered when designing such clients and servers. This document attempts to outline these issues and to make recommendations in order to make the end products as interoperable as possible. This memo provides information for the Internet community.
RFC2682 - Performance Issues in VC-Merge Capable ATM LSRs
This document investigates the impact of VC merging on the additional buffer required for the reassembly buffers and other buffers. This memo provides information for the Internet community.
RFC2681 - A Round-trip Delay Metric for IPPM
This memo defines a metric for round-trip delay of packets across Internet paths. [STANDARDS-TRACK]
RFC2680 - A One-way Packet Loss Metric for IPPM
This memo defines a metric for one-way packet loss across Internet paths. [STANDARDS-TRACK]
RFC2679 - A One-way Delay Metric for IPPM
This memo defines a metric for one-way delay of packets across Internet paths. [STANDARDS-TRACK]
RFC2678 - IPPM Metrics for Measuring Connectivity
This memo defines a series of metrics for connectivity between a pair of Internet hosts. [STANDARDS-TRACK]
RFC2677 - Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP)
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
RFC2676 - QoS Routing Mechanisms and OSPF Extensions
This memo describes extensions to the OSPF protocol to support QoS routes. The focus of this document is on the algorithms used to compute QoS routes and on the necessary modifications to OSPF to support this function, e.g., the information needed, its format, how it is distributed, and how it is used by the QoS path selection process. This memo defines an Experimental Protocol for the Internet community.
RFC2675 - IPv6 Jumbograms
This document describes the IPv6 Jumbo Payload option, which provides the means of specifying such large payload lengths. It also describes the changes needed to TCP and UDP to make use of jumbograms. [STANDARDS-TRACK]
RFC2674 - Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. [STANDARDS-TRACK]
RFC2673 - Binary Labels in the Domain Name System
This document defines a "Bit-String Label" which may appear within domain names. This new label type compactly represents a sequence of "One-Bit Labels" and enables resource records to be stored at any bit- boundary in a binary-named section of the domain name tree. [STANDARDS-TRACK]
RFC2672 - Non-Terminal DNS Name Redirection
This document defines a new DNS Resource Record called "DNAME", which provides the capability to map an entire subtree of the DNS name space to another domain. [STANDARDS-TRACK]
RFC2671 - Extension Mechanisms for DNS (EDNS0)
The Domain Name System's wire protocol includes a number of fixed fields whose range has been or soon will be exhausted and does not allow clients to advertise their capabilities to servers. This document describes backward compatible mechanisms for allowing the protocol to grow. [STANDARDS-TRACK]
RFC2670 - Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfaces
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP-based management of MCNS/DOCSIS compliant Radio Frequency (RF) interfaces. [STANDARDS-TRACK]
RFC2669 - DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP-based management of DOCSIS 1.0 compliant Cable Modems and Cable Modem Termination Systems. [STANDARDS-TRACK]
RFC2668 - Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
RFC2667 - IP Tunnel MIB
This memo defines a Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing tunnels of any type over IPv4 networks. [STANDARDS-TRACK]
RFC2666 - Definitions of Object Identifiers for Identifying Ethernet Chip Sets
This memo defines OBJECT IDENTIFIER values for use with network management protocols in the Internet community. This memo provides information for the Internet community.
RFC2665 - Definitions of Managed Objects for the Ethernet-like Interface Types
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
RFC2664 - FYI on Questions and Answers - Answers to Commonly Asked "New Internet User" Questions
This memo provides an overview to the new Internet User. The intended audience is the common Internet user of today, thus it attempts to provide a more consumer oriented approach to the Internet rather than going into any depth about a topic. This memo provides information for the Internet community.
RFC2663 - IP Network Address Translator (NAT) Terminology and Considerations
This document attempts to describe the operation of NAT devices and the associated considerations in general, and to define the terminology used to identify various flavors of NAT. This memo provides information for the Internet community.
RFC2662 - Definitions of Managed Objects for the ADSL Lines
This document defines a standard SNMP MIB for ADSL lines based on the ADSL Forum standard data model. [STANDARDS-TRACK]
RFC2661 - Layer Two Tunneling Protocol "L2TP"
This document describes the Layer Two Tunneling Protocol (L2TP). [STANDARDS-TRACK]
RFC2660 - The Secure HyperText Transfer Protocol
This memo describes a syntax for securing messages sent using the Hypertext Transfer Protocol (HTTP), which forms the basis for the World Wide Web. Secure HTTP (S-HTTP) provides independently applicable security services for transaction confidentiality, authenticity/integrity and non-repudiability of origin.
RFC2659 - Security Extensions For HTML
This memo describes a syntax for embedding S-HTTP negotiation parameters in HTML documents. This memo defines an Experimental Protocol for the Internet community.
RFC2658 - RTP Payload Format for PureVoice(tm) Audio
This document describes the RTP payload format for PureVoice(tm) Audio. [STANDARDS-TRACK]
RFC2657 - LDAPv2 Client vs. the Index Mesh
LDAPv2 clients as implemented according to RFC 1777 have no notion on referral. The integration between such a client and an Index Mesh, as defined by the Common Indexing Protocol, heavily depends on referrals and therefore needs to be handled in a special way. This document defines one possible way of doing this. This memo defines an Experimental Protocol for the Internet community.
RFC2656 - Registration Procedures for SOIF Template Types
The registration procedure described in this document is specific to SOIF template types. This memo defines an Experimental Protocol for the Internet community.
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. This memo provides information for the Internet community.
RFC2705 - Media Gateway Control Protocol (MGCP) Version 1.0
This document describes an application programming interface and a corresponding protocol (MGCP) for controlling Voice over IP (VoIP) Gateways from external call control elements. MGCP assumes a call control architecture where the call control "intelligence" is outside the gateways and handled by external call control elements. This memo provides information for the Internet community.
RFC2704 - The KeyNote Trust-Management System Version 2
This memo describes version 2 of the KeyNote trust-management system.It specifies the syntax and semantics of KeyNote `assertions', describes `action attribute' processing, and outlines the application architecture into which a KeyNote implementation can be fit. This memo provides information for the Internet community.
RFC2703 - Protocol-independent Content Negotiation Framework
This memo sets out terminology, an abstract framework and goals for protocol-independent content negotiation, and identifies some technical issues which may need to be addressed. This memo provides information for the Internet community.
RFC2702 - Requirements for Traffic Engineering Over MPLS
This document presents a set of requirements for Traffic Engineering over Multiprotocol Label Switching (MPLS). It identifies the functional capabilities required to implement policies that facilitate efficient and reliable network operations in an MPLS domain. This memo provides information for the Internet community.
RFC2701 - Nortel Networks Multi-link Multi-node PPP Bundle Discovery Protocol
This document specifies a standard way for Multi-link PPP to operate across multiple nodes. This memo provides information for the Internet community.
RFC2700 - Internet Official Protocol Standards
This memo describes the current state of standardization of protocols used in the Internet as determined by the Internet Engineering Task Force (IETF). [STANDARDS-TRACK]
RFC2698 - A Two Rate Three Color Marker
This document defines a Two Rate Three Color Marker (trTCM), which can be used as a component in a Diffserv traffic conditioner. This memo provides information for the Internet community.
RFC2697 - A Single Rate Three Color Marker
This document defines a Single Rate Three Color Marker (srTCM), which can be used as component in a Diffserv traffic conditioner. This memo provides information for the Internet community.
RFC2696 - LDAP Control Extension for Simple Paged Results Manipulation
This document describes an LDAPv3 control extension for simple paging of search results. This memo provides information for the Internet community.
RFC2695 - Authentication Mechanisms for ONC RPC
This document describes two authentication mechanisms created by Sun Microsystems that are commonly used in conjunction with the ONC Remote Procedure Call (ONC RPC Version 2) protocol. This memo provides information for the Internet community.
RFC2694 - DNS extensions to Network Address Translators (DNS_ALG)
This document identifies the need for DNS extensions to NATs and outlines how a DNS Application Level Gateway (DNS_ALG) can meet the need. This memo provides information for the Internet community.
RFC2693 - SPKI Certificate Theory
This document gives the theory behind SPKI certificates and ACLs without going into technical detail about those structures or their uses. This memo defines an Experimental Protocol for the Internet community.
RFC2692 - SPKI Requirements
The SPKI Working Group first established a list of things one might want to do with certificates (attached at the end of this document), and then summarized that list of desires into requirements. This document presents that summary of requirements. This memo defines an Experimental Protocol for the Internet community.
RFC2691 - A Memorandum of Understanding for an ICANN Protocol Support Organization
This is the text of the Memorandum of Understanding (MoU) that was signed by ICANN, the IETF, the ITU-T, W3C and ETSI on July 14, 1999 in Oslo. This MoU creates the Protocol Support Organization (PSO) within the Internet Corporation for Assigned Names and Numbers (ICANN). This memo provides information for the Internet community.
RFC2690 - A Proposal for an MOU-Based ICANN Protocol Support Organization
This is a copy of the proposal for an MOU-based Protocol Supporting Organization that was submitted to ICANN on April 23, 1999. This memo provides information for the Internet community.
RFC2689 - Providing Integrated Services over Low-bitrate Links
This document describes an architecture for providing integrated services over low-bitrate links, such as modem lines, ISDN B-channels, and sub-T1 links. This memo provides information for the Internet community.
RFC2688 - Integrated Services Mappings for Low Speed Networks
This document defines the service mappings of the IETF Integrated Services for low-bitrate links, specifically the controlled load and guaranteed services. [STANDARDS-TRACK]
RFC2687 - PPP in a Real-time Oriented HDLC-like Framing
This document proposes the suspend/resume-oriented solution for the real-time encapsulation format part of the architecture. [STANDARDS-TRACK]
RFC2686 - The Multi-Class Extension to Multi-Link PPP
This document proposes the fragment-oriented solution for the real-time encapsulation format part of the architecture. [STANDARDS-TRACK]
RFC2685 - Virtual Private Networks Identifier
This document proposes a format for a globally unique VPN identifier. [STANDARDS-TRACK]
RFC2684 - Multiprotocol Encapsulation over ATM Adaptation Layer 5
This memo replaces RFC 1483. It describes two encapsulations methods for carrying network interconnect traffic over AAL type 5 over ATM. [STANDARDS-TRACK]
RFC2683 - IMAP4 Implementation Recommendations
The IMAP4 specification describes a rich protocol for use in building clients and servers for storage, retrieval, and manipulation of electronic mail. Because the protocol is so rich and has so many implementation choices, there are often trade-offs that must be made and issues that must be considered when designing such clients and servers. This document attempts to outline these issues and to make recommendations in order to make the end products as interoperable as possible. This memo provides information for the Internet community.
RFC2682 - Performance Issues in VC-Merge Capable ATM LSRs
This document investigates the impact of VC merging on the additional buffer required for the reassembly buffers and other buffers. This memo provides information for the Internet community.
RFC2681 - A Round-trip Delay Metric for IPPM
This memo defines a metric for round-trip delay of packets across Internet paths. [STANDARDS-TRACK]
RFC2680 - A One-way Packet Loss Metric for IPPM
This memo defines a metric for one-way packet loss across Internet paths. [STANDARDS-TRACK]
RFC2679 - A One-way Delay Metric for IPPM
This memo defines a metric for one-way delay of packets across Internet paths. [STANDARDS-TRACK]
RFC2678 - IPPM Metrics for Measuring Connectivity
This memo defines a series of metrics for connectivity between a pair of Internet hosts. [STANDARDS-TRACK]
RFC2677 - Definitions of Managed Objects for the NBMA Next Hop Resolution Protocol (NHRP)
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
RFC2676 - QoS Routing Mechanisms and OSPF Extensions
This memo describes extensions to the OSPF protocol to support QoS routes. The focus of this document is on the algorithms used to compute QoS routes and on the necessary modifications to OSPF to support this function, e.g., the information needed, its format, how it is distributed, and how it is used by the QoS path selection process. This memo defines an Experimental Protocol for the Internet community.
RFC2675 - IPv6 Jumbograms
This document describes the IPv6 Jumbo Payload option, which provides the means of specifying such large payload lengths. It also describes the changes needed to TCP and UDP to make use of jumbograms. [STANDARDS-TRACK]
RFC2674 - Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. [STANDARDS-TRACK]
RFC2673 - Binary Labels in the Domain Name System
This document defines a "Bit-String Label" which may appear within domain names. This new label type compactly represents a sequence of "One-Bit Labels" and enables resource records to be stored at any bit- boundary in a binary-named section of the domain name tree. [STANDARDS-TRACK]
RFC2672 - Non-Terminal DNS Name Redirection
This document defines a new DNS Resource Record called "DNAME", which provides the capability to map an entire subtree of the DNS name space to another domain. [STANDARDS-TRACK]
RFC2671 - Extension Mechanisms for DNS (EDNS0)
The Domain Name System's wire protocol includes a number of fixed fields whose range has been or soon will be exhausted and does not allow clients to advertise their capabilities to servers. This document describes backward compatible mechanisms for allowing the protocol to grow. [STANDARDS-TRACK]
RFC2670 - Radio Frequency (RF) Interface Management Information Base for MCNS/DOCSIS compliant RF interfaces
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP-based management of MCNS/DOCSIS compliant Radio Frequency (RF) interfaces. [STANDARDS-TRACK]
RFC2669 - DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for SNMP-based management of DOCSIS 1.0 compliant Cable Modems and Cable Modem Termination Systems. [STANDARDS-TRACK]
RFC2668 - Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
RFC2667 - IP Tunnel MIB
This memo defines a Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing tunnels of any type over IPv4 networks. [STANDARDS-TRACK]
RFC2666 - Definitions of Object Identifiers for Identifying Ethernet Chip Sets
This memo defines OBJECT IDENTIFIER values for use with network management protocols in the Internet community. This memo provides information for the Internet community.
RFC2665 - Definitions of Managed Objects for the Ethernet-like Interface Types
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
RFC2664 - FYI on Questions and Answers - Answers to Commonly Asked "New Internet User" Questions
This memo provides an overview to the new Internet User. The intended audience is the common Internet user of today, thus it attempts to provide a more consumer oriented approach to the Internet rather than going into any depth about a topic. This memo provides information for the Internet community.
RFC2663 - IP Network Address Translator (NAT) Terminology and Considerations
This document attempts to describe the operation of NAT devices and the associated considerations in general, and to define the terminology used to identify various flavors of NAT. This memo provides information for the Internet community.
RFC2662 - Definitions of Managed Objects for the ADSL Lines
This document defines a standard SNMP MIB for ADSL lines based on the ADSL Forum standard data model. [STANDARDS-TRACK]
RFC2661 - Layer Two Tunneling Protocol "L2TP"
This document describes the Layer Two Tunneling Protocol (L2TP). [STANDARDS-TRACK]
RFC2660 - The Secure HyperText Transfer Protocol
This memo describes a syntax for securing messages sent using the Hypertext Transfer Protocol (HTTP), which forms the basis for the World Wide Web. Secure HTTP (S-HTTP) provides independently applicable security services for transaction confidentiality, authenticity/integrity and non-repudiability of origin.
RFC2659 - Security Extensions For HTML
This memo describes a syntax for embedding S-HTTP negotiation parameters in HTML documents. This memo defines an Experimental Protocol for the Internet community.
RFC2658 - RTP Payload Format for PureVoice(tm) Audio
This document describes the RTP payload format for PureVoice(tm) Audio. [STANDARDS-TRACK]
RFC2657 - LDAPv2 Client vs. the Index Mesh
LDAPv2 clients as implemented according to RFC 1777 have no notion on referral. The integration between such a client and an Index Mesh, as defined by the Common Indexing Protocol, heavily depends on referrals and therefore needs to be handled in a special way. This document defines one possible way of doing this. This memo defines an Experimental Protocol for the Internet community.
RFC2656 - Registration Procedures for SOIF Template Types
The registration procedure described in this document is specific to SOIF template types. This memo defines an Experimental Protocol for the Internet community.