IETF Logo Mail Archive

[Ntp] Antw: [EXT] Re: An NTPv5 design sketch

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Tue, 21 April 2020 14:04 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 2B11B3A0D08 for <ntp@ietfa.amsl.com>; Tue, 21 Apr 2020 07:04:49 -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=unavailable 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 Cj2ukRNCBZqR for <ntp@ietfa.amsl.com>; Tue, 21 Apr 2020 07:04:43 -0700 (PDT)
Received: from mx3.uni-regensburg.de (mx3.uni-regensburg.de [194.94.157.148]) (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 38BFF3A0CE3 for <ntp@ietf.org>; Tue, 21 Apr 2020 07:00:53 -0700 (PDT)
Received: from mx3.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4BD836000051 for <ntp@ietf.org>; Tue, 21 Apr 2020 16:00:42 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx3.uni-regensburg.de (Postfix) with ESMTP id 7D795600004D for <ntp@ietf.org>; Tue, 21 Apr 2020 16:00:40 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Tue, 21 Apr 2020 16:00:40 +0200
Message-Id: <5E9EFC87020000A1000386A5@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.2.1
Date: Tue, 21 Apr 2020 16:00:39 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: Rich Salz <rsalz=40akamai.com@dmarc.ietf.org>, Kyle Rose <krose@krose.org>
Cc: Daniel Franke <dfoxfranke@gmail.com>, "ntp@ietf.org" <ntp@ietf.org>, mlichvar@redhat.com
References: <CAJm83bBV+Pox3r6KU49ShwMOvr=R+U_vDKJtSZhfT6XX4qWmbA@mail.gmail.com> <20200414112541.GD1945@localhost> <CAJm83bCxuS_X68-pvpOWCPSmjAjTeYNJVuuOEhV-i82R7B28Mg@mail.gmail.com> <20200414155241.GF1945@localhost> <CAJm83bC1EhwQQ=+B7XPbEkvhOWvxU8zjCd290Fj5N43aMJQTkg@mail.gmail.com> <20200415072023.GG1945@localhost> <CAJm83bAEDuLk6vSa82D3smXO4x7iDywoy+FpC=gdm=m3SLrVLg@mail.gmail.com> <20200416082557.GI1945@localhost> <1ECC0FB5-3079-471E-847D-6E8DFBE1B9D7@akamai.com> <25459_1587477108_5E9EFA73_25459_2_31_CAJU8_nUXUEtsddE9byQgEfMknLSz8ywMs23CNyYKFKOYPgLbQA@mail.gmail.com>
In-Reply-To: <25459_1587477108_5E9EFA73_25459_2_31_CAJU8_nUXUEtsddE9byQgEfMknLSz8ywMs23CNyYKFKOYPgLbQA@mail.gmail.com>
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/FGbC4Mn8pd35lHEYZqAdgMYv7m8>
Subject: [Ntp] Antw: [EXT] Re: An NTPv5 design sketch
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 14:04:49 -0000

>>> Kyle Rose <krose@krose.org> schrieb am 21.04.2020 um 15:51 in Nachricht
<25459_1587477108_5E9EFA73_25459_2_31_CAJU8_nUXUEtsddE9byQgEfMknLSz8ywMs23CNyYKF
OYPgLbQA@mail.gmail.com>:
> On Tue, Apr 21, 2020 at 9:35 AM Salz, Rich <rsalz=
> 40akamai.com@dmarc.ietf.org> wrote:
> 
>>
>> >    The device may be very simple. It may not have an OS and NTP may be
>>     the only networking it does. It could be measuring intervals in a
>>     physics experiment, or controlling a robot in a factory.
>>
>> I would like to see this use-case *not* be a requirement for NTPv5.
>>
> 
> Strong agree, but because NTP's purpose is to synchronize wallclock time
> first. Intervals are a second-class citizen, and anyway conflict with the
> first requirement once you get beyond very short intervals.

An interesting concept would be a "virtually corrected (software) clock" that leaves the OS clock alone, keeping the offset and drift als variable. So at any time the OS clock could be "fixed" from the virtual clock as if it were continuously adjusted all the time. Eventually this would allow to run multiple versions of NTP on a single host ;-)

v2.23.0 | Report a Bug | By Email