IETF Logo Mail Archive

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

Danny Mayer <mayer@pdmconsulting.net> Tue, 19 October 2021 15:17 UTC

Return-Path: <mayer@pdmconsulting.net>
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 08D0A3A0A80 for <ntp@ietfa.amsl.com>; Tue, 19 Oct 2021 08:17:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 VDezKQVFcVu4 for <ntp@ietfa.amsl.com>; Tue, 19 Oct 2021 08:17:50 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) (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 464D93A091E for <ntp@ietf.org>; Tue, 19 Oct 2021 08:17:47 -0700 (PDT)
Received: from [192.168.1.193] (pool-108-26-179-179.bstnma.fios.verizon.net [108.26.179.179]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4HYcn26527zMNYM; Tue, 19 Oct 2021 15:17:42 +0000 (UTC)
Message-ID: <7f975043-7577-fd47-b5fb-f48e579828db@pdmconsulting.net>
Date: Tue, 19 Oct 2021 11:17:41 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.2.0
Content-Language: en-US
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, james.ietf@gmail.com, mlichvar@redhat.com
Cc: "ntp@ietf.org" <ntp@ietf.org>, doug.arnold@meinberg-usa.com
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>
From: Danny Mayer <mayer@pdmconsulting.net>
In-Reply-To: <616E7B69020000A10004491E@gwsmtp.uni-regensburg.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/IvVHvSc8gaf8ts0wCRhRbw1qZBc>
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 15:17:56 -0000

On 10/19/21 4:01 AM, Ulrich Windl wrote:
>
> 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.
> Maybe NTPv6 will demand that TAI should be the new time base. Still we would need the offset to provide UTC and similar.
>
My proposal for an additional field includes the total number of 
leapseconds added to TAI. You can then use this number to calculate the 
TAI time from the UTC timestamps sent. A zero value for the count would 
indicate the server doesn't know.

Danny

v2.23.0 | Report a Bug | By Email