version
Click on the red underlined text to get to the source
...
Each distinct version of an Internet standards-related specification
is published as part of the "Request for Comments" (RFC) document
...
... Every RFC is available in ASCII text. Some RFCs are also available
in other formats. The other versions of an RFC may contain material
(such as diagrams and figures) that is not present in the ASCII
...
... (such as diagrams and figures) that is not present in the ASCII
version, and it may be formatted differently.
...
... standards-track *
* specifications: the ASCII text version is the *
* definitive reference, and therefore it must be a *
* complete and accurate specification of the standard, *
...
...
During the development of a specification, draft versions of the
document are made available for informal review and comment by
placing them in the IETF ...
... Internet-Drafts directory. At any time, an
Internet-Draft may be replaced by a more recent version of the same
specification, restarting the six-month timeout period.
...
... through the full Internet standardization process as if it were a
completely new specification. Once the new version has reached the
Standard level, it will usually replace the previous version, which
...
... completely new specification. Once the new version has reached the
Standard level, it will usually replace the previous version, which
will be moved to Historic status. However, in some cases both
versions ...
... version, which
will be moved to Historic status. However, in some cases both
versions may remain as Internet Standards to honor the requirements
...
... requirements
of an installed base. In this situation, the relationship between
the previous and the new versions must be explicitly stated in the
text of the new version or in another appropriate document (e.g., an
...
... the previous and the new versions must be explicitly stated in the
text of the new version or in another appropriate document (e.g., an
Applicability Statement; see section 3.2).
...
...
To avoid conflict between competing versions of a specification, the
Internet community will not standardize a specification that is
...
... Internet community will not standardize a specification that is
simply an "Internet version" of an existing external specification
unless an explicit cooperative arrangement to do so has been made.
However, there are several ways in which an external specification
...
...
Other proprietary specifications may be incorporated by reference to
a version of the specification as long as the proprietor meets the
requirements of section 10. If the other proprietary specification
...
... Internet Standards Process (as a BCP, as described in section
5). It replaces a previous version, and in time, is likely itself to
be replaced.
...
... time there may be a desire to update it, by replacing it with a new
version. Updating this document uses the same open procedures as are
used for any other BCP.
...
... before the current effort (which relies heavily on its predecessors).
Specific acknowledgments must be extended to Lyman Chapin, Phill
Gross and Christian Huitema as the editors of the previous versions,
to Jon Postel and Dave Crocker for their inputs to those versions, to
...
... Gross and Christian Huitema as the editors of the previous versions,
to Jon Postel and Dave Crocker for their inputs to those versions, to
Andy Ireland, Geoff Stewart, Jim Lampert, and Dick Holleman for their
reviews of the legal aspects of the procedures described herein, and
...
... reviews of the legal aspects of the procedures described herein, and
to John Stewart, Robert Elz and Steve Coya for their extensive input
on the final version.
...