IETF Logo Mail Archive

[Ntp] [Technical Errata Reported] RFC8877 (7012)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 04 July 2022 22:23 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 6DA74C14F74D for <ntp@ietfa.amsl.com>; Mon, 4 Jul 2022 15:23:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.657
X-Spam-Level:
X-Spam-Status: No, score=-1.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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 f6FVrnEsMHtf for <ntp@ietfa.amsl.com>; Mon, 4 Jul 2022 15:23:06 -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 EEAEAC14F74C for <ntp@ietf.org>; Mon, 4 Jul 2022 15:23:06 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 9F27B289F1; Mon, 4 Jul 2022 15:23:06 -0700 (PDT)
To: tal.mizrahi.phd@gmail.com, joachim.fabini@tuwien.ac.at, acmorton@att.com, ek.ietf@gmail.com, evyncke@cisco.com, odonoghue@isoc.org, dsibold.ietf@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: nmalykh@ieee.org, ntp@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220704222306.9F27B289F1@rfcpa.amsl.com>
Date: Mon, 04 Jul 2022 15:23:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/ZY7IK9R6X4v5Wreq9TCSskrJif4>
Subject: [Ntp] [Technical Errata Reported] RFC8877 (7012)
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: Mon, 04 Jul 2022 22:23:11 -0000

The following errata report has been submitted for RFC8877,
"Guidelines for Defining Packet Timestamps".

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

--------------------------------------
Type: Technical
Reported by: Nikolai Malykh <nmalykh@ieee.org>

Section: 4.2

Original Text
-------------
   Wraparound:
      This time format wraps around every 2^(32) seconds, which is
      roughly 136 years.  The next wraparound will occur in the year
      2036.


Corrected Text
--------------
   Wraparound:
      This time format wraps around every 2^(32) seconds, which is
      roughly 136 years.  The next wraparound will occur in the year
      2106.


Notes
-----
1970+136=2106, not 2036

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC8877 (draft-ietf-ntp-packet-timestamps-09)
--------------------------------------
Title               : Guidelines for Defining Packet Timestamps
Publication Date    : September 2020
Author(s)           : T. Mizrahi, J. Fabini, A. Morton
Category            : INFORMATIONAL
Source              : Network Time Protocols
Area                : Internet
Stream              : IETF
Verifying Party     : IESG

v2.23.0 | Report a Bug | By Email