7100
BEST CURRENT PRACTICE
Retirement of the "Internet Official Protocol Standards" Summary Document
Authors: P. Resnick
Date: December 2013
Working Group: NON WORKING GROUP
Stream: IETF
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.
RFC 7100
BEST CURRENT PRACTICE
Internet Engineering Task Force (IETF) P. Resnick
Request for Comments: 7100 Qualcomm Technologies, Inc.
BCP: 9 December 2013
Obsoletes: <a href="./rfc5000">5000</a>
Updates: <a href="./rfc2026">2026</a>
Category: Best Current Practice
ISSN: 2070-1721
<span class="h1">Retirement of the "Internet Official Protocol Standards"</span>
<span class="h1">Summary Document</span>
Abstract
This document updates <a href="./rfc2026">RFC 2026</a> to no longer use STD 1 as a summary of
"Internet Official Protocol Standards". It obsoletes <a href="./rfc5000">RFC 5000</a> and
requests the IESG to move <a href="./rfc5000">RFC 5000</a> (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 <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc7100">http://www.rfc-editor.org/info/rfc7100</a>.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Resnick Best Current Practice [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc7100">RFC 7100</a> Retirement of STD 1 December 2013</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Retiring STD 1</span>
<a href="./rfc2026">RFC 2026</a> [<a href="./rfc2026" title=""The Internet Standards Process -- Revision 3"">RFC2026</a>] 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 <a href="./rfc5000">RFC 5000</a>
[<a href="./rfc5000" title=""Internet Official Protocol Standards"">RFC5000</a>], 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 [<a href="#ref-STDS-TRK" title=""Official Internet Protocol Standards"">STDS-TRK</a>]. The IETF no longer sees the
need for the document to be maintained. Therefore, this document
updates <a href="./rfc2026">RFC 2026</a> [<a href="./rfc2026" title=""The Internet Standards Process -- Revision 3"">RFC2026</a>], effectively removing the above-mentioned
paragraph from <a href="#section-6.1.3">Section 6.1.3</a>, along with the paragraph from
<a href="#section-2.1">Section 2.1</a> 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 <a href="#section-3">section 3</a>).
and the paragraph from <a href="#section-3.3">Section 3.3</a> 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 <a href="./rfc5000">RFC 5000</a> [<a href="./rfc5000" title=""Internet Official Protocol Standards"">RFC5000</a>], the current
incarnation of that document, and requests that the IESG move that
document (and therefore STD 1) to Historic status.
Finally, <a href="./rfc2026">RFC 2026</a> <a href="./rfc2026#section-6.1.3">[RFC2026] Section 6.1.3</a> 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
[<a href="#ref-IESG-MINUTES" title=""IESG Telechat Minutes"">IESG-MINUTES</a>]. Therefore, that paragraph is also effectively
removed from <a href="#section-6.1.3">Section 6.1.3</a>.
<span class="grey">Resnick Best Current Practice [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc7100">RFC 7100</a> Retirement of STD 1 December 2013</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Security Considerations</span>
This document does not impact the security of the Internet.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Normative References</span>
[<a id="ref-IESG-MINUTES">IESG-MINUTES</a>] Internet Engineering Steering Group, "IESG Telechat
Minutes", <<a href="http://www.ietf.org/iesg/minutes.html">http://www.ietf.org/iesg/minutes.html</a>>.
[<a id="ref-RFC2026">RFC2026</a>] Bradner, S., "The Internet Standards Process --
Revision 3", <a href="https://www.rfc-editor.org/bcp/bcp9">BCP 9</a>, <a href="./rfc2026">RFC 2026</a>, October 1996.
[<a id="ref-RFC5000">RFC5000</a>] RFC Editor, "Internet Official Protocol Standards",
<a href="./rfc5000">RFC 5000</a>, May 2008.
[<a id="ref-STDS-TRK">STDS-TRK</a>] RFC Editor, "Official Internet Protocol Standards",
<<a href="https://www.rfc-editor.org/rfcxx00.html">http://www.rfc-editor.org/rfcxx00.html</a>>.
Author's Address
Pete Resnick
Qualcomm Technologies, Inc.
5775 Morehouse Drive
San Diego, CA 92121
US
Phone: +1 858 6511 4478
EMail: [email protected]
Resnick Best Current Practice [Page 3]
Annotations
Select text to annotate