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> Mon, 18 October 2021 14:10 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 6586B3A140D for <ntp@ietfa.amsl.com>; Mon, 18 Oct 2021 07:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 dQAUDQ76O0dh for <ntp@ietfa.amsl.com>; Mon, 18 Oct 2021 07:10:21 -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 561073A1411 for <ntp@ietf.org>; Mon, 18 Oct 2021 07:10:19 -0700 (PDT)
Received: from newusers-MBP.fios-router.home (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)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4HXzKf4vLSzMNQy; Mon, 18 Oct 2021 14:10:14 +0000 (UTC)
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, doug.arnold=40meinberg-usa.com@dmarc.ietf.org, james.ietf@gmail.com
Cc: "ntp@ietf.org" <ntp@ietf.org>
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> <DB8PR02MB57726795E3AD479F0CCFA778CFB99@DB8PR02MB5772.eurprd02.prod.outlook.com> <616D0ADA020000A10004486B@gwsmtp.uni-regensburg.de>
From: Danny Mayer <mayer@pdmconsulting.net>
Message-ID: <08e60c82-5b4c-5f0f-55e4-206b0d8f18c4@pdmconsulting.net>
Date: Mon, 18 Oct 2021 10:10:13 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <616D0ADA020000A10004486B@gwsmtp.uni-regensburg.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/gSC9PgiCY2mBJB_CCNXjmb-tdcU>
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: Mon, 18 Oct 2021 14:10:26 -0000

On 10/18/21 1:49 AM, Ulrich Windl wrote:
>>>> Doug Arnold <doug.arnold=40meinberg-usa.com@dmarc.ietf.org> schrieb am
> 15.10.2021 um 17:53 in Nachricht
> <DB8PR02MB57726795E3AD479F0CCFA778CFB99@DB8PR02MB5772.eurprd02.prod.outlook.com>
>
>> Hello James,
>>
>> I agree that leap smearing is a clumsy and dangerous way to avoid the
>> complication of correctly handling leap seconds in distributed database
>> software.  And if it was up to me all IT equipment would use TAI for all
>> timing except what is displayed to humans.  But it is not up to me.  The
>> people who are making the call tell me that they believe that leap seconds
> is
>> less bad than either moving everything from UTC to TAI, or writing and
>> debugging database software that manages leap seconds properly.
>>
>> So given that state of affairs.  What do we do?
> Hi!
>
> I guess the standard C library needs new functions to get the correct time
> first ;-)
> time_t has a problem.
>
> Amazingly gettimeofday can use struct timezone, while clock_gettime() can't.
> So adding the TAI offset to struct timezone would not help much.
>
> Regards,
> Ulrich

The TAI-UTC decision was made over two decades ago. We just have to live 
with the consequences.

Danny

v2.23.0 | Report a Bug | By Email