IETF Logo Mail Archive

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

Dan Drown <dan-ntp@drown.org> Tue, 30 November 2021 03:30 UTC

Return-Path: <dan-ntp@drown.org>
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 7BA6F3A0CB9 for <ntp@ietfa.amsl.com>; Mon, 29 Nov 2021 19:30:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.809
X-Spam-Level: *
X-Spam-Status: No, score=1.809 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, RCVD_IN_XBL=0.375, SPF_PASS=-0.001] autolearn=no 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 efSldwXsZo4C for <ntp@ietfa.amsl.com>; Mon, 29 Nov 2021 19:30:14 -0800 (PST)
Received: from vps3.drown.org (vps3.drown.org [IPv6:2600:3c00::f03c:91ff:fedf:5654]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 448623A0CB8 for <ntp@ietf.org>; Mon, 29 Nov 2021 19:30:14 -0800 (PST)
Received: by vps3.drown.org (Postfix, from userid 48) id F10422FC477; Mon, 29 Nov 2021 21:30:09 -0600 (CST)
Received: from 2603-8080-2709-c400-8d88-6649-85f3-d6ab.res6.spectrum.com (2603-8080-2709-c400-8d88-6649-85f3-d6ab.res6.spectrum.com [2603:8080:2709:c400:8d88:6649:85f3:d6ab]) by mail.drown.org (Horde Framework) with HTTPS; Mon, 29 Nov 2021 21:30:09 -0600
Date: Mon, 29 Nov 2021 21:30:09 -0600
Message-ID: <20211129213009.Horde.ZI8mIvl18cySSVg4h4DkEhj@mail.drown.org>
From: Dan Drown <dan-ntp@drown.org>
To: ntp@ietf.org
References: <20211123131501.Horde.ErUH7VWw3Nr2PFkAGzGIEuI@mail.drown.org> <20211124223810.Horde.KKjrsykVQUMJgW4WVO5ZZmt@mail.drown.org> <YZ9ZADfVlh6z9I4N@localhost> <20211125211838.Horde.B6KZzBvmcXd79vBLQemYwkA@mail.drown.org> <YaSl6dVISGbBCMgc@localhost>
In-Reply-To: <YaSl6dVISGbBCMgc@localhost>
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset="utf-8"; format="flowed"; DelSp="Yes"
MIME-Version: 1.0
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/snS0cSOwS19m7kZjKTm5UToxfQ4>
Subject: Re: [Ntp] comments on draft-mlichvar-ntp-ntpv5-03 / Message Format
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: Tue, 30 Nov 2021 03:30:16 -0000

Quoting Miroslav Lichvar <mlichvar@redhat.com>:
> I'd like to keep the word "offset" there. Maybe the explanation can be
> added in parenthesis like this?
>
>       *  In the UTC (0) and TAI (1) timescales it is the TAI-UTC offset
>          (TAI minus UTC) as a signed integer, or 0x8000 if unknown.
>
>       *  In the UT1 timescale (2) it is the UT1-UTC offset (UT1 minus
>          UTC) using the time16 type (0x8000 if unknown).
>
>       *  In the leap-smeared UTC, it is the current offset between the
>          leap smeared time and UTC (former minus latter) using the
>          time16 type (0x8000 if unknown).

I would be fine with that.  Does leap-smeared UTC need a (3) to  
identify the scale identifier?

v2.23.0 | Report a Bug | By Email