rfc1140.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

Network Working Group                          Internet Activities Board
Request for Comments: 1140                             J. Postel, Editor
Obsoletes: RFCs 1130,                                           May 1990
          1100, 1083



                    IAB 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 Activities Board (IAB).
   Distribution of this memo is unlimited.

Table of Contents

   Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2
   1.  The Standardization Process  . . . . . . . . . . . . . . . . 2
   2.  The Request for Comments Documents . . . . . . . . . . . . . 5
   3.  Other Reference Documents  . . . . . . . . . . . . . . . . . 6
   3.1.  Assigned Numbers . . . . . . . . . . . . . . . . . . . . . 6
   3.2.  Annotated Internet Protocols . . . . . . . . . . . . . . . 6
   3.3.  Gateway Requirements . . . . . . . . . . . . . . . . . . . 6
   3.4.  Host Requirements  . . . . . . . . . . . . . . . . . . . . 6
   3.5.  The MIL-STD Documents  . . . . . . . . . . . . . . . . . . 7
   4.  Explanation of Terms . . . . . . . . . . . . . . . . . . . . 7
   4.1.  Definitions of Protocol State  . . . . . . . . . . . . . . 8
   4.1.1.  Standard Protocol  . . . . . . . . . . . . . . . . . . . 8
   4.1.2.  Draft Standard Protocol  . . . . . . . . . . . . . . . . 9
   4.1.3.  Proposed Standard Protocol . . . . . . . . . . . . . . . 9
   4.1.4.  Experimental Protocol  . . . . . . . . . . . . . . . . . 9
   4.1.5.  Historic Protocol  . . . . . . . . . . . . . . . . . . . 9
   4.2.  Definitions of Protocol Status . . . . . . . . . . . . . . 9
   4.2.1.  Required Protocol  . . . . . . . . . . . . . . . . . . . 9
   4.2.2.  Recommended Protocol . . . . . . . . . . . . . . . . .  10
   4.2.3.  Elective Protocol  . . . . . . . . . . . . . . . . . .  10
   4.2.4.  Limited Use Protocol . . . . . . . . . . . . . . . . .  10
   4.2.5.  Not Recommended Protocol . . . . . . . . . . . . . . .  10
   5.  The Standards Track  . . . . . . . . . . . . . . . . . . .  10
   5.1.  The RFC Processing Decision Table  . . . . . . . . . . .  10
   5.2.  The Standards Track Diagram  . . . . . . . . . . . . . .  12
   6.  The Protocols  . . . . . . . . . . . . . . . . . . . . . .  14
   6.1.  Recent Changes . . . . . . . . . . . . . . . . . . . . .  14
   6.1.1.  New RFCs . . . . . . . . . . . . . . . . . . . . . . .  14
   6.1.2.  Other Changes  . . . . . . . . . . . . . . . . . . . .  17
   6.2.  Standard Protocols . . . . . . . . . . . . . . . . . . .  18



Internet Activities Board                                       [Page 1]

RFC 1140                     IAB Standards                      May 1990


   6.3.  Network-Specific Standard Protocols  . . . . . . . . . .  19
   6.4.  Draft Standard Protocol  . . . . . . . . . . . . . . . .  20
   6.5.  Proposed Standard Protocol . . . . . . . . . . . . . . .  21
   6.6.  Experimental Protocol  . . . . . . . . . . . . . . . . .  22
   6.7.  Historic Protocol  . . . . . . . . . . . . . . . . . . .  22
   7.  Contacts . . . . . . . . . . . . . . . . . . . . . . . . .  23
   7.1.  IAB, IETF, and IRTF Contacts . . . . . . . . . . . . . .  23
   7.1.1.  Internet Activities Board (IAB) Contact  . . . . . . .  23
   7.1.2.  Internet Engineering Task Force (IETF) Contact . . . .  23
   7.1.3.  Internet Research  Task Force (IETF) Contact . . . . .  24
   7.2.  Internet Assigned Numbers Authority (IANA) Contact . . .  24
   7.3.  Request for Comments Editor Contact  . . . . . . . . . .  25
   7.4.  Network Information Center Contact . . . . . . . . . . .  25
   7.5.  Other Sources for Requests for Comments  . . . . . . . .  26
   7.5.1.  NSF Network Service Center (NNSC)  . . . . . . . . . .  26
   7.5.2.  NSF Network Information Service (NIS)  . . . . . . . .  26
   7.5.3.  CSNET Coordination and Information Center (CIC)  . . .  26
   8.  Security Considerations  . . . . . . . . . . . . . . . . .  27
   9.  Author's Address . . . . . . . . . . . . . . . . . . . . .  27

Introduction

   Discussion of the standardization process and the RFC document series
   is presented first, then the explanation of the terms is presented,
   the lists of protocols in each stage of standardization follows and
   finally come pointers to references and contacts for further
   information.

   This memo is issued quarterly, please be sure the copy you are
   reading is dated within the last three months.  Current copies may be
   obtained from the Network Information Center or from the Internet
   Assigned Numbers Authority (see the contact information at the end of
   this memo).  Do not use this edition after 31-Aug-90.

   See Section 6.1 for a description of recent changes.

1.  The Standardization Process

   The Internet Activities Board maintains this list of documents that
   define standards for the Internet protocol suite (see RFC-1120 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)).  The IAB provides 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 majority of Internet protocol development and standardization



Internet Activities Board                                       [Page 2]

RFC 1140                     IAB Standards                      May 1990


   activity takes place in the working groups of the Internet
   Engineering Task Force.

   Protocols which are to become standards in the Internet go through a
   series of states (proposed standard, draft standard, and standard)
   involving increasing amounts of scrutiny and experimental testing.
   At each step, the Internet Engineering Steering Group (IESG) of the
   IETF must make a recommendation for advancement of the protocol and
   the IAB must ratify it.  If a recommendation is not ratified, the
   protocol is remanded to the IETF for further work.

   To allow time for the Internet community to consider and react to
   standardization proposals, the IAB imposes a minimum delay of 4
   months before a proposed standard can be advanced to a draft standard
   and 6 months before a draft standard can be promoted to standard.

   It is general IAB 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 the IAB may convene a special review committee
   consisting of experts from the IETF, IRTF and the IAB with the
   purpose of recommending an explicit action to the IAB.

   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 in six months.

   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 the IAB believes 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.

   In addition to the working groups of the IETF, protocol development
   and experimentation may take place as a result of the work of the



Internet Activities Board                                       [Page 3]

RFC 1140                     IAB Standards                      May 1990


   research groups of the Internet Research Task Force, or the work of
   other individuals interested in Internet protocol development.  The
   IAB encourages the documentation of such experimental work in the RFC
   series, 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, and the IAB has approved
   this step.

   A few protocols have achieved widespread implementation without the
   approval of the IESG and the IAB.  For example, some vendor protocols
   have become very important to the Internet community even though they
   have not been recommended by the IESG or ratified by the IAB.
   However, the IAB strongly recommends that the IAB standards process
   be used in the evolution of the protocol suite to maximize
   interoperability (and to prevent incompatible protocol requirements
   from arising).  The IAB reserves the use of the terms "standard",
   "draft standard", and "proposed standard" in any RFC or other
   publication of Internet protocols to only those protocols which the
   IAB has approved.

   In addition to a state (like "proposed standard") a protocol is also
   assigned a status, or requirement level.  A protocol can be required,
   meaning that all systems in the Internet must implement it.  For
   example, the Internet Protocol (IP) is required.  A protocol may be
   recommended, meaning that systems should implement this protocol.  A
   protocol may be elective, meaning that systems may implement this
   protocol; that is, if (and only if) the functionality of this
   protocol is needed or useful for a system it must use this protocol
   to provide the functionality.  A protocol may be termed limited use
   or even not recommended if it is not intended to be generally
   implemented; for example, experimental or historic protocols.

   When a protocol is on the standards track, that is in the proposed
   standard, draft standard, or standard state (see Section 5), the
   status is the current status.  However, the IAB will also endeavor to
   indicate the eventual status this protocol will have when the
   standardization is completed.

   The IAB realizes that a one word label is not sufficient to
   characterize the implementation requirements for a protocol in all
   situations.  In many cases, an additional paragraph about the status
   will be provided, and in some cases reference will be made to
   separate requirements documents.

   Few protocols are required to be implemented in all systems.  This is
   because there is such a variety of possible systems; for example,
   gateways, terminal servers, workstations, multi-user hosts.  It is
   not necessary for a gateway to implement TCP or the protocols that



Internet Activities Board                                       [Page 4]

RFC 1140                     IAB Standards                      May 1990


   use TCP (though it may be useful).  It is expected that general
   purpose hosts will implement at least IP (including ICMP and IGMP),
   TCP and UDP, Telnet, FTP, NTP, SMTP, Mail, and the Domain Name System
   (DNS).

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).

   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 such as
   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 both the IESG and the IAB.  For documents describing
   experimental work, the RFC Editor will typically request review
   comments from the relevant IETF working group or IRTF research group
   and provide those comments to the author prior to committing to
   publication.  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 "IAB Official Protocol Standards" memo is
   the reference for determining the correct RFC to refer to for the
   current specification of each protocol.

   The RFCs are available from the Network Information Center at SRI



Internet Activities Board                                       [Page 5]

RFC 1140                     IAB Standards                      May 1990


   International, 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 four other reference documents of interest in checking the
   current status of protocol specifications and standardization.  These
   are the Assigned Numbers, the Annotated Internet Protocols, 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.5.

3.1.  Assigned Numbers

   This document lists the assigned values of the parameters used in the
   various protocols.  For example, IP protocol codes, TCP port numbers,
   Telnet Option Codes, ARP hardware types, and Terminal Type names.
   Assigned Numbers was most recently issued as RFC-1060.

   Another document, Internet Numbers, lists the assigned IP network
   numbers, and the autonomous system numbers.  Internet Numbers was
   most recently issued as RFC-1117.

3.2.  Annotated Internet Protocols

   This document lists the protocols and describes any known problems
   and ongoing experiments.  This document was most recently issued as
   RFC-1011 under the title "Official Internet Protocols".

3.3.  Gateway Requirements

   This document reviews the specifications that apply to gateways and
   supplies guidance and clarification for any ambiguities.  Gateway
   Requirements is RFC-1009.  A working group of the IETF is actively
   preparing a revision.

3.4.  Host Requirements

   This pair of documents reviews the specifications that apply to hosts
   and supplies guidance and clarification for any ambiguities.  Host
   Requirements was recently issued as RFC-1122 and RFC-1123.







Internet Activities Board                                       [Page 6]

RFC 1140                     IAB Standards                      May 1990


3.5.  The MIL-STD Documents

   The Internet community specifications for IP (RFC-791) and TCP (RFC-
   793) and the DoD MIL-STD specifications are intended to describe
   exactly the same protocols.  Any difference in the protocols
   specified by these sets of documents should be reported to DCA and to
   the IAB.  The RFCs and the MIL-STDs for IP and TCP differ in style
   and level of detail.  It is strongly advised that the two sets of
   documents be used together.

   The IAB and the DoD MIL-STD specifications for the FTP, SMTP, and
   Telnet protocols are essentially the same documents (RFCs 765, 821,
   854).  The MIL-STD versions have been edited slightly.  Note that the
   current Internet specification for FTP is RFC-959.

          Internet Protocol (IP)                      MIL-STD-1777
          Transmission Control Protocol (TCP)         MIL-STD-1778
          File Transfer Protocol (FTP)                MIL-STD-1780
          Simple Mail Transfer Protocol (SMTP)        MIL-STD-1781
          Telnet Protocol and Options (TELNET)        MIL-STD-1782

   These documents are available from the Naval Publications and Forms
   Center.  Requests can be initiated by telephone, telegraph, or mail;
   however, it is preferred that private industry use form DD1425, if
   possible.  These five documents are included in the 1985 DDN Protocol
   Handbook (available from the Network Information Center, see Section
   7.4).

          Naval Publications and Forms Center, Code 3015
          5801 Tabor Ave
          Philadelphia, PA 19120
          Phone: [phone] (order tape)
                 1-215-697-4834 (conversation)

4.  Explanation of Terms

   There are two independent categorization of protocols.  The first is