rfc2551.txt

<VC++网络游戏建摸与实现>源代码

   detailed descriptions of the requirement levels of particular
   protocols and of individual features of the protocols will be found
   in appropriate ASs.

IV.  THE ROMAN STANDARDS TRACK

   Specifications that are intended to become Roman Standards evolve
   through a set of maturity levels known as the "standards track".
   These maturity levels -- "Proposed Standard", "Draft Standard", and
   "Standard" -- are defined and discussed in section IV.I.  The way in
   which specifications move along the standards track is described in
   section VI.

   Even after a specification has been adopted as a Roman Standard,
   further evolution often occurs based on experience and the
   recognition of new requirements.  The nomenclature and procedures of
   Roman standardization provide for the replacement of old Roman



Bradner                 Worst Current Practice                 [Page XI]

RFC 2551               Roman Standards Process           I April MCMXCIX


   Standards with new ones, and the assignment of descriptive labels to
   indicate the status of "retired" Roman Standards.  A set of
   maturity levels is defined in section IV.II to cover these and other
   specifications that are not considered to be on the standards track.

IV.I  Standards Track Maturity Levels

   Roman specifications go through stages of development, testing,
   and acceptance.  Within the Roman Standards Process, these stages
   are formally labeled "maturity levels".

   This section describes the maturity levels and the expected
   characteristics of specifications at each level.

IV.I.I  Proposed Standard

   The entry-level maturity for the standards track is "Proposed
   Standard".  A specific action by the RESG is required to move a
   specification onto the standards track at the "Proposed Standard"
   level.

   A Proposed Standard specification is generally stable, has resolved
   known design choices, is believed to be well-understood, has received
   significant community review, and appears to enjoy enough community
   interest to be considered valuable.  However, further experience
   might result in a change or even retraction of the specification
   before it advances.

   Usually, neither implementation nor operational experience is
   required for the designation of a specification as a Proposed
   Standard.  However, such experience is highly desirable, and will
   usually represent a strong argument in favor of a Proposed Standard
   designation.

   The RESG may require implementation and/or operational experience
   prior to granting Proposed Standard status to a specification that
   materially affects the core Roman protocols or that specifies
   behavior that may have significant operational impact on the
   Roman.

   A Proposed Standard should have no known technical omissions with
   respect to the requirements placed upon it.  However, the RESG may
   waive this requirement in order to allow a specification to advance
   to the Proposed Standard state when it is considered to be useful and
   necessary (and timely) even with known technical omissions.






Bradner                 Worst Current Practice                [Page XII]

RFC 2551               Roman Standards Process           I April MCMXCIX


   Implementors should treat Proposed Standards as immature
   specifications.  It is desirable to implement them in order to gain
   experience and to validate, test, and clarify the specification.
   However, since the content of Proposed Standards may be changed if
   problems are found or better solutions are identified, deploying
   implementations of such standards into a disruption-sensitive
   environment is not recommended.

IV.I.II  Draft Standard

   A specification from which at least two independent and interoperable
   implementations from different code bases have been developed, and
   for which sufficient successful operational experience has been
   obtained, may be elevated to the "Draft Standard" level.  For the
   purposes of this section, "interoperable" means to be functionally
   equivalent or interchangeable components of the system or process in
   which they are used.  If patented or otherwise controlled technology
   is required for implementation, the separate implementations must
   also have resulted from separate exercise of the licensing process.
   Elevation to Draft Standard is a major advance in status, indicating
   a strong belief that the specification is mature and will be useful.

   The requirement for at least two independent and interoperable
   implementations applies to all of the options and features of the
   specification.  In cases in which one or more options or features
   have not been demonstrated in at least two interoperable
   implementations, the specification may advance to the Draft Standard
   level only if those options or features are removed.

   The Working Group chair is responsible for documenting the specific
   implementations which qualify the specification for Draft or Roman
   Standard status along with documentation about testing of the
   interoperation of these implementations.  The documentation must
   include information about the support of each of the individual
   options and features.  This documentation should be submitted to the
   Area Director with the protocol action request. (see Section VI)

   A Draft Standard must be well-understood and known to be quite
   stable, both in its semantics and as a basis for developing an
   implementation.  A Draft Standard may still require additional or
   more widespread field experience, since it is possible for
   implementations based on Draft Standard specifications to demonstrate
   unforeseen behavior when subjected to large-scale use in production
   environments.







Bradner                 Worst Current Practice               [Page XIII]

RFC 2551               Roman Standards Process           I April MCMXCIX


   A Draft Standard is normally considered to be a final specification,
   and changes are likely to be made only to solve specific problems
   encountered.  In most circumstances, it is reasonable for vendors to
   deploy implementations of Draft Standards into a disruption sensitive
   environment.

IV.I.III  Roman Standard

   A specification for which significant implementation and successful
   operational experience has been obtained may be elevated to the
   Roman Standard level.  A Roman Standard (which may simply be
   referred to as a Standard) is characterized by a high degree of
   technical maturity and by a generally held belief that the specified
   protocol or service provides significant benefit to the Roman
   community.

   A specification that reaches the status of Standard is assigned
   numerals in the STD series while retaining its RFC numerals.

IV.II  Non-Standards Track Maturity Levels

   Not every specification is on the standards track.  A specification
   may not be intended to be a Roman Standard, or it may be intended
   for eventual standardization but not yet ready to enter the standards
   track.  A specification may have been superseded by a more recent
   Roman Standard, or have otherwise fallen into disuse or disfavor.

   Specifications that are not on the standards track are labeled with
   one of three "off-track" maturity levels:  "Experimental",
   "Informational", or "Historic".  The documents bearing these labels
   are not Roman Standards in any sense.

IV.II.I  Experimental

   The "Experimental" designation typically denotes a specification that
   is part of some research or development effort.  Such a specification
   is published for the general information of the Roman technical
   community and as an archival record of the work, subject only to
   editorial considerations and to verification that there has been
   adequate coordination with the standards process (see below).  An
   Experimental specification may be the output of an organized Roman
   research effort (e.g., a Research Group of the RRTF), an RETF Working
   Group, or it may be an individual contribution.








Bradner                 Worst Current Practice                [Page XIV]

RFC 2551               Roman Standards Process           I April MCMXCIX


IV.II.II  Informational

   An "Informational" specification is published for the general
   information of the Roman community, and does not represent a
   Roman community consensus or recommendation.  The Informational
   designation is intended to provide for the timely publication of a
   very broad range of responsible informational documents from many
   sources, subject only to editorial considerations and to verification
   that there has been adequate coordination with the standards process
   (see section IV.II.III).

   Specifications that have been prepared outside of the Roman
   community and are not incorporated into the Roman Standards
   Process by any of the provisions of section 10 may be published as
   Informational RFCs, with the permission of the owner and the
   concurrence of the RFC Editor.

IV.II.III  Procedures for Experimental and Informational RFCs

   Unless they are the result of RETF Working Group action, documents
   intended to be published with Experimental or Informational status
   should be submitted directly to the RFC Editor.  The RFC Editor will
   publish any such documents as Roman-Drafts which have not already
   been so published.  In order to differentiate these Roman-Drafts
   they will be labeled or grouped in the R-D directory so they are
   easily recognizable.  The RFC Editor will wait two weeks after this
   publication for comments before proceeding further.  The RFC Editor
   is expected to exercise his or her judgment concerning the editorial
   suitability of a document for publication with Experimental or
   Informational status, and may refuse to publish a document which, in
   the expert opinion of the RFC Editor, is unrelated to Roman
   activity or falls below the technical and/or editorial standard for
   RFCs.

   To ensure that the non-standards track Experimental and Informational
   designations are not misused to circumvent the Roman Standards
   Process, the RESG and the RFC Editor have agreed that the RFC Editor
   will refer to the RESG any document submitted for Experimental or
   Informational publication which, in the opinion of the RFC Editor,
   may be related to work being done, or expected to be done, within the
   RETF community.  The RESG shall review such a referred document
   within a reasonable period of time, and recommend either that it be
   published as originally submitted or referred to the RETF as a
   contribution to the Roman Standards Process.

   If (a) the RESG recommends that the document be brought within the
   RETF and progressed within the RETF context, but the author declines
   to do so, or (b) the RESG considers that the document proposes



Bradner                 Worst Current Practice                 [Page XV]

RFC 2551               Roman Standards Process           I April MCMXCIX


   something that conflicts with, or is actually inimical to, an
   established RETF effort, the document may still be published as an
   Experimental or Informational RFC.  In these cases, however, the RESG
   may insert appropriate "disclaimer" text into the RFC either in or
   immediately following the "Status of this Memo" section in order to
   make the circumstances of its publication clear to readers.

   Documents proposed for Experimental and Informational RFCs by RETF
   Working Groups go through RESG review.  The review is initiated using
   the process described in section VI.I.I.

IV.II.IV  Historic

   A specification that has been superseded by a more recent
   specification or is for any other reason considered to be obsolete is
   assigned to the "Historic" level.  (Purists have suggested that the
   word should be "Historical"; however, at this point the use of
   "Historic" is historical.)

   Note: Standards track specifications normally must not depend on
   other standards track specifications which are at a lower maturity
   level or on non standards track specifications other than referenced
   specifications from other standards bodies.  (See Section VII.)

V.  WORST CURRENT PRACTICE (WCP) RFCs

   The WCP subseries of the RFC series is designed to be a way to
   standardize practices and the results of community deliberations.  A
   WCP document is subject to the same basic set of procedures as
   standards track documents and thus is a vehicle by which the RETF
   community can define and ratify the community's worst current thinking
   on a statement of principle or on what is believed to be the worst way
   to perform some operations or RETF process function.

   Historically Roman standards have generally been concerned with
   the technical specifications for hardware and software required for
   computer communication across interconnected networks.  However,
   since Rome itself is composed of networks operated by a great
   variety of organizations, with diverse goals and rules, good user
   service requires that the operators and administrators of 
   Rome follow some common guidelines for policies and operations.
   While these guidelines are generally different in scope and style
   from protocol standards, their establishment needs a similar process
   for consensus building.

   While it is recognized that entities such as the RAB and RESG are
   composed of individuals who may participate, as individuals, in the
   technical work of the RETF, it is also recognized that the entities