Network Working Group Internet Engineering Task Force Request for Comments: 2500 J. Reynolds Obsoletes: 2400, 2300, 2200, 2000, 1920, 1880, R. Braden 1800, 1780, 1720, 1610, 1600, 1540, 1500, 1410, Editors 1360, 1280, 1250, 1200, 1140, 1130, 1100, 1083 June 1999 STD: 1 Category: Standards Track Internet Official Protocol Standards Status of this Memo This memo describes the state of standardization of protocols used in the Internet as determined by the Internet Engineering Task Force (IETF). This memo is an Internet Standard. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 2 2. Current Technical Specifications . . . . . . . . . . . . . 4 2.1. Standard Protocols . . . . . . . . . . . . . . . . . . . 5 2.2. Network-Specific Standard Protocols . . . . . . . . . . 6 2.3. Draft Standard Protocols . . . . . . . . . . . . . . . . 7 2.4. Proposed Standard Protocols . . . . . . . . . . . . . . 9 2.5. Experimental Protocols . . . . . . . . . . . . . . . . . 18 3. Current Applicability Statements . . . . . . . . . . . . . 21 4. Non-Standard Protocols . . . . . . . . . . . . . . . . . . 22 4.1. Informational Protocol . . . . . . . . . . . . . . . . . 22 4.2. Historic Protocols . . . . . . . . . . . . . . . . . . . 24 5. Contacts . . . . . . . . . . . . . . . . . . . . . . . . . 25 5.1. IAB, IETF, and IRTF Contacts . . . . . . . . . . . . . . 25 5.2. Internet Assigned Numbers Authority (IANA) Contact . . . 25 5.3. Request for Comments Editor Contact . . . . . . . . . . 26 5.4. Requests for Comments Distribution Contact . . . . . . . 26 5.5. Sources for Requests for Comments . . . . . . . . . . . 26 6. Security Considerations . . . . . . . . . . . . . . . . . 26 7. Editors' Addresses . . . . . . . . . . . . . . . . . . . . 27 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 28 IETF Standards Track [Page 1] RFC 2500 Internet Standards June 1999 1. Introduction This memo summarizes the status of Internet protocols and specifications. It is published by the RFC Editor in accordance with Section 2.1 of "The Internet Standards Process -- Revision 3", RFC 2026, which specifies the rules and procedures by which all Internet stnadards are set. This memo is prepared by the RFC Editor for the IESG and IAB. It is a member of a series of summary memos that are published approximately every one hundred RFCs; please see www.rfc-editor.org. This memo lists the level and status of the archival documents known as RFCs (Request for Comments) within the Internet standards process. The reader is urged to review RFC 2026 for essential context for interpreting this memo. The following introductory text is quoted directly from RFC 2026: "The Internet, a loosely-organized international collaboration of autonomous, interconnected networks, supports host-to-host communication through voluntary adherence to open protocols and procedures defined by Internet Standards. There are also many isolated interconnected networks, which are not connected to the global Internet but use the Internet Standards. The Internet Standards Process described in this document is concerned with all protocols, procedures, and conventions that are used in or by the Internet, whether or not they are part of the TCP/IP protocol suite. In the case of protocols developed and/or standardized by non-Internet organizations, however, the Internet Standards Process normally applies to the application of the protocol or procedure in the Internet context, not to the specification of the protocol itself. In general, an Internet Standard is a specification that is stable and well-understood, is technically competent, has multiple, independent, and interoperable implementations with substantial operational experience, enjoys significant public support, and is recognizably useful in some or all parts of the Internet. Each distinct version of an Internet standards-related specification is published as part of the "Request for Comments" (RFC) document series. This archival series is the official publication channel for Internet standards documents and other publications of the IESG, IAB, and Internet community. RFCs can be obtained from a number of Internet hosts using anonymous FTP, gopher, World Wide Web, and other Internet document-retrieval systems. IETF Standards Track [Page 2] RFC 2500 Internet Standards June 1999 The rules for formatting and submitting an RFC are defined in [5]. Every RFC is available in ASCII text. Some RFCs are also available in other formats. The other versions of an RFC may contain material (such as diagrams and figures) that is not present in the ASCII version, and it may be formatted differently. ********************************************************* * * * A stricter requirement applies to standards-track * * specifications: the ASCII text version is the * * definitive reference, and therefore it must be a * * complete and accurate specification of the standard, * * including all necessary diagrams and illustrations. * * * ********************************************************* The status of Internet protocol and service specifications is summarized periodically in an RFC entitled "Internet Official Protocol Standards" [1]. This RFC shows the level of maturity and other helpful information for each Internet protocol or service specification (see section 3). Specifications subject to the Internet Standards Process fall into one of two categories: Technical Specification (TS) and Applicability Statement (AS). Some RFCs document Internet Standards. These RFCs form the "STD" subseries of the RFC series [4]. When a specification has been adopted as an Internet Standard, it is given the additional label "STDxxx", but it keeps its RFC number and its place in the RFC series. (see section 4.1.3) Some RFCs standardize the results of community deliberations about statements of principle or conclusions about what is the best way to perform some operations or IETF process function. These RFCs form the specification has been adopted as a BCP, it is given the additional label "BCPxxx", but it keeps its RFC number and its place in the RFC series. (see section 5) Not all specifications of protocols or services for the Internet should or will become Internet Standards or BCPs. Such non- standards track specifications are not subject to the rules for Internet standardization. Non-standards track specifications may be published directly as "Experimental" or "Informational" RFCs at the discretion of the RFC Editor in consultation with the IESG (see section 4.2)." IETF Standards Track [Page 3] RFC 2500 Internet Standards June 1999 Section 2 of this memo lists all Technical Specification RFCs that are in the standards track, and Section 3 lists Applicability Statement RFCs in the standards track. Section 4 lists those protocol specification RFCs that are off the standards track (Informational and Historic status). This memo does not list Informational RFCs that may be of general interest to the community but do not specify protocols for the Internet. It also does not list BCP RFCs. Telnet options have been added into the lists. 2. Current Technical Specifications Subsections 2.1-2.5 list the standards in groups by protocol state. In the following lists, shorthand nicknames have been shown for many of the major protocols. These names are commonly used in discourse on Internet mailing lists. IETF Standards Track [Page 4] RFC 2500 Internet Standards June 1999 2.1. Standard Protocols Protocol Name RFC STD * ======== ===================================== ==== === = -------- Internet Official Protocol Standards 2500 1 -------- Assigned Numbers 1700 2 IP Internet Protocol 791 5 as amended by:-------- -------- IP Subnet Extension 950 5 -------- IP Broadcast Datagrams 919 5 -------- IP Broadcast Datagrams with Subnets 922 5 ICMP Internet Control Message Protocol 792 5 IGMP Internet Group Multicast Protocol 1112 5 UDP User Datagram Protocol 768 6 TCP Transmission Control Protocol 793 7 TELNET Telnet Protocol 854,855 8 FTP File Transfer Protocol 959 9 SMTP Simple Mail Transfer Protocol 821 10 SMTP-SIZE SMTP Service Ext for Message Size 1870 10 SMTP-EXT SMTP Service Extensions 1869 10 MAIL Format of Electronic Mail Messages 822 11 NTPV2 Network Time Protocol (Version 2) 1119 12 DOMAIN Domain Name System 1034,1035 13 DNS-MX Mail Routing and the Domain System 974 14 SNMP Simple Network Management Protocol 1157 15 SMI Structure of Management Information 1155 16 Concise-MIB Concise MIB Definitions 1212 16 MIB-II Management Information Base-II 1213 17 NETBIOS NetBIOS Service Protocols 1001,1002 19 ECHO Echo Protocol 862 20 DISCARD Discard Protocol 863 21 CHARGEN Character Generator Protocol 864 22 QUOTE Quote of the Day Protocol 865 23 USERS Active Users Protocol 866 24 DAYTIME Daytime Protocol 867 25 TIME Time Server Protocol 868 26 TOPT-BIN Binary Transmission 856 27 TOPT-ECHO Echo 857 28 TOPT-SUPP Suppress Go Ahead 858 29 TOPT-STAT Status 859 30 TOPT-TIM Timing Mark 860 31 TOPT-EXTOP Extended-Options-List 861 32 TFTP Trivial File Transfer Protocol 1350 33 TP-TCP ISO Transport Service on top of the TCP 1006 35 ETHER-MIB Ethernet MIB 1643 50 PPP Point-to-Point Protocol (PPP) 1661 51 PPP-HDLC PPP in HDLC Framing 1662 51 IP-SMDS IP Datagrams over the SMDS Service 1209 52 IETF Standards Track [Page 5] RFC 2500 Internet Standards June 1999 POP3 Post Office Protocol, Version 3 1939 53 OSPF2 Open Shortest Path First Routing V2 2328 54 IP-FR Multiprotocol over Frame Relay 2427 55* RIP2 RIP Version 2-Carrying Additional Info. 2453 56* RIP2-APP RIP Version 2 Protocol App. Statement 1722 57* SMIv2 Structure of Management Information v2 2578 58* CONV-MIB Textual Conventions for SNMPv2 2579 58* CONF-MIB Conformance Statements for SNMPv2 2580 58* [Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] 2.2. Network-Specific Standard Protocols Protocol Name RFC STD * ======== ===================================== ===== === = IP-ATM Classical IP and ARP over ATM 2225 ATM-ENCAP Multiprotocol Encapsulation over ATM 1483 IP-TR-MC IP Multicast over Token-Ring LANs 1469 IP-FDDI Transmission of IP and ARP over FDDI Net 1390 36 IP-X.25 X.25 and ISDN in the Packet Mode 1356 ARP Address Resolution Protocol 826 37 RARP A Reverse Address Resolution Protocol 903 38 IP-ARPA Internet Protocol on ARPANET BBN1822 39 IP-WB Internet Protocol on Wideband Network 907 40 IP-E Internet Protocol on Ethernet Networks 894 41 IP-EE Internet Protocol on Exp. Ethernet Nets 895 42 IP-IEEE Internet Protocol on IEEE 802 1042 43 IP-DC Internet Protocol on DC Networks 891 44 IP-HC Internet Protocol on Hyperchannel 1044 45 IP-ARC Transmitting IP Traffic over ARCNET Nets 1201 46 IP-SLIP Transmission of IP over Serial Lines 1055 47 IP-NETBIOS Transmission of IP over NETBIOS 1088 48 IP-IPX Transmission of 802.2 over IPX Networks 1132 49 IP-HIPPI IP over HIPPI 2067 [Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] IETF Standards Track [Page 6] RFC 2500 Internet Standards June 1999 2.3. Draft Standard Protocols Protocol Name RFC ======== ===================================== ===== VACM-SNMP View-based Access Control Model for SMMP 2575* USM-SNMPV3 User-based Security Model for SNMPv3 2574* SNMP-APP SNMP Applications 2573* MPD-SNMP Message Processing & Dispatching SNMP 2572* ARCH-SNMP Architecture Describing SNMP Management Frameworks 2571* ICMPv6 ICMPv6 for IPv6 2463* IPV6-AUTO IPv6 Stateless Address Autoconfiguation 2462* IPV6-ND Neighbor Discovery for IP Version 6 2461* IPV6 IPv6 Specification 2460* URI-GEN URI: Generic Syntax 2396 IARP Inverse Address Resolution Protocol 2390 TN3270E Telnet Option - TN3270 Enhancements 2355* TFTP-Opt TFTP Options 2349 TFTP-Blk TFTP Blocksize Option 2348 TFTP-Ext TFTP Option Extension 2347 ONE-PASS One-Time Password System 2289 SMTP-Pipe SMTP Serv. Ext. for Command Pipelining 2197 DHCP-BOOTP DHCP Options and BOOTP Extensions 2132 DHCP Dynamic Host Configuration Protocol 2131 FRAME-MIB Management Information Base for Frame