Clarifying the Historical Record for RFC 32
draft-flanagan-rfc32alt-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        H. Flanagan
Internet-Draft                                                RFC Editor
Intended status: Informational                              July 8, 2019
Expires: January 9, 2020

              Clarifying the Historical Record for RFC 32
                       draft-flanagan-rfc32alt-00

Abstract

   This document identifies an issue found in the historical record of
   the RFC Series with regards to RFC 32, a number issued to two
   separate documents in the early days of the Series.  This document
   serves as a reference point such that errata can be registered
   against those RFCs that refer to RFC 32.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 9, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://trustee.ietf.org/license-info) 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.

Flanagan                 Expires January 9, 2020                [Page 1]
Internet-Draft      Clarifying the Record for RFC 32           July 2019

Table of Contents

   1.  Conflict Description and Resolution . . . . . . . . . . . . .   2
   2.  Informative References  . . . . . . . . . . . . . . . . . . .   2
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3

1.  Conflict Description and Resolution

   This document describes an issue found in the historical record as
   captured in the RFC Index [RFC-INDEX] of the RFC Series with regard
   to RFC 32: a number issued to two separate documents in the early
   days of the Series.  This document serves as a reference such that
   errata can be registered against those RFCs that refer to either
   document assigned the identifier RFC 32.

   The blog series "365 Days of RFCs" [DAYS-365] by Darius Kazemi
   included discovery of the fact that while the RFC Editor index
   referred to "Some Thoughts on SRI's Proposed Real Time Clock" by
   Jerry Cole as [RFC0032], other RFCs later in the series instead
   referred to "Connecting M.I.T.  Computers to the ARPA Computer-to-
   Computer Communication Network" by Dietrich Vedder via the same RFC
   identifier.  While there are theories around how this happened,
   absolute certainty regarding the cause of the duplicate identifier
   issuance is unlikely to be uncovered this many years after the fact.

   For the sake of clarifying the historical record, "Some Thoughts on
   SRI's Proposed Real Time Clock" will continue to be recorded as RFC
   32 in the index of RFCs managed by the RFC Editor.  The document
   "Connecting M.I.T.  Computers to the ARPA Computer-to-Computer
   Communication Network", is hosted (with permission from the author)
   on the RFC Editor website [NWG-RFC32].  All RFCs that refer to the
   either the Cole document or the Vedder document will have an errata
   issued in order to capture the discrepancy and point individuals to
   the correct document.

2.  Informative References

   [DAYS-365]
              Kazemi, D., "365 Days of RFCs", April 2019,
              <https://write.as/365-rfcs/table-of-contents>.

   [NWG-RFC32]
              Vedder, D., "Connecting M.I.T. Computers to the ARPA
              Computer-to-Computer Communication Network", January 1969,
              <https://www.rfc-editor.org/TBD>.

Flanagan                 Expires January 9, 2020                [Page 2]
Internet-Draft      Clarifying the Record for RFC 32           July 2019

   [RFC-INDEX]
              RFC Editor, "RFC Index", April 2019,
              <https://www.rfc-editor.org/rfc-index.html>.

   [RFC0032]  Cole, J., "Some Thoughts on SRI's Proposed Real Time
              Clock", RFC 32, DOI 10.17487/RFC0032, February 1970,
              <https://www.rfc-editor.org/info/rfc32>.
Show full document text