Re: [Ntp] Temperature Compensation for NTP?

Harlan Stenn <stenn@nwtime.org> Tue, 08 December 2020 21:50 UTC

Return-Path: <stenn@nwtime.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 67B3A3A11BE for <ntp@ietfa.amsl.com>; Tue, 8 Dec 2020 13:50:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-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 jfNdQGlbWhVp for <ntp@ietfa.amsl.com>; Tue, 8 Dec 2020 13:50:52 -0800 (PST)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) (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 DF4CC3A11BB for <ntp@ietf.org>; Tue, 8 Dec 2020 13:50:52 -0800 (PST)
Received: from [10.208.75.152] (075-139-201-087.res.spectrum.com [75.139.201.87]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4CrDQ44VLHzMNC7; Tue, 8 Dec 2020 21:50:52 +0000 (UTC)
To: ntp@ietf.org
References: <20201208214421.CE92B40605C@ip-64-139-1-69.sjc.megapath.net>
From: Harlan Stenn <stenn@nwtime.org>
Message-ID: <d406413e-c539-cb74-daf4-5298a8a1db83@nwtime.org>
Date: Tue, 08 Dec 2020 13:50:52 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <20201208214421.CE92B40605C@ip-64-139-1-69.sjc.megapath.net>
Content-Type: text/plain; charset="windows-1252"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/qj7zAPEofjzJbVPlsWdWaWYbMvk>
Subject: Re: [Ntp] Temperature Compensation for NTP?
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, 08 Dec 2020 21:50:54 -0000

On 12/8/2020 1:44 PM, Hal Murray wrote:
> 
> philipp@redfish-solutions.com said:
>> Given we have better understanding now of the thermal stability of solid
>> state (crystal) oscillators, why not include that into the algorithm if we’re
>> going to flesh it out specifically? 
> 
> I think the algorithm(s) should be split out to a separate document, if any.

In which case somebody will only implement the protocol and do whatever
they want with the algorithms, and clients will connect to this server
and there will be a significant chance that because of the different
algorithms, the behavior will be different and there will be train wrecks.

We've already seen what happens when people put leap smearing servers on
the public internet, and somebody says "Oh, I got bitten by not having
enough servers last time, so I'll use 4 now" and then the learned that
during the next leap event two of their upstreams offered correct time
while 2 offered smeared time, so "no consensus" on time and off they went.

Different timing algorithms will cause much bigger problems.

NTP is all about a defined impulse response.

-- 
Harlan Stenn <stenn@nwtime.org>
http://networktimefoundation.org - be a member!