[Ntp] [Editorial Errata Reported] RFC5905 (8903)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 06 May 2026 15:54 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ntp@ietf.org
Delivered-To: ntp@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 39D8EEA04C59; Wed, 6 May 2026 08:54:23 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 1D2E92AC7EA; Wed, 6 May 2026 08:54:23 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20260506155423.1D2E92AC7EA@rfcpa.rfc-editor.org>
Date: Wed, 06 May 2026 08:54:23 -0700
Message-ID-Hash: LPL5IWN4CJAQPS5UOZEJY2UFQ2XVUMSP
X-Message-ID-Hash: LPL5IWN4CJAQPS5UOZEJY2UFQ2XVUMSP
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ntp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: aidanjredden@gmail.com, mills@udel.edu, jrmii@isc.org, jack.burbank@jhuapl.edu, william.kasch@jhuapl.edu, ntp@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Ntp] [Editorial Errata Reported] RFC5905 (8903)
List-Id: Network Time Protocol <ntp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/V6rQMj2gbu58Kdz56vO-WACg5gU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Owner: <mailto:ntp-owner@ietf.org>
List-Post: <mailto:ntp@ietf.org>
List-Subscribe: <mailto:ntp-join@ietf.org>
List-Unsubscribe: <mailto:ntp-leave@ietf.org>

The following errata report has been submitted 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/eid8903

--------------------------------------
Type: Editorial
Reported by: Aidan R <aidanjredden@gmail.com>

Section: 11.2.1

Original Text
-------------
This results in three tuples, lowpoint (p, -1, theta -
   lambda), midpoint (p, 0, theta), and highpoint (p, +1, theta +
   lambda), where lambda is the root synchronization distance.

Corrected Text
--------------
This results in three tuples, lowpoint (p, -1, theta -
   LAMBDA), midpoint (p, 0, theta), and highpoint (p, +1, theta +
   LAMBDA), where LAMBDA is the root synchronization distance.

Notes
-----
Two distinct quantities are inconsistently referred to as either "lambda" or "LAMBDA": the peer synchronisation distance, and the root synchronisation distance.
In Section 10, the peer synchronisation distance is defined as (delta / 2) + epsilon and denoted by the minuscule lambda.
In section 11.2.3, the root synchronisation distance is defined as EPSILON + DELTA / 2 and denoted by the majuscule LAMBDA. The root synchronisation distance is also referred to as LAMBDA in Section 4.
However, in sections 11.2.1 and 11.2.2, the root synchronisation distance is referred to with the minuscule lambda, leading to an editorial inconsistency between the identifiers for peer and root synchronisation distances.

Instructions:
-------------
This erratum is currently posted as "Reported". (If it is spam, it 
will be removed shortly by the RFC Production Center.) Please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
will log in to change the status and edit the report, if necessary.

--------------------------------------
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
Stream              : IETF
Verifying Party     : IESG