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

Martin Burnicki <martin.burnicki@meinberg.de> Wed, 06 January 2021 10:59 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 CA2E63A12D8 for <ntp@ietfa.amsl.com>; Wed, 6 Jan 2021 02:59:03 -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 BhP_WpsvPLHQ for <ntp@ietfa.amsl.com>; Wed, 6 Jan 2021 02:59:01 -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 9783B3A12CF for <ntp@ietf.org>; Wed, 6 Jan 2021 02:59:01 -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 BDE7171C102D; Wed, 6 Jan 2021 11:58:59 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=meinberg.de; s=dkim; t=1609930739; 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=SzXx2WH6NIG/O5DqBbEBnD/0HbLs6GmyX44plZWwEZU=; b=XMo2DCDmCruzZ9V7BfkWZsIe+kK8qvthPVg81m5iDeRyrq7bmZlS0r0OOKg97iD0pL0Vuc xYfAn/FtxpwKoMqJF/qtufbNrgiZu6e/znUlDteTeqijxOlYaqq4JIJb2/IjWgy8nZunyu Wx7Ldl5VFkddp3faiXJCsRZldxkBQ6PvwNnHCcwbxlp/IJ5HAoOWB8VTOrL/SUZoCZwC94 TexorqBk89hRIGWkKaHOSoD4gRudtRiUts7uNBImNfiNkbx30tvLmgYHZcEhGwlVCV9nvu sXp8TOsWPK6tjYM2rJ6KaBOdvR9+lh93PSC5qbJlpo2iKHY7kGbRaydVnUrwFg==
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:58:58 +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> <59A706AB-A151-4779-989B-B957F2C50FD0@redfish-solutions.com>
From: Martin Burnicki <martin.burnicki@meinberg.de>
Organization: Meinberg Funkuhren GmbH & Co. KG, Bad Pyrmont, Germany
Message-ID: <f6871e77-7130-0234-b30f-a1efd7fc501d@meinberg.de>
Date: Wed, 06 Jan 2021 11:58:57 +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: <59A706AB-A151-4779-989B-B957F2C50FD0@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/ihXzU3yJMObWiLDYR6jXeEC9aIA>
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:59:04 -0000

Philip Prindeville wrote:
> 
>> On Jan 5, 2021, at 9:09 AM, Martin Burnicki <martin.burnicki=40meinberg.de@dmarc.ietf.org> wrote:
>>
>> Except the versions that aren't updated anymore, or embedded of IoT
>> devices. This has been discussed many times before.
> 
> If those devices aren’t updated any more, it’s equally possible that they’ll never get an NTPv5 compatible client, either.

And if these clients are part of a huge network, you have to provide a
one server that talks NTPv5 for the cool clients, and another server
that provides NTPv4 for existing IoT and embedded devices?

> That would necessitate an “update” of sorts, which we’ve both agreed isn’t going to happen.

Or you would have to provide (and maintain) an NTP server implementation
that supports both v4 and v5, depending on the version of the request.


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