RFC 7100

RFC 7100: Retirement of the "Internet Official Protocol Standards" Summary Document 🎀

Okay bestie, this one is a Best Current Practice (that's BCP 9 ✨), so it's the IETF's official "here's how we do things now" doc. It was written by P. Resnick of Qualcomm Technologies, Inc., and published in December 2013 🌸. It's RFC 7100, with ISSN 2070-1721. It obsoletes RFC 5000 and updates RFC 2026, and it's all about retiring a summary doc that nobody's been keeping up 💅.

Abstract

This doc updates RFC 2026 so it no longer uses STD 1 as the summary of "Internet Official Protocol Standards" 🦋. It obsoletes RFC 5000 and asks 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 was approved for publication by the Internet Engineering Steering Group (IESG) ✨. More info on BCPs is in Section 2 of RFC 5741 🌈.

For the current status of this doc, any errata, and how to send feedback, check out 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) as in effect on the date of publication 💅. Please read these carefully, because they cover 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 they're provided without warranty as described in the Simplified BSD License 👑.

1. Retiring STD 1 🌸

Okay so RFC 2026 [RFC2026] and its predecessors said there should be an RFC describing the status of IETF protocols 😭. Here's the exact wording:

The RFC Editor shall publish periodically an "Internet Official
Protocol Standards" RFC [1], summarizing the status of all
Internet protocol and service specifications.

That doc, now RFC 5000 [RFC5000], has always been listed in the Internet Standard series as STD 1 🦋. But it hasn't been kept up to date in recent years, and people have moved on to the online list the RFC Editor maintains [STDS-TRK] 💀. The IETF doesn't see the need to keep maintaining it anymore 🙈. So this doc updates RFC 2026 [RFC2026] to effectively remove the paragraph quoted above from Section 6.1.3 💖, along with the paragraph from Section 2.1 that says:

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).

It also removes the paragraph from Section 3.3 that says:

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.

On top of that, this doc obsoletes RFC 5000 [RFC5000], the current version of that doc, and asks the IESG to move it (and therefore STD 1) to Historic status 🍓.

Last thing: RFC 2026 [RFC2026] Section 6.1.3 also called for an "official summary of standards actions completed and pending" in the Internet Society's newsletter 🧚. That hasn't been done in recent years either. The "publication of record" for standards actions has been the IESG minutes for a while now [IESG-MINUTES] ✨. So that paragraph is effectively removed from Section 6.1.3 too 💅.

2. Security Considerations 🔒

This document does not impact the security of the Internet 🫶. Honestly, no drama here, just a very chill retirement 🌈.

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