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

Martin Burnicki <martin.burnicki@meinberg.de> Mon, 11 January 2021 09:58 UTC

Return-Path: <martin.burnicki@meinberg.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 593713A0489 for <ntp@ietfa.amsl.com>; Mon, 11 Jan 2021 01:58:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level:
X-Spam-Status: No, score=-2.361 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, 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=meinberg.de
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 Y-HK06VD1fdJ for <ntp@ietfa.amsl.com>; Mon, 11 Jan 2021 01:58:32 -0800 (PST)
Received: from server1a.meinberg.de (server1a.meinberg.de [176.9.44.212]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FD183A046B for <ntp@ietf.org>; Mon, 11 Jan 2021 01:58:31 -0800 (PST)
Received: from srv-kerioconnect.py.meinberg.de (unknown [193.158.22.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by server1a.meinberg.de (Postfix) with ESMTPSA id 0D8EC71C0598; Mon, 11 Jan 2021 10:58:30 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=meinberg.de; s=dkim; t=1610359110; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=N3XAKJNovNDhl1xd8jOoUkDUZD+1NOPXEquGHXf0/ck=; b=KBgK/D66SeZfP1wnJ5LYx5Yr9pjCdr0ybaS3OXIxQkPcudsMqu9CPlEEvC4MGUfBoZePVP paPD0GzDIUo+7AQmtDChT1lpxxYzH8/oo7qTsHMGiuIZfK+pt1R+oxPO8NVXA+NhRm0sxZ szFC1+FeyRltttInvZm/6mSJpsA2IrEy4FuvnGSuJBOoKUFEQGUgA/f1ZS7O4/JKrAlalK iJCSz2WRgk9Hiqhw3gcoEfu5PpWgvOknxGDzmAgSRDfutHqdnReLpztOj4oxY/E4vhJCQ3 4BW1r+VOtBrlO+yGjx3mHy2QwMPQYqgcIiv0cn9f52dzbBGUYv5zOcqeQaBtSA==
X-Footer: bWVpbmJlcmcuZGU=
Received: from localhost ([127.0.0.1]) by srv-kerioconnect.py.meinberg.de with ESMTPSA (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)); Mon, 11 Jan 2021 10:58:28 +0100
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, doug.arnold@meinberg-usa.com, 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> <5FF80A6B020000A10003E084@gwsmtp.uni-regensburg.de> <0D49017F-D7C4-49C5-936D-272B633D5575@meinberg-usa.com> <5FFBF681020000A10003E15D@gwsmtp.uni-regensburg.de>
From: Martin Burnicki <martin.burnicki@meinberg.de>
Organization: Meinberg Funkuhren GmbH & Co. KG, Bad Pyrmont, Germany
Message-ID: <af158418-a9ec-57e8-1a5b-c698fe903330@meinberg.de>
Date: Mon, 11 Jan 2021 10:58:27 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <5FFBF681020000A10003E15D@gwsmtp.uni-regensburg.de>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/JzBWHbLOsaAjsshePufNqRrymRQ>
Subject: Re: [Ntp] Antw: Re: 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: Mon, 11 Jan 2021 09:58:34 -0000

Ulrich Windl wrote:
>>>> Doug Arnold <doug.arnold@meinberg-usa.com> schrieb am 08.01.2021 um 16:17
> in
> Nachricht <0D49017F-D7C4-49C5-936D-272B633D5575@meinberg-usa.com>:
>> I think that the point of a leap smear is that no special handling of leap 
>> seconds is needed by the client.  It is introduced gradually over a number
> of 
>> polling periods.
> 
> But if you have two servers using leap smear, and to servers not using leap
> smear, all will claim to return the correct time one second after the leap
> event.

The general problem is admin have to be very careful when leap second
smearing comes into the game. Specifically in a mixed environment with
time servers that don't smear, and other time servers that smear in a
different way.

> With the same logic as claiming UNSYNC during theleap event for non-smearing
> servers, smearing servers should return UNSYNC until the time is "correct"
> again IMHO.

Sorry, that wouldn't be useful. If NTP servers smear the time, it's not
for the sake of the NTP servers but for the sake of the clients.

If you returned UNSYNC during the smear interval, the clients would stop
accepting the servers and not follow the smearing at all. Instead they
would re-synchronize to the servers and STEP the time after the leap
second, which is exactly what you want to avoid when smearing a leap second.


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