[Ntp] Gorry Fairhurst's No Record on draft-ietf-ntp-roughtime-17: (with COMMENT)

Gorry Fairhurst via Datatracker <noreply@ietf.org> Wed, 04 March 2026 17:57 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ntp@ietf.org
Delivered-To: ntp@mail2.ietf.org
Received: from [10.244.6.246] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 5F07EC455DE7; Wed, 4 Mar 2026 09:57:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Gorry Fairhurst via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.59.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <177264702121.97016.7498600677488786507@dt-datatracker-6ff7c68975-7k42g>
Date: Wed, 04 Mar 2026 09:57:01 -0800
Message-ID-Hash: GTB3BVJYWE5IJ7E4BTFTEURCLNUQMIUP
X-Message-ID-Hash: GTB3BVJYWE5IJ7E4BTFTEURCLNUQMIUP
X-MailFrom: noreply@ietf.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: draft-ietf-ntp-roughtime@ietf.org, kodonog@pobox.com, ntp-chairs@ietf.org, ntp@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Subject: [Ntp] Gorry Fairhurst's No Record on draft-ietf-ntp-roughtime-17: (with COMMENT)
List-Id: Network Time Protocol <ntp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/3yH8KmZ-oD4Do9r9ijfgRQI3iJY>
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>

Gorry Fairhurst has entered the following ballot position for
draft-ietf-ntp-roughtime-17: No Record

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-ntp-roughtime/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

## Thanks to the Reviewers

Thanks to Colin Perkins for the TSVART review, and the text proposed to address
that review.

### S5 - Comment
"A Roughtime packet may exceed the maximum deliverable length of a UDP
   packet."
- NiT, I think this could be betteer, perhaps something like:
"The size of a Roughtime packet could exceed the maximum deliverable length of
a UDP
   packet."

### S5 - Comment
  "MTU issues
   may lead to persistent nonresponse due to network devices between
   client and server."
- This seems like an odd term: /MTU issues/. Do you perhaps mean the "Path MTU
may be insufficient to carry a datagram of the required size"? - Or do you mean
that "PMTUD may be unable to determine an effective PMTU", or both? or
something else, please consider a small change.

## S5.2 - Comment
"   The size of the request message SHOULD be at least 1024 bytes when
   the UDP transport mode is used."
- What happens if the interface MTU is too small to allow datagrams with this
size, or the path is unable to deliver datagrams with this size. Is it OK for
the request to fail? - If so, please state this - or please specify what ought
to happen.

## S5.2 - Comment
- As above, but for the return path, we should not assume the two paths have a
symmetric PMTU. Again, please specify what ought to happen. It could be helpful
to also note how a server handles persistent lack of a response.

Gorry Fairhurst