Re: [Ntp] Finding leap-seconds.list

Danny Mayer <mayer@ntp.org> Fri, 09 November 2018 15:47 UTC

Return-Path: <mayer@ntp.org>
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 BFF7D130E16 for <ntp@ietfa.amsl.com>; Fri, 9 Nov 2018 07:47:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_PERMERROR=0.01] 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 uU2C9-FdMNBo for <ntp@ietfa.amsl.com>; Fri, 9 Nov 2018 07:47:51 -0800 (PST)
Received: from chessie.everett.org (chessie.everett.org [IPv6:2001:470:1:205::234]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D3B9130E14 for <ntp@ietf.org>; Fri, 9 Nov 2018 07:47:51 -0800 (PST)
Received: from L34097OUS.local (pool-71-174-223-67.bstnma.east.verizon.net [71.174.223.67]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 42s4Kx3BPhzL7K; Fri, 9 Nov 2018 15:47:49 +0000 (UTC)
To: Martin Burnicki <martin.burnicki@meinberg.de>, Paul Eggert <eggert@cs.ucla.edu>, Thomas Peterson <hidinginthebbc@gmail.com>, Dieter Sibold <dsibold.ietf@gmail.com>, Denis Reilly <denis.reilly@orolia.com>
Cc: ntp@ietf.org
References: <5884DA3A-B95B-4D6B-9A31-E964CE4F02EF@gmail.com> <53bc1310-c198-557a-54ca-57b5b0af9bcb@meinberg.de> <AM6PR0602MB3733A11C62B7A0ED49F318B5FFC40@AM6PR0602MB3733.eurprd06.prod.outlook.com> <9A89609A-9A4E-41EB-A857-91252E5F6D04@gmail.com> <43c65279-12fa-4510-1d8f-b6e1b03caf7e@gmail.com> <a7d8d58b-7370-1b4c-0c70-fd775dfbf854@cs.ucla.edu> <5f8998a5-d550-95b8-fa46-5e1c1ca7b0e9@meinberg.de>
From: Danny Mayer <mayer@ntp.org>
Message-ID: <733a2063-f557-459e-b4e9-0db6c88ab430@ntp.org>
Date: Fri, 09 Nov 2018 10:47:47 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.3.0
MIME-Version: 1.0
In-Reply-To: <5f8998a5-d550-95b8-fa46-5e1c1ca7b0e9@meinberg.de>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/FJwfGTtFPjgothVIdCCfXPpAKB4>
Subject: Re: [Ntp] Finding leap-seconds.list
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Fri, 09 Nov 2018 15:47:53 -0000

I have been following this discussion and I'd like to push the reset
button. Discussion about the tz database is not just off-topic but is
irrelevant to this working group. Many people on this list may be
interested but there are other forums for that.

My understanding is that IERS is the body responsible for deciding when
to declare a leap-second. From the point that they announce a
leap-second there are various methods used to distribute that
announcement. From my understanding of this from then on there is an
informal process to add the information into leap-second files and those
distributed to various different places around the internet. The first
part is a manual process and requires a human being to do that. The
distribution of the information seems to be a vague process. The various
standards agencies such as NIST in the US are government agencies and as
such are only responsible for standards and information in their own
countries though you would expect that they are responsible more making
available a leap-second file.

So the real question is whether or not we need to formalize the
distribution of the leap-second file and how would we accomplish that?
Also how would it be kept uptodate? For that matter is there an
agreed-upon standard format for the contents of the leap-second file?

Danny