IETF Logo Mail Archive

[Ntp] Antw: Re: Antw: [EXT] Re: Negative leap‑second?

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Wed, 03 August 2022 08:26 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.de>
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 8F258C14CF1C for <ntp@ietfa.amsl.com>; Wed, 3 Aug 2022 01:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gqUH6D1QFTHs for <ntp@ietfa.amsl.com>; Wed, 3 Aug 2022 01:26:27 -0700 (PDT)
Received: from mx2.uni-regensburg.de (mx2.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:3:bdf8]) (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 1A443C14CF13 for <ntp@ietf.org>; Wed, 3 Aug 2022 01:26:25 -0700 (PDT)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3E8B76000052 for <ntp@ietf.org>; Wed, 3 Aug 2022 10:26:20 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id 33315600004D for <ntp@ietf.org>; Wed, 3 Aug 2022 10:26:19 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Wed, 03 Aug 2022 10:26:19 +0200
Message-Id: <62EA3129020000A10004C103@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.4.0
Date: Wed, 03 Aug 2022 10:26:17 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: mlichvar@redhat.com
Cc: "ntp@ietf.org" <ntp@ietf.org>, stenn@nwtime.org, mayer@pdmconsulting.net
References: <b023985d-76c3-c6b9-3b5b-f10b3cabd2f5@pdmconsulting.net> <f95814cf-0391-a6f9-caab-edae86e70085@nwtime.org> <62EA1897020000A10004C0F9@gwsmtp.uni-regensburg.de> <Yuob5zi4/Lpw6jzN@localhost>
In-Reply-To: <Yuob5zi4/Lpw6jzN@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/ThBAinMe-D_3VCZ9agnGmgw34lY>
Subject: [Ntp] Antw: Re: Antw: [EXT] Re: Negative leap‑second?
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 03 Aug 2022 08:26:31 -0000

>>> Miroslav Lichvar <mlichvar@redhat.com> schrieb am 03.08.2022 um 08:55 in
Nachricht <Yuob5zi4/Lpw6jzN@localhost>:
> On Wed, Aug 03, 2022 at 08:41:27AM +0200, Ulrich Windl wrote:
>> >>> Harlan Stenn <stenn@nwtime.org> schrieb am 03.08.2022 um 03:55 in
>> Nachricht
>> > Doing this will give folks plenty of opportunity to make sure that leap 
>> > second processing code works, on an ongoing basis.
>> 
>> Harlan,
>> 
>> I think such a procedure would convince people to switch to TAI instead
;‑)
> 
> I don't see that happening. It's not just about replacing all
> instances of CLOCK_REALTIME with CLOCK_TAI. The timestamps need
> to be processed, stored and exchanged over network. The cost of
> modifying and testing all those applications would be enormous. I
> think for almost everyone it's cheaper to just shut down the whole
> operation around leap second.

That's what I wanted to say: People (and their applications) won't like the
frequent loss or addition of a second,
so they might want a solution without such.

> 
> ‑‑ 
> Miroslav Lichvar

v2.23.0 | Report a Bug | By Email