[Ntp] Antw: [EXT] comments on draft‑mlichvar‑ntp‑ntpv5‑03

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Wed, 24 November 2021 07:32 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.de>
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 E1DDE3A0C48 for <ntp@ietfa.amsl.com>; Tue, 23 Nov 2021 23:32:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GytkF1k_KlRl for <ntp@ietfa.amsl.com>; Tue, 23 Nov 2021 23:32:21 -0800 (PST)
Received: from mx3.uni-regensburg.de (mx3.uni-regensburg.de [194.94.157.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21FBB3A0C47 for <ntp@ietf.org>; Tue, 23 Nov 2021 23:32:20 -0800 (PST)
Received: from mx3.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C9937600004F for <ntp@ietf.org>; Wed, 24 Nov 2021 08:32:14 +0100 (CET)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx3.uni-regensburg.de (Postfix) with ESMTP id A5314600004D for <ntp@ietf.org>; Wed, 24 Nov 2021 08:32:10 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Wed, 24 Nov 2021 08:32:10 +0100
Message-Id: <619DEA79020000A10004599E@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.1
Date: Wed, 24 Nov 2021 08:32:09 +0100
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: dan-ntp@drown.org, "ntp@ietf.org" <ntp@ietf.org>
References: <20211123131501.Horde.ErUH7VWw3Nr2PFkAGzGIEuI@mail.drown.org>
In-Reply-To: <20211123131501.Horde.ErUH7VWw3Nr2PFkAGzGIEuI@mail.drown.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/4zlN2xkLA3rnHMK8I8zBLSlWP08>
Subject: [Ntp] Antw: [EXT] comments on draft‑mlichvar‑ntp‑ntpv5‑03
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Nov 2021 07:32:26 -0000

>>> Dan Drown <dan-ntp@drown.org> schrieb am 23.11.2021 um 20:15 in Nachricht
<20211123131501.Horde.ErUH7VWw3Nr2PFkAGzGIEuI@mail.drown.org>:
> After reading this draft, I'm glad to see these things are included:
> 
> 1. the unknown leap seconds flag seems useful for embedded systems  
> that don't have easy access to that information
> 2. the explicit interleaved mode with server cookies
> 3. client timestamps are switched to a client cookie
> 4. the removal of all modes except client/server
> 
> I have a few comments, and I think I'll break them up into multiple  
> emails to make discussion easier.
> 
> This email will be on the "3. Data Types" section.
> 
> For the time16 definition "the maximum value is 32767/32768" This  
> confused me on first read because I parsed it as either/or at first  
> which made no sense. I had to think about it until I realized this was  
> talking about a fraction. I'm proposing a change to: "the maximum  
> value is the fraction 32767/32768 (almost 1 second)"
> 
> Should the log2 format be explained in more detail in this section?  
> I've seen a lot of people confused about this data type, so I'm hoping  
> a definition would help. Maybe something like "log2 ‑ an 8 bit signed  
> integer representing the rounded log2 value of seconds. For example, a  
> log2 value of ‑2 would be 2 to the power of ‑2 or 0.25 seconds"
> 
> Should the change from NTPv4's time32 format be mentioned here?   
> Something like:
> "A 32‑bit fixed‑point type containing values in seconds. It has 4  
> unsigned integer bits and 28 fractional bits. The maximum value is 16  
> seconds and the resolution is about 3.7 nanoseconds. Note: this is  
> different than the 32 bit time format in NTPv4 (RFC5905)"

I wonder: Up to NTPv3 floating-point math was avoided, but starting in NTPv4
floating-point math is used.
Do we want to use floating-point math in NTPv5, too? What about those embedded
systems?
If so, are those many special fixed-point formats justified (outside of
packets)?

Regards,
Ulrich


> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp