rfc1600.txt

RFC 的详细文档！


RFC 1600                   Internet Standards                 March 1994


   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 as its agent for
   forwarding documents with IESG approval and for registering concerns
   in response to notifications (4) to the RFC Editor.  Documents from
   Area Directors or Working Group Chairs may be considered in the same
   way as documents from "other".

5.2.  The Standards Track Diagram

   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 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 1600                   Internet Standards                 March 1994


         |
         +<----------------------------------------------+
         |                                               ^
         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 1600                   Internet Standards                 March 1994


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:

      1600 - This memo.

      1595 - Definitions of Managed Objects for the SONET/SDH Interface
             Type

             A Proposed Standard protocol.

      1594 - FYI on Questions and Answers - Answers to Commonly asked
             "New Internet User" Questions

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

      1593 - SNA APPN Node MIB

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

      1592 - Simple Network Management Protocol Distributed Protocol
             Interface Version 2.0

             An Experimental protocol.

      1591 - Domain Name System Structure and Delegation

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

      1590 - Media Type Registration Procedure

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

      1589 - A Kernel Model for Precision Timekeeping

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





Internet Architecture Board                                    [Page 14]

RFC 1600                   Internet Standards                 March 1994


      1588 - White Pages Meeting Report

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

      1587 - Not yet issued.

      1586 - Not yet issued.

      1585 - Not yet issued.

      1584 - not yet issued.

      1583 - Not yet issued.

      1582 - Extensions to RIP to Support Demand Circuits

             A Proposed Standard protocol.

      1581 - Protocol Analysis for Extensions to RIP to Support Demand
             Circuits

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

      1580 - Not yet issued.

      1579 - Firewall-Friendly FTP

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

      1578 - FYI on Questions and Answers - Answers to Commonly Asked
             "Primary and Secondary School Internet User" Questions

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

      1577 - Classical IP and ARP over ATM

             A Proposed Standard protocol.

      1576 - TN3270 Current Practices

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





Internet Architecture Board                                    [Page 15]

RFC 1600                   Internet Standards                 March 1994


      1575 - An Echo Function for CLNP (ISO 8473)

             A Draft Standard protocol.

      1574 - Essential Tools for the OSI Internet

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

      1573 - Evolution of the Interfaces Group of MIB-II

             A Proposed Standard protocol.

      1572 - Telnet Environment Option

             A Proposed Standard protocol.

      1571 - Telnet Environment Option Interoperability Issues

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

      1570 - PPP LCP Extensions

             A Proposed Standard protocol.

      1569 - Principles of Operation for the TPC.INT Subdomain: Radio
             Paging -- Technical Procedures

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

      1568 - Simple Network Paging Protocol - Version 1(b)

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

      1567 - X.500 Directory Monitoring MIB

             A Proposed Standard protocol.

      1566 - Mail Monitoring MIB

             A Proposed Standard protocol.

      1565 - Network Services Monitoring MIB

             A Proposed Standard protocol.



Internet Architecture Board                                    [Page 16]

RFC 1600                   Internet Standards                 March 1994


      1564 - DSA Metrics (OSI-DS 34 (v3))

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

      1563 - The text/enriched MIME Content-type

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

      1562 - Naming Guidelines for the AARNet X.500 Directory Service

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

      1561 - Use of ISO CLNP in TUBA Environments

             An Experimental protocol.

      1560 - The MultiProtocol Internet

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

      1559 - DECnet Phase IV MIB Extensions