IETF Logo Mail Archive

Re: [Ntp] Antw: [EXT] Re: New Version Notification for draft-gruessing-ntp-ntpv5-requirements-03.txt

Miroslav Lichvar <mlichvar@redhat.com> Tue, 19 October 2021 08:18 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 36C663A0029 for <ntp@ietfa.amsl.com>; Tue, 19 Oct 2021 01:18:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level:
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, 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 bePxXDUOVWyQ for <ntp@ietfa.amsl.com>; Tue, 19 Oct 2021 01:18:04 -0700 (PDT)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B3573A08EC for <ntp@ietf.org>; Tue, 19 Oct 2021 01:18:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1634631483; 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=nRqzMAgC+/e1lzfWh/wH2kUurK86tT7s40qbPh0H6Hw=; b=cAvtPmR8hJRA1KgN9a1MZq7QdPEpCW2QZCTjA5ieufFs/31HKG4panXuL9khFg6a5DrLO3 6qe4C6MhaKpe9z/DCp6+bx5PYL/U+RkHEOwuRAY7nHIA9ID4NMjs5MWEDQqJjIqd0t3sC/ bAmXLaEje7Nc+IsWFn2fIKXSnHvIjAo=
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-372-nG7f_T21O2mXi3outOBdfw-1; Tue, 19 Oct 2021 04:17:57 -0400
X-MC-Unique: nG7f_T21O2mXi3outOBdfw-1
Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A020518125C1; Tue, 19 Oct 2021 08:17:56 +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 A29521017E35; Tue, 19 Oct 2021 08:17:55 +0000 (UTC)
Date: Tue, 19 Oct 2021 10:17:46 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: james.ietf@gmail.com, "ntp@ietf.org" <ntp@ietf.org>, doug.arnold@meinberg-usa.com
Message-ID: <YW5/KqAZdI+EmlTn@localhost>
References: <163386015957.12424.6997038478834885480@ietfa.amsl.com> <CAO+dDx=6baLhf9LwSMvR1F0ieuLO6NXmExYLDvcCF2tgchHs8w@mail.gmail.com> <DB8PR02MB5772AC97BFE2D7C1139EFDC0CFB89@DB8PR02MB5772.eurprd02.prod.outlook.com> <E469D9A7-7445-49D9-A8A2-82BA7BF1FA27@gmail.com> <YW2FvUiaHC/hbxkG@localhost> <616E7B69020000A10004491E@gwsmtp.uni-regensburg.de>
MIME-Version: 1.0
In-Reply-To: <616E7B69020000A10004491E@gwsmtp.uni-regensburg.de>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22
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/7H2zL61gOyOhFzXBeYtCk2AyzBA>
Subject: Re: [Ntp] Antw: [EXT] Re: New Version Notification for draft-gruessing-ntp-ntpv5-requirements-03.txt
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Time Protocol <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, 19 Oct 2021 08:18:09 -0000

On Tue, Oct 19, 2021 at 10:01:45AM +0200, Ulrich Windl wrote:
> >>> Miroslav Lichvar <mlichvar@redhat.com> schrieb am 18.10.2021 um 16:33 in
> Nachricht <YW2FvUiaHC/hbxkG@localhost>:
> 
> ...
> > Same for UTC vs TAI.
> 
> I thing the TAI offset (whole seconds) should be part of every NTPv5 timing packet. So we can keep the old timestamp format while providing TAI.

That's the Timescale Offset field in my draft. If the selected
timescale is UTC or TAI, it contains the TAI-UTC offset, or 0x8000 if
unknown. The expectation is that client will request the timescale
which it is using for timestamping of NTP packets.

> Maybe NTPv6 will demand that TAI should be the new time base. Still we would need the offset to provide UTC and similar.

If all computer clocks were keeping time in TAI, or at least could
convert all their timestamps to TAI, that would make sense. But I
think it's more likely that UTC will stop leaping before TAI is
adopted everywhere.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email