rfc1500.txt

RFC 的详细文档！

   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 1500                   Internet Standards                August 1993


         |
         +<----------------------------------------------+
         |                                               ^
         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 1500                   Internet Standards                August 1993


6.  The Protocols

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

6.1.  Recent Changes

6.1.1.  New RFCs:

      1501 - OS/2 User Group

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

      1500 - This memo.

      1499 - Not yet issued.

      1498 - On the Naming and Binding of Network Destinations

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

      1497 - BOOTP Vendor Information Extensions

             This memo is a status report on BOOTP types and is a part
             of the BOOTP specification which is currently a Draft
             Standard.

      1496 - Rules for Downgrading Messages from X.400/88 to X.400/84
             When MIME Content-Types are Present in the Messages

             A Proposed Standard protocol.

      1495 - Mapping between X.400 and RFC-822 Message Bodies

             A Proposed Standard protocol.

      1494 - Equivalences between 1988 X.400 and RFC-822 Message Bodies

             A Proposed Standard protocol.

      1493 - Definitions of Managed Objects for Bridges

             A Draft Standard protocol.






Internet Architecture Board                                    [Page 14]

RFC 1500                   Internet Standards                August 1993


      1492 - An Access Control Protocol, Sometimes Called TACACS

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

      1491 - A Survey of Advanced Usages of X.500

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

      1490 - Multiprotocol Interconnect over Frame Relay

             A Draft Standard protocol.

      1489 - Registration of a Cyrillic Character Set

             This document defines a character set, and is referenced by
             "Assigned Numbers" (STD 2).

      1488 - The X.500 String Representation of Standard
             Attribute Syntaxes

             A Proposed Standard protocol.

      1487 - X.500 Lightweight Directory Access Protocol

             A Proposed Standard protocol.

      1486 - An Experiment in Remote Printing

             An Experimental protocol.

      1485 - A String Representation of Distinguished Names (OSI-DS 23
             (v5))

             A Proposed Standard protocol.

      1484 - Using the OSI Directory to achieve User Friendly
             Naming (OSI-DS 24 (v1.2))

             An Experimental protocol.

      1483 - Multiprotocol Encapsulation over ATM Adaptation Layer 5

             A Proposed Standard protocol.






Internet Architecture Board                                    [Page 15]

RFC 1500                   Internet Standards                August 1993


      1482 - Aggregation Support in the NSFNET Policy-Based Routing
             Database

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

      1481 - IAB Recommendation for an Intermediate Strategy to Address
             the Issue of Scaling

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

      1480 - The US Domain

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

      1479 - Inter-Domain Policy Routing Protocol Specification:
             Version-1

             A Proposed Standard protocol.

      1478 - An Architecture for Inter-Domain Policy Routing

             A Proposed Standard protocol.

      1477 - IDPR as a Proposed Standard

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

      1476 - RAP: Internet Route Access Protocol

             An Experimental protocol.

      1475 - TP/IX: The Next Internet

             An Experimental protocol.

      1474 - The Definitions of Managed Objects for the Bridge Network
             Control Protocol of the Point-to-Point Protocol

             A Proposed Standard protocol.

      1473 - The Definitions of Managed Objects for the IP Network
             Control Protocol of the Point-to-Point Protocol

             A Proposed Standard protocol.



Internet Architecture Board                                    [Page 16]

RFC 1500                   Internet Standards                August 1993


      1472 - The Definitions of Managed Objects for the Security
             Protocols of the Point-to-Point Protocol

             A Proposed Standard protocol.

      1471 - The Definitions of Managed Objects for the Link Control
             Protocol of the Point-to-Point Protocol

             A Proposed Standard protocol.

      1470 - FYI on a Network Management Tool Catalog: Tools for
             Monitoring and Debugging TCP/IP Internets and
             Interconnected Devices

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

      1469 - IP Multicast over Token-Ring Local Area Networks

             A Proposed Standard protocol.

      1468 - Japanese Character Encoding for Internet Messages

             This document defines a character set, and is referenced by
             "Assigned Numbers" (STD 2).

      1467 - Status of CIDR Deployment in the Internet

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

      1466 - Guidelines for Management of IP Address Space

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

      1465 - Routing Coordination for X.400 MHS Services Within a Multi
             Protocol / Multi Network Environment Table Format V3 for
             Static Routing

             An Experimental protocol.

      1464 - Using the Domain Name System To Store Arbitrary String
             Attributes

             An Experimental protocol.