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

Miroslav Lichvar <mlichvar@redhat.com> Tue, 05 January 2021 08:33 UTC

Return-Path: <mlichvar@redhat.com>
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 B58253A0EF4 for <ntp@ietfa.amsl.com>; Tue, 5 Jan 2021 00:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.37
X-Spam-Level:
X-Spam-Status: No, score=-2.37 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
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 DRfOnk_9MHvA for <ntp@ietfa.amsl.com>; Tue, 5 Jan 2021 00:33:38 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEF4B3A0EF2 for <ntp@ietf.org>; Tue, 5 Jan 2021 00:33:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1609835616; 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: in-reply-to:in-reply-to:references:references; bh=nIR2dW51lVRnvSOR4J+miCFIgB5URMQ1p9AG95y+B2k=; b=IAjuRu5VUVzjmuYcfQ/+sYnUQvJUvWe4N0O1VmqwmtsaLX9V9k1yXKe7N9/v2NQHG0ObHD O5EnlUJzdh1mSlS2Byq1O0TVfodcBD2md3acopDV7BGOam0pc+EZSdOqlakckUHPJd5EAz j4QrlfBKZ8WPRAtEWVR1KEy3tB8S4Hk=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-211-kMXg7XaAOBmw7ioFdmP1GA-1; Tue, 05 Jan 2021 03:33:33 -0500
X-MC-Unique: kMXg7XaAOBmw7ioFdmP1GA-1
Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 3A01C107ACE4; Tue, 5 Jan 2021 08:33:31 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 8025660BE5; Tue, 5 Jan 2021 08:33:29 +0000 (UTC)
Date: Tue, 05 Jan 2021 09:33:28 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Magnus Danielson <magnus@rubidium.se>
Cc: ntp@ietf.org
Message-ID: <20210105083328.GA3008666@localhost>
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>
MIME-Version: 1.0
In-Reply-To: <b1e61f7d-6cea-5e99-69f0-7eae815d9e19@rubidium.se>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/gG8-vxV88PohGOaxUOJF625_BUQ>
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: Tue, 05 Jan 2021 08:33:40 -0000

On Mon, Jan 04, 2021 at 06:48:16PM +0100, Magnus Danielson wrote:
> > The Linux system TAI clock can be read by applications, but there is
> > no support for timestamping of packets with this clock, i.e. it is
> > currently not useful for NTP.
> 
> The hardware time-stamping support will support PTP-timescale, which has
> a know relationship to TAI. With whatever relationship there will be
> between NTPv5 transport time-scale and TAI, the PTP relationship will
> also be known and thus can be used.

With hardware timestamping there is a separate (hardware) clock used
for timestamping. It's not related to the CLOCK_TAI system clock
discussed here. I assume we don't want NTPv5 to require a hardware
clock.

NTP is used for synchronization of various clocks. Most of them are
based on UTC. NTPv5 cannot support only TAI.

-- 
Miroslav Lichvar