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

Martin Burnicki <martin.burnicki@meinberg.de> Wed, 06 January 2021 16: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 DDF113A1001 for <ntp@ietfa.amsl.com>; Wed, 6 Jan 2021 08:59:22 -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 8PNIZz3UgoDa for <ntp@ietfa.amsl.com>; Wed, 6 Jan 2021 08:59:20 -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 B96543A0FFA for <ntp@ietf.org>; Wed, 6 Jan 2021 08:59:20 -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 0AEFC71C06CF; Wed, 6 Jan 2021 17:59:18 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=meinberg.de; s=dkim; t=1609952358; 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=fJKvbb8kiylRi+W9MGLy54dkMGIk23jgjzx1lYDraBw=; b=deL6oyj4NpzA2wzgRR35USxXy2HB6DsBhuk0fA3pzP7Dl36iF4Jp37s2TYHDJUfk93PtpJ 1Ni5iVR6cgNVqP/N1Z7/lS4J48Ri6YM18deZXbp+o2E1IsAYg316GHaXaxaRTBRFjP5hXW ZXKALWVzkAzkpbE+EyNpAozXbjfPATGWO52DrsBsVbF16dqGe17Qb3JI0W+EM2D4RCe9eb PFuowwfX7+7Q5BvJsgBzmlzTKVZPgfZd09E7+FZ1b4+nN8p9EHi07gtpfbm3AbAyfXVQ6j 3csUtxmll4Z3O6GVCSbIXgnBXfCDYLNw9KZeiP7Gri7q0sIJKbHrs4hMqwdjxA==
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 17:59:13 +0100
To: FUSTE Emmanuel <emmanuel.fuste@thalesgroup.com>, "ntp@ietf.org" <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> <f6871e77-7130-0234-b30f-a1efd7fc501d@meinberg.de> <5d9b2399-dbb4-99c8-4495-69ad03479a23@thalesgroup.com> <c28ac809-1d5b-0e1d-48fa-88d4c45d870b@meinberg.de> <76d5de51-1f00-7b6c-95e5-2bf6b932e0cf@thalesgroup.com>
From: Martin Burnicki <martin.burnicki@meinberg.de>
Organization: Meinberg Funkuhren GmbH & Co. KG, Bad Pyrmont, Germany
Message-ID: <de724ba2-1330-4b72-8ab6-823e086acc34@meinberg.de>
Date: Wed, 06 Jan 2021 17:59:12 +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: <76d5de51-1f00-7b6c-95e5-2bf6b932e0cf@thalesgroup.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/iGZ0ZQamxYTm56BVhNEVmqofFgc>
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 16:59:23 -0000

FUSTE Emmanuel wrote:
> Le 06/01/2021 à 15:29, Martin Burnicki a écrit :
>> I think whether hardware timestamping is supported or not isn't related
>> to the packet format. Even NTPv4 can use timestamping in the kernel
>> driver, if the OS supports it.
> Yes but as the common time-stamping hardware only has and support only 
> one time-stamping clock and is responsible to put this clock value in 
> the outbound packet, format matter.
> You could not share the same interface with hardware time-stamping 
> between NTPv4 and PTP for this reason unless you are on custom or very 
> uncommon hardware.

However, timestamping a packet with SO_TIMESTAMP and modifying an
outgoing packet on the fly (PTP Onestep) are still 2 different things.

I know there is no clean and pretty solution to hardware-timestamp
outgoing NTP packets right now, so this could indeed be an option for a
v5 version which can have TAI support anyway.

However, if you want hardware timestamping support for NTP to yield the
level with accuracy you can yield with PTP, the question that comes to
my mind is whether a timestamper in a NIC can recognize and timestamp
NTP packets in the same way as PTP packets, and if PTP-aware switches
that measure the packet delay can also be configured to measure and
provide the delay of NTP packets.

Otherwise you can simply use PTP for such cases, and use NTP for cases
with different requirements.


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