rfc1780.txt

RFC 的详细文档！

   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 temporary states,
   those illustrated by double line boxes are long term states.  A
   protocol will normally be expected to remain in a temporary state for
   several months (minimum six months for proposed standard, minimum
   four months for draft standard).  A protocol may be in a long term
   state for many years.

   A protocol may enter the standards track only on the recommendation
   of the IESG; and may move from one state to another along the track
   only on the recommendation of the IESG.  That is, it takes action by
   the IESG to either start a protocol on the track or 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                                    [Page 12]

RFC 1780                   Internet Standards                 March 1995


         |
         +<----------------------------------------------+
         |                                               ^
         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                                    [Page 13]

RFC 1780                   Internet Standards                 March 1995


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.  Recent Changes

6.1.1.  New RFCs:

      1786 - Representation of IP Routing Policies in a Routing Registry
             (ripe-81++)

             This is an information document and does not specify any
             level of standard.

      1785 - TFTP Option Negotiation Analysis

             This is an information document and does not specify any
             level of standard.

      1784 - TFTP Timeout Interval and Transfer Size Options

             A Proposed Standard protocol.

      1783 - TFTP Blocksize Option

             A Proposed Standard protocol.

      1782 - TFTP Option Extension

             A Proposed Standard protocol.

      1781 - Using the OSI Directory to Achieve User Friendly Naming

             A Proposed Standard protocol.

      1780 - Internet Official Protocol Standards

             This memo.

      1779 - A String Representation of Distinguished Names

             A Draft Standard protocol.

      1778 - The String Representation of Standard Attribute Syntaxes

             A Draft Standard protocol.




Internet Architecture Board                                    [Page 14]

RFC 1780                   Internet Standards                 March 1995


      1777 - Lightweight Directory Access Protocol

             A Draft Standard protocol.

      1776 - Not yet issued.

      1775 - To Be "On" the Internet

             This is an information document and does not specify any
             level of standard.

      1774 - BGP-4 Protocol Analysis

             This is an information document and does not specify any
             level of standard.

      1773 - Experience with the BGP-4 protocol

             This is an information document and does not specify any
             level of standard.

      1772 - Application of the Border Gateway Protocol in the Internet

             A Draft Standard protocol.

      1771 - A Border Gateway Protocol 4 (BGP-4)

             A Draft Standard protocol.

      1770 - IPv4 Option for Sender Directed Multi-Destination Delivery

             This is an information document and does not specify any
             level of standard.

      1769 - Simple Network Time Protocol (SNTP)

             This is an information document and does not specify any
             level of standard.

      1768 - Host Group Extensions for CLNP Multicasting

             An Experimental protocol.

      1767 - MIME Encapsulation of EDI Objects

             A Proposed Standard protocol.





Internet Architecture Board                                    [Page 15]

RFC 1780                   Internet Standards                 March 1995


      1766 - Tags for the Identification of Languages

             A Proposed Standard protocol.

      1765 - OSPF Database Overflow

             An Experimental protocol.

      1764 - The PPP XNS IDP Control Protocol (XNSCP)

             A Proposed Standard protocol.

      1763 - The PPP Banyan Vines Control Protocol (BVCP)

             A Proposed Standard protocol.

      1762 - The PPP DECnet Phase IV Control Protocol (DNCP)

             A Draft Standard protocol.

      1761 - Snoop Version 2 Packet Capture File Format

             This is an information document and does not specify any
             level of standard.

      1760 - The S/KEY One-Time Password System

             This is an information document and does not specify any
             level of standard.

      1759 - Printer MIB

             A Proposed Standard protocol.

      1758 - NADF Standing Documents: A Brief Overview

             This is an information document and does not specify any
             level of standard.

      1757 - Remote Network Monitoring Management Information Base

             A Draft Standard protocol.

      1756 - Remote Write ProtocolL - Version 1.0

             An Experimental protocol.





Internet Architecture Board                                    [Page 16]

RFC 1780                   Internet Standards                 March 1995


      1755 - ATM Signaling Support for IP over ATM

             A Proposed Standard protocol.

      1754 - IP over ATM Working Group's Recommendations for the ATM
             Forum's Multiprotocol

             This is an information document and does not specify any
             level of standard.

      1753 - IPng Technical Requirements Of the Nimrod Routing and
             Addressing Architecture

             This is an information document and does not specify any
             level of standard.

      1752 - The Recommendation for the IP Next Generation Protocol

             A Proposed Standard protocol.

      1751 - A Convention for Human-Readable 128-bit Keys

             This is an information document and does not specify any
             level of standard.

      1750 - Randomness Recommendations for Security

             This is an information document and does not specify any
             level of standard.

      1749 - IEEE 802.5 Station Source Routing MIB using SMIv2

             A Proposed Standard protocol.

      1748 - IEEE 802.5 MIB using SMIv2

             A Draft Standard protocol.

      1747 - Definitions of Managed Objects for SNA Data Link Control
             (SDLC) using SMIv2

             A Proposed Standard protocol.

      1746 - Ways to Define User Expectations

             This is an information document and does not specify any
             level of standard.