Re: [Ntp] Finding leap-seconds.list

Jared Mauch <jared@puck.nether.net> Fri, 09 November 2018 22:30 UTC

Return-Path: <jared@puck.nether.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 5A6901276D0 for <ntp@ietfa.amsl.com>; Fri, 9 Nov 2018 14:30:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Awx9WMD9c1aV for <ntp@ietfa.amsl.com>; Fri, 9 Nov 2018 14:30:31 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A952124D68 for <ntp@ietf.org>; Fri, 9 Nov 2018 14:30:31 -0800 (PST)
Received: from [IPv6:2603:3015:3606:cbe1:7c0b:cea:cb5:a1e9] (unknown [IPv6:2603:3015:3606:cbe1:7c0b:cea:cb5:a1e9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 1C0D45406DF; Fri, 9 Nov 2018 17:30:26 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <20ebe882-92f1-ddae-0698-f450979d986a@nwtime.org>
Date: Fri, 09 Nov 2018 17:30:25 -0500
Cc: ntp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0443A48-8492-4EEA-9BBE-B7544A4C6789@puck.nether.net>
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> <CANCZdfpJZLEORhak2QWDuHgjrQ_UZzBNv4_RR9prDKU7qtZVHQ@mail.gmail.com> <e5a21e9a-bbb6-3a57-df83-717dfc628c06@meinberg.de> <20ebe882-92f1-ddae-0698-f450979d986a@nwtime.org>
To: Harlan Stenn <stenn@nwtime.org>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/fp-IAb9Y7I6ru5x9LB5XEGiX2h0>
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 22:30:33 -0000


> On Nov 8, 2018, at 4:24 AM, Harlan Stenn <stenn@nwtime.org> wrote:
> 
> By default, the "update-leap" script in the Reference Implementation
> queries:
> 
>   https://www.ietf.org/timezones/data/leap-seconds.list
> 
> H


This may be poor behavior updating it from a source that perhaps isn’t well maintained.

I was the one at the mic advocating that without a document saying it is hosted at IETF it should go away.

What this also means is that if someone writes up a doc saying it should live at the IETF that would remove my primary concern.

There are the secondary issues of what NTP implementations use it.  I would like to know if it’s just FreeBSD users that fetch it and the frequency, etc.

I suspect it’s not often, and if the file is not well maintained, publishing it at the IETF without documenting how and when it’s updated may actually make things worse if we don’t prescribe some procedure to maintain it.

If it’s a relic of a single implementation (whatever form/type it is), perhaps it’s best for them to maintain the document and update it at their site.  It’s also perhaps too late, but if this file is so important, is it described in the BCP for operating NTP, or is this yet another esoteric NTP thing that’s not well documented so ends up being inconsistently used?

I would be interested in seeing an implementation report for who uses it.  (I would also perhaps argue that freebsd-update is not really a consumer of it).

- Jared