idnits 2.17.1 draft-rfced-rfcxx00-retired-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 2013) is 3877 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 1083 (Obsoleted by RFC 1100) -- Obsolete informational reference (is this intentional?): RFC 1280 (Obsoleted by RFC 1360) -- Obsolete informational reference (is this intentional?): RFC 2200 (Obsoleted by RFC 2300) -- Obsolete informational reference (is this intentional?): RFC 5000 (Obsoleted by RFC 7100) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet-Draft S. Ginoza 3 Category: Informational AMS 4 September 2013 6 List of Internet Official Protocol Standards: 7 Replaced by an Online Database 8 draft-rfced-rfcxx00-retired-06 10 Abstract 12 At one time, the RFC Editor published snapshots of the "Internet 13 Official Protocol Standards". These documents were known as xx00 14 documents, the last of which was published in May 2008. These 15 snapshots have been replaced by an online database, so the RFC Editor 16 will will no longer be publishing these snapshots as RFCs. As a 17 result, the RFC Editor will classify unpublished RFC xx00 numbers 18 through 7000 as never issued. Starting with RFC 7100, xx00 numbers 19 will be available for assignment. 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on March 11, 2014. 38 Copyright Notice 40 Copyright (c) 2013 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 1. Introduction 55 [RFC1083], published in December 1988, was the first document 56 published in the RFC series that detailed a "list of documents that 57 define the standards for the Internet protocol suite" and any ongoing 58 experiments. Snapshots were published from time to time. [RFC1280] 59 was the first of these publications to be published as STD 1. 60 Starting with [RFC2200], RFC numbers ending with 00 were reserved for 61 snapshots of the Official Protocol Standards. [RFC5000], published 62 in May 2008, was the last snapshot documented in an RFC. This 63 document notes that the xx00 documents are being replaced by the 64 online resource provided by the RFC Editor, and the tradition of 65 publishing snapshots is being discontinued. RFC numbers typically 66 reserved for these documents (i.e., those numbers ending with 00) 67 will be available for assignment to other RFCs-to-be. 69 2. Online List of Official Internet Protocol Standards 71 In the past, publishing a snapshot of the current list of Standards 72 Track and Experimental documents was helpful to the Internet 73 community, as the information was not available otherwise. In 1996, 74 [RFC2026] documented the IETF's desire for the periodic publication 75 of the "Internet Official Protocol Standards". However, in 2000, the 76 RFC Editor produced an online list that is dynamically updated and 77 available to individuals with access to the public Internet [STDS- 78 TRK]. As the list has been online for over 10 years, and the IETF 79 has indicated that they no longer see a need for the snapshot 80 document to be maintained [RETIRE-STD1], the official list of 81 Standards Track and Experimental documents will now provided by the 82 online list. 84 3. STD 1 86 STD 1 has been in an abnormal state since RFC 5000 was published. 87 After consultation with the IAB, RFC 5000 was published as an 88 Informational document, but it was still identified as STD 1 in the 89 document header. The status was listed as Informational, because the 90 document does not describe an implementable Standard. However, it 91 was associated with STD 1 to keep the document consistent with its 92 historic connection to the subseries identifier. 94 The IETF has decided to move RFC 5000 (and therefore STD 1) to 95 Historic status [RETIRE-STD1]. Marking STD 1 as Historic will result 96 in identifier STD 1 not being available for future use. 98 4. Cleaning Up RFC Editor Data 100 As part of the cleanup related to ending the series of RFC xx00 101 documents titled "Internet Official Protocol Standards", the RFC 102 Editor will mark a number of unused numbers ending in 00 through RFC 103 7000 "never issued". All RFC numbers ending in 00 from 7100 upwards 104 will now be available to be assigned for any RFC. 106 5. IANA Considerations 108 This document does not request any IANA actions. 110 6. Security Considerations 112 This document does not impact the security of the Internet. 114 7. Informative References 116 [RETIRE-STD1] Resnick, P., "Retirement of the "Internet Official 117 Protocol Standards" Summary Document", Work in 118 Progress, August 2013. 120 [RFC1083] Defense Advanced Research Projects Agency and Internet 121 Activities Board, "IAB official protocol standards", 122 RFC 1083, December 1988. 124 [RFC1280] Postel, J., "IAB Official Protocol Standards", RFC 125 1280, March 1992. 127 [RFC2026] Bradner, S., "The Internet Standards Process -- 128 Revision 3", BCP 9, RFC 2026, October 1996. 130 [RFC2200] Postel, J., "Internet Official Protocol Standards", RFC 131 2200, June 1997. 133 [RFC5000] RFC Editor, "Internet Official Protocol Standards", STD 134 1, RFC 5000, May 2008. 136 [STDS-TRK] RFC Editor, "Official Internet Protocol Standards", 137 . 139 8. Acknowledgements 141 We would like to thank Nevil Brownlee, Brian Carpenter, Heather 142 Flanagan, and Alice Russo for their review and input on this 143 document. We would also like to thank Dongjin Son and Bob Braden for 144 their efforts in writing the scripts that produce the "Official 145 Internet Protocol Standards" page. 147 Author's Address 149 Sandy Ginoza 150 Association Management Solutions 151 48377 Fremont Blvd., Suite 117 152 Fremont, CA 94538 153 United States 155 Phone: +1 (510) 492-4000 156 EMail: sginoza@amsl.com