[Ntp] [Errata Held for Document Update] RFC5905 (6423)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 27 July 2022 15:30 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65104C14F6E7; Wed, 27 Jul 2022 08:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nadAAYBxryXT; Wed, 27 Jul 2022 08:30:52 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95BD3C16ECC6; Wed, 27 Jul 2022 08:30:52 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 69C156AA26; Wed, 27 Jul 2022 08:30:52 -0700 (PDT)
To: stijnvandrongelen@gmail.com, mills@udel.edu, jrmii@isc.org, jack.burbank@jhuapl.edu, william.kasch@jhuapl.edu
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: ek.ietf@gmail.com, iesg@ietf.org, ntp@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220727153052.69C156AA26@rfcpa.amsl.com>
Date: Wed, 27 Jul 2022 08:30:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/MWFci39svE8066FqVeYw9BxeR-Y>
Subject: [Ntp] [Errata Held for Document Update] RFC5905 (6423)
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jul 2022 15:30:56 -0000

The following errata report has been held for document update 
for RFC5905, "Network Time Protocol Version 4: Protocol and Algorithms Specification". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6423

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Stijn van Drongelen <stijnvandrongelen@gmail.com>
Date Reported: 2021-02-07
Held by: Erik Kline (IESG)

Section: 6

Original Text
-------------
| 1 Jan 1972  | 41,317     | 0   | 2,272,060,800 | First day UTC    |

Corrected Text
--------------
| 1 Jan 1972  | 41,317     | 0   | 2,272,060,800 | First day "modern" UTC |

Notes
-----
The initial definition of UTC was introduced in 1963 with CCIR Recommendation 374. The time standard specified that seconds had a varying duration. In 1970, CCIR Recommendation 460 introduced the current definition of UTC, using leap seconds, which was implemented on the first second of 1972. Consult D. McCarthy's "Note on Coordinated Universal Time" (numbered CCTF/09-32 by the Consultative Committee for Time and Frequency of the BIPM) for more information.

---

There may perhaps be more precise terminology than "modern", but this point should be addressed by a document that updates or replaces this one.

--------------------------------------
RFC5905 (draft-ietf-ntp-ntpv4-proto-13)
--------------------------------------
Title               : Network Time Protocol Version 4: Protocol and Algorithms Specification
Publication Date    : June 2010
Author(s)           : D. Mills, J. Martin, Ed., J. Burbank, W. Kasch
Category            : PROPOSED STANDARD
Source              : Network Time Protocols
Area                : Internet
Stream              : IETF
Verifying Party     : IESG