IETF Logo Mail Archive

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

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Wed, 09 December 2020 07:05 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.de>
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 7AFF03A0D1C for <ntp@ietfa.amsl.com>; Tue, 8 Dec 2020 23:05:10 -0800 (PST)
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 8BEgOCv5Yljz for <ntp@ietfa.amsl.com>; Tue, 8 Dec 2020 23:05:09 -0800 (PST)
Received: from mx3.uni-regensburg.de (mx3.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:4:4e79]) (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 1AC233A0B26 for <ntp@ietf.org>; Tue, 8 Dec 2020 23:05:08 -0800 (PST)
Received: from mx3.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 72467600004A for <ntp@ietf.org>; Wed, 9 Dec 2020 08:05:06 +0100 (CET)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx3.uni-regensburg.de (Postfix) with ESMTP id 426E4600004D for <ntp@ietf.org>; Wed, 9 Dec 2020 08:05:06 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Wed, 09 Dec 2020 08:05:06 +0100
Message-Id: <5FD07720020000A10003D684@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.0
Date: Wed, 09 Dec 2020 08:05:04 +0100
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: Hal Murray <hmurray@megapathdsl.net>
Cc: "ntp@ietf.org" <ntp@ietf.org>
References: <5FCF48F1020000A10003D5E1@gwsmtp.uni-regensburg.de> <F8A667ED0200007A43047E14@gwsmtp.uni-regensburg.de>
In-Reply-To: <F8A667ED0200007A43047E14@gwsmtp.uni-regensburg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/vI0c51Wt7kY6vpN8-h7MrF6y160>
Subject: [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 07:05:10 -0000

>>> Hal Murray <hmurray@megapathdsl.net> schrieb am 08.12.2020 um 12:30 in
Nachricht <20201208113010.0F8AA40605C@ip-64-139-1-69.sjc.megapath.net>:
>>  Should NTPv5 have such a (similar) capability?
> 
> My opinion.  No.
> 
> I think we should separate the protocol description from the implementation 
> details.

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?

Regards,
Ulrich

v2.23.0 | Report a Bug | By Email