RFC 7101
List of Internet Official Protocol Standards: Replaced by a Web Page
RFC 7101: List of Internet Official Protocol Standards: Replaced by a Web Page π
Okay bestie, let's get the basics π. This one is from the Internet Architecture Board (IAB) π¦, written by Sandy Ginoza of Association Management Solutions (AMS) πΈ. It's an Informational doc, published in December 2013 β¨, with ISSN 2070-1721. The header doesn't list any RFCs it obsoletes or updates, so it's a standalone announcement π§.
Abstract
Once upon a time the RFC Editor published snapshots of the "Internet Official Protocol Standards" π. These were called xx00 documents, and the last one dropped in May 2008 π. The snapshots have since been replaced by a web page, so the RFC Editor is done publishing them as RFCs π . That means unpublished RFC xx00 numbers from 0 through 7000 get classified as never issued. Starting with RFC 7100, xx00 numbers are open for assignment π.
Status of This Memo
Not a Standards Track spec, just here for info π.
This doc is a product of the Internet Architecture Board (IAB) and holds information the IAB thought was worth keeping on the permanent record π. It reflects the IAB's consensus. Docs the IAB approves for publication are not candidates for any level of Internet Standard, see Section 2 of RFC 5741 π.
For the current status, any errata, and how to give feedback, check http://www.rfc-editor.org/info/rfc7101 π.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved π.
This doc 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 them closely, because they spell out your rights and restrictions for this doc π.
1. Introduction β¨
[RFC1083], published in December 1988, was the first RFC-series doc to lay out a "list of documents that define the standards for the Internet protocol suite" plus any ongoing experiments π§. Snapshots came out now and then. [RFC1280] was the first of those to be published as STD 1 π. Starting with [RFC2200], RFC numbers ending in 00 were reserved for snapshots of the Official Protocol Standards π. [RFC5000], published in May 2008, was the last snapshot documented in an RFC π₯². This doc notes that the xx00 documents are being replaced by the online resource from the RFC Editor, and the snapshot tradition is being discontinued π«Ά. The numbers that were usually set aside for these docs (the ones ending in 00) are now available for other RFCs-to-be π¦.
2. Online List of Official Internet Protocol Standards π
Back in the day, a snapshot of the current list of Standards Track and Experimental docs was genuinely helpful, because the info wasn't available anywhere else π. In 1996, [RFC2026] documented the IETF's wish for periodic publication of the "Internet Official Protocol Standards" ποΈ. Then in 2000, the RFC Editor made an online list that updates dynamically and is available to anyone with public Internet access [STDS-TRK] π». That list has been online for over 10 years, and the IETF has said it no longer sees a need to maintain the snapshot doc [RFC7100]. So the official list of Standards Track docs will now live online π«§.
3. STD 1 πΈ
STD 1 has been in an abnormal state since RFC 5000 came out π΅βπ«. After talking with the IAB, RFC 5000 was published as an Informational doc, but it still had the STD 1 label in its header. It was marked Informational because the doc doesn't describe an implementable Standard. It was still tied to STD 1 though, to keep it consistent with its historic link to that subseries identifier π§·.
The IETF has decided to move RFC 5000 (and therefore STD 1) to Historic status [RFC7100]. Once STD 1 is marked Historic, the identifier STD 1 won't be available for future use πͺ¦.
4. Cleaning Up RFC Editor Data π§Ή
As part of wrapping up the xx00 series titled "Internet Official Protocol Standards", the RFC Editor is marking a bunch of unused numbers ending in 00, through RFC 7000, as "never issued" ποΈ. Every RFC number ending in 00 from 7100 onward is now available to assign to any RFC π .
5. Security Considerations π
This document does not impact the security of the Internet. Not a single packet, not a single key, not one lock. Totally safe, bestie π.
6. Informative References π
- [RFC1083] Defense Advanced Research Projects Agency and Internet Activities Board, "IAB official protocol standards", RFC 1083, December 1988.
- [RFC1280] Postel, J., "IAB Official Protocol Standards", RFC 1280, March 1992.
- [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
- [RFC2200] Postel, J., "Internet Official Protocol Standards", RFC 2200, June 1997.
- [RFC5000] RFC Editor, "Internet Official Protocol Standards", STD 1, RFC 5000, May 2008.
- [RFC7100] Resnick, P., "Retirement of the "Internet Official Protocol Standards" Summary Document", BCP 9, RFC 7100, December 2013.
- [STDS-TRK] RFC Editor, "Official Internet Protocol Standards",
<http://www.rfc-editor.org/rfcxx00.html>.
7. Acknowledgements π«Ά
Huge thanks to Nevil Brownlee, Brian Carpenter, Heather Flanagan, and Alice Russo for reviewing and weighing in on this doc π. Also a big shoutout to Dongjin Son and Bob Braden for writing the scripts that generate the "Official Internet Protocol Standards" page π.
Author's Address π
Sandy Ginoza
Association Management Solutions
48377 Fremont Blvd., Suite 117
Fremont, CA 94538
United States
Phone: +1 (510) 492-4000
EMail: sginoza@amsl.com
That's the whole tea, bestie πβ¨π
π¦ where this page comes from
- ietf: rfc7101 2013-12
- π girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms