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

Martin Burnicki <martin.burnicki@meinberg.de> Mon, 11 January 2021 10:27 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 E80813A096C for <ntp@ietfa.amsl.com>; Mon, 11 Jan 2021 02:27:25 -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 ZiOMmWKa97BZ for <ntp@ietfa.amsl.com>; Mon, 11 Jan 2021 02:27:23 -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 6C1803A095F for <ntp@ietf.org>; Mon, 11 Jan 2021 02:27:23 -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 6BEF671C06FA; Mon, 11 Jan 2021 11:27:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=meinberg.de; s=dkim; t=1610360840; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=s8voe3qfg1t3+Gq70Q8CU8T8HgFFGnElYZRkdZs9Vgs=; b=kDtct94hmL2Fd80UUhkOTIIhkZjajSTEHE/WruflWGXJfSsGWLNnds3ydQREuyj+BOdLxY /oB2t5PHHw37hmsYsDDdxk9WjiYjH5VxiDpJqWur1iV/7kK2HJTsSqeRibe6WHL3Fz8Yyk yUCDvnTQS4Fnl4a3Q2OE0vObGJFP3bkhE2RPuf8/xQ06DjG75ECIMvzX3Aoq/7FAJfRVpj 7ZYpNm667w5h9BTYa8bV2XlO5To/p3tO+iIbhVN5l5rVDr4FmgncSlBD94ts4TKrC8tFCi 18Sp7dBeDbe0EQ0TIw0PUfa2Qi9mbLPEOGUSA1h8oRWyYZZhAFMnd66Nc68gXQ==
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 11:27:17 +0100
To: Magnus Danielson <magnus@rubidium.se>, ntp@ietf.org
References: <20210111072208.0856840605C@ip-64-139-1-69.sjc.megapath.net> <7415fb75-63b0-c3fd-acdb-b1b58ec44435@rubidium.se>
From: Martin Burnicki <martin.burnicki@meinberg.de>
Organization: Meinberg Funkuhren GmbH & Co. KG, Bad Pyrmont, Germany
Message-ID: <ac08e481-2e5e-20f0-e99b-f37fec2f78da@meinberg.de>
Date: Mon, 11 Jan 2021 11:27:17 +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: <7415fb75-63b0-c3fd-acdb-b1b58ec44435@rubidium.se>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/_ZvBRqMQrc6dewvmTLtL9s6N_Aw>
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 10:27:26 -0000

Magnus,

Magnus Danielson wrote:
> On 2021-01-11 08:22, Hal Murray wrote:
>> if you are using smearing servers you have to be careful to not use any 
>> non-smearing servers.
>>
>> If you are using real/correct (non-smearing) servers, you have to make sure 
>> you don't use any smearing servers.
> 
> Which is exactly the division of servers and problem to handle them at
> client side, as client operation needs to know which servers too choose
> from. As you create a wider range of server types, all of a sudden you
> create less servers that we can use for any type of operation.

Once more I disagree. If you want smearing at the client side, client
software could be modified to do this right now.

If the client receives a leap second warning from the server, it could
include apply a smear offset when adjusting the system time, and each
client had to be individually configured if and how to smear its own
system time.

The reason for letting the NTP server send smeared time to its clients
is that you *only* have to configure your server(s) accordingly, and
*all* NTP clients get the same, smeared time.

> This is
> why putting this on the server side is unhelpful for the community. If
> we have a common NTP core time and then map that out to whatever format
> the client need, we can have a common set of of servers, serving a wide
> range of clients need together.

Of course you can run into a mess if you use smearing and non-smearing
servers at the same time.

However, admins who have to take care how the clients behave just need
to select a few appropriate servers for their clients instead of having
to check that each client supports smearing at the client side in the
same way. If you have a huge number of different clients, the effort is
probably much higher and more error prone than just having to select a
few servers.


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