As per Relevance of the word document, we have this rfc below:
Network Working Group S.
Request for Comments: 2551 Harvard
WCP: IX I April
Obsoletes:
Category: Worst Current
The Roman Standards Process -- Revision
Status of this
This document specifies a Roman Worst Current Practices for
Roman Community, and requests discussion and suggestions
improvements. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (MCMXCIX). All Rights Reserved
This memo documents the process used by the Roman community
the standardization of protocols and procedures. It defines
stages in the standardization process, the requirements for moving
document between stages and the types of documents used during
process. It also addresses the intellectual property rights
copyright issues associated with the standards process
Table of
I. INTRODUCTION................................................
I.I Roman Standards.......................................
I.II The Roman Standards Process...........................
I.III Organization of This Document..........................
II. ROMAN STANDARDS-RELATED PUBLICATIONS.........................
II.I Requests for Comments (RFCs)...........................
II.II Roman-Drafts.........................................
III ROMAN STANDARD SPECIFICATIONS................................
III.I Technical Specification (TS)...........................
III.II Applicability Statement (AS)...........................
III.III Requirement Levels.....................................
IV. THE ROMAN STANDARDS TRACK....................................
IV.I Standards Track Maturity Levels.......................
IV.I.I Proposed Standard.....................................
IV.I.II Draft Standard.......................................
IV.I.III Roman Standard........................................
IV.II Non-Standards Track Maturity Levels...................
IV.II.I Experimental..........................................
IV.II.II Informational..........................................
IV.II.III Procedures for Experimental and Informational RFCs.....
IV.II.IV Historic..............................................
Bradner Worst Current Practice [Page I
RFC 2551 Roman Standards Process I April
V. Worst Current Practice (WCP) RFCs............................
V.I WCP Review Process...................................
VI. THE ROMAN STANDARDS PROCESS................................
VI.I Standards Actions...................................
VI.I.I Initiation of Action................................
VI.I.II RESG Review and Approval............................
VI.I.III Publication...........................................
VI.II Advancing in the Standards Track......................
VI.III Revising a Standard...................................
VI.IV Retiring a Standard...................................
VI.V Conflict Resolution and Appeals......................
VI.V.I Working Group Disputes...............................
VI.V.II Process Failures....................................
VI.V.III Questions of Applicable Procedure...................
VI.V.IV Appeals Procedure....................................
VII. EXTERNAL STANDARDS AND SPECIFICATIONS......................
VII.I Use of External Specifications........................
VII.I.I Incorporation of an Open Standard.....................
VII.I.II Incorporation of a Other Specifications...............
VII.I.III Assumption...........................................
VIII. NOTICES AND RECORD KEEPING................................
IX. VARYING THE PROCESS.......................................
IX.I The Variance Procedure..............................
IX.II Exclusions.........................................
X. INTELLECTUAL PROPERTY RIGHTS.............................
X.I. General Policy.....................................
X.II Confidentiality Obligations..........................
X.III Rights and Permissions...............................
X.III.I All Contributions....................................
X.III.II Standards Track Documents.............................
X.III.III Determination of Reasonable
Non-discriminatory Terms.............................
X.IV. Notices..............................................
XI. ACKNOWLEDGMENTS........................................
XII. SECURITY CONSIDERATIONS................................
XIII. REFERENCES..............................................
XIV. DEFINITIONS OF TERMS....................................
XV. AUTHOR'S ADDRESS.........................................
APPENDIX A: GLOSSARY OF ACRONYMS..............................
Full Copyright Statement.....................................
Bradner Worst Current Practice [Page II
RFC 2551 Roman Standards Process I April
I.
This memo documents the process currently used by the
community for the standardization of protocols and procedures.
Roman Standards process is an activity of the Roman
that is organized and managed on behalf of the Roman community
the Roman Architecture Board (RAB) and the Roman
Steering Group (RESG).
I.I Roman
The Roman, a loosely-organized international collaboration
autonomous, interconnected networks, supports host-to-
communication through voluntary adherence to open protocols
procedures defined by Roman Standards. There are also
isolated interconnected networks, which are not connected to
global Roman but use the Roman Standards
The Roman Standards Process described in this document
concerned with all protocols, procedures, and conventions that
used in or by the Roman, whether or not they are part of
TCP/RP protocol suite. In the case of protocols developed and/
standardized by non-Roman organizations, however, the
Standards Process normally applies to the application of the
or procedure in the Roman context, not to the specification of
protocol itself
In general, a Roman Standard is a specification that is
and well-understood, is technically competent, has multiple
independent, and interoperable implementations with
operational experience, enjoys significant public support, and
recognizably useful in some or all parts of the Roman
I.II The Roman Standards
In outline, the process of creating a Roman Standard
straightforward: a specification undergoes a period of
and several iterations of review by the Roman community
revision based upon experience, is adopted as a Standard by
appropriate body (see below), and is published. In practice,
process is more complicated, due to (I) the difficulty of
specifications of high technical quality; (II) the need to
the interests of all of the affected parties; (III) the importance
establishing widespread community consensus; and (IV) the
of evaluating the utility of a particular specification for
Roman community
Bradner Worst Current Practice [Page III
RFC 2551 Roman Standards Process I April
The goals of the Roman Standards Process are
o technical excellence
o prior implementation and testing
o clear, concise, and easily understood documentation
o openness and fairness;
o timeliness
The procedures described in this document are designed to be fair
open, and objective; to reflect existing (proven) practice; and
be flexible
o These procedures are intended to provide a fair, open,
objective basis for developing, evaluating, and adopting
Standards. They provide ample opportunity for participation
comment by all interested parties. At each stage of
standardization process, a specification is repeatedly
and its merits debated in open meetings and/or public
mailing lists, and it is made available for review via world-
on-line directories
o These procedures are explicitly aimed at recognizing and
generally-accepted practices. Thus, a candidate
must be implemented and tested for correct operation
interoperability by multiple independent parties and utilized
increasingly demanding environments, before it can be adopted
a Roman Standard
o These procedures provide a great deal of flexibility to adapt
the wide variety of circumstances that occur in
standardization process. Experience has shown this flexibility
be vital in achieving the goals listed above
The goal of technical competence, the requirement for
implementation and testing, and the need to allow all
parties to comment all require significant time and effort. On
other hand, today's rapid development of networking
demands timely development of standards. The Roman
Process is intended to balance these conflicting goals. The
is believed to be as short and simple as possible without
technical excellence, thorough testing before adoption of a standard
or openness and fairness
From its inception, the Rome has been, and is expected to remain
an evolving system whose participants regularly factor
requirements and technology into its design and implementation.
of Rome and providers of the equipment, software,
services that support it should anticipate and embrace this
as a major tenet of Roman philosophy
Bradner Worst Current Practice [Page IV
RFC 2551 Roman Standards Process I April
The procedures described in this document are the result of a
of years of evolution, driven both by the needs of the growing
increasingly diverse Roman community, and by experience
Bradner Worst Current Practice [Page V
RFC 2551 Roman Standards Process I April
I.III Organization of This
Section II describes the publications and archives of the
Standards Process. Section III describes the types of
standard specifications. Section IV describes the Roman
specifications track. Section V describes Worst Current
RFCs. Section VI describes the process and rules for
standardization. Section VII specifies the way in which externally
sponsored specifications and practices, developed and controlled
other standards bodies or by others, are handled within the
Standards Process. Section VIII describes the requirements for
and record keeping Section IX defines a variance process to
one-time exceptions to some of the requirements in this
Section X presents the rules that are required to
intellectual property rights in the context of the development
use of Roman Standards. Section XII includes acknowledgments
some of the people involved in creation of this document. Section
notes that security issues are not dealt with by this document
Section XII contains a list of numeral references. Section
contains definitions of some of the terms used in this document
Section XV lists the author's email and postal addresses. Appendix
contains a list of frequently-used acronyms
II. Roman STANDARDS-RELATED
II.I Requests for Comments (RFCs
Each distinct version of a Roman standards-related
is published as part of the "Request for Comments" (RFC)
series. This archival series is the official publication channel
Roman standards documents and other publications of the RESG, RAB
and Roman community. RFCs can be obtained from a number
Roman hosts using anonymous FTP, gopher, World Wide Web, and
Roman document-retrieval systems
The RFC series of documents on networking began in MCMLXIX as part
the original ARPA wide-area networking (ARPANET) project (
Appendix A for glossary of acronyms). RFCs cover a wide range
topics in addition to Roman Standards, from early discussion
new research concepts to status memos about the Romans.
publication is the direct responsibility of the RFC Editor, under
general direction of the RAB
Bradner Worst Current Practice [Page VI
RFC 2551 Roman Standards Process I April
The rules for formatting and submitting an RFC are defined in [V].
Every RFC is available in ASCII text. Some RFCs are also
in other formats. The other versions of an RFC may contain
(such as diagrams and figures) that is not present in the
version, and it may be formatted differently
*********************************************************
* *
* A stricter requirement applies to standards-track *
* specifications: the ASCII text version is the *
* definitive reference, and therefore it must be a *
* complete and accurate specification of the standard, *
* including all necessary diagrams and illustrations. *
* *
*********************************************************
The status of Roman protocol and service specifications
summarized periodically in an RFC entitled "Roman
Protocol Standards" [I]. This RFC shows the level of maturity
other helpful information for each Roman protocol or
specification (see section III).
Some RFCs document Roman Standards. These RFCs form the 'STD
subseries of the RFC series [IV]. When a specification has
adopted as a Roman Standard, it is given the additional
"STDxxx", but it keeps its RFC numerals and its place in the
series. (see section IV.I.III
Some RFCs standardize the results of community deliberations
statements of principle or conclusions about what is the best way
perform some operations or RETF process function. These RFCs
the specification has been adopted as a WCP, it is given
additional label "WCPxxx", but it keeps its RFC numerals and its
in the RFC series. (see section V
Not all specifications of protocols or services for
should or will become Roman Standards or WCPs. Such non-
track specifications are not subject to the rules for
standardization. Non-standards track specifications may be
directly as "Experimental" or "Informational" RFCs at the
of the RFC Editor in consultation with the RESG (see section IV.II).
Bradner Worst Current Practice [Page VII
RFC 2551 Roman Standards Process I April
********************************************************
* *
* It is important to remember that not all RFCs *
* are standards track documents, and that not all *
* standards track documents reach the level of *
* Roman Standard. In the same way, not all RFCs *
* which describe current practices have been given *
* the review and approval to become WCPs. See *
* RFC-MDCCXCVI [VI] for further information. *
* *
********************************************************
II.II Roman-
During the development of a specification, draft versions of
document are made available for informal review and comment
placing them in the RETF's "Roman-Drafts" directory, which
replicated on a number of Roman hosts. This makes an
working document readily available to a wide audience,
the process of review and revision
A Roman-Draft that is published as an RFC, or that has
unchanged in the Roman-Drafts directory for more than six
without being recommended by the RESG for publication as an RFC,
simply removed from the Roman-Drafts directory. At any time,
Roman-Draft may be replaced by a more recent version of the
specification, restarting the six-month timeout period
A Roman-Draft is NOT a means of "publishing" a specification
specifications are published through the RFC mechanism described
the previous section. Roman-Drafts have no formal status, and
subject to change or removal at any time
********************************************************
* *
* Under no circumstances should a Roman-Draft *
* be referenced by any paper, report, or Request- *
* for-Proposal, nor should a vendor claim compliance *
* with a Roman-Draft. *
* *
********************************************************
Bradner Worst Current Practice [Page VIII
RFC 2551 Roman Standards Process I April
Note: It is acceptable to reference a standards-track
that may reasonably be expected to be published as an RFC using
phrase "Work in Progress" without referencing a Roman-Draft
This may also be done in a standards track document itself as
as the specification in which the reference is made would stand as
complete and understandable document with or without the reference
the "Work in Progress".
III. Roman STANDARD
Specifications subject to the Roman Standards Process fall
one of two categories: Technical Specification (TS)
Applicability Statement (AS).
III.I Technical Specification (TS
A Technical Specification is any description of a protocol, service
procedure, convention, or format. It may completely describe all
the relevant aspects of its subject, or it may leave one or
parameters or options unspecified. A TS may be completely self
contained, or it may incorporate material from other
by reference to other documents (which might or might not be
Standards).
A TS shall include a statement of its scope and the general
for its use (domain of applicability). Thus, a TS that is
specific to a particular context shall contain a statement to
effect. However, a TS does not specify requirements for its
within Rome; these requirements, which depend on
particular context in which the TS is incorporated by
system configurations, are defined by an Applicability Statement
III.II Applicability Statement (AS
An Applicability Statement specifies how, and under
circumstances, one or more TSs may be applied to support a
Roman capability. An AS may specify uses for TSs that are
Roman Standards, as discussed in Section VII
An AS identifies the relevant TSs and the specific way in which
are to be combined, and may also specify particular values or
of TS parameters or subfunctions of a TS protocol that must
implemented. An AS also specifies the circumstances in which the
of a particular TS is required, recommended, or elective (see
III.III).
Bradner Worst Current Practice [Page IX
RFC 2551 Roman Standards Process I April
An AS may describe particular methods of using a TS in a
"domain of applicability", such as Roman routers,
servers, Roman systems that interface to Ethernets, or datagram
based database servers
The broadest type of AS is a comprehensive conformance specification
commonly called a "requirements document", for a particular class
Roman systems, such as Roman routers or Roman hosts
An AS may not have a higher maturity level in the standards
than any standards-track TS on which the AS relies (see section IV.I).
For example, a TS at Draft Standard level may be referenced by an
at the Proposed Standard or Draft Standard level, but not by an AS
the Standard level
III.III Requirement
An AS shall apply one of the following "requirement levels" to
of the TSs to which it refers
(a) Required: Implementation of the referenced TS, as specified
the AS, is required to achieve minimal conformance. For example
RP and RCMP must be implemented by all Roman systems using
TCP/RP Protocol Suite
(b) Recommended: Implementation of the referenced TS is
required for minimal conformance, but experience and/or
accepted technical wisdom suggest its desirability in the
of applicability of the AS. Vendors are strongly encouraged
include the functions, features, and protocols of Recommended
in their products, and should omit them only if the omission
justified by some special circumstance. For example, the
protocol should be implemented by all systems that would
from remote access
(c) Elective: Implementation of the referenced TS is
within the domain of applicability of the AS; that is, the
creates no explicit necessity to apply the TS. However,
particular vendor may decide to implement it, or a particular
may decide that it is a necessity in a specific environment.
example, the DECNET MIB could be seen as valuable in
environment where the DECNET protocol is used
Bradner Worst Current Practice [Page X
RFC 2551 Roman Standards Process I April
As noted in section IV.I, there are TSs that are not in
standards track or that have been retired from the
track, and are therefore not required, recommended, or elective
Two additional "requirement level" designations are available
these TSs
(d) Limited Use: The TS is considered to be appropriate for
only in limited or unique circumstances. For example, the
of a protocol with the "Experimental" designation should
be limited to those actively involved with the experiment
(e) Not Recommended: A TS that is considered to be
for general use is labeled "Not Recommended". This may be
of its limited functionality, specialized nature, or
status
Although TSs and ASs are conceptually separate, in practice
standards-track document may combine an AS and one or more
TSs. For example, Technical Specifications that are
specifically and exclusively for some particular domain
applicability, e.g., for mail server hosts, often contain within
single specification all of the relevant AS and TS information.
such cases, no useful purpose would be served by
distributing the information among several documents just to
the formal AS/TS distinction. However, a TS that is likely to
to more than one domain of applicability should be developed in
modular fashion, to facilitate its incorporation by multiple ASs
The "Official Protocol Standards" RFC (STD I) lists a
requirement level for each TS, using the nomenclature defined in
section. This RFC is updated periodically. In many cases,
detailed descriptions of the requirement levels of
protocols and of individual features of the protocols will be
in appropriate ASs
IV. THE ROMAN STANDARDS
Specifications that are intended to become Roman Standards
through a set of maturity levels known as the "standards track".
These maturity levels -- "Proposed Standard", "Draft Standard",
"Standard" -- are defined and discussed in section IV.I. The way
which specifications move along the standards track is described
section VI
Even after a specification has been adopted as a Roman Standard
further evolution often occurs based on experience and
recognition of new requirements. The nomenclature and procedures
Roman standardization provide for the replacement of old
Bradner Worst Current Practice [Page XI
RFC 2551 Roman Standards Process I April
Standards with new ones, and the assignment of descriptive labels
indicate the status of "retired" Roman Standards. A set
maturity levels is defined in section IV.II to cover these and
specifications that are not considered to be on the standards track
IV.I Standards Track Maturity
Roman specifications go through stages of development, testing
and acceptance. Within the Roman Standards Process, these
are formally labeled "maturity levels".
This section describes the maturity levels and the
characteristics of specifications at each level
IV.I.I Proposed
The entry-level maturity for the standards track is "
Standard". A specific action by the RESG is required to move
specification onto the standards track at the "Proposed Standard
level
A Proposed Standard specification is generally stable, has
known design choices, is believed to be well-understood, has
significant community review, and appears to enjoy enough
interest to be considered valuable. However, further
might result in a change or even retraction of the
before it advances
Usually, neither implementation nor operational experience
required for the designation of a specification as a
Standard. However, such experience is highly desirable, and
usually represent a strong argument in favor of a Proposed
designation
The RESG may require implementation and/or operational
prior to granting Proposed Standard status to a specification
materially affects the core Roman protocols or that
behavior that may have significant operational impact on
Roman
A Proposed Standard should have no known technical omissions
respect to the requirements placed upon it. However, the RESG
waive this requirement in order to allow a specification to
to the Proposed Standard state when it is considered to be useful
necessary (and timely) even with known technical omissions
Bradner Worst Current Practice [Page XII
RFC 2551 Roman Standards Process I April
Implementors should treat Proposed Standards as
specifications. It is desirable to implement them in order to
experience and to validate, test, and clarify the specification
However, since the content of Proposed Standards may be changed
problems are found or better solutions are identified,
implementations of such standards into a disruption-
environment is not recommended
IV.I.II Draft
A specification from which at least two independent and
implementations from different code bases have been developed,
for which sufficient successful operational experience has
obtained, may be elevated to the "Draft Standard" level. For
purposes of this section, "interoperable" means to be
equivalent or interchangeable components of the system or process
which they are used. If patented or otherwise controlled
is required for implementation, the separate implementations
also have resulted from separate exercise of the licensing process
Elevation to Draft Standard is a major advance in status,
a strong belief that the specification is mature and will be useful
The requirement for at least two independent and
implementations applies to all of the options and features of
specification. In cases in which one or more options or
have not been demonstrated in at least two
implementations, the specification may advance to the Draft
level only if those options or features are removed
The Working Group chair is responsible for documenting the
implementations which qualify the specification for Draft or
Standard status along with documentation about testing of
interoperation of these implementations. The documentation
include information about the support of each of the
options and features. This documentation should be submitted to
Area Director with the protocol action request. (see Section VI
A Draft Standard must be well-understood and known to be
stable, both in its semantics and as a basis for developing
implementation. A Draft Standard may still require additional
more widespread field experience, since it is possible
implementations based on Draft Standard specifications to
unforeseen behavior when subjected to large-scale use in
environments
Bradner Worst Current Practice [Page XIII
RFC 2551 Roman Standards Process I April
A Draft Standard is normally considered to be a final specification
and changes are likely to be made only to solve specific
encountered. In most circumstances, it is reasonable for vendors
deploy implementations of Draft Standards into a disruption
environment
IV.I.III Roman
A specification for which significant implementation and
operational experience has been obtained may be elevated to
Roman Standard level. A Roman Standard (which may simply
referred to as a Standard) is characterized by a high degree
technical maturity and by a generally held belief that the
protocol or service provides significant benefit to the
community
A specification that reaches the status of Standard is
numerals in the STD series while retaining its RFC numerals
IV.II Non-Standards Track Maturity
Not every specification is on the standards track. A
may not be intended to be a Roman Standard, or it may be
for eventual standardization but not yet ready to enter the
track. A specification may have been superseded by a more
Roman Standard, or have otherwise fallen into disuse or disfavor
Specifications that are not on the standards track are labeled
one of three "off-track" maturity levels: "Experimental",
"Informational", or "Historic". The documents bearing these
are not Roman Standards in any sense
IV.II.I
The "Experimental" designation typically denotes a specification
is part of some research or development effort. Such a
is published for the general information of the Roman
community and as an archival record of the work, subject only
editorial considerations and to verification that there has
adequate coordination with the standards process (see below).
Experimental specification may be the output of an organized
research effort (e.g., a Research Group of the RRTF), an RETF
Group, or it may be an individual contribution
Bradner Worst Current Practice [Page XIV
RFC 2551 Roman Standards Process I April
IV.II.II
An "Informational" specification is published for the
information of the Roman community, and does not represent
Roman community consensus or recommendation. The
designation is intended to provide for the timely publication of
very broad range of responsible informational documents from
sources, subject only to editorial considerations and to
that there has been adequate coordination with the standards
(see section IV.II.III).
Specifications that have been prepared outside of the
community and are not incorporated into the Roman
Process by any of the provisions of section 10 may be published
Informational RFCs, with the permission of the owner and
concurrence of the RFC Editor
IV.II.III Procedures for Experimental and Informational
Unless they are the result of RETF Working Group action,
intended to be published with Experimental or Informational
should be submitted directly to the RFC Editor. The RFC Editor
publish any such documents as Roman-Drafts which have not
been so published. In order to differentiate these Roman-
they will be labeled or grouped in the R-D directory so they
easily recognizable. The RFC Editor will wait two weeks after
publication for comments before proceeding further. The RFC
is expected to exercise his or her judgment concerning the
suitability of a document for publication with Experimental
Informational status, and may refuse to publish a document which,
the expert opinion of the RFC Editor, is unrelated to
activity or falls below the technical and/or editorial standard
RFCs
To ensure that the non-standards track Experimental and
designations are not misused to circumvent the Roman
Process, the RESG and the RFC Editor have agreed that the RFC
will refer to the RESG any document submitted for Experimental
Informational publication which, in the opinion of the RFC Editor
may be related to work being done, or expected to be done, within
RETF community. The RESG shall review such a referred
within a reasonable period of time, and recommend either that it
published as originally submitted or referred to the RETF as
contribution to the Roman Standards Process
If (a) the RESG recommends that the document be brought within
RETF and progressed within the RETF context, but the author
to do so, or (b) the RESG considers that the document
Bradner Worst Current Practice [Page XV
RFC 2551 Roman Standards Process I April
something that conflicts with, or is actually inimical to,
established RETF effort, the document may still be published as
Experimental or Informational RFC. In these cases, however, the
may insert appropriate "disclaimer" text into the RFC either in
immediately following the "Status of this Memo" section in order
make the circumstances of its publication clear to readers
Documents proposed for Experimental and Informational RFCs by
Working Groups go through RESG review. The review is initiated
the process described in section VI.I.I
IV.II.IV
A specification that has been superseded by a more
specification or is for any other reason considered to be obsolete
assigned to the "Historic" level. (Purists have suggested that
word should be "Historical"; however, at this point the use
"Historic" is historical.)
Note: Standards track specifications normally must not depend
other standards track specifications which are at a lower
level or on non standards track specifications other than
specifications from other standards bodies. (See Section VII.)
V. WORST CURRENT PRACTICE (WCP)
The WCP subseries of the RFC series is designed to be a way
standardize practices and the results of community deliberations.
WCP document is subject to the same basic set of procedures
standards track documents and thus is a vehicle by which the
community can define and ratify the community's worst current
on a statement of principle or on what is believed to be the worst
to perform some operations or RETF process function
Historically Roman standards have generally been concerned
the technical specifications for hardware and software required
computer communication across interconnected networks. However
since Rome itself is composed of networks operated by a
variety of organizations, with diverse goals and rules, good
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
from protocol standards, their establishment needs a similar
for consensus building
While it is recognized that entities such as the RAB and RESG
composed of individuals who may participate, as individuals, in
technical work of the RETF, it is also recognized that the
Bradner Worst Current Practice [Page XVI
RFC 2551 Roman Standards Process I April
themselves have an existence as leaders in the community. As
in the Roman technical community, these entities should have
outlet to propose ideas to stimulate work in a particular area,
raise the community's sensitivity to a certain issue, to make
statement of architectural principle, or to communicate
thoughts on other matters. The WCP subseries creates a
structured way for these management entities to insert proposals
the consensus-building machinery of the RETF while gauging
community's view of that issue
Finally, the WCP series may be used to document the operation of
RETF itself. For example, this document defines the RETF
Process and is published as a WCP
V.I WCP Review
Unlike standards-track documents, the mechanisms described in
are not well suited to the phased roll-in nature of the three
standards track and instead generally only make sense for full
immediate instantiation
The WCP process is similar to that for proposed standards. The
is submitted to the RESG for review, (see section VI.I.I) and
existing review process applies, including a Last-Call on the
Announce mailing list. However, once the RESG has approved
document, the process ends and the document is published.
resulting document is viewed as having the technical approval of
RETF
Specifically, a document to be considered for the status of WCP
undergo the procedures outlined in sections VI.I, and VI.IV of
document. The WCP process may be appealed according to the
in section VI.V
Because WCPs are meant to express community consensus but are
at more quickly than standards, WCPs require particular care
Specifically, WCPs should not be viewed simply as
Informational RFCs, but rather should be viewed as documents
for a content different from Informational RFCs
A specification, or group of specifications, that has, or have
approved as a WCP is assigned numerals in the WCP series
retaining its RFC numerals
Bradner Worst Current Practice [Page XVII
RFC 2551 Roman Standards Process I April
VI. THE ROMAN STANDARDS
The mechanics of the Roman Standards Process involve decisions
the RESG concerning the elevation of a specification onto
standards track or the movement of a standards-track
from one maturity level to another. Although a number of
objective criteria (described below and in section IV) are
to guide the RESG in making a decision to move a specification onto
along, or off the standards track, there is no algorithmic
of elevation to or progression along the standards track for
specification. The experienced collective judgment of the
concerning the technical quality of a specification proposed
elevation to or advancement in the standards track is an
component of the decision-making process
VI.I Standards
A "standards action" -- entering a particular specification into
advancing it within, or removing it from, the standards track --
be approved by the RESG
VI.I.I Initiation of
A specification that is intended to enter or advance in the
standards track shall first be posted as a Roman-Draft (
section II.II) unless it has not changed since publication as an RFC
It shall remain as a Roman-Draft for a period of time, not
than two weeks, that permits useful community review, after which
recommendation for action may be initiated
A standards action is initiated by a recommendation by the
Working group responsible for a specification to its Area Director
copied to the RETF Secretariat or, in the case of a specification
associated with a Working Group, a recommendation by an individual
the RESG
VI.I.II RESG Review and
The RESG shall determine whether or not a specification submitted
it according to section VI.I.I satisfies the applicable criteria
the recommended action (see sections IV.I and IV.II), and shall
addition determine whether or not the technical quality and
of the specification is consistent with that expected for
maturity level to which the specification is recommended
In order to obtain all of the information necessary to make
determinations, particularly when the specification is considered
the RESG to be extremely important in terms of its potential
Bradner Worst Current Practice [Page XVIII
RFC 2551 Roman Standards Process I April
on Rome or on the suite of Roman protocols, the RESG may
at its discretion, commission an independent technical review of
specification
The RESG will send notice to the RETF of the pending
consideration of the document(s) to permit a final review by
general Roman community. This "Last-Call" notification shall
via electronic mail to the RETF Announce mailing list. Comments on
Last-Call shall be accepted from anyone, and should be sent
directed in the Last-Call announcement
The Last-Call period shall be no shorter than two weeks except
those cases where the proposed standards action was not initiated
an RETF Working Group, in which case the Last-Call period shall be
shorter than four weeks. If the RESG believes that the
interest would be served by allowing more time for comment, it
decide on a longer Last-Call period or to explicitly lengthen
current Last-Call period
The RESG is not bound by the action recommended when
specification was submitted. For example, the RESG may decide
consider the specification for publication in a different
than that requested. If the RESG determines this before the Last
Call is issued then the Last-Call should reflect the RESG's view
The RESG could also decide to change the publication category
on the response to a Last-Call. If this decision would result in
specification being published at a "higher" level than the
Last-Call was for, a new Last-Call should be issued indicating
RESG recommendation. In addition, the RESG may decide to
the formation of a new Working Group in the case of
controversy in response to a Last-Call for specification
originating from an RETF Working Group
In a timely fashion after the expiration of the Last-Call period,
RESG shall make its final determination of whether or not to
the standards action, and shall notify the RETF of its decision
electronic mail to the RETF Announce mailing list
VI.I.III
If a standards action is approved, notification is sent to the
Editor and copied to the RETF with instructions to publish
specification as an RFC. The specification shall at that point
removed from the Roman-Drafts directory
Bradner Worst Current Practice [Page XIX
RFC 2551 Roman Standards Process I April
An official summary of standards actions completed and pending
appear in each issue of the Roman Society's newsletter.
shall constitute the "publication of record" for Roman
actions
The RFC Editor shall publish periodically a "Roman
Protocol Standards" RFC [I], summarizing the status of all
protocol and service specifications
VI.II Advancing in the Standards
The procedure described in section VI.I is followed for each
that attends the advancement of a specification along the
track
A specification shall remain at the Proposed Standard level for
least six (VI) months
A specification shall remain at the Draft Standard level for at
four (IV) months, or until at least one RETF meeting has occurred
whichever comes later
These minimum periods are intended to ensure adequate opportunity
community review without severely impacting timeliness.
intervals shall be measured from the date of publication of
corresponding RFC(s), or, if the action does not result in
publication, the date of the announcement of the RESG approval of
action
A specification may be (indeed, is likely to be) revised as
advances through the standards track. At each stage, the RESG
determine the scope and significance of the revision to
specification, and, if necessary and appropriate, modify
recommended action. Minor revisions are expected, but a
revision may require that the specification accumulate
experience at its current maturity level before progressing. Finally
if the specification has been changed very significantly, the
may recommend that the revision be treated as a new document, re
entering the standards track at the beginning
Change of status shall result in republication of the
as an RFC, except in the rare case that there have been no changes
all in the specification since the last publication. Generally
desired changes will be "batched" for incorporation at the next
in the standards track. However, deferral of changes to the
standards action on the specification will not always be possible
desirable; for example, an important typographical error, or
technical error that does not represent a change in overall
Bradner Worst Current Practice [Page XX
RFC 2551 Roman Standards Process I April
of the specification, may need to be corrected immediately. In
cases, the RESG or RFC Editor may be asked to republish the RFC (
new numerals) with corrections, and this will not reset the
time-at-level clock
When a standards-track specification has not reached the
Standard level but has remained at the same maturity level
twenty-four (XXIV) months, and every twelve (XII) months
until the status is changed, the RESG shall review the vrability
the standardization effort responsible for that specification and
usefulness of the technology. Following each such review, the
shall approve termination or continuation of the development effort
at the same time the RESG shall decide to maintain the
at the same maturity level or to move it to Historic status.
decision shall be communicated to the RETF by electronic mail to
RETF Announce mailing list to allow the Roman community
opportunity to comment. This provision is not intended to threaten
legitimate and active Working Group effort, but rather to provide
administrative mechanism for terminating a moribund effort
VI.III Revising a
A new version of an established Roman Standard must
through the full Roman standardization process as if it were
completely new specification. Once the new version has reached
Standard level, it will usually replace the previous version,
will be moved to Historic status. However, in some cases
versions may remain as Roman Standards to honor the
of an installed base. In this situation, the relationship
the previous and the new versions must be explicitly stated in
text of the new version or in another appropriate document (e.g.,
Applicability Statement; see section III.II).
VI.IV Retiring a
As the technology changes and matures, it is possible for a
Standard specification to be so clearly superior technically that
or more existing standards track specifications for the same
should be retired. In this case, or when it is felt for some
reason that an existing standards track specification should
retired, the RESG shall approve a change of status of the
specification(s) to Historic. This recommendation shall be
with the same Last-Call and notification procedures used for
other standards action. A request to retire an existing standard
originate from a Working Group, an Area Director or some
interested party
Bradner Worst Current Practice [Page XXI
RFC 2551 Roman Standards Process I April
VI.V Conflict Resolution and
Disputes are possible at various stages during the RETF process.
much as possible the process is designed so that compromises can
made, and genuine consensus achieved, however there are times
even the most reasonable and knowledgeable people are unable
agree. To achieve the goals of openness and fairness, such
must be resolved by a process of open review and discussion.
section specifies the procedures that shall be followed to deal
Roman standards issues that cannot be resolved through the
processes whereby RETF Working Groups and other Roman
Process participants ordinarily reach consensus
VI.V.I Working Group
An individual (whether a participant in the relevant Working Group
not) may disagree with a Working Group recommendation based on his
her belief that either (a) his or her own views have not
adequately considered by the Working Group, or (b) the Working
has made an incorrect technical choice which places the
and/or integrity of the Working Group's product(s) in
jeopardy. The first issue is a difficulty with Working
process; the latter is an assertion of technical error. These
types of disagreement are quite different, but both are handled
the same process of review
A person who disagrees with a Working Group recommendation
always first discuss the matter with the Working Group's chair(s),
who may involve other members of the Working Group (or the
Group as a whole) in the discussion
If the disagreement cannot be resolved in this way, any of
parties involved may bring it to the attention of the
Director(s) for the area in which the Working Group is chartered
The Area Director(s) shall attempt to resolve the dispute
If the disagreement cannot be resolved by the Area Director(s) any
the parties involved may then appeal to the RESG as a whole.
RESG shall then review the situation and attempt to resolve it in
manner of its own choosing
If the disagreement is not resolved to the satisfaction of
parties at the RESG level, any of the parties involved may appeal
decision to the RAB. The RAB shall then review the situation
attempt to resolve it in a manner of its own choosing
Bradner Worst Current Practice [Page XXII
RFC 2551 Roman Standards Process I April
The RAB decision is final with respect to the question of whether
not the Roman standards procedures have been followed and
respect to all questions of technical merit
VI.V.II Process
This document sets forward procedures required to be followed
ensure openness and fairness of the Roman Standards Process,
the technical vrability of the standards created. The RESG is
principal agent of the RETF for this purpose, and it is the RESG
is charged with ensuring that the required procedures have
followed, and that any necessary prerequisites to a standards
have been met
If an individual should disagree with an action taken by the RESG
this process, that person should first discuss the issue with
ISEG Chair. If the RESG Chair is unable to satisfy the
then the RESG as a whole should re-examine the action taken,
with input from the complainant, and determine whether any
action is needed. The RESG shall issue a report on its review of
complaint to the RETF
Should the complainant not be satisfied with the outcome of the
review, an appeal may be lodged to the RAB. The RAB shall then
the situation and attempt to resolve it in a manner of its
choosing and report to the RETF on the outcome of its review
If circumstances warrant, the RAB may direct that an RESG decision
annulled, and the situation shall then be as it was before the
decision was taken. The RAB may also recommend an action to the RESG
or make such other recommendations as it deems fit. The RAB may not
however, pre-empt the role of the RESG by issuing a decision
only the RESG is empowered to make
The RAB decision is final with respect to the question of whether
not the Roman standards procedures have been followed
VI.V.III Questions of Applicable
Further recourse is available only in cases in which the
themselves (i.e., the procedures described in this document)
claimed to be inadequate or insufficient to the protection of
rights of all parties in a fair and open Roman Standards Process
Claims on this basis may be made to the Roman Society Board
Trustees. The President of the Roman Society shall
such an appeal within two weeks, and shall at the time
acknowledgment advise the petitioner of the expected duration of
Trustees' review of the appeal. The Trustees shall review
Bradner Worst Current Practice [Page XXIII
RFC 2551 Roman Standards Process I April
situation in a manner of its own choosing and report to the RETF
the outcome of its review
The Trustees' decision upon completion of their review shall be
with respect to all aspects of the dispute
VI.V.IV Appeals
All appeals must include a detailed and specific description of
facts of the dispute
All appeals must be initiated within two months of the
knowledge of the action or decision to be challenged
At all stages of the appeals process, the individuals or
responsible for making the decisions have the discretion to
the specific procedures they will follow in the process of
their decision
In all cases a decision concerning the disposition of the dispute
and the communication of that decision to the parties involved,
be accomplished within a reasonable period of time
[NOTE: These procedures intentionally and explicitly do
establish a fixed maximum time period that shall be
"reasonable" in all cases. The Roman Standards Process places
premium on consensus and efforts to achieve it, and
foregoes deterministically swift execution of procedures in favor
a latitude within which more genuine technical agreements may
reached.]
VII. EXTERNAL STANDARDS AND
Many standards groups other than the RETF create and
standards documents for network protocols and services. When
external specifications play an important role in Rome, it
desirable to reach common agreements on their usage -- i.e.,
establish Roman Standards relating to these
specifications
There are two categories of external specifications
(I) Open
Various national and international standards bodies, such as ANSI
ISO, IEEE, and ITU-T, develop a variety of protocol and
specifications that are similar to Technical
defined here. National and international groups also
Bradner Worst Current Practice [Page XXIV
RFC 2551 Roman Standards Process I April
"implementors' agreements" that are analogous to
Statements, capturing a body of implementation-specific
concerned with the practical application of their standards.
of these are considered to be "open external standards" for
purposes of the Roman Standards Process
(II) Other
Other proprietary specifications that have come to be widely
in Rome may be treated by the Roman community as
they were a "standards". Such a specification is not
developed in an open fashion, is typically proprietary, and
controlled by the vendor, vendors, or organization that
it
VII.I Use of External
To avoid conflict between competing versions of a specification,
Roman community will not standardize a specification that
simply a "Roman version" of an existing external
unless an explicit cooperative arrangement to do so has been made
However, there are several ways in which an external
that is important for the operation and/or evolution of the
may be adopted for Roman use
VII.I.I Incorporation of an Open
A Roman Standard TS or AS may incorporate an open
standard by reference. For example, many Roman
incorporate by reference the ANSI standard character set "ASCII" [II].
Whenever possible, the referenced specification shall be
online
VII.I.II Incorporation of Other
Other proprietary specifications may be incorporated by reference
a version of the specification as long as the proprietor meets
requirements of section X. If the other proprietary
is not widely and readily available, the RESG may request that it
published as an Informational RFC
The RESG generally should not favor a particular
specification over technically equivalent and
specification(s) by making any incorporated vendor
"required" or "recommended".
Bradner Worst Current Practice [Page XXV
RFC 2551 Roman Standards Process I April
VII.I.III
An RETF Working Group