Re: [Ntp] The bump, or why NTP v5 must specify impulse response

Philip Prindeville <philipp@redfish-solutions.com> Tue, 21 April 2020 17:56 UTC

Return-Path: <philipp@redfish-solutions.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 D27673A08D1 for <ntp@ietfa.amsl.com>; Tue, 21 Apr 2020 10:56:55 -0700 (PDT)
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 ptpf08WiYVOp for <ntp@ietfa.amsl.com>; Tue, 21 Apr 2020 10:56:54 -0700 (PDT)
Received: from mail.redfish-solutions.com (mail.redfish-solutions.com [45.33.216.244]) (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 4E9553A08CD for <ntp@ietf.org>; Tue, 21 Apr 2020 10:56:54 -0700 (PDT)
Received: from macbook2.redfish-solutions.com (macbook2.redfish-solutions.com [192.168.1.39]) (authenticated bits=0) by mail.redfish-solutions.com (8.15.2/8.15.2) with ESMTPSA id 03LHuqNq022279 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 21 Apr 2020 11:56:52 -0600
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Philip Prindeville <philipp@redfish-solutions.com>
In-Reply-To: <39a14fe5-845d-aa3a-f236-5e767b6cce95@nwtime.org>
Date: Tue, 21 Apr 2020 11:56:52 -0600
Cc: ntp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A6E880D-C467-4AC5-A8C2-F3C61B323A53@redfish-solutions.com>
References: <CACsn0cm3jpKZTUQ=novTgVaFhc1xCJgmUF3oOgdrzQa-HgOCUQ@mail.gmail.com> <CAJm83bAqbMMs2W3SyH+3c17wcC85paY4-_jk2SxczgsxBLyYyA@mail.gmail.com> <CAJm83bAQeR_6U3jgmbWzdus3pu+OO2_KP+M9RtbCFYOfDQy4dw@mail.gmail.com> <DB8PR02MB56111CCA23CDCF97A3C9F3E8CFDD0@DB8PR02MB5611.eurprd02.prod.outlook.com> <F7E5836A-4C7A-4A1A-B769-65EADE2C8F5C@gmail.com> <7d909ae3-a830-1270-6920-fa088a56525e@nwtime.org> <6C9832A9-E18B-4DE2-934F-9E471FC22F7B@akamai.com> <bc7920e2-dc81-ba7f-ec24-7926cda8589d@nwtime.org> <alpine.DEB.2.20.2004161430210.5561@grey.csi.cam.ac.uk> <93795d4a-25e7-c918-47d4-44aa6d92ee5e@nwtime.org> <20200416135547.GF412294@roeckx.be> <2d483354-a707-fbca-e914-cbe1479a4c25@nwtime.org> <CAJm83bAMxGrx_PSPQUjERzT2TT_0Tiutx=R0LRF2m9bY4QTj4w@mail.gmail.com> <39a14fe5-845d-aa3a-f236-5e767b6cce95@nwtime.org>
To: Harlan Stenn <stenn@nwtime.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Scanned-By: MIMEDefang 2.84 on 192.168.1.3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/M_ZcupC5y6ZQuBqswIrxeIGvfWs>
X-Mailman-Approved-At: Tue, 21 Apr 2020 11:13:15 -0700
Subject: Re: [Ntp] The bump, or why NTP v5 must specify impulse response
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, 21 Apr 2020 17:56:56 -0000


> On Apr 17, 2020, at 4:48 AM, Harlan Stenn <stenn@nwtime.org> wrote:
> 
> [snip]
> 
> More to the point, NTPv4 and all of its predecessors specified:
> 
> - the packet format
> - the algorithms
> - a set of behavioral limits and specifications
> 
> This means others were allowed to write specifications (regulations)
> assuming and/or relying on "NTP" - the packet format, algorithms, and
> behavior.
> 
> Removing or separating the algorithmic and behavioral specifications
> from the NTP specification at best cost-shifts that discussion
> elsewhere, and I submit it does this to groups that are likely
> completely unaware that they can no longer rely on behavior that they
> had no idea they previously relied on.
> 
> Are you planning to just do a protocol spec and "do the algorithms and
> behavior spec later", or worse yet, let others do that if they think
> it's important?


Not to throw gasoline on the fire, but Postel told me decades ago, “don’t confuse protocol and policy” (he was [ahem] encouraging me to drop 3 paragraphs from the draft of RFC 1048).  It was good advice then and it holds.

Algorithms are, in essence, a “policy” for disciplining a clock.

A compromise might be to define requirements for the protocol parametrically, in terms of drift, jitter, etc. while not defining the algorithms to do that.

This opens the field up to more active research in ways to improve the protocol and the use of clocks without tying anyone’s hands.

The protocol could provide a “reference algorithm” that’s used as a baseline and as an example of a certain performance “envelope” under well-defined circumstances.

Given how long NTPv4 has been around (for both right and wrong reasons), it’s reasonable to expect NTPv5 to live at least half as long.  A lot of technology can potentially emerge during that time and we should have the flexibility to incorporate it as it develops.

Look how far we’ve come since Cesium ovens as reference clocks.

-Philip