Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03

Miroslav Lichvar <mlichvar@redhat.com> Wed, 24 November 2021 08:25 UTC

Return-Path: <mlichvar@redhat.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 3C8A63A0BCB for <ntp@ietfa.amsl.com>; Wed, 24 Nov 2021 00:25:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.701, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
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 SlGui0f3SliA for <ntp@ietfa.amsl.com>; Wed, 24 Nov 2021 00:25:02 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (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 2F3333A0C98 for <ntp@ietf.org>; Wed, 24 Nov 2021 00:25:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1637742300; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=xOuP/kwFd06xi8+fVPkgdhnj99CWCow41XsGWF2ofEk=; b=APV3Lv0fxKYQu9+juBqB11UmINl9cTTum6pyQlIwCXEuADlHT6vYZi9HzP9uamp0f3ZnzM 8dK46nBb5yPaZ2X8Ys2y7RV2LONQ7y83OqN7/M90Bkq1H22axho7oGIVYWfpJ3P7v5lVuS obC5YpDtR2ii/cLFA4O4qHNBZdKDb+4=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-199-h4o7EtOiPoyRJ3LMLWvQNA-1; Wed, 24 Nov 2021 03:24:59 -0500
X-MC-Unique: h4o7EtOiPoyRJ3LMLWvQNA-1
Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1F197190D340; Wed, 24 Nov 2021 08:24:58 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 4939E19C46; Wed, 24 Nov 2021 08:24:57 +0000 (UTC)
Date: Wed, 24 Nov 2021 09:24:55 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Dan Drown <dan-ntp@drown.org>
Cc: ntp@ietf.org
Message-ID: <YZ3213QDZweiN3bk@localhost>
References: <20211123131501.Horde.ErUH7VWw3Nr2PFkAGzGIEuI@mail.drown.org>
MIME-Version: 1.0
In-Reply-To: <20211123131501.Horde.ErUH7VWw3Nr2PFkAGzGIEuI@mail.drown.org>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/SmJ3Mx_0ZHCeIkBqxjPl-_C5y98>
Subject: Re: [Ntp] 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 08:25:06 -0000

On Tue, Nov 23, 2021 at 01:15:01PM -0600, Dan Drown wrote:
> 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.

All three suggestions make sense to me. Should make it clearer.
Thanks!

> 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)"

-- 
Miroslav Lichvar