Документ взят из кэша поисковой машины. Адрес оригинального документа : http://mirror.msu.net/pub/rfc-editor/rfc-ed-all/pdfrfc/rfc2300.txt.pdf Дата изменения: Wed Mar 27 23:26:35 2002 Дата индексирования: Tue Oct 2 18:59:35 2012 Кодировка: Поисковые слова: guide 8.0

Network Working Group Internet Architecture Board Request for Comments: 2300 J. Postel, Editor Obsoletes: 2200, 2000, 1920, 1880, 1800, May 1998 1780, 1720, 1610, 1600, 1540, 1500, 1410, 1360, 1280, 1250, 1200, 1140, 1130, 1100, 1083 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 Architecture Board (IAB). This memo is an Internet Standard. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (1998). Table of Contents Introduction . . . . . . . . . . . . . . . . . . . . . . 1. The Standardization Process . . . . . . . . . . . . 2. The Request for Comments Documents . . . . . . . . . 3. Other Reference Documents . . . . . . . . . . . . . 3.1. Assigned Numbers . . . . . . . . . . . . . . . . . 3.2. Gateway Requirements . . . . . . . . . . . . . . . 3.3. Host Requirements . . . . . . . . . . . . . . . . 3.4. The MIL-STD Documents . . . . . . . . . . . . . . 4. Explanation of Terms . . . . . . . . . . . . . . . . 4.1. Definitions of Protocol State (Maturity Level) . . 4.1.1. Standard Protocol . . . . . . . . . . . . . . . 4.1.2. Draft Standard Protocol . . . . . . . . . . . . 4.1.3. Proposed Standard Protocol . . . . . . . . . . . 4.1.4. Experimental Protocol . . . . . . . . . . . . . 4.1.5. Informational Protocol . . . . . . . . . . . . . 4.1.6. Historic Protocol . . . . . . . . . . . . . . . 4.2. Definitions of Protocol Status (Requirement Level) 4.2.1. Required Protocol . . . . . . . . . . . . . . . 4.2.2. Recommended Protocol . . . . . . . . . . . . . . 4.2.3. Elective Protocol . . . . . . . . . . . . . . . 4.2.4. Limited Use Protocol . . . . . . . . . . . . . . 4.2.5. Not Recommended Protocol . . . . . . . . . . . . 5. The Standards Track . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3 5 6 6 6 6 6 7 8 8 8 8 8 9 9 9 9 9 9 9 9 10 All Rights Reserved.

Internet Architecture Board Standards Track

[Page 1]


RFC 2300

Internet Standards

May 1998

5.1. The RFC Processing Decision Table . . . . . . . . 5.2. The Standards Track Diagram . . . . . . . . . . . 6. The Protocols . . . . . . . . . . . . . . . . . . . 6.1. Recent Changes . . . . . . . . . . . . . . . . . . 6.1.1. New RFCs . . . . . . . . . . . . . . . . . . . . 6.1.2. Other Changes . . . . . . . . . . . . . . . . . 6.2. Standard Protocols . . . . . . . . . . . . . . . . 6.3. Network-Specific Standard Protocols . . . . . . . 6.4. Draft Standard Protocols . . . . . . . . . . . . . 6.5. Proposed Standard Protocols . . . . . . . . . . . 6.6. Telnet Options . . . . . . . . . . . . . . . . . . 6.7. Experimental Protocols . . . . . . . . . . . . . . 6.8. Informational Protocols . . . . . . . . . . . . . 6.9. Historic Protocols . . . . . . . . . . . . . . . . 6.10 Obsolete Protocols . . . . . . . . . . . . . . . . 7. Contacts . . . . . . . . . . . . . . . . . . . . . . 7.1. IAB, IETF, and IRTF Contacts . . . . . . . . . . . 7.1.1. Internet Architecture Board (IAB) Contact . . . 7.1.2. Internet Engineering Task Force (IETF) Contact . 7.1.3. Internet Research Task Force (IRTF) Contact . . 7.2. Internet Assigned Numbers Authority (IANA) Contact 7.3. Request for Comments Editor Contact . . . . . . . 7.4. Network Information Center Contact . . . . . . . . 7.5. Sources for Requests for Comments . . . . . . . . 8. Security Considerations . . . . . . . . . . . . . . 9. Author's Address . . . . . . . . . . . . . . . . . . 10. Full Copyright Statement . . . . . . . . . . . . . . Introduction

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . .

10 11 13 13 13 33 34 36 37 39 46 47 50 52 53 54 54 54 54 55 56 57 57 58 58 58 59

A discussion of the standardization process and the RFC document series is presented first, followed by an explanation of the terms. Sections 6.2 - 6.10 contain the lists of protocols in each stage of standardization. Finally are pointers to references and contacts for further information. This memo is intended to be issued every one hundred RFCs; please be sure the copy you are reading is current. Current copies may be obtained from the Requests for Comments Editor (RFC-EDITOR) or from the Internet Assigned Numbers Authority (IANA) (see the contact information at the end of this memo). See Section 6.1 for a description of recent changes. In the official lists in sections 6.2 - 6.10, an asterisk (*) next to a protocol denotes that it is new to this document or has been moved from one protocol level to another, or differs from the previous edition of this document.

Internet Architecture Board Standards Track

[Page 2]


RFC 2300

Internet Standards

May 1998

1.

The Standardization Process The Internet Architecture Board maintains this list of documents that define standards for the Internet protocol suite. See RFC-1601 for the charter of the IAB and RFC-1160 for an explanation of the role and organization of the IAB and its subsidiary groups, the Internet Engineering Task Force (IETF) and the Internet Research Task Force (IRTF). Each of these groups has a steering group called the IESG and IRSG, respectively. The IETF develops these standards with the goal of co-ordinating the evolution of the Internet protocols; this co-ordination has become quite important as the Internet protocols are increasingly in general commercial use. The definitive description of the Internet standards process is found in RFC-1602. The majority of Internet protocol development and standardization activity takes place in the working groups of the IETF. Protocols which are to become standards in the Internet go through a series of states or maturity levels (proposed standard, draft standard, and standard) involving increasing amounts of scrutiny and testing. When a protocol completes this process it is assigned a STD number (see RFC-1311). At each step, the Internet Engineering Steering Group (IESG) of the IETF must make a recommendation for advancement of the protocol. To allow time for the Internet community to consider and react to standardization proposals, a minimum delay of 6 months before a proposed standard can be advanced to a draft standard and 4 months before a draft standard can be promoted to standard. It is general practice that no proposed standard can be promoted to draft standard without at least two independent implementations (and the recommendation of the IESG). Promotion from draft standard to standard generally requires operational experience and demonstrated interoperability of two or more implementations (and the recommendation of the IESG). In cases where there is uncertainty as to the proper decision concerning a protocol a special review committee may be appointed consisting of experts from the IETF, IRTF and the IAB with the purpose of recommending an explicit action. Advancement of a protocol to proposed standard is an important step since it marks a protocol as a candidate for eventual standardization (it puts the protocol "on the standards track"). Advancement to draft standard is a major step which warns the community that, unless major objections are raised or flaws are discovered, the protocol is likely to be advanced to standard.

Internet Architecture Board Standards Track

[Page 3]


RFC 2300

Internet Standards

May 1998

Some protocols have been superseded by better ones or are otherwise unused. Such protocols are still documented in this memorandum with the designation "historic". Because it is useful to document the results of early protocol research and development work, some of the RFCs document protocols which are still in an experimental condition. The protocols are designated "experimental" in this memorandum. They appear in this report as a convenience to the community and not as evidence of their standardization. Other protocols, such as those developed by other standards organizations, or by particular vendors, may be of interest or may be recommended for use in the Internet. The specifications of such protocols may be published as RFCs for the convenience of the Internet community. These protocols are labeled "informational" in this memorandum. In addition to the working groups of the IETF, protocol development and experimentation may take place as a result of the work of the research groups of the Internet Research Task Force, or the work of other individuals interested in Internet protocol development. The the documentation of such experimental work in the RFC series is encouraged, but none of this work is considered to be on the track for standardization until the IESG has made a recommendation to advance the protocol to the proposed standard state. A few protocols have achieved widespread implementation without the approval of the IESG. For example, some vendor protocols have become very important to the Internet community even though they have not been recommended by the IESG. However, the IAB strongly recommends that the standards process be used in the evolution of the protocol suite to maximize interoperability (and to prevent incompatible protocol requirements from arising). The use of the terms "standard", "draft standard", and "proposed standard" are reserved in any RFC or other publication of Internet protocols to only those protocols which the IESG has approved. In addition to a state (like "Proposed Standard"), a protocol is also assigned a status, or requirement level, in this document. The possible requirement levels ("Required", "Recommended", "Elective", "Limited Use", and "Not Recommended") are defined in Section 4.2. When a protocol is on the standards track, that is in the proposed standard, draft standard, or standard state (see Section 5), the status shown in Section 6 is the current status. Few protocols are required to be implemented in all systems; this is because there is such a variety of possible systems, for example,

Internet Architecture Board Standards Track

[Page 4]


RFC 2300

Internet Standards

May 1998

gateways, routers, terminal servers, workstations, and multi-user hosts. The requirement level shown in this document is only a one word label, which may not be sufficient to characterize the implementation requirements for a protocol in all situations. For some protocols, this document contains an additional status paragraph (an applicability statement). In addition, more detailed status information may be contained in separate requirements documents (see Section 3). 2. The Request for Comments Documents The documents called Request for Comments (or RFCs) are the working notes of the "Network Working Group", that is the Internet research and development community. A document in this series may be on essentially any topic related to computer communication, and may be anything from a meeting report to the specification of a standard. Notice: All standards are published as RFCs, but not all RFCs specify standards. Anyone can submit a document for publication as an RFC. Submissions must be made via electronic mail to the RFC Editor (see the contact information at the end of this memo, and see RFC 2223). While RFCs are not refereed publications, they do receive technical review from the task forces, individual technical experts, or the RFC Editor, as appropriate. The RFC series comprises a wide range of documents, ranging from informational documents of general interests to specifications of standard Internet protocols. In cases where submission is intended to document a proposed standard, draft standard, or standard protocol, the RFC Editor will publish the document only with the approval of the IESG. For documents describing experimental work, the RFC Editor will notify the IESG before publication, allowing for the possibility of review by the relevant IETF working group or IRTF research group and provide those comments to the author. See Section 5.1 for more detail. Once a document is assigned an RFC number and published, that RFC is never revised or re-issued with the same number. There is never a question of having the most recent version of a particular RFC. However, a protocol (such as File Transfer Protocol (FTP)) may be improved and re-documented many times in several different RFCs. It is important to verify that you have the most recent RFC on a particular protocol. This "Internet Official Protocol Standards"

Internet Architecture Board Standards Track

[Page 5]


RFC 2300

Internet Standards

May 1998

memo is the reference for determining the correct RFC for the current specification of each protocol. The RFCs are available from the RFC-EDITOR, and a number of other sites. For more information about obtaining RFCs, see Sections 7.4 and 7.5. 3. Other Reference Documents There are three other reference documents of interest in checking the current status of protocol specifications and standardization. These are the Assigned Numbers, the Gateway Requirements, and the Host Requirements. Note that these documents are revised and updated at different times; in case of differences between these documents, the most recent must prevail. Also, one should be aware of the MIL-STD publications on IP, TCP, Telnet, FTP, and SMTP. These are described in Section 3.4. 3.1. Assigned Numbers lists the assigned values of the protocols. For example, IP protocol Option Codes, ARP hardware types, and Numbers was most recently issued as

The "Assigned Numbers" document parameters used in the various codes, TCP port numbers, Telnet Terminal Type names. Assigned RFC-1700. 3.2.

Requirements for IP Version 4 Routers

This document reviews the specifications that apply to gateways and supplies guidance and clarification for any ambiguities. Requirements for IP Version 4 Routers is RFC-1812. 3.3. Host Requirements

This pair of documents reviews and updates the specifications that apply to hosts, and it supplies guidance and clarification for any ambiguities. Host Requirements was issued as RFC-1122 and RFC-1123. 3.4. The MIL-STD Documents

The DoD MIL-STD Internet specifications are out of date and have been discontinued. The DoD's Joint Technical Architecture (JTA) lists the current set of IETF STDs and RFCs that the DoD intends to use in all new and upgraded Command, Control, Communications, Computers, and Intelligence (C4I) acquisitions. A copy of the JTA can be obtained from http://www-jta.itsi.disa.mil.

Internet Architecture Board Standards Track

[Page 6]


RFC 2300

Internet Standards

May 1998

4.

Explanation of Terms There are two independent categorization of protocols. The first is the "maturity level" or STATE of standardization, one of "standard", "draft standard", "proposed standard", "experimental", "informational" or "historic". The second is the "requirement level" or STATUS of this protocol, one of "required", "recommended", "elective", "limited use", or "not recommended". The status or requirement level is difficult to portray in a one word label. These status labels should be considered only as an indication, and a further description, or applicability statement, should be consulted. When a protocol is advanced to proposed standard or draft standard, it is labeled with a current status. At any given time a protocol occupies a cell of the following matrix. Protocols are likely to be in cells in about the following proportions (indicated by the relative number of Xs). A new protocol is most likely to start in the (proposed standard, elective) cell, or the (experimental, limited use) cell. STATUS Req Rec Ele Lim Not +-----+-----+-----+-----+-----+ | X | XXX | XXX | | | +-----+-----+-----+-----+-----+ | X | X | XXX | | | +-----+-----+-----+-----+-----+ | | X | XXX | | | +-----+-----+-----+-----+-----+ | | | | | | +-----+-----+-----+-----+-----+ | | | | XXX | | +-----+-----+-----+-----+-----+ | | | | | XXX | +-----+-----+-----+-----+-----+

Std S Draft T Prop A Info T Expr E Hist

What is a "system"? Some protocols are particular to hosts and some protocols are used in both. The definitions of will refer to a "system" which is either a host both). It should be clear from the context of protocol which types of systems are intended. to the or the gateways; a few terms below a gateway (or particular

Internet Architecture Board Standards Track

[Page 7]


RFC 2300

Internet Standards

May 1998

4.1.

Definitions of Protocol State

Every protocol listed in this document is assigned to a "maturity level" or STATE of standardization: "standard", "draft standard", "proposed standard", "experimental", or "historic". 4.1.1. Standard Protocol

The IESG has established this as an official standard protocol for the Internet. These protocols are assigned STD numbers (see RFC1311). These are separated into two groups: (1) IP protocol and above, protocols that apply to the whole Internet; and (2) network-specific protocols, generally specifications of how to do IP on particular types of networks. 4.1.2. Draft Standard Protocol as a possible testing and comment be submitted to the be made in a Draft Protocol.

The IESG is actively considering this protocol Standard Protocol. Substantial and widespread are desired. Comments and test results should IESG. There is a possibility that changes will Standard Protocol before it becomes a Standard 4.1.3. Proposed Standard Protocol

These are protocol proposals that may be considered by the IESG for standardization in the future. Implementation and testing by several groups is desirable. Revision of the protocol specification is likely. 4.1.4. Experimental Protocol

A system should not implement an experimental protocol unless it is participating in the experiment and has coordinated its use of the protocol with the developer of the protocol. Typically, experimental protocols are those that are developed as part of an ongoing research project not related to an operational service offering. While they may be proposed as a service protocol at a later stage, and thus become proposed standard, draft standard, and then standard protocols, the designation of a protocol as experimental may sometimes be meant to suggest that the protocol, although perhaps mature, is not intended for operational use.

Internet Architecture Board Standards Track

[Page 8]


RFC 2300

Internet Standards

May 1998

4.1.5.

Informational Protocol

Protocols developed by other standard organizations, or vendors, or that are for other reasons outside the purview of the IESG, may be published as RFCs for the convenience of the Internet community as informational protocols. 4.1.6. Historic Protocol

These are protocols that are unlikely to ever become standards in the Internet either because they have been superseded by later developments or due to lack of interest. 4.2. Definitions of Protocol Status This document lists a "requirement level" or STATUS for each protocol. The status is one of "required", "recommended", "elective", "limited use", or "not recommended". 4.2.1. Required Protocol

A system must implement the required protocols. 4.2.2. Recommended Protocol

A system should implement the recommended protocols. 4.2.3. Elective Protocol

A system may or may not implement an elective protocol. The general notion is that if you are going to do something like this, you must do exactly this. There may be several elective protocols in a general area, for example, there are several electronic mail protocols, and several routing protocols. 4.2.4. Limited Use Protocol

These protocols are for use in limited circumstances. This may be because of their experimental state, specialized nature, limited functionality, or historic state. 4.2.5. Not Recommended Protocol

These protocols are not recommended for general use. This may be because of their limited functionality, specialized nature, or experimental or historic state.

Internet Architecture Board Standards Track

[Page 9]


RFC 2300

Internet Standards

May 1998

5.

The Standards Track This section discusses in more detail the procedures used by the RFC Editor and the IESG in making decisions about the labeling and publishing of protocols as standards.

5.1.

The RFC Processing Decision Table

Here is the current decision table for processing submissions by the RFC Editor. The processing depends on who submitted it, and the status they want it to have. +==========================================================+ |**************| SOURCE | +==========================================================+ | Desired | IAB | IESG | IRSG | Other | | Status | | | | | +==========================================================+ | | | | | | | Standard | Bogus | Publish | Bogus | Bogus | | or | (2) | (1) | (2) | (2) | | Draft | | | | | | Standard | | | | | +--------------+----------+----------+----------+----------+ | | | | | | | | Refer | Publish | Refer | Refer | | Proposed | (3) | (1) | (3) | (3) | | Standard | | | | | | | | | | | +--------------+----------+----------+----------+----------+ | | | | | | | | Notify | Publish | Notify | Notify | | Experimental | (4) | (1) | (4) | (4) | | Protocol | | | | | | | | | | | +--------------+----------+----------+----------+----------+ | | | | | | | Information | Publish | Publish |Discretion|Discretion| | or Opinion | (1) | (1) | (5) | (5) | | Paper | | | | | | | | | | | +==========================================================+ (1) Publish. (2) Bogus. Inform the source of the rules. RFCs specifying Standard, or Draft Standard must come from the IESG, only.

Internet Architecture Board Standards Track

[Page 10]


RFC 2300

Internet Standards

May 1998

(3) Refer to an Area Director for review by a WG. Expect to see the document again only after approval by the IESG. (4) Notify both the IESG and IRSG. If no concerns are raised in two weeks then do Discretion (5), else RFC Editor to resolve the concerns or do Refer (3). (5) RFC Editor's discretion. The RFC Editor decides if a review is needed and if so by whom. RFC Editor decides to publish or not. Of course, in all cases the RFC Editor can request or make minor changes for style, format, and presentation purposes. The IESG has designated the IESG Secretary forwarding documents with IESG approval and in response to notifications (4) to the RFC Area Directors or Working Group Chairs may way as documents from "other". 5.2. The Standards Track Diagram as its agent for for registering concerns Editor. Documents from be considered in the same

There is a part of the STATUS and STATE categorization that is called the standards track. Actually, only the changes of state are significant to the progression along the standards track, though the status assignments may change as well. The states illustrated by single line boxes are those illustrated by double line boxes are long protocol will normally be expected to remain in several months (minimum six months for proposed four months for draft standard). A protocol may state for many years. temporary states, term states. A a temporary state for standard, minimum be in a long term

A protocol may enter the standards track only on the of the IESG; and may move from one state to another only on the recommendation of the IESG. That is, it the IESG to either start a protocol on the track or

recommendation along the track takes action by to move it along.

Generally, as the protocol enters the standards track a decision is made as to the eventual STATUS, requirement level or applicability (elective, recommended, or required) the protocol will have, although a somewhat less stringent current status may be assigned, and it then is placed in the the proposed standard STATE with that status. So the initial placement of a protocol is into state 1. At any time the STATUS decision may be revisited.

Internet Architecture Board Standards Track

[Page 11]


RFC 2300

Internet Standards

May 1998

| +<----------------------------------------------+ | ^ V 0 | 4 +-----------+ +===========+ | enter |-->----------------+-------------->|experiment | +-----------+ | +=====+=====+ | | V 1 | +-----------+ V | proposed |-------------->+ +--->+-----+-----+ | | | | | V 2 | +<---+-----+-----+ V | draft std |-------------->+ +--->+-----+-----+ | | | | | V 3 | +<---+=====+=====+ V | standard |-------------->+ +=====+=====+ | | V 5 +=====+=====+ | historic | +===========+ The transition from proposed standard (1) to draft standard (2) can only be by action of the IESG and only after the protocol has been proposed standard (1) for at least six months. The transition from draft standard (2) to standard (3) can only be by action of the IESG and only after the protocol has been draft standard (2) for at least four months. Occasionally, the decision may be that the protocol is not ready for standardization and will be assigned to the experimental state (4). This is off the standards track, and the protocol may be resubmitted to enter the standards track after further work. There are other paths into the experimental and historic states that do not involve IESG action. Sometimes one protocol is replaced by another and thus becomes historic, or it may happen that a protocol on the standards track is in a sense overtaken by another protocol (or other events) and becomes historic (state 5).

Internet Architecture Board Standards Track

[Page 12]


RFC 2300

Internet Standards

May 1998

6.

The Protocols Subsection 6.1 lists recent RFCs and other changes. Subsections 6.2 - 6.10 list the standards in groups by protocol state.

6.1. 6.1.1.

Recent Changes New RFCs: 2352 - A Convention For Using Legal Names as Domain Names This is an information document and does not specify any level of standard. 2351 - Mapping of Airline Reservation, Ticketing, and Messaging Traffic over IP This is an information document and does not specify any level of standard. 2350 - Not yet issued. 2349 - TFTP Timeout Interval and Transfer Size Options A Draft Standard protocol. 2348 - TFTP Blocksize Option A Draft Standard protocol. 2347 - TFTP Option Extension A Draft Standard protocol. 2346 - Making Postscript and PDF International This is an information document and does not specify any level of standard. 2345 - Domain Names and Company Name Retrieval An Experimental protocol. 2344 - Reverse Tunneling for Mobile IP A Proposed Standard protocol.

Internet Architecture Board Standards Track

[Page 13]


RFC 2300

Internet Standards

May 1998

2343 - RTP Payload Format for Bundled MPEG An Experimental protocol. 2342 - IMAP4 Namespace A Proposed Standard protocol. 2341 - Cisco Layer Two Forwarding (Protocol) "L2F" A Historic protocol. 2340 - Not yet issued. 2339 - An Agreement Between the Internet Society, the IETF, and Sun Microsystems, Inc. in the matter of NFS V.4 Protocols This is an information document and does not specify any level of standard. 2338 - Virtual Router Redundancy Protocol A Proposed Standard protocol. 2337 - Intra-LIS IP multicast among routers over ATM using Sparse Mode PIM An Experimental protocol. 2336 - Not yet issued. 2335 - A Distributed NHRP Service Using SCSP A Proposed Standard protocol. 2334 - Server Cache Synchronization Protocol (SCSP) A Proposed Standard protocol. 2333 - NHRP Protocol Applicability Statement A Proposed Standard protocol. 2332 - NBMA Next Hop Resolution Protocol (NHRP) A Proposed Standard protocol.

Internet Architecture Board Standards Track

[Page 14]


RFC 2300

Internet Standards

May 1998

2331 - ATM Signalling Support for IP over ATM - UNI Signalling 4.0 Update A Proposed Standard protocol. 2330 - Framework for IP Performance Metrics This is an information document and does not specify any level of standard. 2329 - OSPF Standardization Report This is an information document and does not specify any level of standard. 2328 - OSPF Version 2 A Standard protocol. 2327 - SDP: Session Description Protocol A Proposed Standard protocol. 2326 - Real Time Streaming Protocol (RTSP) A Proposed Standard protocol. 2325 - Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2 This is an information document and does not specify any level of standard. 2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) This is an information document and does not specify any level of standard. 2323 - IETF Identification and Security Guidelines This is an information document and does not specify any level of standard. 2322 - Management of IP numbers by peg-dhcp This is an information document and does not specify any level of standard.

Internet Architecture Board Standards Track

[Page 15]


RFC 2300

Internet Standards

May 1998

2321 - RITA -- The Reliable Internetwork Troubleshooting Agent This is an information document and does not specify any level of standard. 2320 - Definitions of Managed Objects for Classical IP and ARP Over ATM Using SMIv2 (IPOA-MIB) A Proposed Standard protocol. 2319 - Ukrainian Character Set KOI8-U This is an information document and does not specify any level of standard. 2318 - The text/css Media Type This is an information document and does not specify any level of standard. 2317 - Classless IN-ADDR.ARPA delegation This is a Best Current Practices document and does not specify any level of standard. 2316 - Report of the IAB Security Architecture Workshop This is an information document and does not specify any level of standard. 2315 - PKCS #7: Cryptographic Message Syntax Version 1.5 This is an information document and does not specify any level of standard. 2314 - PKCS #10: Certification Request Syntax Version 1.5 This is an information document and does not specify any level of standard. 2313 - PKCS #1: RSA Encryption Version 1.5 This is an information document and does not specify any level of standard.

Internet Architecture Board Standards Track

[Page 16]


RFC 2300

Internet Standards

May 1998

2312 - S/MIME Version 2 Certificate Handling This is an information document and does not specify any level of standard. 2311 - S/MIME Version 2 Message Specification This is an information document and does not specify any level of standard. 2310 - The Safe Response Header Field An Experimental protocol. 2309 - Recommendations on Queue Management and Congestion Avoidance in the Internet This is an information document and does not specify any level of standard. 2308 - Negative Caching of DNS Queries (DNS NCACHE) A Proposed Standard protocol. 2307 - An Approach for Using LDAP as a Network Information Service An Experimental protocol. 2306 - Tag Image File Format (TIFF) - F Profile for Facsimile This is an information document and does not specify any level of standard. 2305 - A Simple Mode of Facsimile Using Internet Mail A Proposed Standard protocol. 2304 - Minimal FAX address format in Internet Mail A Proposed Standard protocol. 2303 - Minimal PSTN address format in Internet Mail A Proposed Standard protocol.

Internet Architecture Board Standards Track

[Page 17]


RFC 2300

Internet Standards

May 1998

2302 - Tag Image File Format (TIFF) - image/tiff MIME Sub-type Registration A Proposed Standard protocol. 2301 - File Format for Internet Fax A Proposed Standard protocol. 2300 - This memo. 2299 - Not yet issued. 2298 - An Extensible Message Format for Message Disposition Notifications A Proposed Standard protocol. 2297 - Ipsilon's General Switch Management Protocol Specification Version 2.0 This is an information document and does not specify any level of standard. 2296 - HTTP Remote Variant Selection Algorithm -- RVSA/1.0 An Experimental protocol. 2295 - Transparent Content Negotiation in HTTP An Experimental protocol. 2294 - Representing the O/R Address hierarchy in the X.500 Directory Information Tree A Proposed Standard protocol. 2293 - Representing Tables and Subtrees in the X.500 Directory A Proposed Standard protocol. 2292 - Advanced Sockets API for IPv6 This is an information document and does not specify any level of standard.

Internet Architecture Board Standards Track

[Page 18]


RFC 2300

Internet Standards

May 1998

2291 - Requirements for a Distributed Authoring and Versioning Protocol for the World Wide Web This is an information document and does not specify any level of standard. 2290 - Mobile-IPv4 Configuration Option for PPP IPCP A Proposed Standard protocol. 2289 - A One-Time Password System A Draft Standard protocol. 2288 - Using Existing Bibliographic Identifiers as Uniform Resource Names This is an information document and does not specify any level of standard. 2287 - Definitions of System-Level Managed Objects for Applications A Proposed Standard protocol. 2286 - Test Cases for HMAC-RIPEMD160 and HMAC-RIPEMD128 This is an information document and does not specify any level of standard. 2285 - Benchmarking Terminology for LAN Switching Devices This is an information document and does not specify any level of standard. 2284 - PPP Extensible Authentication Protocol (EAP) A Proposed Standard protocol. 2283 - Multiprotocol Extensions for BGP-4 A Proposed Standard protocol. 2282 - IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees This is a Best Current Practices document and does not specify any level of standard.

Internet Architecture Board Standards Track

[Page 19]


RFC 2300

Internet Standards

May 1998

2281 - Cisco Hot Standby Router Protocol (HSRP) This is an information document and does not specify any level of standard. 2280 - Routing Policy Specification Language (RPSL) A Proposed Standard protocol. 2279 - UTF-8, a transformation format of ISO 10646 A Proposed Standard protocol. 2278 - IANA Charset Registration Procedures This is a Best Current Practices document and does not specify any level of standard. 2277 - IETF Policy on Character Sets and Languages This is a Best Current Practices document and does not specify any level of standard. 2276 - Architectural Principles of Uniform Resource Name Resolution This is an information document and does not specify any level of standard. 2275 - View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) A Proposed Standard protocol. 2274 - User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) A Proposed Standard protocol. 2273 - SNMPv3 Applications A Proposed Standard protocol. 2272 - Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) A Proposed Standard protocol.

Internet Architecture Board Standards Track

[Page 20]


RFC 2300

Internet Standards

May 1998

2271 - An Architecture for Describing SNMP Management Frameworks A Proposed Standard protocol. 2270 - Using a Dedicated AS for Sites Homed to a Single Provider This is an information document and does not specify any level of standard. 2269 - Using the MARS Model in non-ATM NBMA Networks This is an information document and does not specify any level of standard. 2268 - A Description of the RC2(r) Encryption Algorithm This is an information document and does not specify any level of standard. 2267 - Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing This is an information document and does not specify any level of standard. 2266 - Definitions of Managed Objects for IEEE 802.12 Repeater Devices A Proposed Standard protocol. 2265 - View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP) A Proposed Standard protocol. 2264 - User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) A Proposed Standard protocol. 2263 - SNMPv3 Applications A Proposed Standard protocol. 2262 - Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) A Proposed Standard protocol.

Internet Architecture Board Standards Track

[Page 21]


RFC 2300

Internet Standards

May 1998

2261 - An Architecture for Describing SNMP Management Frameworks A Proposed Standard protocol. 2260 - Scalable Support for Multi-homed Multi-provider Connectivity This is an information document and does not specify any level of standard. 2259 - Simple Nomenclator Query Protocol (SNQP) This is an information document and does not specify any level of standard. 2258 - Internet Nomenclator Project This is an information document and does not specify any level of standard. 2257 - Agent Extensibility (AgentX) Protocol Version 1 A Proposed Standard protocol. 2256 - A Summary of the X.500(96) User Schema for use with LDAPv3 A Proposed Standard protocol. 2255 - The LDAP URL Format A Proposed Standard protocol. 2254 - The String Representation of LDAP Search Filters A Proposed Standard protocol. 2253 - Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names A Proposed Standard protocol. 2252 - Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions A Proposed Standard protocol.

Internet Architecture Board Standards Track

[Page 22]


RFC 2300

Internet Standards

May 1998

2251 - Lightweight Directory Access Protocol (v3) A Proposed Standard protocol. 2250 - RTP Payload Format for MPEG1/MPEG2 Video A Proposed Standard protocol. 2249 - Mail Monitoring MIB A Proposed Standard protocol. 2248 - Network Services Monitoring MIB A Proposed Standard protocol. 2247 - Using Domains in LDAP/X.500 Distinguished Names A Proposed Standard protocol. 2246 - Not yet issued. 2245 - Anonymous SASL Mechanism A Proposed Standard protocol. 2244 - ACAP -- Application Configuration Access Protocol A Proposed Standard protocol. 2243 - OTP Extended Responses A Proposed Standard protocol. 2242 - NetWare/IP Domain Name and Information A Proposed Standard protocol. 2241 - DHCP Options for Novell Directory Services A Proposed Standard protocol. 2240 - A Legal Basis for Domain Name Allocation This is an information document and does not specify any level of standard.

Internet Architecture Board Standards Track

[Page 23]


RFC 2300

Internet Standards

May 1998

2239 - Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2 A Proposed Standard protocol. 2238 - Definitions of Managed Objects for HPR using SMIv2 A Proposed Standard protocol. 2237 - Japanese Character Encoding for Internet Messages This is an information document and does not specify any level of standard. 2236 - Internet Group Management Protocol, Version 2 A Proposed Standard protocol. 2235 - Hobbes' Internet Timeline This is an information document and does not specify any level of standard. 2234 - Augmented BNF for Syntax Specifications: ABNF A Proposed Standard protocol. 2233 - The Interfaces Group MIB using SMIv2 A Proposed Standard protocol. 2232 - Definitions of Managed Objects for DLUR using SMIv2 A Proposed Standard protocol. 2231 - MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations A Proposed Standard protocol. 2230 - Key Exchange Delegation Record for the DNS This is an information document and does not specify any level of standard.

Internet Architecture Board Standards Track

[Page 24]


RFC 2300

Internet Standards

May 1998

2229 - A Dictionary Server Protocol This is an information document and does not specify any level of standard. 2228 - FTP Security Extensions A Proposed Standard protocol. 2227 - Simple Hit-Metering and Usage-Limiting for HTTP A Proposed Standard protocol. 2226 - IP Broadcast over ATM Networks A Proposed Standard protocol. 2225 - Classical IP and ARP over ATM A Proposed Standard protocol. 2224 - NFS URL Scheme This is an information document and does not specify any level of standard. 2223 - Instructions to RFC Authors This is an information document and does not specify any level of standard. 2222 - Simple Authentication and Security Layer (SASL) A Proposed Standard protocol. 2221 - IMAP4 Login Referrals A Proposed Standard protocol. 2220 - The Application/MARC Content-type This is an information document and does not specify any level of standard. 2219 - Use of DNS Aliases for Network Services This is a Best Current Practices document and does not specify any level of standard.

Internet Architecture Board Standards Track

[Page 25]


RFC 2300

Internet Standards

May 1998

2218 - A Common Schema for the Internet White Pages Service A Proposed Standard protocol. 2217 - Telnet Com Port Control Option An Experimental protocol. 2216 - Network Element Service Specification Template This is an information document and does not specify any level of standard. 2215 - General Characterization Parameters for Integrated Service Network Elements A Proposed Standard protocol. 2214 - Integrated Services Management Information Base Guaranteed Service Extensions using SMIv2 A Proposed Standard protocol. 2213 - Integrated Services Management Information Base using SMIv2 A Proposed Standard protocol. 2212 - Specification of Guaranteed Quality of Service A Proposed Standard protocol. 2211 - Specification of the Controlled-Load Network Element Service A Proposed Standard protocol. 2210 - The Use of RSVP with IETF Integrated Services A Proposed Standard protocol. 2209 - Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing Rules A Proposed Standard protocol.

Internet Architecture Board Standards Track

[Page 26]


RFC 2300

Internet Standards

May 1998

2208 - Resource ReSerVation Protocol (RSVP) -- Version 1 Applicability Statement Some Guidelines on Deployment A Proposed Standard protocol. 2207 - RSVP Extensions for IPSEC Data Flows A Proposed Standard protocol. 2206 - RSVP Management Information Base using SMIv2 A Proposed Standard protocol. 2205 - Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification A Proposed Standard protocol. 2204 - ODETTE File Transfer Protocol This is an information document and does not specify any level of standard. 2203 - RPCSEC_GSS Protocol Specification A Proposed Standard protocol. 2202 - Test Cases for HMAC-MD5 and HMAC-SHA-1 This is an information document and does not specify any level of standard. 2201 - Core Based Trees (CBT) Multicast Routing Architecture An Experimental protocol. 2200 - Internet Official Protocol Standards A Standard protocol. 2199 - Request for Comments Summary - RFC Numbers 2100-2199 This is an information document and does not specify any level of standard. 2198 - RTP Payload for Redundant Audio Data A Proposed Standard protocol.

Internet Architecture Board Standards Track

[Page 27]


RFC 2300

Internet Standards

May 1998

2197 - SMTP Service Extension for Command Pipelining A Draft Standard protocol. 2196 - Site Security Handbook This is an information document and does not specify any level of standard. 2195 - IMAP/POP AUTHorize Extension for Simple Challenge/Response A Proposed Standard protocol. 2194 - Review of Roaming Implementations This is an information document and does not specify any level of standard. 2193 - IMAP4 Mailbox Referrals A Proposed Standard protocol. 2192 - IMAP URL Scheme A Proposed Standard protocol. 2191 - VENUS - Very Extensive Non-Unicast Service This is an information document and does not specify any level of standard. 2190 - RTP Payload Format for H.263 Video Streams A Proposed Standard protocol. 2189 - Core Based Trees (CBT version 2) Multicast Routing An Experimental protocol. 2188 - AT&T/Neda's Efficient Short Remote Operations (ESRO) Protocol Specification Version 1. This is an information document and does not specify any level of standard.

Internet Architecture Board Standards Track

[Page 28]


RFC 2300

Internet Standards

May 1998

2187 - Application of Internet Cache Protocol (ICP), version 2 This is an information document and does not specify any level of standard. 2186 - Internet Cache Protocol (ICP), version 2 This is an information document and does not specify any level of standard. 2185 - Routing Aspects of IPv6 Transition This is an information document and does not specify any level of standard. 2184 - MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations A Proposed Standard protocol. 2183 - Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field A Proposed Standard protocol. 2182 - Selection and Operation of Secondary DNS Servers This is a Best Current Practices document and does not specify any level of standard. 2181 - Clarifications to the DNS Specification A Proposed Standard protocol. 2180 - IMAP4 Multi-Accessed Mailbox Practice This is an information document and does not specify any level of standard. 2179 - Network Security For Trade Shows This is an information document and does not specify any level of standard. 2178 - OSPF Version 2 A Draft Standard protocol.

Internet Architecture Board Standards Track

[Page 29]


RFC 2300

Internet Standards

May 1998

2177 - IMAP4 IDLE command A Proposed Standard protocol. 2176 - IPv4 over MAPOS Version 1 This is an information document and does not specify any level of standard. 2175 - MAPOS 16 - Multiple Access Protocol over SONET/SDH with 16 Bit Addressing This is an information document and does not specify any level of standard. 2174 - A MAPOS version 1 Extension - Switch-Switch Protocol This is an information document and does not specify any level of standard. 2173 - A MAPOS version 1 Extension - Node Switch Protocol This is an information document and does not specify any level of standard. 2172 - MAPOS Version 1 Assigned Numbers This is an information document and does not specify any level of standard. 2171 - MAPOS - Multiple Access Protocol over SONET/SDH Version 1 This is an information document and does not specify any level of standard. 2170 - Application REQuested IP over ATM (AREQUIPA) This is an information document and does not specify any level of standard. 2169 - A Trivial Convention for using HTTP in URN Resolution An Experimental protocol. 2168 - Resolution of Uniform Resource Identifiers using the Domain Name System An Experimental protocol.

Internet Architecture Board Standards Track

[Page 30]


RFC 2300

Internet Standards

May 1998

2167 - Referral Whois (RWhois) Protocol V1.5 This is an information document and does not specify any level of standard. 2166 - APPN Implementer's Workshop Closed Pages Document DLSw v2.0 Enhancements This is an information document and does not specify any level of standard. 2165 - Service Location Protocol A Proposed Standard protocol. 2164 - Use of an X.500/LDAP directory to support MIXER address mapping A Proposed Standard protocol. 2163 - Using the Internet DNS to Distribute MIXER Conformant Global Address Mapping (MCGAM) A Proposed Standard protocol. 2162 - MaXIM-11 - Mapping between X.400 / Internet mail and Mail-11 mail An Experimental protocol. 2161 - A MIME Body Part for ODA An Experimental protocol. 2160 - Carrying PostScript in X.400 and MIME A Proposed Standard protocol. 2159 - A MIME Body Part for FAX A Proposed Standard protocol. 2158 - X.400 Image Body Parts A Proposed Standard protocol.

Internet Architecture Board Standards Track

[Page 31]


RFC 2300

Internet Standards

May 1998

2157 - Mapping between X.400 and RFC-822/MIME Message Bodies A Proposed Standard protocol. 2156 - MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME A Proposed Standard protocol. 2155 - Definitions of Managed Objects for APPN using SMIv2 A Proposed Standard protocol. 2154 - OSPF with Digital Signature An Experimental protocol. 2151 - A Primer On Internet and TCP/IP Tools and Utilities This is an information document and does not specify any level of standard. 2150 - Humanities and Arts: Sharing Center Stage on the Internet This is an information document and does not specify any level of standard. 2148 - Deployment of the Internet White Pages Service This is a Best Current Practices document and does not specify any level of standard. 2115 - Management Information Base for Frame Relay DTEs Using SMIv2 A Draft Standard protocol. 2094 - Group Key Management Protocol (GKMP) Architecture An Experimental protocol. 2093 - Group Key Management Protocol (GKMP) Specification An Experimental protocol.

Internet Architecture Board Standards Track

[Page 32]


RFC 2300

Internet Standards

May 1998

6.1.2.

Other Changes:

The following are changes to protocols listed in the previous edition. 2349 - TFTP Timeout Interval and Transfer Size Options Elevated to Draft Standard. 2348 - TFTP Blocksize Option Elevated to Draft Standard. 2347 - TFTP Option Extension Elevated to Draft Standard. 2328 - OSPF Version 2 Elevated to Standard. 2289 - A One-Time Password System Elevated to Draft Standard. 2197 - SMTP Service Extension for Command Pipelining Elevated to Draft Standard. 2115 - Management Information Base for Frame Relay DTEs Using SMIv2 Elevated to Draft Standard.

Internet Architecture Board Standards Track

[Page 33]


RFC 2300

Internet Standards

May 1998

6.2.

Standard Protocols Status ======== Req Req Req Req Req RFC STD * ==== === = 2300 1 1700 2 1122 3 1123 3 791 5 5 5 5 5 5 6 7 8 9 10 10 10 11 11 12 13 14 15 16 16 17 19 20 21 22 23 24 25 26 33 35 50 51 51 52 53 54 *

Protocol ======== ----------------------------IP

Name ===================================== Internet Official Protocol Standards Assigned Numbers Host Requirements - Communications Host Requirements - Applications Internet Protocol as amended by:--------------IP Subnet Extension -------IP Broadcast Datagrams -------IP Broadcast Datagrams with Subnets ICMP Internet Control Message Protocol IGMP Internet Group Multicast Protocol UDP User Datagram Protocol TCP Transmission Control Protocol TELNET Telnet Protocol FTP File Transfer Protocol SMTP Simple Mail Transfer Protocol SMTP-SIZE SMTP Service Ext for Message Size SMTP-EXT SMTP Service Extensions MAIL Format of Electronic Mail Messages CONTENT Content Type Header Field NTPV2 Network Time Protocol (Version 2) DOMAIN Domain Name System DNS-MX Mail Routing and the Domain System SNMP Simple Network Management Protocol SMI Structure of Management Information Concise-MIB Concise MIB Definitions MIB-II Management Information Base-II NETBIOS NetBIOS Service Protocols ECHO Echo Protocol DISCARD Discard Protocol CHARGEN Character Generator Protocol QUOTE Quote of the Day Protocol USERS Active Users Protocol DAYTIME Daytime Protocol TIME Time Server Protocol TFTP Trivial File Transfer Protocol TP-TCP ISO Transport Service on top of the TCP ETHER-MIB Ethernet MIB PPP Point-to-Point Protocol (PPP) PPP-HDLC PPP in HDLC Framing IP-SMDS IP Datagrams over the SMDS Service POP3 Post Office Protocol, Version 3 OSPF2 Open Shortest Path First Routing V2

Req 950 Req 919 Req 922 Req 792 Rec 1112 Rec 768 Rec 793 Rec 854,855 Rec 959 Rec 821 Rec 1870 Rec 1869 Rec 822 Rec 1049 Rec 1119 Rec 1034,1035 Rec 974 Rec 1157 Rec 1155 Rec 1212 Rec 1213 Ele 1001,1002 Rec 862 Ele 863 Ele 864 Ele 865 Ele 866 Ele 867 Ele 868 Ele 1350 Ele 1006 Ele 1643 Ele 1661 Ele 1662 Ele 1209 Ele 1939 Ele 2328

Internet Architecture Board Standards Track

[Page 34]


RFC 2300

Internet Standards

May 1998

[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] Applicability Statements: IGMP -- The Internet Architecture Board intends to move towards general adoption of IP multicasting, as a more efficient solution than broadcasting for many applications. The host interface has been standardized in RFC-1112; however, multicast-routing gateways are in the experimental stage and are not widely available. An Internet host should support all of RFC-1112, except for the IGMP protocol itself which is optional; see RFC-1122 for more details. Even without IGMP, implementation of RFC-1112 will provide an important advance: IP-layer access to local network multicast addressing. It is expected that IGMP will become recommended for all hosts and gateways at some future date. SMI, MIB-II SNMP -- The Internet Architecture Board recommends that all IP and TCP implementations be network manageable. At the current time, this implies implementation of the Internet MIB-II (RFC-1213), and at least the recommended management protocol SNMP (RFC-1157). RIP -- The Routing Information Protocol (RIP) is widely implemented and used in the Internet. However, both implementors and users should be aware that RIP has some serious technical limitations as a routing protocol. The IETF is currently devpeloping several candidates for a new standard "open" routing protocol with better properties than RIP. The IAB urges the Internet community to track these developments, and to implement the new protocol when it is standardized; improved Internet service will result for many users. TP-TCP -- As OSI protocols become more widely implemented and used, there will be an increasing need to support interoperation with the TCP/IP protocols. The Internet Engineering Task Force is formulating strategies for interoperation. RFC-1006 provides one interoperation mode, in which TCP/IP is used to emulate TP0 in order to support OSI applications. Hosts that wish to run OSI connection-oriented applications in this mode should use the procedure described in RFC1006. In the future, the IAB expects that a major portion of the Internet will support both TCP/IP and OSI (inter-)network protocols in parallel, and it will then be possible to run OSI applications across the Internet using full OSI protocol "stacks". OSPF -- RFC 1370 is an applicability statement for OSPF.

Internet Architecture Board Standards Track

[Page 35]


RFC 2300

Internet Standards

May 1998

6.3.

Network-Specific Standard Protocols

All Network-Specific Standards have Elective status. Protocol ======== IP-ATM IP-FR ATM-ENCAP IP-TR-MC IP-FDDI IP-X.25 ARP RARP IP-ARPA IP-WB IP-E IP-EE IP-IEEE IP-DC IP-HC IP-ARC IP-SLIP IP-NETBIOS IP-IPX IP-HIPPI Name ===================================== Classical IP and ARP over ATM Multiprotocol over Frame Relay Multiprotocol Encapsulation over ATM IP Multicast over Token-Ring LANs Transmission of IP and ARP over FDDI Net X.25 and ISDN in the Packet Mode Address Resolution Protocol A Reverse Address Resolution Protocol Internet Protocol on ARPANET Internet Protocol on Wideband Network Internet Protocol on Ethernet Networks Internet Protocol on Exp. Ethernet Nets Internet Protocol on IEEE 802 Internet Protocol on DC Networks Internet Protocol on Hyperchannel Transmitting IP Traffic over ARCNET Nets Transmission of IP over Serial Lines Transmission of IP over NETBIOS Transmission of 802.2 over IPX Networks IP over HIPPI State RFC ===== ===== Prop 2225 Draft 1490 Prop 1483 Prop 1469 Std 1390 Draft 1356 Std 826 Std 903 Std BBN1822 Std 907 Std 894 Std 895 Std 1042 Std 891 Std 1044 Std 1201 Std 1055 Std 1088 Std 1132 Draft 2067 STD * === = *

36 37 38 39 40 41 42 43 44 45 46 47 48 49

[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] Applicability Statements: It is expected that a system will support one or more physical networks and for each physical network supported the appropriate protocols from the above list must be supported. That is, it is elective to support any particular type of physical network, and for the physical networks actually supported it is required that they be supported exactly according to the protocols in the above list. See also the Host and Gateway Requirements RFCs for more specific information on network-specific ("link layer") protocols.

Internet Architecture Board Standards Track

[Page 36]


RFC 2300

Internet Standards

May 1998

6.4.

Draft Standard Protocols Name Status RFC ===================================== ============== ===== TFTP Options Elective 2349* TFTP Blocksize Option Elective 2348* TFTP Option Extension Elective 2347* One-Time Password System Elective 2289* SMTP Serv. Ext. for Command Pipelining Elective 2197* DHCP Options and BOOTP Extensions Recommended 2132 Dynamic Host Configuration Protocol Elective 2131 Management Information Base for Frame Elective 2115* Clarifications and Extensions BOOTP Elective 1542 Interoperation Between DHCP and BOOTP Elective 1534 Bootstrap Protocol Recommended 951,1497 MIME Conformance Criteria Elective 2049 MIME Msg Header Ext for Non-ASCII Elective 2047 MIME Media Types Elective 2046 Multipurpose Internet Mail Extensions Elective 2045 PPP Challenge Handshake Authentication Elective 1994 PPP Multilink Protocol Elective 1990 PPP Link Quality Monitoring Elective 1989 Coexistence between SNMPV1 & SNMPV2 Elective 1908 MIB for SNMPv2 Elective 1907 Transport Mappings for SNMPv2 Elective 1906 Protocol Operations for SNMPv2 Elective 1905 Conformance Statements for SNMPv2 Elective 1904 Textual Conventions for SNMPv2 Elective 1903 SMI for SNMPv2 Elective 1902 Content-MD5 Header Field Elective 1864 OSPF Version 2 MIB Elective 1850 String Representation ... Elective 1779 X.500 String Representation ... Elective 1778 X.500 Lightweight ... Elective 1777 Application of BGP-4 Elective 1772 Border Gateway Protocol 4 Elective 1771 PPP DECnet Phase IV Control Protocol Elective 1762 Remote Network Monitoring MIB Elective 1757 IEEE 802.5 Token Ring MIB Elective 1748 RIP Version 2 MIB Extension Elective 1724 RIP Version 2-Carrying Additional Info. Elective 1723 RIP Version 2 Protocol App. Statement Elective 1722 SIP Interface Type MIB Elective 1694 Def Man Objs Parallel-printer-like Elective 1660 Def Man Objs RS-232-like Elective 1659 Def Man Objs Character Stream Elective 1658 BGP-4 MIB Elective 1657 SMTP Service Ext or 8bit-MIMEtransport Elective 1652

Protocol ======== TFTP-Opt TFTP-Blk TFTP-Ext ONE-PASS SMTP-Pipe BOOTP DHCP FRAME-MIB ------DHCP-BOOTP BOOTP MIME-CONF MIME-MSG MIME-MEDIA MIME PPP-CHAP PPP-MP PPP-LINK COEX-MIB SNMPv2-MIB TRANS-MIB OPS-MIB CONF-MIB CONV-MIB SMIV2 CON-MD5 OSPF-MIB STR-REP X.500syn X.500lite BGP-4-APP BGP-4 PPP-DNCP RMON-MIB 802.5-MIB RIP2-MIB RIP2 RIP2-APP SIP-MIB ------------------BGP-4-MIB SMTP-8BIT

Internet Architecture Board Standards Track

[Page 37]


RFC 2300

Internet Standards

May 1998

OSI-NSAP ISO-TS-ECHO DECNET-MIB BRIDGE-MIB NTPV3 IP-MTU FINGER NICNAME

Guidelines for OSI NSAP Allocation Echo for ISO-8473 DECNET MIB BRIDGE-MIB Network Time Protocol (Version 3) Path MTU Discovery Finger Protocol WhoIs Protocol

Elective Elective Elective Elective Elective Elective Elective Elective

1629 1575 1559 1493 1305 1191 1288 954

[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] Applicability Statements: PPP -- Point to Point Protocol is a method of sending IP over serial lines, which are a type of physical network. It is anticipated that PPP will be advanced to the network-specifics standard protocol state in the future.

Internet Architecture Board Standards Track

[Page 38]


RFC 2300

Internet Standards

May 1998

6.5.

Proposed Standard Protocols Name ===================================== Reverse Tunneling for Mobile IP IMAP4 Namespace Virtual Router Redundancy Protocol Distributed NHRP Service Using SCSP Server Cache Synchronization Protocol NHRP Protocol Applicability Statement NBMA Next Hop Resolution Protocol ATM Sig Support (IPOA) UNI Signalling Session Description Protocol Real Time Streaming Protocol Classical IP and ARP Over ATM MIB Negative Caching of DNS Queries Simple Mode of FAX Using Internet Mail Minimal FAX addr format in Internet Mail Min. PSTN addr format in Internet Mail Tag Image File Format File Format for Internet Fax Extensible Message Format for MDN O/R Address hierarchy in X.500 Tables and Subtrees in X.500 Mobile-IPv4 Config Opt for PPP IPCP System-Level Managed Objects for Apps PPP Extensible Authentication Protocol Multiprotocol Extensions for BGP-4 Routing Policy Specification Language UTF-8 transformation format of ISO 10646 View-based Access Control Model for SMMP User-based Security Model for SNMPv3 SNMPv3 Applications Message Processing & Dispatching SNMP Architecture Describing SNMP Frameworks IEEE 802.12 Repeater MIB Agent Extensibility Protocol Summary of the X.500(96) with LDAPv3 LDAP URL Format String Rep of LDAP Search Filters LDAPv3: UTF-8 String Rep LDAP3-: Attribute Syntax Definitions Lightweight Directory Access Protocol RTP Payload Format for MPEG1/MPEG2 Mail Monitoring MIB Network Services Monitoring MIB Using Domains LDAP/X.500 Dist. Names Anonymous SASL Mechanism Status ============== Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective RFC ===== 2344* 2342* 2338* 2335* 2334* 2333* 2332* 2331* 2327* 2326* 2320* 2308* 2305* 2304* 2303* 2302* 2301* 2298* 2294* 2293* 2290* 2287* 2284* 2283* 2280* 2279* 2275* 2274* 2273* 2272* 2271* 2266* 2257* 2256* 2255* 2254* 2253* 2252* 2251* 2250* 2249* 2248* 2247* 2245*

Protocol ======== MOBILIPREV IMAP4NAME VRRP NHRP-SCSP SCSP NHRP-APP NHRP UNI-SIG SDP RTSP IPOA-MIB DNS-NCACHE SMFAX-IM MINFAX-IM MIN-PSTN TIFF FFIF EMF-MDN OR-ADD SUBTABLE -------SLM-APP PPP-EAP MEXT-BGP4 RPSL UTF-8 VACM-SNMP USM-SNMPV3 SNMPV3-APP MPD-SNMP ARCH-SNMP -------AGENTX -------LDAP-URL STR-LDAP LDAP3-UTF8 LDAP3-ATD LDAPV3 RTP-MPEG MAIL-MIB NSM-MIB -------SASL-ANON

Internet Architecture Board Standards Track

[Page 39]


RFC 2300

Internet Standards

May 1998

ACAP OTP-ER NETWAREIP DHCP-NDS MAUS-MIB HPR-MIB IGMP ABNF INTERGRMIB DLUR-MIB MIME-EXT FTPSECEXT ----------------AAL5-MTU SASL IMAP4LOGIN --------------------------------GQOS --------RSVP-IS RSVP-MPR RSVP-APP RSVP-IPSEC RSVP-MIB RSVP RPCSEC-GSS RTP-RAD IMAPPOPAU IMAP4MAIL IMAP-URL --------MIME-EXT --------DNS-CLAR IMAP4-IDLE SLP --------DNS-MCGAM --------------------------------MIXER APPN-MIB

Application Configuration Access OTP Extended Responses NetWare/IP Domain Name and Information DHCP Options for Novell Directory Serv. IEEE 802.3 Medium Attachment Units MIB Definitions of Managed Objects for HPR Internet Group Management Protocol V2 Augmented BNF for Syntax Specifications Interfaces Group MIB Definitions of Managed Objects for DLUR MIME Parameter Value & Encoded Word Ext FTP Security Extensions Simple Hit-Metering, Usage-Limiting HTTP IP Broadcast over ATM Networks Default IP MTU for use over ATM AAL5 Simple Authentication and Security Layer IMAP4 Login Referrals Schema for Internet White Pages Service Characterization Parameters for ISNE Integrated Services MIB Guar Serv Ext Integrated Services MIB using SMIv2 Spec. of Guaranteed Quality of Service Spec. of Controlled-Load Net Ele Serv Use of RSVP with IETF Integrated Serv RSVP Messaging Processing Rules RSVP Applicability Statement RSVP Extensions for IPSEC Data Flows RSVP Management Information Base Resource ReSerVation Protocol V1 RPCSEC_GSS Protocol Specification RTP Payload for Redundant Audio Data IMAP/POP AUTHorize Extension IMAP4 Mailbox Referrals IMAP URL Scheme RTP Payload Format for H.263 Video ST MIME Parameter Value & Encoded Word Ext The Content-Disposition Header Field Clarifications to the DNS Specification IMAP4 IDLE command Service Location Protocol X.500/LDAP Directory/MIXER Address Map. Using DNS to Distribute MCGAM Carrying PostScript in X.400 and MIME A MIME Body Part for FAX X.400 Image Body Parts Mapping between X.400 and RFC-822/MIME Mime Internet X.400 Enhanced Relay Definitions of Managed Objects for APPN

Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective

2244* 2243* 2242* 2241* 2239* 2238* 2236* 2234* 2233* 2232* 2231* 2228* 2227* 2226* 2225* 2222* 2221* 2218* 2215* 2214* 2213* 2212* 2211* 2210* 2209* 2208* 2207* 2206* 2205* 2203* 2198* 2195* 2193* 2192* 2190* 2184* 2183* 2181* 2177* 2165* 2164* 2163* 2160* 2159* 2158* 2157* 2156* 2155*

Internet Architecture Board Standards Track

[Page 40]


RFC 2300

Internet Standards

May 1998

IPv6-Jumbo MAIL-SERV URN-SYNTAX RADIUS SDNSDU DNS-UPDATE DC-MIB ISDN-MIB ITOT BAP-BACP VEMMI-URL ROUT-ALERT MIME-RELAT CIDMID-URL MHTML HTTP-STATE 802.3-MIB PPP-NBFCP TABLE-MIB RIP-TRIG IMAP4-LIT IMAP4-QUO IMAP4-ACL HMAC-MD5 RIP2-MD5 RIPNG-IPV6 URI-ATT GSSAP MIME-MODEL RMON-MIB IPV6-UNI HTML-INT DAA HTTP-1.1 DNS-SEC IMAPV4 URLZ39.50 SNANAU-APP PPP-SNACP ENTITY-MIB RTP-JPEG SMTP-ENH RTP-H.261 RTP-CELLB SPKM DLSW-MIB IPV6-PPP MULTI-UNI

TCP and UDP over IPv6 Jumbograms Mailbox Names for Common Services URN Syntax Remote Authentication Dial In Service Secure Domain Name System Dynamic Update Dynamic Updates in the DNS Dial Control MIB using SMIv2 ISDN MIB using SMIv2 ISO Transport Service on top of TCP PPP-BAP, PPP-BACP VEMMI URL Specification IP Router Alert Option MIME Multipart/Related Content-type Content-ID and Message-ID URLs MIME E-mail Encapsulation HTTP State Management Mechanism 802.3 Repeater MIB using SMIv2 PPP NetBIOS Frames Control Protocol IP Forwarding Table MIB Trigger RIP IMAP4 non-synchronizing literals IMAP4 QUOTA extension IMAP4 ACL Extension HMAC-MD5 IP Auth. with Replay Prevention RIP-2 MD5 Authentication RIPng for IPv6 URI Attribute Type and Object Class Generic Security Service Application Model Primary MIME Types Remote Network Monitoring MIB IPv6 Provider-Based Unicast Address HTML Internationalization Digest Access Authentication Hypertext Transfer Protocol -- HTTP/1.1 Domain Name System Security Extensions Internet Message Access Protocol v4rev1 Uniform Resource Locators for Z39.50 SNANAU APPC MIB using SMIv2 PPP SNA Control Protocol Entity MIB using SMIv2 RTP Payload Format for JPEG-compressed SMTP Enhanced Error Codes RTP Payload Format for H.261 RTP Payload Format of Sun's CellB Simple Public-Key GSS-API Mechanism DLSw MIB using SMIv2 IP Version 6 over PPP Multicast over UNI 3.0/3.1 based ATM

Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective

2147 2142 2141 2138 2137 2136 2128 2127 2126 2125 2122 2113 2112 2111 2110 2109 2108 2097 2096 2091 2088 2087 2086 2085 2082 2080 2079 2078 2077 2074 2073 2070 2069 2068 2065 2060 2056 2051 2043 2037 2035 2034 2032 2029 2025 2024 2023 2022

Internet Architecture Board Standards Track

[Page 41]


RFC 2300

Internet Standards

May 1998

RMON-MIB RMON MIB using SMIv2 802.12-MIB IEEE 802.12 Interface MIB IPV6-FDDI Transmission of IPv6 Packets Over FDDI TCP-ACK TCP Selective Acknowledgement Options URL-ACC URL Access-Type MIME-PGP MIME Security with PGP MIB-UDP SNMPv2 MIB for UDP MIB-TCP SNMPv2 MIB for TCP MIB-IP SNMPv2 MIB for IP MOBILEIPMIBMobile IP MIB Definition using SMIv2 MOBILEIPAPPApplicability Statement for IP Mobility MINI-IP Minimal Encapsulation within IP IPENCAPIP IP Encapsulation within IP MOBILEIPSUPIP Mobility Support TCPSLOWSRT TCP Slow Start, Congestion Avoidance... BGP-COMM BGP Communities Attribute DNS-NOTIFY Mech. for Notification of Zone Changes DNS-IZT Incremental Zone Transfer in DNS SMTP-ETRN SMTP Service Extension ETRN SNA Serial Number Arithmetic MTU-IPV6 Path MTU Discovery for IP version 6 PPP-FRAME PPP in Frame Relay IPV6-ETHER Transmission IPv6 Packets Over Ethernet IPV6-AUTO IPv6 Stateless Address Autoconfiguation IPV6-ND Neighbor Discovery for IP Version 6 PPP-ECP PPP Encryption Control Protocol GSSAPI-KER Kerberos Version 5 GSS-API Mechanism PPP-CCP PPP Compression Control Protocol GSSAPI-SOC GSS-API Auth for SOCKS Version 5 LDAP-STR String Rep. of LDAP Search Filters LDAP-URL LDAP URL Format TRANS-IPV6 Transition Mechanisms IPv6 Hosts/Routers AUTH-SOCKS Username Authentication for SOCKS V5 SOCKSV5 SOCKS Protocol Version 5 WHOIS++M How to Interact with a Whois++ Mesh WHOIS++A Architecture of Whois++ Index Service DSN Delivery Status Notifications EMS-CODE Enhanced Mail System Status Codes MIME-RPT Multipart/Report SMTP-DSN SMTP Delivery Status Notifications RTP-AV RTP Audio/Video Profile RTP Transport Protocol for Real-Time Apps DNS-IPV6 DNS Extensions to support IPv6 ICMPv6 ICMPv6 for IPv6 IPV6-Addr IPv6 Addressing Architecture IPV6 IPv6 Specification HTML Hypertext Markup Language - 2.0 MIME-Sec MIME Object Security Services

Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective

2021 2020 2019 2018 2017 2015 2013 2012 2011 2006 2005 2004 2003 2002 2001 1997 1996 1995 1985 1982 1981 1973 1972 1971 1970 1968 1964 1962 1961 1960 1959 1933 1929 1928 1914 1913 1894 1893 1892 1891 1890 1889 1886 1885 1884 1883 1866 1848

Internet Architecture Board Standards Track

[Page 42]


RFC 2300

Internet Standards

May 1998

MIME-Encyp WHOIS++ -------XDR RPC --------------ESP IPV6-AH -------RREQ URL CLDAP OSPF-DC OSI-Dir MIME-EDI Lang-Tag XNSCP BVCP Print-MIB ATM-SIG IPNG 802.5-SSR SDLCSMIv2 BGP4/IDRP AT-MIB MacMIME URL POP3-AUTH IMAP4-AUTH RDBMS-MIB MODEM-MIB ATM-MIB TMUX SNANAU-MIB PPP-TRANS --------------TN3270-En PPP-BCP UPS-MIB PPP-SONET PPP-ISDN DNS-R-MIB DNS-S-MIB FR-MIB PPP-X25 OSPF-NSSA

MIME: Signed and Encrypted Architecture of the WHOIS++ service Binding Protocols for ONC RPC Version 2 External Data Representation Standard Remote Procedure Call Protocol V. 2 ESP DES-CBC Transform IP Authentication using Keyed MD5 IP Encapsulating Security Payload IP Authentication Header Security Architecture for IP Requirements for IP Version 4 Routers Relative Uniform Resource Locators Connection-less LDAP Ext. OSPF to Support Demand Circuits OSI User Friendly Naming ... MIME Encapsulation of EDI Objects Tags for Identification of Languages PPP XNS IDP Control Protocol PPP Banyan Vines Control Protocol Printer MIB ATM Signaling Support for IP over ATM Recommendation for IP Next Generation 802.5 SSR MIB using SMIv2 SNADLC SDLC MIB using SMIv2 BGP4/IDRP for IP/OSPF Interaction Appletalk MIB MIME Encapsulation of Macintosh files Uniform Resource Locators POP3 AUTHentication command IMAP4 Authentication Mechanisms RDMS MIB - using SMIv2 Modem MIB - using SMIv2 ATM Management Version 8.0 using SMIv2 Transport Multiplexing Protocol SNA NAUs MIB using SMIv2 PPP Reliable Transmission Ethernet-like Interface Types MIB Postmaster Convention X.400 Operations TN3270 Enhancements PPP Bridging Control Protocol UPS Management Information Base PPP over SONET/SDH PPP over ISDN DNS Resolver MIB Extensions DNS Server MIB Extensions Frame Relay Service MIB PPP in X.25 The OSPF NSSA Option

Elective Elective Elective Elective Elective Ele/Req Ele/Req Ele/Req Ele/Req Ele/Req Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective

1847 1835 1833 1832 1831 1829 1828 1827 1826 1825 1812 1808 1798 1793 1781 1767 1766 1764 1763 1759 1755 1752 1749 1747 1745 1742 1740 1738 1734 1731 1697 1696 1695 1692 1666 1663 1650 1648 1647 1638 1628 1619 1618 1612 1611 1604 1598 1587

Internet Architecture Board Standards Track

[Page 43]


RFC 2300

Internet Standards

May 1998

OSPF-Multi SONET-MIB RIP-DC -------PPP-LCP X500-MIB CIPX IPXCP SRB-MIB CIDR-STRA CIDR-ARCH CIDR-APP -------HOST-MIB -------FDDI-MIB KERBEROS GSSAPI DASS -------HARPOON Equiv IDPR IDPR-ARCH PPP/Bridge PPP/IP MIB PPP/SEC MIB PPP/LCP MIB X25-MIB SNMPv2 PEM-KEY PEM-ALG PEM-CKM PEM-ENC SNMP-IPX SNMP-AT SNMP-OSI FTP-FTAM IDENT-MIB IDENT DS3/E3-MIB DS1/E1-MIB BGP-OSPF -------SNMP-X.25 SNMP-LAPB PPP-ATCP PPP-OSINLCP

Multicast Extensions to OSPF Elective MIB SONET/SDH Interface Type Elective Extensions to RIP to Support Demand Cir. Elective Evolution of the Interfaces Group of MIB-II Elective PPP LCP Extensions Elective X.500 Directory Monitoring MIB Elective Compressing IPX Headers Over WAM Media Elective PPP Internetworking Packet Exchange Control Elective Source Routing Bridge MIB Elective CIDR Address Assignment... Elective CIDR Architecture... Elective CIDR Applicability Statement Elective 802.3 MAU MIB Elective Host Resources MIB Elective Token Ring Extensions to RMON MIB Elective FDDI Management Information Base Elective Kerberos Network Authentication Ser (V5) Elective Generic Security Service API: C-bindings Elective Distributed Authentication Security... Elective X.400 Use of Extended Character Sets Elective Rules for Downgrading Messages... Elective X.400/MIME Body Equivalences Elective Inter-Domain Policy Routing Protocol Elective Architecture for IDPR Elective MIB Bridge PPP MIB Elective IP Network Control Protocol of PPP MIB Elective Security Protocols of PPP MIB Elective Link Control Protocol of PPP MIB Elective Multiprotocol Interconnect on X.25 MIB Elective Introduction to SNMPv2 Elective PEM - Key Certification Elective PEM - Algorithms, Modes, and Identifiers Elective PEM - Certificate-Based Key Management Elective PEM - Message Encryption and Auth Elective SNMP over IPX Elective SNMP over AppleTalk Elective SNMP over OSI Elective FTP-FTAM Gateway Specification Elective Identification MIB Elective Identification Protocol Elective DS3/E3 Interface Type Elective DS1/E1 Interface Type Elective BGP OSPF Interaction Elective Route Advertisement In BGP2 And BGP3 Elective SNMP MIB Extension for X.25 Packet Layer Elective SNMP MIB Extension for X.25 LAPB Elective PPP AppleTalk Control Protocol Elective PPP OSI Network Layer Control Protocol Elective

1584 1595 1582 1573 1570 1567 1553 1552 1525 1519 1518 1517 1515 1514 1513 1512 1510 1509 1507 1502 1496 1494 1479 1478 1474 1473 1472 1471 1461 1441 1424 1423 1422 1421 1420 1419 1418 1415 1414 1413 1407 1406 1403 1397 1382 1381 1378 1377

Internet Architecture Board Standards Track

[Page 44]


RFC 2300

Internet Standards

May 1998

SNMP-PARTY-MIB Administration of SNMP SNMP-SEC SNMP Security Protocols SNMP-ADMIN SNMP Administrative Model TOS Type of Service in the Internet PPP-IPCP PPP Control Protocol ------X.400 1988 to 1984 downgrading TCP-EXT TCP Extensions for High Performance NETFAX File Format for the Exchange of Images IARP Inverse Address Resolution Protocol FDDI-MIB FDDI-MIB ------Encoding Network Addresses ------Replication and Distributed Operations ------COSINE and Internet X.500 Schema BGP-MIB Border Gateway Protocol MIB (Version 3) ICMP-ROUT ICMP Router Discovery Messages OSI-UDP OSI TS on UDP STD-MIBs Reassignment of Exp MIBs to Std MIBs IPX-IP Tunneling IPX Traffic through IP Nets IS-IS OSI IS-IS for TCP/IP Dual Environments IP-CMPRS Compressing TCP/IP Headers NNTP Network News Transfer Protocol

Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective Elective

1353 1352 1351 1349 1332 1328 1323 1314 1293 1285 1277 1276 1274 1269 1256 1240 1239 1234 1195 1144 977

[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] [Note: Ele/Req indicates elective for use with IPv4 and required for use with IPv6.] Applicability Statements:

Internet Architecture Board Standards Track

[Page 45]


RFC 2300

Internet Standards

May 1998

6.6.

Telnet Options

For convenience, all the Telnet Options are collected here with both their state and status. Protocol Name Number ======== ===================================== TOPT-BIN Binary Transmission 0 TOPT-ECHO Echo 1 TOPT-RECN Reconnection 2 TOPT-SUPP Suppress Go Ahead 3 TOPT-APRX Approx Message Size Negotiation 4 TOPT-STAT Status 5 TOPT-TIM Timing Mark 6 TOPT-REM Remote Controlled Trans and Echo 7 TOPT-OLW Output Line Width 8 TOPT-OPS Output Page Size 9 TOPT-OCRD Output Carriage-Return Disposition 10 TOPT-OHT Output Horizontal Tabstops 11 TOPT-OHTD Output Horizontal Tab Disposition 12 TOPT-OFD Output Formfeed Disposition 13 TOPT-OVT Output Vertical Tabstops 14 TOPT-OVTD Output Vertical Tab Disposition 15 TOPT-OLD Output Linefeed Disposition 16 TOPT-EXT Extended ASCII 17 TOPT-LOGO Logout 18 TOPT-BYTE Byte Macro 19 TOPT-DATA Data Entry Terminal 20 TOPT-SUP SUPDUP 21 TOPT-SUPO SUPDUP Output 22 TOPT-SNDL Send Location 23 TOPT-TERM Terminal Type 24 TOPT-EOR End of Record 25 TOPT-TACACS TACACS User Identification 26 TOPT-OM Output Marking 27 TOPT-TLN Terminal Location Number 28 TOPT-3270 Telnet 3270 Regime 29 TOPT-X.3 X.3 PAD 30 TOPT-NAWS Negotiate About Window Size 31 TOPT-TS Terminal Speed 32 TOPT-RFC Remote Flow Control 33 TOPT-LINE Linemode 34 TOPT-XDL X Display Location 35 TOPT-ENVIR Telnet Environment Option 36 TOPT-AUTH Telnet Authentication Option 37 TOPT-ENVIR Telnet Environment Option 39 TOPT-TN3270E TN3270 Enhancements 40 TOPT-AUTH Telnet XAUTH 41 State ===== Std Std Prop Std Prop Std Std Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Prop Draft Prop Hist Exp Prop Prop Exp Status ====== Rec Rec Ele Rec Ele Rec Rec Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Ele Not Ele Ele Ele RFC STD ==== === 856 27 857 28 ... 858 29 ... 859 30 860 31 726 ... ... 652 653 654 655 656 657 658 698 727 735 1043 736 749 779 1091 885 927 933 946 1041 1053 1073 1079 1372 1184 1096 1408 1416 1572 1647

Internet Architecture Board Standards Track

[Page 46]


RFC 2300

Internet Standards

May 1998

TOPT-CHARSET Telnet CHARSET TOPR-RSP Telnet Remote Serial Port TOPT-COMPORT Telnet Com Port Control TOPT-EXTOP Extended-Options-List

42 43 44 255

Exp Exp Exp Std

2066 2217 861 * 32

Rec

[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] 6.7. Experimental Protocols

All Experimental protocols have the Limited Use status. Protocol ======== ------RTP-MPEG ------------LDAP-NIS HTTP-RVSA TCN-HTTP ------------------------MAP-MAIL MIME-ODA OSPF-DIG GKMP-ARCH GKMP-SPEC IP-SCSI X.500-NAME TFTP-MULTI IP-Echo METER-MIB TFM-ARCH DNS-SRV URAS GPS-AR ETFTP BGP-RR BGP-ASC SMKD HTML-TBL MIME-VP SNMPV2SM SNMPV2AI SNMPV2CB Name ===================================== Domain Names and Company Name Retrieva RTP Payload Format for Bundled MPEG Intra-LIS IP Multicast/Routers over ATM using PIM Safe Response Header Field Approach Using LDAP as a Network Information Service HTTP Remote Variant Selection Algorithm Transparent Content Negotiation in HTTP Core Based Trees (CBT) Multicast Routing Architecture Core Based Trees (CBT version 2) Multicast Routing Trivial Convention using HTTP in URN Resolution Resolution of URIs using DNS X.400 Mapping and Mail-11 A MIME Body Part for ODA OSPF with Digital Signature Group Key Management Protocol (GKMP) Architecture Group Key Management Protocol (GKMP) Specification Encapsulating IP with the SCSI Managing the X.500 Root Naming Context TFTP Multicast Option IP Echo Host Service Traffic Flow Measurement Meter MIB Traffic Flow Measurement Architecture Location of Services in the DNS Uniform Resource Agents GPS-Based Addressing and Routing Enhanced Trivial File Transfer Protocol BGP Route Reflection Autonomous System Confederations for BGP Scalable Multicast Key Distribution HTML Tables Voice Profile for Internet Mail User-based Security Model for SNMPv2 SNMPv2 Administrative Infrastructure Introduction to Community-based SNMPv2 RFC ===== 2345* 2343* 2337* 2310* 2307* 2296* 2295* 2201* 2189* 2169* 2168* 2162* 2161* 2154* 2094* 2093* 2143 2120 2090 2075 2064 2063 2052 2016 2009 1986 1966 1965 1949 1942 1911 1910 1909 1901

Internet Architecture Board Standards Track

[Page 47]


RFC 2300

Internet Standards

May 1998

------DNS-LOC SGML-MT CONT-MT UNARP ------------------ESP3DES ------------------ST2 ------------------------TCP/IPXMIB ------ICMP-DM CLNP-MULT OSPF-OVFL RWP NARP DNS-ENCODE TCP-POS T/TCP MIME-UNI FOOBAR X500-CHART X500-DIR SNMP-DPI CLNP-TUBA REM-PRINT EHF-MAIL RAP TP/IX X400 DNS IRCP TOS-LS SIFT/UFT DIR-ARP TEL-SPX TEL-KER TRACE-IP DNS-IP RMCP

IPv6 Testing Address Allocation Location Information in the DNS SGML Media Types Access Type Content-ID ARP Extension - UNARP Form-based File Upload in HTML BGP/IDRP Route Server Alternative IP Authentication using Keyed SHA ESP Triple DES Transform SMTP 521 Reply Code SMTP Serv. Ext. for Checkpoint/Restart SMTP Serv. Ext. Large and Binary MIME Msgs. Stream Protocol Version 2 Content-Disposition Header Schema Publishing in X.500 Directory X.400-MHS use X.500 to support X.400-MHS Routing Class A Subnet Experiment TCP/IPX Connection Mib Specification TCP And UDP Over IPX Networks With Fixed Path MTU ICMP Domain Name Messages Host Group Extensions for CLNP Multicasting OSPF Database Overflow Remote Write ProtocolL - Version 1.0 NBMA Address Resolution Protocol DNS Encoding of Geographical Location An Extension to TCP: Partial Order Service TCP Extensions for Transactions Using Unicode with MIME FTP Operation Over Big Address Records Charting Networks in the X.500 Directory Representing IP Information in the X.500 Directory SNMP Distributed Protocol Interface Use of ISO CLNP in TUBA Environments TPC.INT Subdomain Remote Printing - Technical Encoding Header Field for Internet Messages Internet Route Access Protocol TP/IX: The Next Internet Routing Coordination for X.400 Services Storing Arbitrary Attributes in DNS Internet Relay Chat Protocol Link Security TOS Sender-Initiated/Unsolicited File Transfer Directed ARP Telnet Authentication: SPX Telnet Authentication: Kerberos V4 Traceroute Using an IP Option Experiment in DNS Based IP Routing Remote Mail Checking Protocol

1897 1876 1874 1873 1868 1867 1863 1852 1851 1846 1845 1830 1819 1806 1804 1801 1797 1792 1791 1788 1768 1765 1756 1735 1712 1693 1644 1641 1639 1609 1608 1592 1561 1528 1505 1476 1475 1465 1464 1459 1455 1440 1433 1412 1411 1393 1383 1339

Internet Architecture Board Standards Track

[Page 48]


RFC 2300

Internet Standards

May 1998

TCP-HIPER MSP2 DSLCP -------IN-ENCAP CLNS-MIB CFDP IP-AX.25 ALERTS MPP SNMP-BULK DNS-RR IMAP2 NTP-OSI DMF-MAIL RDP TCP-ACO IP-DVMRP VMTP COOKIE-JAR NETBLT IRTP LDP RLP NVP-II PVP

TCP Extensions for High Performance Message Send Protocol 2 Dynamically Switched Link Control X.500 and Domains Internet Encapsulation Protocol CLNS-MIB Coherent File Distribution Protocol IP Encapsulation of AX.25 Frames Managing Asynchronously Generated Alerts Message Posting Protocol Bulk Table Retrieval with the SNMP New DNS RR Definitions Interactive Mail Access Protocol NTP over OSI Remote Operations Digest Message Format for Mail Reliable Data Protocol TCP Alternate Checksum Option IP Distance Vector Multicast Routing Versatile Message Transaction Protocol Authentication Scheme Bulk Data Transfer Protocol Internet Reliable Transaction Protocol Loader Debugger Protocol Resource Location Protocol Network Voice Protocol Packet Video Protocol

1323 1312 1307 1279 1241 1238 1235 1226 1224 1204 1187 1183 1176 1165 1153 908,1151 1146 1075 1045 1004 998 938 909 887 ISI-memo ISI-memo

[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.]

Internet Architecture Board Standards Track

[Page 49]


RFC 2300

Internet Standards

May 1998

6.8.

Informational Protocols

Information protocols have no status. Protocol ======= -------KOI8-U TEXT-CSS PKCS-7 PKCS-10 PKCS-1 SMIME-CERT SMIME-MSG TIFF GSMP HSRP RC2-ENCRP SNQP -------KEYX-DNS DSP NFS-URL APP-MARC ODETTE-FTP ESRO ICP IPV4-MAPOS MAPOS-SONET RWHOIS PPP-EXT UTF-7 CAST-128 DLSCAP PNG RC5 SNTP PGP-MEF PPP-DEFL PPP-PRED PPP-BSD PPP-DCE PPP-MAG PPP-STAC GZIP DEFLATE ZLIB HTTP-1.0 Name ==================================== Mapping Airline Reservation, Ticketing, Messaging Ukrainian Character Set KOI8-U The text/css Media Type PKCS #7: Cryptographic Message Syntax Version 1.5 PKCS #10: Certification Request Syntax Version 1.5 PKCS #1: RSA Encryption Version 1.5 S/MIME Version 2 Certificate Handling S/MIME Version 2 Message Specification Tag Image File Format F Profile for Facsimile Ipsilon's General Switch Management Protocol Cisco Hot Standby Router Protocol (HSRP) A Description of the RC2(r) Encryption Algorithm Simple Nomenclator Query Protocol Japanese Character Encoding for Internet Messages Key Exchange Delegation Record for the DNS A Dictionary Server Protocol NFS URL Scheme The Application/MARC Content-type ODETTE File Transfer Protocol AT&T/Neda's Efficient Short Remote Operations Protocol Internet Cache Protocol Version 2 IPv4 over MAPOS Version 1 Multiple Access Protocol over SONET/SDH Version 1 Referral Whois Protocol PPP Vendor Extensions UTF-7 CAST-128 Encryption Algorithm Data Link Switching Client Access Protocol Portable Network Graphics Version 1.0 RC5, RC5-CBC, RC5-CBC-Pad, and RC5-CTS Algorithms Simple Network Time Protocol v4 for IPv4, IPv6 and OSI PGP Message Exchange Formats PPP Deflate Protocol PPP Predictor Compression Protocol PPP BSD Compression Protocol PPP for Data Compression in DCE PPP Magnalink Variable Resource Compression PPP Stac LZS Compression Protocol GZIP File Format Specification Version 4.3 DEFLATE Compressed Data Format Specification V. 1.3 ZLIB Compressed Data Format Specification V. 3.3 Hypertext Transfer Protocol -- HTTP/1.0 RFC ===== 2351* 2319* 2318* 2315* 2314* 2313* 2312* 2311* 2302* 2297* 2281* 2268* 2259* 2237* 2230* 2229* 2224* 2220* 2204* 2188* 2186* 2176* 2171* 2167* 2153 2152 2144 2114 2083 2040 2030 1991 1979 1978 1977 1976 1975 1974 1952 1951 1950 1945

Internet Architecture Board Standards Track

[Page 50]


RFC 2300

Internet Standards

May 1998

---------------------SNPP --------

text/enriched MIME Content-type Application/CALS-1840 Content-type PPP IPCP Extensions for Name Server Addresses Simple Network Paging Protocol - Version 2 ISO Transport Class 2 Non-use Explicit Flow Control over TCP RFC1006 extension -------IP in IP Tunneling -------PPP Network Control Protocol for LAN Extension TESS The Exponential Security System NFSV3 NFS Version 3 Protocol Specification -------A Format for Bibliographic Records ------Data Link Switching: Switch-to-Switch Protocol BGP-4 Experience with the BGP-4 Protocol SDMD IPv4 Option for Sender Directed MD Delivery SNOOP Snoop Version 2 Packet Capture File Format BINHEX MIME Content Type for BinHex Encoded Files DNS-NSAP DNS NSAP Resource Records RADIO-PAGE TPC.INT Subdomain: Radio Paging -- Technical Procedures GRE-IPv4 Generic Routing Encapsulation over IPv4 GRE Generic Routing Encapsulatio ADSNA-IP Advanced SNA/IP: A Simple SNA Transport Protocol TACACS Terminal Access Control Protocol MD4 MD4 Message Digest Algorithm SUN-NFS Network File System Protocol SUN-RPC Remote Procedure Call Protocol Version 2 GOPHER The Internet Gopher Protocol LISTSERV Listserv Distribute Protocol ------Replication Requirements PCMAIL Pcmail Transport Protocol MTP Multicast Transport Protocol BSD Login BSD Login DIXIE DIXIE Protocol Specification IP-X.121 IP to X.121 Address Mapping for DDN OSI-HYPER OSI and LLC1 on HYPERchannel HAP2 Host Access Protocol SUBNETASGN On the Assignment of Subnet Numbers SNMP-TRAPS Defining Traps for use with SNMP DAS Directory Assistance Service LPDP Line Printer Daemon Protocol [Note: an asterisk at the end of a line indicates a change from the previous edition of this document.]

1896 1895 1877 1861 1859 1853 1841 1824 1813 1807 1795 1773 1770 1761 1741 1706 1703 1702 1701 1538 1492 1320 1094 1057 1436 1429 1275 1056 1301 1282 1249 1236 1223 1221 1219 1215 1202 1179

Internet Architecture Board Standards Track

[Page 51]


RFC 2300

Internet Standards

May 1998

6.9.

Historic Protocols

All Historic protocols have Not Recommended status. Protocol ======== L2F IPSO SNMPv2 SNMPv2 SNMPv2 SNMPv2 RIP -------BGP3 -------EGP SNMP-MUX OIM-MIB-II IMAP3 SUN-RPC 802.4-MIP CMOT ---------------------NFILE HOSTNAME SFTP SUPDUP BGP MIB-I SGMP HEMS STATSRV POP2 RATP HFEP THINWIRE HMP GGP RTELNET CLOCK MPM NETRJS NETED RJE XNET Name ===================================== Cisco Layer Two Forwarding Protocol DoD Security Options for IP Manager-to-Manager MIB Party MIB for SNMPv2 Security Protocols for SNMPv2 Administrative Model for SNMPv2 Routing Information Protocol Mapping full 822 to Restricted 822 Border Gateway Protocol 3 (BGP-3) Gateway Requirements Exterior Gateway Protocol SNMP MUX Protocol and MIB OSI Internet Management: MIB-II Interactive Mail Access Protocol Version Remote Procedure Call Protocol Version 1 IEEE 802.4 Token Bus MIB Common Management Information Services Mail Privacy: Procedures Mail Privacy: Key Management Mail Privacy: Algorithms A File Access Protocol HOSTNAME Protocol Simple File Transfer Protocol SUPDUP Protocol Border Gateway Protocol MIB-I Simple Gateway Monitoring Protocol High Level Entity Management Protocol Statistics Server Post Office Protocol, Version 2 Reliable Asynchronous Transfer Protocol Host - Front End Protocol Thinwire Protocol Host Monitoring Protocol Gateway Gateway Protocol Remote Telnet Service DCNET Time Server Protocol Internet Message Protocol Remote Job Service Network Standard Text Editor Remote Job Entry Cross Net Debugger RFC ===== 2341 Elective 1108 Elective 1451 Elective 1447 Elective 1446 Elective 1445 Ele 1058 1137 1267,1268 Req 1009 Rec 904 1227 1214 3 1203 1050 1230 1189 1113 1114 1115 1037 953 913 734 1163,1164 1156 1028 1021 996 937 916 929 914 869 823 818 778 759 740 569 407 IEN-158 STD === *

34

4 18

Internet Architecture Board Standards Track

[Page 52]


RFC 2300

Internet Standards

May 1998

NAMESERVER Host Name Server Protocol MUX Multiplexing Protocol GRAPHICS Graphics Protocol

IEN-116 IEN-90 NIC-24308

[Note: an asterisk at the end of a line indicates a change from the previous edition of this document.] 6.10. Obsolete Protocols

Some of the protocols listed in this memo are described in RFCs that are obsoleted by newer RFCs. "Obsolete" or "obsoleted" is not an official state or status of protocols. This subsection is for information only. While it may seem to be obviously wrong to have an obsoleted RFC in the list of standards, there may be cases when an older standard is in the process of being replaced. This process may take a year or two. Many obsoleted protocols are of little interest and are dropped from this memo altogether. Some obsoleted protocols have received enough recognition that it seems appropriate to list them under their current status and with the following reference to their current replacement. RFC RFC Status ==== ==== ========= 1305 obsoletes 1119 Stan/Rec Title * =================================== = Network Time Protocol version 2

Thanks to Lynn Wheeler for compiling the information in this subsection. [Note: an asterisk at the end of a line indicates a change from the previous edition of this document.]

Internet Architecture Board Standards Track

[Page 53]


RFC 2300

Internet Standards

May 1998

7. 7.1.

Contacts IAB, IETF, and IRTF Contacts Internet Architecture Board (IAB) Contact

7.1.1.

Please send your comments about this list of protocols and especially about the Draft Standard Protocols to the Internet Architecture Board care of Abel Winerib, IAB Executive Director. Contacts: Abel Winerib Executive Director of the IAB Intel, JF2-64 2111 NE 25th Avenue Hillsboro, OR 97124 1-503-696-8972 AWinerib@ibeam.jf.intel.com

Brian E. Carpenter Chair of the IAB IBM United Kingdon Laboratories Hursley Park Winchester Hampshire SO21 2JN +44 1962 816833 brian@hursley.ibm.com

7.1.2.

Internet Engineering Task Force (IETF) Contact

Contacts: Fred Baker Chair of the IETF cisco Systems, Inc. 519 Lado Drive Santa Barbara, CA 93111 1-805-681-0115 fred@cisco.com

Internet Architecture Board Standards Track

[Page 54]


RFC 2300

Internet Standards

May 1998

Steve Coya IESG Secretary Corporation for National Research Initiatives 1895 Preston White Drive, Suite 100 Reston, VA 22091 1-703-620-8990 scoya@IETF.ORG Steve Coya Executive Director of the IETF Corporation for National Research Initiatives 1895 Preston White Drive, Suite 100 Reston, VA 22091 1-703-620-8990 scoya@IETF.ORG

7.1.3.

Internet Research Task Force (IRTF) Contact

Contact: Abel Winerib Chair of the IRTF Intel, JF2-64 2111 NE 25th Avenue Hillsboro, OR 97124 1-503-696-8972 AWinerib@ibeam.jf.intel.com

Internet Architecture Board Standards Track

[Page 55]


RFC 2300

Internet Standards

May 1998

7.2.

Internet Assigned Numbers Authority Contact Contact: Joyce K. Reynolds Internet Assigned Numbers Authority USC/Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292-6695 1-310-822-1511 IANA@IANA.ORG

The protocol standards are managed by the Internet Assigned Numbers Authority. Please refer to the document "Assigned Numbers" (RFC-1700) for further information about the status of protocol documents. There are two documents that summarize the requirements for host and gateways in the Internet, "Host Requirements" (RFC-1122 and RFC-1123) and "Requirements for IP Version 4 Routers" (RFC-1812). How to obtain the most recent edition of this "Internet Official Protocol Standards" memo: The file "in-notes/std/std1.txt" may be copied via FTP from the FTP.ISI.EDU computer using the FTP username "anonymous" and FTP password "guest".

Internet Architecture Board Standards Track

[Page 56]


RFC 2300

Internet Standards

May 1998

7.3.

Request for Comments Editor Contact Contact: Jon Postel RFC Editor USC/Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292-6695 1-310-822-1511 RFC-Editor@ISI.EDU

Documents may be submitted via electronic mail to the RFC Editor for consideration for publication as RFC. If you are not familiar with the format or style requirements please request the "Instructions for RFC Authors". In general, the style of any recent RFC may be used as a guide. 7.4. The Network Information Center and Requests for Comments Distribution Contact

RFCs can be obtained via FTP from FTP.ISI.EDU, with the pathname innotes/rfcnnnn.txt (where "nnnn" refers to the number of the RFC). Login with FTP username "anonymous" and password "name@host.domain". RFCs can also be obtained via electronic mail from ISI.EDU by using the RFC-INFO service. Address the request to "rfc-info@isi.edu" with a message body of: Retrieve: RFC Doc-ID: RFCnnnn (Where "nnnn" refers to the number of the RFC (always use 4 the DOC-ID of RFC 822 is "RFC0822")). The RFC-INFO@ISI.EDU provides other ways of selecting RFCs based on keywords and more information send a message to "rfc-info@isi.edu" with message body "help: help". contact: RFC-Manager@ISI.EDU digits server such; for the

Internet Architecture Board Standards Track

[Page 57]


RFC 2300

Internet Standards

May 1998

7.5.

Sources for Requests for Comments

Details on many sources of RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to "rfc-info@ISI.EDU" with the message body "help: ways_to_get_rfcs". For example: To: rfc-info@ISI.EDU Subject: getting rfcs help: ways_to_get_rfcs 8. Security Considerations Security issues are not addressed in this memo. 9. Author's Address Jon Postel USC/Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Phone: 310-822-1511 Fax: 310-823-6714 EMail: Postel@ISI.EDU

Internet Architecture Board Standards Track

[Page 58]


RFC 2300

Internet Standards

May 1998

Full Copyright Statement Copyright (C) The Internet Society (1998). All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Internet Architecture Board Standards Track

[Page 59]