Re: [Ntp] Antw: [EXT] Re: Timescales

Miroslav Lichvar <mlichvar@redhat.com> Wed, 09 December 2020 15:21 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 ACA5A3A0D84 for <ntp@ietfa.amsl.com>; Wed, 9 Dec 2020 07:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=-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 M8L3owwa_UX3 for <ntp@ietfa.amsl.com>; Wed, 9 Dec 2020 07:21:33 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.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 EBE1D3A0DDB for <ntp@ietf.org>; Wed, 9 Dec 2020 07:21:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1607527291; 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=XvAPZQB4K4NUJtK8QpvZnAlVEjYsVE5tqg3O79UByfU=; b=VFqvSVw4tU13IBiuogHeTxFC00Jkhx6hQ25JfloA8DaeeDl1MfEtN8jiMpez5wu7uwqMji tTRo9NOOnihUaO94JG7V9y6RUJZpMA0fANE69n8TFQtNPhc+5T51voK97x75LKSISVFc+G ejGCzonhJQJCQR9eXj2KRGJyNC0SrE4=
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-332-zkqZdvhcPf24qSeHt_R-1w-1; Wed, 09 Dec 2020 10:21:29 -0500
X-MC-Unique: zkqZdvhcPf24qSeHt_R-1w-1
Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 18BA71015C8C; Wed, 9 Dec 2020 15:21:28 +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 6949219C78; Wed, 9 Dec 2020 15:21:26 +0000 (UTC)
Date: Wed, 09 Dec 2020 16:21:25 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Magnus Danielson <magnus@rubidium.se>
Cc: ntp@ietf.org
Message-ID: <20201209152125.GF2352378@localhost>
References: <20201209101830.7CB0240605C@ip-64-139-1-69.sjc.megapath.net> <20201209113003.GA2352378@localhost> <5FD0D13C020000A10003D6CB@gwsmtp.uni-regensburg.de> <20201209134612.GC2352378@localhost> <f85591b1-5d4f-d468-1011-bbeb276ebdec@thalesgroup.com> <20201209142205.GD2352378@localhost> <0d54883b-8cd7-cd61-0b44-145548a3e44d@rubidium.se>
MIME-Version: 1.0
In-Reply-To: <0d54883b-8cd7-cd61-0b44-145548a3e44d@rubidium.se>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23
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/MBpEQu5F0z50gjvbuTo1P3OFbRI>
Subject: Re: [Ntp] Antw: [EXT] Re: Timescales
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, 09 Dec 2020 15:21:35 -0000

On Wed, Dec 09, 2020 at 04:11:32PM +0100, Magnus Danielson wrote:
> In my mind, the train to discuss the need for leap-second information
> has already gone. Too many applications start to need it for them to
> function well, and if NTPv5 is not able to deliver that, then it should
> either be redesigned to just dropped as an effort and focus on a
> revision of NTP that does support it, because what is needed is a
> solution that supports this. In the meanwhile, PTP has the needed
> support and we could just drop NTP and go all PTP then. Personally I
> think there is great value in NTP for many applications, if only it can
> handle this properly along getting secure with NTS.

I don't understand everything you said, but I think we are in
agreement. My draft supports both UTC and TAI. It also provides the
TAI-UTC offset when known.

That's similar to PTP. It can work in TAI or the "arbitrary"
timescale, typically UTC. There is a field for the TAI-UTC offset and
there is a flag to indicate it is valid.

-- 
Miroslav Lichvar