idnits 2.17.1 draft-flanagan-rfc32alt-00.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 : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 8, 2019) is 1744 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Missing reference section? 'RFC-INDEX' on line 97 looks like a reference -- Missing reference section? 'DAYS-365' on line 88 looks like a reference -- Missing reference section? 'RFC0032' on line 101 looks like a reference -- Missing reference section? 'NWG-RFC32' on line 92 looks like a reference Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group H. Flanagan 3 Internet-Draft RFC Editor 4 Intended status: Informational July 8, 2019 5 Expires: January 9, 2020 7 Clarifying the Historical Record for RFC 32 8 draft-flanagan-rfc32alt-00 10 Abstract 12 This document identifies an issue found in the historical record of 13 the RFC Series with regards to RFC 32, a number issued to two 14 separate documents in the early days of the Series. This document 15 serves as a reference point such that errata can be registered 16 against those RFCs that refer to RFC 32. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at https://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on January 9, 2020. 35 Copyright Notice 37 Copyright (c) 2019 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (https://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Conflict Description and Resolution . . . . . . . . . . . . . 2 53 2. Informative References . . . . . . . . . . . . . . . . . . . 2 54 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 3 55 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 57 1. Conflict Description and Resolution 59 This document describes an issue found in the historical record as 60 captured in the RFC Index [RFC-INDEX] of the RFC Series with regard 61 to RFC 32: a number issued to two separate documents in the early 62 days of the Series. This document serves as a reference such that 63 errata can be registered against those RFCs that refer to either 64 document assigned the identifier RFC 32. 66 The blog series "365 Days of RFCs" [DAYS-365] by Darius Kazemi 67 included discovery of the fact that while the RFC Editor index 68 referred to "Some Thoughts on SRI's Proposed Real Time Clock" by 69 Jerry Cole as [RFC0032], other RFCs later in the series instead 70 referred to "Connecting M.I.T. Computers to the ARPA Computer-to- 71 Computer Communication Network" by Dietrich Vedder via the same RFC 72 identifier. While there are theories around how this happened, 73 absolute certainty regarding the cause of the duplicate identifier 74 issuance is unlikely to be uncovered this many years after the fact. 76 For the sake of clarifying the historical record, "Some Thoughts on 77 SRI's Proposed Real Time Clock" will continue to be recorded as RFC 78 32 in the index of RFCs managed by the RFC Editor. The document 79 "Connecting M.I.T. Computers to the ARPA Computer-to-Computer 80 Communication Network", is hosted (with permission from the author) 81 on the RFC Editor website [NWG-RFC32]. All RFCs that refer to the 82 either the Cole document or the Vedder document will have an errata 83 issued in order to capture the discrepancy and point individuals to 84 the correct document. 86 2. Informative References 88 [DAYS-365] 89 Kazemi, D., "365 Days of RFCs", April 2019, 90 . 92 [NWG-RFC32] 93 Vedder, D., "Connecting M.I.T. Computers to the ARPA 94 Computer-to-Computer Communication Network", January 1969, 95 . 97 [RFC-INDEX] 98 RFC Editor, "RFC Index", April 2019, 99 . 101 [RFC0032] Cole, J., "Some Thoughts on SRI's Proposed Real Time 102 Clock", RFC 32, DOI 10.17487/RFC0032, February 1970, 103 . 105 Appendix A. Acknowledgements 107 With many thanks to Darius Kazemi for identifying the issue described 108 in this document. 110 Author's Address 112 Heather Flanagan 113 RFC Editor 115 Email: rse@rfc-editor.org 116 URI: https://orcid.org/0000-0002-2647-2220