Re: [Ntp] Antw: [EXT] Re: Temperature Compensation for NTP?

FUSTE Emmanuel <emmanuel.fuste@thalesgroup.com> Wed, 09 December 2020 09:55 UTC

Return-Path: <emmanuel.fuste@thalesgroup.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 D994E3A140D for <ntp@ietfa.amsl.com>; Wed, 9 Dec 2020 01:55:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.122
X-Spam-Level:
X-Spam-Status: No, score=-2.122 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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=thalesgroup.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 rwacuCqt42Qj for <ntp@ietfa.amsl.com>; Wed, 9 Dec 2020 01:55:20 -0800 (PST)
Received: from thsbbfxrt01p.thalesgroup.com (thsbbfxrt01p.thalesgroup.com [192.54.144.131]) (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 A53933A1405 for <ntp@ietf.org>; Wed, 9 Dec 2020 01:55:19 -0800 (PST)
Received: from thsbbfxrt01p.thalesgroup.com (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4CrXTw3Tzzz45V5 for <ntp@ietf.org>; Wed, 9 Dec 2020 10:55:16 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thalesgroup.com; s=xrt20181201; t=1607507716; bh=YYPIt8oftpOBJVm6c9jPaR0PFFJGMVJpCv2AshkN7kI=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Transfer-Encoding:MIME-Version:From; b=UtVnTD8CY/UYpDdAnR4l3f2bJM0GjR3q4vOMqmkShUv1H0jWIdYrI/aDjlU22LnSi YLJG2XI1zDB+4vTmGYX9lMOGysnFE266vFUdcukyykoL8J/PpmqXZQnKNeGlUE1XID tGkELcYxStcvQ3u2Fj2WRNMjUfw/9KKnryfhgnlYfClIRADCgBXn9CIGTGPJ+ftAgM L6eUb2qozaDSZKl3wY+tN5xpGgU4w9YVzQ8N2EOJAGTPpl8b705cgsD2Qezh4oS8DQ BHuaI1NLFRUKwnuXAGX6SYKLIxq7mI//mWQZJ/c8axjliyNZSQKqy+OMFyijRljApx SJSvjqTbWZ7Eg==
From: FUSTE Emmanuel <emmanuel.fuste@thalesgroup.com>
To: "ntp@ietf.org" <ntp@ietf.org>
Thread-Topic: [Ntp] Antw: [EXT] Re: Temperature Compensation for NTP?
Thread-Index: AQHWzhFkVzHV44TUREqty05q14y/EQ==
Date: Wed, 09 Dec 2020 09:55:15 +0000
Message-ID: <06a3f575-0f32-8686-40c4-e948e619527e@thalesgroup.com>
References: <5FCF48F1020000A10003D5E1@gwsmtp.uni-regensburg.de> <F8A667ED0200007A43047E14@gwsmtp.uni-regensburg.de> <5FD07720020000A10003D684@gwsmtp.uni-regensburg.de>
In-Reply-To: <5FD07720020000A10003D684@gwsmtp.uni-regensburg.de>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
x-pmwin-version: 4.0.3, Antivirus-Engine: 3.79.0, Antivirus-Data: 5.80
Content-Type: text/plain; charset="utf-8"
Content-ID: <D80EEABAC99D7A419950BF049504C620@iris.infra.thales>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/XBNahMQq29ntuEEqSFJ3zgGq5uU>
Subject: Re: [Ntp] Antw: [EXT] Re: 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: Wed, 09 Dec 2020 09:55:28 -0000

Le 09/12/2020 à 08:05, Ulrich Windl a écrit :
>
> As said before, I think describing the protocol without the algorithms and clock model behind does not make sense, and when describing the clock model, one has to explain where clock wander and error estimate mainly comes from.
> Also one of the design goals of NTP has been to provide "reasonalbe" time and error estimate even when there are no servers available and to lengthen the polling interval. I think considering the temperature (optionally), can help improving those capabilities, so why ignore?
>
Because improving capabilities of the oscillator is not the NTP job. NTP 
algorithm is a consumer of those capabilities, we should have way to 
provide these capabilities to the NTP algorithm but it is not the job of 
NTP to interfere with them.
Chrony implement poor man temperature compensation, great. But if I use 
TCXO or OCXO considering the temperature (and which one ?) is non sense.
And I could even implement this basic crystal TC in a kernel driver for 
better integration with the timekeeping machinery and interface for the 
same result, NTP is completely out of the picture.
If I know the aging curve I could implement it too in this same driver 
or in chrony to better free running precision.
An oscillator could characterized by stability temp stability in ppm/c, 
Alan variance, phase noise, aging curve and more.
For sure, only a metrology lab or the oscillator maker could give you 
the characteristics of an oscillator and on most hardware and computers, 
the oscillator spec are not provided or know.
NTP appliance provider job is to use such advanced oscillators and 
compensation technique to provide better global characteristics and be 
better clock source for serving NTP.
The job of NTP is to steer the system clock and so possibly the 
underlying oscillator in one way and to provide measurements in the 
other way.
So the only question is : what property/characteristics/metric of the 
underlying oscillator/clock the NTP servo/clock model need to do its job 
better rather than default values ?
With the modern granularity and precision of measurements thanks to HW 
time stamping availability and oscillators quality, the spectrum of 
possibility is too wide for hard coded good for all default values.

Regards,
Emmanuel.