rfc1610.txt

RFC 的详细文档！

Internet Architecture Board                                    [Page 11]

RFC 1610                   Internet Standards                  July 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 1610                   Internet Standards                  July 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 1610                   Internet Standards                  July 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:

      1640 - The Process for Organization of Internet Standards Working
             Group (POISED)

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

      1639 - FTP Operation Over Big Address Records (FOOBAR)

             An Experimental protocol.

      1638 - PPP Bridging Control Protocol (BCP)

             A Proposed Standard protocol.

      1637 - DNS NSAP Resource Records

             An Experimental protocol.

      1636 - Report of IAB Workshop on Security in the Internet
             Architecture - February 8-10, 1994

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

      1635 - How to Use Anonymous FTP

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

      1634 - Novell IPX Over Various WAN Media (IPXWAN)

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

      1633 - Integrated Services in the Internet Architecture: an
             Overview

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



Internet Architecture Board                                    [Page 14]

RFC 1610                   Internet Standards                  July 1994


      1632 - A Revised Catalog of Available X.500 Implementations

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

      1631 - The IP Network Address Translator (NAT)

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

      1630 - Universal Resource Identifiers in WWW: A Unifying Syntax
             for the Expression of Names and Addresses of Objects on the
             Network as used in the World-Wide Web

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

      1629 - Guidelines for OSI NSAP Allocation in the Internet

             A Draft Standard protocol.

      1628 - UPS Management Information Base

             A Proposed Standard protocol.

      1627 - Network 10 Considered Harmful (Some Practices Shouldn't be
             Codified)

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

      1626 - Default IP MTU for use over ATM AAL5

             A Proposed Standard protocol.

      1625 - WAIS over Z39.50-1988

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

      1624 - Computation of the Internet Checksum via Incremental Update

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

      1623 - Definitions of Managed Objects for the Ethernet-like
             Interface Types




Internet Architecture Board                                    [Page 15]

RFC 1610                   Internet Standards                  July 1994


             A Standard protocol.

      1622 - Pip Header Processing

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

      1621 - Pip Near-term Architecture

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

      1620 - Internet Architecture Extensions for Shared Media

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

      1619 - PPP over SONET/SDH

             A Proposed Standard protocol.

      1618 - PPP over ISDN

             A Proposed Standard protocol.

      1617 - Naming and Structuring Guidelines for X.500 Directory
             Pilots

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

      1616 - X.400(1988) for the Academic and Research Community in
             Europe

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

      1615 - Migrating from X.400(84) to X.400(88)

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

      1614 - Network Access to Multimedia Information

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





Internet Architecture Board                                    [Page 16]

RFC 1610                   Internet Standards                  July 1994


      1613 - cisco Systems X.25 over TCP (XOT)

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

      1612 - DNS Resolver MIB Extensions

             A Proposed Standard protocol.

      1611 - DNS Server MIB Extensions

             A Proposed Standard protocol.

      1610 - This memo.

      1609 - Charting Networks in the X.500 Directory

             An Experimental protocol.

      1608 - Representing IP Information in the X.500 Directory

             An Experimental protocol.