IETF Logo Mail Archive

Re: [Ntp] Temperature Compensation for NTP?

Kurt Roeckx <kurt@roeckx.be> Tue, 08 December 2020 12:04 UTC

Return-Path: <kurt@roeckx.be>
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 AA58E3A0C51 for <ntp@ietfa.amsl.com>; Tue, 8 Dec 2020 04:04:50 -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, SPF_PASS=-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 LHGqfO-FwXXI for <ntp@ietfa.amsl.com>; Tue, 8 Dec 2020 04:04:48 -0800 (PST)
Received: from excelsior.roeckx.be (excelsior.roeckx.be [IPv6:2a05:7300:0:100::3]) (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 A56063A0C4A for <ntp@ietf.org>; Tue, 8 Dec 2020 04:04:48 -0800 (PST)
Received: from intrepid.roeckx.be (localhost [127.0.0.1]) by excelsior.roeckx.be (Postfix) with ESMTP id 21463A8A010D; Tue, 8 Dec 2020 12:04:45 +0000 (UTC)
Received: by intrepid.roeckx.be (Postfix, from userid 1000) id D20021FE0DE5; Tue, 8 Dec 2020 13:04:44 +0100 (CET)
Date: Tue, 08 Dec 2020 13:04:44 +0100
From: Kurt Roeckx <kurt@roeckx.be>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <X89r3DaFE9RSo5NX@roeckx.be>
References: <5FCF48F1020000A10003D5E1@gwsmtp.uni-regensburg.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5FCF48F1020000A10003D5E1@gwsmtp.uni-regensburg.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/xMTy63AZlaM0SxM13U9Qf2ZnIgY>
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 12:04:51 -0000

On Tue, Dec 08, 2020 at 10:35:45AM +0100, Ulrich Windl wrote:
> Should NTPv5 have such a (similar) capability?

I'm not sure what you're asking. This just seems to be an
implementation detail. You apply a correction, and as a result,
hopefully, your maximum error should get smaller. I don't see
how it's relevant for the protocol.

Should the RFC also cover which corrections you can all apply, and
how that has an effect on the values you send to the client? There
is at least a proposal where that would be outside the scope.


Kurt

v2.23.0 | Report a Bug | By Email