[Ntp] Antw: [EXT] Re: CLOCK_TAI (was NTPv5: big picture)

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Fri, 08 January 2021 07:32 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 E57063A1083 for <ntp@ietfa.amsl.com>; Thu, 7 Jan 2021 23:32:05 -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 cfqHw0h59F5K for <ntp@ietfa.amsl.com>; Thu, 7 Jan 2021 23:32:04 -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 EBE003A107C for <ntp@ietf.org>; Thu, 7 Jan 2021 23:32:03 -0800 (PST)
Received: from mx3.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 956766000050 for <ntp@ietf.org>; Fri, 8 Jan 2021 08:31:59 +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 3F307600004D for <ntp@ietf.org>; Fri, 8 Jan 2021 08:31:56 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Fri, 08 Jan 2021 08:31:56 +0100
Message-Id: <5FF80A6B020000A10003E084@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.0
Date: Fri, 08 Jan 2021 08:31:55 +0100
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: martin.burnicki=40meinberg.de@dmarc.ietf.org, mlichvar@redhat.com, emmanuel.fuste@thalesgroup.com
Cc: "ntp@ietf.org" <ntp@ietf.org>, magnus@rubidium.se
References: <20210102081603.1F63C40605C@ip-64-139-1-69.sjc.megapath.net> <cecaf661-92af-8b35-4c53-2f025c928144@rubidium.se> <20210104164449.GE2992437@localhost> <b1e61f7d-6cea-5e99-69f0-7eae815d9e19@rubidium.se> <20210105083328.GA3008666@localhost> <ba5d2cde-6b5e-d9b6-1877-c4060bf43e80@rubidium.se> <20210105144225.GH3008666@localhost> <35c4be55-b6af-82b5-aacd-d5a591383dec@rubidium.se> <20210105162901.GJ3008666@localhost> <c78ad54e-dd10-fc8e-fc88-cf65f9fb29a5@thalesgroup.com> <20210107115226.GB3415835@localhost> <a0e137c3-5e4a-2277-2e1d-2284b39de309@meinberg.de> <F5292A54020000F16A6A8CFC@gwsmtp.uni-regensburg.de> <31C5A262020000D985F26575@gwsmtp.uni-regensburg.de> <DD4618490200001F6A6A8CFC@gwsmtp.uni-regensburg.de> <56C209690200001686EDC2A6@gwsmtp.uni-regensburg.de>
In-Reply-To: <56C209690200001686EDC2A6@gwsmtp.uni-regensburg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/UljCH8ZB9hhcHY3WXz7Q_CEOtnk>
Subject: [Ntp] Antw: [EXT] Re: CLOCK_TAI (was NTPv5: big picture)
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: Fri, 08 Jan 2021 07:32:06 -0000

>>> Martin Burnicki <martin.burnicki=40meinberg.de@dmarc.ietf.org> schrieb am
07.01.2021 um 16:55 in Nachricht
<a0e137c3-5e4a-2277-2e1d-2284b39de309@meinberg.de>:
> Miroslav Lichvar wrote:
>> On Wed, Jan 06, 2021 at 09:57:56AM +0000, FUSTE Emmanuel wrote:
>>>
>>> I clearly don't understand the resistance to go to a linear TAI like 
>>> form for the core time-stamping format as long as the TAI-UTC offset is 
>>> part of the core protocol frame.
>> 
>> That offset is not always available, e.g. with a DCF77 refclock.
>> Relying on other sources is not always acceptable.
>> 
>>> You will have to do some conversions and adaptations in the OS 
>>> adaptation layer, as today for all NTP implementations, and this layer 
>>> will not be messier as the core is today. No need to wait that operating 
>>> systems fully support a non-leaping timescale, or TAI-UTC offset
natively.
>> 
>> No, it will be messier. That's the other problem.
>> 
>> If your OS doesn't have a TAI clock or it doesn't support timestamping
>> with the TAI clock, you will have to resolve the ambiguity in your NTP
>> implementation. That will not be 100% reliable as you cannot be sure
>> if the timestamp is captured before or after the leap. You are only
>> guessing. If the client doesn't know that the server is only guessing,
>> it may get unexpected errors in measurements and its clock disrupted.
>> 
>> The best thing you can do on such an OS is to suspend the operation
>> around leap second, the same thing as when using a leaping timescale.

Does "around the leap second" mean "until leap smear is complete" in case of
leap smearing?

>> In other words, there is no advantage of using a non-leaping timescale
>> for the time transfer. It would only make things even more messier
>> than they already are.
> 
> Once more, I strongly agree.
> 
> Martin
> -- 
> Martin Burnicki
> 
> Senior Software Engineer
> 
> MEINBERG Funkuhren GmbH & Co. KG
> Email: martin.burnicki@meinberg.de 
> Phone: +49 5281 9309-414
> Linkedin: https://www.linkedin.com/in/martinburnicki/ 
> 
> Lange Wand 9, 31812 Bad Pyrmont, Germany
> Amtsgericht Hannover 17HRA 100322
> Geschäftsführer/Managing Directors: Günter Meinberg, Werner Meinberg,
> Andre Hartmann, Heiko Gerstung
> Websites: https://www.meinberg.de  https://www.meinbergglobal.com 
> Training: https://www.meinberg.academy 
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp