IETF Logo Mail Archive

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

Danny Mayer <mayer@pdmconsulting.net> Thu, 21 October 2021 15:29 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 057A13A17F0; Thu, 21 Oct 2021 08:29:31 -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, HTML_MESSAGE=0.001, 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 kxXfFUJthDs8; Thu, 21 Oct 2021 08:29:26 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [IPv6:2001:470:1:205::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 03FF93A17E8; Thu, 21 Oct 2021 08:29:25 -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)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4HZrxW1fPFzMNYW; Thu, 21 Oct 2021 15:29:19 +0000 (UTC)
Content-Type: multipart/alternative; boundary="------------MVDbeP4MZ2SZE04OZlwH80sK"
Message-ID: <4df6eb44-1691-1609-5bc8-5055e5d82780@pdmconsulting.net>
Date: Thu, 21 Oct 2021 11:29:18 -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: kristof.teichel@ptb.de, Hal Murray <halmurray@sonic.net>
Cc: ntp@ietf.org, ntp <ntp-bounces@ietf.org>
References: <20211021111435.0A1E128C0F3@107-137-68-211.lightspeed.sntcca.sbcglobal.net> <OFF123426F.49671C73-ONC1258775.00413019-C1258775.0041DAE2@ptb.de>
From: Danny Mayer <mayer@pdmconsulting.net>
In-Reply-To: <OFF123426F.49671C73-ONC1258775.00413019-C1258775.0041DAE2@ptb.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/OrhJ9Dj0Y6jEyKvP6Wxy27C6CBE>
Subject: Re: [Ntp] 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: Thu, 21 Oct 2021 15:29:31 -0000

On 10/21/21 7:59 AM, kristof.teichel@ptb.de wrote:
> I only have second-hand insight, really.
> What I gather is that there is a growing fear of a situation similar 
> to the Y2K bug scare, because it is predicted that (for the first time 
> I believe) there could soon be a negative leap second and time sync 
> appliances might just fail in the face of having to deal with that.
> I will try to get better info, in particular quantifying chances and 
> timeframe.

The only way that is likely to happen is if the earth rotation speeds 
up, which is extremely unlikely. The only ways that I can think of that 
happening would be either a volcano about to spew enough energy in the 
right direction and an asteroid hitting the earth with a glancing blow. 
Either would be catastrophic. It would be better to not remove a 
leapsecond and just wait for the next time a positive leapsecond 
adjustment is needed.

Danny

v2.23.0 | Report a Bug | By Email