Retirement of the "Internet Official Protocol Standards" Summary Document
The IETF stops maintaining the Internet Official Protocol Standards list known as STD 1.
Resnick, P., "Retirement of the "Internet Official Protocol Standards" Summary Document", BCP 9, RFC 7100, DOI 10.17487/RFC7100, December 2013, <https://www.rfc-editor.org/info/rfc7100>.
@misc{rfc7100,
series = {Request for Comments},
number = 7100,
howpublished = {RFC 7100},
publisher = {RFC Editor},
doi = {10.17487/RFC7100},
url = {https://www.rfc-editor.org/info/rfc7100},
author = {P. Resnick},
title = {{Retirement of the "Internet Official Protocol Standards" Summary Document}},
pagetotal = 3,
year = 2013,
month = dec,
} RFC text
Contents
Internet Engineering Task Force (IETF) P. Resnick
Request for Comments: 7100 Qualcomm Technologies, Inc.
BCP: 9 December 2013
Obsoletes: 5000
Updates: 2026
Category: Best Current Practice
ISSN: 2070-1721
Retirement of the "Internet Official Protocol Standards"
Summary Document
Abstract
This document updates RFC 2026 to no longer use STD 1 as a summary of
"Internet Official Protocol Standards". It obsoletes RFC 5000 and
requests the IESG to move RFC 5000 (and therefore STD 1) to Historic
status.
Status of This Memo
This memo documents an Internet Best Current Practice.
This document is a product of the Internet Engineering Task Force
(IETF). It has been approved for publication by the Internet
Engineering Steering Group (IESG). Further information on BCPs is
available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7100.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
1. Retiring STD 1
RFC 2026 [RFC2026] and its predecessors call for the publication of
an RFC describing the status of IETF protocols:
The RFC Editor shall publish periodically an "Internet Official
Protocol Standards" RFC [1], summarizing the status of all
Internet protocol and service specifications.
The "Internet Official Protocol Standards" document, now as RFC 5000
[RFC5000], has always been listed in the Internet Standard series as
STD 1. However, the document has not been kept up to date in recent
years, and it has fallen out of use in favor of the online list
produced by the RFC Editor [STDS-TRK]. The IETF no longer sees the
need for the document to be maintained. Therefore, this document
updates RFC 2026 [RFC2026], effectively removing the above-mentioned
paragraph from Section 6.1.3, along with the paragraph from
Section 2.1 that states:
The status of Internet protocol and service specifications is
summarized periodically in an RFC entitled "Internet Official
Protocol Standards" [1]. This RFC shows the level of maturity and
other helpful information for each Internet protocol or service
specification (see section 3).
and the paragraph from Section 3.3 that states:
The "Official Protocol Standards" RFC (STD1) lists a general
requirement level for each TS, using the nomenclature defined in
this section. This RFC is updated periodically. In many cases,
more detailed descriptions of the requirement levels of particular
protocols and of individual features of the protocols will be
found in appropriate ASs.
Additionally, this document obsoletes RFC 5000 [RFC5000], the current
incarnation of that document, and requests that the IESG move that
document (and therefore STD 1) to Historic status.
Finally, RFC 2026 [RFC2026] Section 6.1.3 also calls for the
publication of an "official summary of standards actions completed
and pending" in the Internet Society's newsletter. This has also not
been done in recent years, and the "publication of record" for
standards actions has for some time been the minutes of the IESG
[IESG-MINUTES]. Therefore, that paragraph is also effectively
removed from Section 6.1.3.
2. Security Considerations
This document does not impact the security of the Internet.
3. Normative References
[IESG-MINUTES] Internet Engineering Steering Group, "IESG Telechat
Minutes", <http://www.ietf.org/iesg/minutes.html>.
[RFC2026] Bradner, S., "The Internet Standards Process --
Revision 3", BCP 9, RFC 2026, October 1996.
[RFC5000] RFC Editor, "Internet Official Protocol Standards",
RFC 5000, May 2008.
[STDS-TRK] RFC Editor, "Official Internet Protocol Standards",
<http://www.rfc-editor.org/rfcxx00.html>.
Author's Address
Pete Resnick
Qualcomm Technologies, Inc.
5775 Morehouse Drive
San Diego, CA 92121
US
Phone: +1 858 6511 4478
EMail: presnick@qti.qualcomm.com
AI ELI5
On this page
§1Why STD 1 Is Retired
RFC 2026 and its predecessors called for the RFC Editor to publish an "Internet Official Protocol Standards" RFC summarizing the status of all Internet protocol and service specifications. That document, by now RFC 5000, was always listed in the Internet Standard series as STD 1.
The RFC says it had not been kept up to date in recent years and had fallen out of use in favor of the online list produced by the RFC Editor. The IETF no longer saw the need to maintain it.
There was a big paper list of every rule and how finished it was. Nobody updated it anymore, and a website kept the same list fresh, so the paper list was not needed.
§1.1What Changes in RFC 2026
This BCP updates RFC 2026 by effectively removing three paragraphs that mention the summary: one in Section 2.1, one in Section 3.3 (which says the document lists a general requirement level for each technical specification) and one in Section 6.1.3.
It also obsoletes RFC 5000 and requests that the IESG move that document, and therefore STD 1, to Historic status.
Section 6.1.3 of RFC 2026 also called for an official summary of standards actions, completed and pending, in the Internet Society's newsletter. That had not been done in recent years either. The publication of record for standards actions had for some time been the IESG minutes, so that paragraph is removed as well.
The rule book had a few sentences saying to keep the list. Those sentences are crossed out, and the list itself is retired.
§2Security Considerations
The document states only that it does not impact the security of the Internet. It is a process change and defines no protocol behavior.
Crossing a list off the to-do pile does not make anything less safe.