Re: [Ntp] NTPv5 draft

Miroslav Lichvar <mlichvar@redhat.com> Tue, 01 December 2020 08:20 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 0EC4F3A0AE5 for <ntp@ietfa.amsl.com>; Tue, 1 Dec 2020 00:20:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 mel7zaJ7UWi7 for <ntp@ietfa.amsl.com>; Tue, 1 Dec 2020 00:20:11 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17D4B3A0AF3 for <ntp@ietf.org>; Tue, 1 Dec 2020 00:20:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1606810810; 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=MclH31ASGD5TFWf8u/itKKXfdA1svtd3JiEdbe9AY9k=; b=dOu3/p8J1VpP/A6E6Sk+yQWRtVSjeH4+Hf0BOcC5bfLXqINtB9csSiZoAxk1x52T5PNJyv GJ+Y9bU1lGPRrwuVt72w11E/mrg0nWZeTa34HVvdzK2jwfS8WHp+2zCHgDGuGTU/qZ5PDt Q/NYEGaVOvsWDhroSWj0ApdNnFjBp8k=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-486-rH1x1V9XMgy9_CuDtUcFhQ-1; Tue, 01 Dec 2020 03:20:08 -0500
X-MC-Unique: rH1x1V9XMgy9_CuDtUcFhQ-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 17E4A9A220; Tue, 1 Dec 2020 08:20:07 +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 C96E019C44; Tue, 1 Dec 2020 08:20:05 +0000 (UTC)
Date: Tue, 01 Dec 2020 09:20:03 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Steven Sommars <stevesommarsntp@gmail.com>
Cc: Kurt Roeckx <kurt@roeckx.be>, Dieter Sibold <dsibold.ietf@gmail.com>, NTP WG <ntp@ietf.org>
Message-ID: <20201201082003.GC1900232@localhost>
References: <20201111161947.GG1559650@localhost> <AA848C67-CFB7-43FC-B190-FD3911360373@gmail.com> <20201130200240.GI971977@roeckx.be> <CAD4huA79u3NkR8LS96Gqgs58mJguoN7=p=CJnitzgh_RzNWCVg@mail.gmail.com>
MIME-Version: 1.0
In-Reply-To: <CAD4huA79u3NkR8LS96Gqgs58mJguoN7=p=CJnitzgh_RzNWCVg@mail.gmail.com>
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/QqxUuDi5csIqbGd8BxWRCKg2W-E>
Subject: Re: [Ntp] NTPv5 draft
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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, 01 Dec 2020 08:20:13 -0000

On Mon, Nov 30, 2020 at 02:32:35PM -0600, Steven Sommars wrote:
> Agree, these fields could use better descriptions or (better) replacement.
> 
> One manufacturer (LeoNTP) lowers precision to indicate reduced accuracy and
> claims to obey the NTP specification.

I think that's just a workaround for limited resolution of the root
dispersion field. That's no longer a problem with the NTPv5 draft,
where the field has a resolution of 3.7 nanoseconds.

> Should a stratum 1 NTP server report root distance=0  ?   National labs
> differ.

If we ignore rounding, then no, there is no single clock that can
claim to be perfectly accurate to UTC. I think the only case where it
makes sense to report a dispersion and delay of exact zero is a clock
in the local/orphan mode, which is the "true" time for an isolated
network.

> Using NTP short format the smallest non-zero root dispersion is 15
> microseconds.  One can argue for finer granularity

The draft does that.

-- 
Miroslav Lichvar