IETF Logo Mail Archive

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

Hal Murray <halmurray@sonic.net> Thu, 21 October 2021 11:14 UTC

Return-Path: <halmurray@sonic.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 E7EF33A0FD8 for <ntp@ietfa.amsl.com>; Thu, 21 Oct 2021 04:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.401
X-Spam-Level: **
X-Spam-Status: No, score=2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_B=4.299, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 JOo8-zRNFupx for <ntp@ietfa.amsl.com>; Thu, 21 Oct 2021 04:14:36 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (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 D055A3A0B1A for <ntp@ietf.org>; Thu, 21 Oct 2021 04:14:36 -0700 (PDT)
Received: from 107-137-68-211.lightspeed.sntcca.sbcglobal.net (107-137-68-211.lightspeed.sntcca.sbcglobal.net [107.137.68.211]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id 19LBEZrH008814 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 21 Oct 2021 04:14:35 -0700
Received: from hgm (localhost [IPv6:::1]) by 107-137-68-211.lightspeed.sntcca.sbcglobal.net (Postfix) with ESMTP id 0A1E128C0F3; Thu, 21 Oct 2021 04:14:35 -0700 (PDT)
X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1
To: ntp@ietf.org
cc: Hal Murray <halmurray@sonic.net>
From: Hal Murray <halmurray@sonic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 21 Oct 2021 04:14:35 -0700
Message-Id: <20211021111435.0A1E128C0F3@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
X-Sonic-CAuth: UmFuZG9tSVZtaBuIfW+R7rQgicvPPGaW1XtVGYYV/7Nygi8KuMEy9Tqrb4cFKqkc5mP4bzw3VeQbMV5xnwbtRPFptXdcOOhqvM4wLjA+B/g=
X-Sonic-ID: C;NAaXEmAy7BGitpJC86s3og== M;XPDFEmAy7BGitpJC86s3og==
X-Sonic-Spam-Details: -1.5/5.0 by cerberusd
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/erhpq378DZ50T7vI8aPgg4PrREw>
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 11:14:41 -0000

kristof.teichel@ptb.de said:
> I can 100% attest to this. All of my colleagues and superiors that I've ever
> talked to about this were shocked and appalled to learn that the WG was
> considering anything other than UTC as the basis for dissemination.

Note that GPS and similar are not using UTC as the "basis for dissemination".  They use something without leap seconds.  They also provide enough information for a client to translate their time to UTC.


> In that vein, I'm also supposed to communicate that the whole issue might
> become moot "soon", since leap seconds might just be removed as a thing
> that happens in UTC. 

I haven't been following that and I haven't noticed anything recently.  Can anybody provide any info on what is going on?  What are the chances they will go away?  If so, when?


-- 
These are my opinions.  I hate spam.

v2.23.0 | Report a Bug | By Email