rfc1920.txt

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

          Standard, or Draft Standard must come from the IESG, only.




Internet Architecture Board Standards Track                    [Page 11]

RFC 1920                   Internet Standards                 March 1996


      (3) Refer to an Area Director for review by a WG.  Expect to see
          the document again only after approval by the IESG.

      (4) Notify both the IESG and IRSG.  If no concerns are raised in
          two weeks then do Discretion (5), else RFC Editor to resolve
          the concerns or do Refer (3).

      (5) RFC Editor's discretion.  The RFC Editor decides if a review
          is needed and if so by whom.  RFC Editor decides to publish or
          not.

   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 Standards Track                    [Page 12]

RFC 1920                   Internet Standards                 March 1996


         |
         +<----------------------------------------------+
         |                                               ^
         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 Standards Track                    [Page 13]

RFC 1920                   Internet Standards                 March 1996


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:

      1920 - Internet Official Protocol Standards

             This memo.

      1918 - Address Allocation for Private Internets

             This is a Best Current Practices document and does not
             specify any level of standard.

      1917 - An Appeal to the Internet Community to Return Unused IP
             Networks (Prefixes) to the IANA

             This is a Best Current Practices document and does not
             specify any level of standard.

      1916 - Enterprise Renumbering: Experience and Information
             Solicitation

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

      1915 - Variance for The PPP Connection Control Protocol and The
             PPP Encryption Control Protocol

             This is a Best Current Practices document and does not
             specify any level of standard.

      1914 - How to Interact with a Whois++ Mesh

             A Proposed Standard protocol.

      1913 - Architecture of the Whois++ Index Service

             A Proposed Standard protocol.

      1912 - Common DNS Operational and Configuration Errors

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



Internet Architecture Board Standards Track                    [Page 14]

RFC 1920                   Internet Standards                 March 1996


      1911 - Voice Profile for Internet Mail

             An Experimental protocol.

      1910 - User-based Security Model for SNMPv2

             An Experimental protocol.

      1909 - An Administrative Infrastructure for SNMPv2

             An Experimental protocol.

      1908 - Coexistence between Version 1 and Version 2 of the
             Internet-standard Network Management Framework

             A Draft Standard protocol.

      1907 - Management Information Base for Version 2 of the Simple
             Network Management Protocol (SNMPv2)

             A Draft Standard protocol.

      1906 - Transport Mappings for Version 2 of the Simple Network
             Management Protocol (SNMPv2)

             A Draft Standard protocol.

      1905 - Protocol Operations for Version 2 of the Simple Network
             Management Protocol (SNMPv2)

             A Draft Standard protocol.

      1904 - Conformance Statements for Version 2 of the Simple Network
             Management Protocol (SNMPv2)

             A Draft Standard protocol.

      1903 - Textual Conventions for Version 2 of the Simple Network
             Management Protocol (SNMPv2)

             A Draft Standard protocol.

      1902 - Structure of Management Information for Version 2 of the
             Simple Network Management Protocol (SNMPv2)

             A Draft Standard protocol.





Internet Architecture Board Standards Track                    [Page 15]

RFC 1920                   Internet Standards                 March 1996


      1901 - Introduction to Community-based SNMPv2

             An Experimental protocol.

      1900 - Renumbering Needs Work

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

      1899 - not yet issued.

      1898 - CyberCash Credit Card Protocol Version 0.8

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

      1897 - IPv6 Testing Address Allocation

             An Experimental protocol.

      1896 - The text/enriched MIME Content-type

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

      1895 - The Application/CALS-1840 Content-type

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

      1894 - An Extensible Message Format for Delivery Status
             Notifications

             A Proposed Standard protocol.

      1893 - Enhanced Mail System Status Codes

             A Proposed Standard protocol.

      1892 - The Multipart/Report Content Type for the Reporting of Mail
             System Administrative Messages

             A Proposed Standard protocol.

      1891 - SMTP Service Extension for Delivery Status Notifications

             A Proposed Standard protocol.




Internet Architecture Board Standards Track                    [Page 16]

RFC 1920                   Internet Standards                 March 1996


      1890 - RTP Profile for Audio and Video Conferences with Minimal
             Control

             A Proposed Standard protocol.

      1889 - RTP: A Transport Protocol for Real-Time Applications

             A Proposed Standard protocol.

      1888 - not yet issued.

      1887 - An Architecture for IPv6 Unicast Address Allocation

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