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

James <james.ietf@gmail.com> Thu, 21 October 2021 15:52 UTC

Return-Path: <james.ietf@gmail.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 D4BFF3A041C for <ntp@ietfa.amsl.com>; Thu, 21 Oct 2021 08:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 XBjFp8kTZkTn for <ntp@ietfa.amsl.com>; Thu, 21 Oct 2021 08:52:51 -0700 (PDT)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D582E3A040D for <ntp@ietf.org>; Thu, 21 Oct 2021 08:52:50 -0700 (PDT)
Received: by mail-ed1-x52e.google.com with SMTP id u13so2921957edy.10 for <ntp@ietf.org>; Thu, 21 Oct 2021 08:52:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=aNNy/ZNIuDfBIfFlYtha35SCtNeYyH5t6zTXPvWxe5Y=; b=VBBD+W9diNTDFCJPFgxRhyklj9U+0c1jhyzu0cvY9YzAQ1JehJ+COuOB1Ssee02Bif SJh3Tgm254kXU+It6bZleNE7sQ7aSr52uoqPskdrPpzpugEzHB0AIAuLwa6ua6+S8CF4 96FLz2+/C9UydfFeBtEw6CXwwLo1qfmoDC2qpkbowJ0sJaEgrDHIcuk/JSdK54zwuhSu 2/DPKxMhPA3l83QItyRt3/9lBqURziLes1Rrcneo2//+UqDC6THcbQTDLD+YCTPrnWS1 VFIj8G9AaPDOY9cfLuCIwhAT+2gdtw6wbepJBkff1bGirKYH6FR5oiiM5UX48K8/C3sp xWdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=aNNy/ZNIuDfBIfFlYtha35SCtNeYyH5t6zTXPvWxe5Y=; b=psQM3hse0HEf+jGycoV5dkObqcr77uprm0oISF7mSMkgGJpZGUGj7QbQ+XpP6fVW86 LDL95pyAIH8Ct3ArH10bRzXg6ZH18P9oTMzbuH4XBMNt+Vh3mubux7nauIYfaaPONz5N kxRLmcUgnIvkUHgbbz6j8HCD0GqFzJ0aqwXnzMphF8prlN6hlZKiK7LxlFOnmo/mU72u g3PK5vq01BcSj+XsYUXVq29GlhnmDeInupgbYAwI9nU8WZDnDCqhjZtw0WTAM0FN1Zkp JGvDdp69koTUW00C+LWyuzIyWmmNYOawDvc+J2t1APTVlc8tPjtIWbTKHsFR284ca6c5 gX+w==
X-Gm-Message-State: AOAM533S+1EGyO01M14Ggied9/24xhhGss/Z8DhdNL0zRYIbbIuWLgh8 prQOBQZTpTto3OYIsUmOxQM=
X-Google-Smtp-Source: ABdhPJyyXURLzW24ZtBG4J36hmHC5Wlhh+hYB9zsxgDcOFsS+qwz7f2xgyiN2+9q2JXmcWNnkbXnPw==
X-Received: by 2002:a17:907:7ba6:: with SMTP id ne38mr8439101ejc.150.1634831568962; Thu, 21 Oct 2021 08:52:48 -0700 (PDT)
Received: from smtpclient.apple ([2001:984:65b0:1:adb1:da7e:739e:f998]) by smtp.gmail.com with ESMTPSA id ca4sm2720207ejb.1.2021.10.21.08.52.48 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Oct 2021 08:52:48 -0700 (PDT)
From: James <james.ietf@gmail.com>
Message-Id: <ABCEA72C-8634-4A45-95B5-6EFBAFC91084@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7E67D63C-304F-4FB3-A77C-43BBA14B92E6"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Thu, 21 Oct 2021 17:52:47 +0200
In-Reply-To: <4df6eb44-1691-1609-5bc8-5055e5d82780@pdmconsulting.net>
Cc: kristof.teichel@ptb.de, Hal Murray <halmurray@sonic.net>, NTP WG <ntp@ietf.org>
To: Danny Mayer <mayer@pdmconsulting.net>
References: <20211021111435.0A1E128C0F3@107-137-68-211.lightspeed.sntcca.sbcglobal.net> <OFF123426F.49671C73-ONC1258775.00413019-C1258775.0041DAE2@ptb.de> <4df6eb44-1691-1609-5bc8-5055e5d82780@pdmconsulting.net>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/H0Ae8O0-D8SkxUNpksOwwbtnH5I>
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:52:56 -0000

As was reported earlier this year [1]:

> Peter Whibberley, senior research scientist with National Physical Laboratory’s time and frequency group, said: “It is certainly correct that the Earth is spinning faster now than at any time in the last 50 years.
> ...
> The World Radiocommunication Conference will decide on the fate of the leap second in 2023.
> ...
> Global warming will also have an effect by melting ice and snow at higher elevations, causing the Earth to spin faster, although only by a small amount.

I’d be curious to know if there are any data that contradicts the NPL’s position regarding rotation speed or the other parts of that article.

- J

1: https://www.telegraph.co.uk/news/2021/01/04/earth-spinning-faster-now-time-past-half-century/


> On 21 Oct 2021, at 17:29, Danny Mayer <mayer@pdmconsulting.net> wrote:
> On 10/21/21 7:59 AM, kristof.teichel@ptb.de <mailto: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
> 
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp