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

Martin Burnicki <martin.burnicki@meinberg.de> Wed, 06 January 2021 10:50 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 77A7C3A12C3 for <ntp@ietfa.amsl.com>; Wed, 6 Jan 2021 02:50:09 -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=unavailable 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 M3ILQ47zeJCo for <ntp@ietfa.amsl.com>; Wed, 6 Jan 2021 02:50:07 -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 0D4463A12BC for <ntp@ietf.org>; Wed, 6 Jan 2021 02:50:06 -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 50CF371C0ED7; Wed, 6 Jan 2021 11:50:04 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=meinberg.de; s=dkim; t=1609930204; 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=AMukOVZiSEKG4aMDRIgLUPt9vgGEpUuhHNR4yvTLpF8=; b=RQMHAACg0S2EaCR/PMm3Ya8W4u1QqxoIrP9HJZ65rvhcZfEoIUlxnvwg0T8IDlqoaysxpv oEYw6TczC14AqpLqtOuKy72dg1NalFKnfj1wLvTgRD5mcVw3iTnQ4Xq2eZDOdMkJAhQ30m C5gq47G60wgpWnTogjIfWmP7SjhSd1+9DcoI2l7B8lmKOWHBZoVpYwtkeshofLsfXY1D8z fIJ9oEKOL9ZZKstk160+3TmRgl/yoPbrtRZekcAG8OO6/6piu9lWlvu0aIHBdWU59zfmtr Yed2UgxBzjv83wGNCLqieUktyKRm08qJtNrwAdC2XZRuhemnEfy9uP//cVMYIw==
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)); Wed, 6 Jan 2021 11:50:01 +0100
To: Philip Prindeville <philipp@redfish-solutions.com>, Martin Burnicki <martin.burnicki=40meinberg.de@dmarc.ietf.org>
Cc: Miroslav Lichvar <mlichvar@redhat.com>, Hal Murray <hmurray@megapathdsl.net>, ntp@ietf.org
References: <20210105124544.5EF5C40605C@ip-64-139-1-69.sjc.megapath.net> <f876a3ff-16ee-fc63-c27c-d5a3cb847a3d@meinberg.de> <4E78BB38-5FA2-4974-AB25-85C5AD9E7DBE@redfish-solutions.com>
From: Martin Burnicki <martin.burnicki@meinberg.de>
Organization: Meinberg Funkuhren GmbH & Co. KG, Bad Pyrmont, Germany
Message-ID: <8cdc69d3-c795-6fee-3e5c-9ae11694e3da@meinberg.de>
Date: Wed, 06 Jan 2021 11:50:00 +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: <4E78BB38-5FA2-4974-AB25-85C5AD9E7DBE@redfish-solutions.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/ALMbHsXGZZ0jAC3nTWxQLnDzxBQ>
Subject: Re: [Ntp] 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: Wed, 06 Jan 2021 10:50:09 -0000

Philip Prindeville wrote:
>> On Jan 5, 2021, at 9:09 AM, Martin Burnicki <martin.burnicki=40meinberg.de@dmarc.ietf.org> wrote:
>>
>> For NTP, things are different. There is a huge base of NTPv4
>> installations, and making NTPv5 basically compatible with v4 would IMO
>> strongly increase the acceptance of NTPv5.
> 
> 
> The logical corollary to this argument is that because there ARE a lot of servers, it’s not unreasonable to think that there will be a lot of both NTPv4 and NTPv5 servers co-existing in the future, and the user is free to peer with either.

So you think it's not necessary to upgrade v4 nodes to v5, as it has
been done from v3 to v4? Simply systems should stick with v4 and only
enhanced system should start using v5?

In this case, wouldn't it be better to start defining a completely new
protocol and e.g. call it "Extended Time Protocol", which can be chosen
instead of NTP? This would be similar to PTP, which you can use instead
of NTP. ;-)

> Which eliminates the need for NTPv5 servers to also speak NTPv4.

If you have a large network with different types of client you will need
to provide NTPv4 and "ETP" (AKA NTPv5) if NTPv5 has requirements that
are not needed and can't be supported by some clients.


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