Re: [Ntp] Finding leap-seconds.list

Denis Reilly <denis.reilly@orolia.com> Wed, 07 November 2018 19:17 UTC

Return-Path: <denis.reilly@orolia.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 693AC130DBE for <ntp@ietfa.amsl.com>; Wed, 7 Nov 2018 11:17:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=orolia.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 YsQXJyqfkBJA for <ntp@ietfa.amsl.com>; Wed, 7 Nov 2018 11:17:54 -0800 (PST)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70044.outbound.protection.outlook.com [40.107.7.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9DEB130934 for <ntp@ietf.org>; Wed, 7 Nov 2018 11:17:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orolia.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jNEybGQO7XD7va1St8KOXPpsKrY62gIL+rTx+7OGQpo=; b=v6DVGNLVeR/QjS0Pmw1OrbpFzPcYYQpvKzPM7OUd8EVrOH+baUZv0I52YEhEgR3cg5phG5ZIL7b+9VKD4bgjqCLRuRY/9q4GY0oIk77LiFPPAP+//BSMRnSJ5UuZO77MhDhvmfAURUCwffZY16CRjhXoBaQkw14uhqEo5ihJwgw=
Received: from AM6PR0602MB3733.eurprd06.prod.outlook.com (52.133.31.28) by AM6PR0602MB3750.eurprd06.prod.outlook.com (52.133.31.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1294.28; Wed, 7 Nov 2018 19:17:50 +0000
Received: from AM6PR0602MB3733.eurprd06.prod.outlook.com ([fe80::e0c5:158f:2a93:fa7]) by AM6PR0602MB3733.eurprd06.prod.outlook.com ([fe80::e0c5:158f:2a93:fa7%5]) with mapi id 15.20.1294.034; Wed, 7 Nov 2018 19:17:50 +0000
From: Denis Reilly <denis.reilly@orolia.com>
To: Martin Burnicki <martin.burnicki@meinberg.de>, Thomas Peterson <hidinginthebbc@gmail.com>, "ntp@ietf.org" <ntp@ietf.org>
CC: Paul Eggert <eggert@cs.ucla.edu>
Thread-Topic: [Ntp] Finding leap-seconds.list
Thread-Index: AQHUdrZ2iOOACytu4kK7d3gVVqeMpaVEmeQAgAAUhrA=
Date: Wed, 07 Nov 2018 19:17:49 +0000
Message-ID: <AM6PR0602MB3733A11C62B7A0ED49F318B5FFC40@AM6PR0602MB3733.eurprd06.prod.outlook.com>
References: <5884DA3A-B95B-4D6B-9A31-E964CE4F02EF@gmail.com> <53bc1310-c198-557a-54ca-57b5b0af9bcb@meinberg.de>
In-Reply-To: <53bc1310-c198-557a-54ca-57b5b0af9bcb@meinberg.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=denis.reilly@orolia.com;
x-originating-ip: [66.193.84.98]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM6PR0602MB3750; 6:0kidIIgyL3GgArN6V+ARlFjdggTheDgy4WtTUAWQkWhNadUChcBjMU3wtzIuHfxQFTtjmmj9ZfDl2VAx6a3UkjZLPPzzr1o+OyauUdH8eXXb7YqKKszWD/pMMk2elkztaZ5PYiMd2cTjD1CPmdmYkjn69EhaSrjV/1eOXy7ehLHCg/22bEUM/x3Gok047qPuMZVEWV5IJEWQ6GqCai0leErwZA68qFAUCvuEqpBVIWd0eflwnndRzjsbFyNsMYQIROUHb/Bm29A3CP/UJJeew1hEI+9/65XLhtiiQPuHdr/FWQhCHdMq6c3W3X9ZnBGRWhKpl2JxdMOvS4uA4Cbi3qQA/G9QKj/pIOzPS7spurBj0BN3LDbwYxxWiiqM80PI17UYyDxUPmg9SCS77yTzQZJOXFFwKK4ffDopiiwRi9MzHoLwqSJv0jiuC40CDXL9G1eBoAQox4SqdrACfFI+vA==; 5:ajl6RIDAKN+sJOmerHKaEFZdzhv8gfh5SoYWwI9buVN5Ap4Lpoxwdwegw33RgLjrFwoKdaY5+kAjYEuGlDCEnFam2EenTMmuaOplm7ISGj7+riUNHUyaSJJzOKDFoTnbgeab2gBKafGt98KfHGDd0U9WkAn8BDSyMfeenoGAgdE=; 7:jhqtfoCNP81F5dvUvGUySPR3AB1PI506D5s6LRLTPOO3x7Wzk77W+WGn6LY7bnSq0BoifVc3Xly6BR4n3b6U2oCnsjRDBv4QMQFWRYLMDZnIM54ghStyn1oSOzZkhCJI+8uisPW+FM8CV3rFzOjrVQ==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 4f4650fd-12d6-4992-4556-08d644e5b571
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(5600074)(711020)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:AM6PR0602MB3750;
x-ms-traffictypediagnostic: AM6PR0602MB3750:
x-microsoft-antispam-prvs: <AM6PR0602MB375032C03C8C459C1C09C079FFC40@AM6PR0602MB3750.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(278428928389397)(116415991822766)(128460861657000)(81160342030619)(122605397693432)(85827821059158)(270544422350281);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231382)(944501410)(52105095)(148016)(149066)(150057)(6041310)(20161123564045)(20161123560045)(20161123562045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991095); SRVR:AM6PR0602MB3750; BCL:0; PCL:0; RULEID:; SRVR:AM6PR0602MB3750;
x-forefront-prvs: 08497C3D99
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(136003)(366004)(376002)(396003)(39850400004)(13464003)(52314003)(199004)(189003)(252514010)(14454004)(9686003)(11346002)(53936002)(5660300001)(99286004)(71200400001)(71190400001)(2900100001)(6436002)(33656002)(446003)(44832011)(2906002)(25786009)(39060400002)(106356001)(486006)(66574009)(966005)(476003)(4326008)(6306002)(8936002)(68736007)(229853002)(105586002)(55016002)(102836004)(97736004)(81166006)(81156014)(76176011)(8676002)(316002)(14444005)(7736002)(45080400002)(74316002)(256004)(26005)(305945005)(15974865002)(5024004)(6246003)(6506007)(66066001)(478600001)(53546011)(3846002)(6116002)(186003)(110136005)(2501003)(86362001)(7696005); DIR:OUT; SFP:1101; SCL:1; SRVR:AM6PR0602MB3750; H:AM6PR0602MB3733.eurprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: orolia.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: o8GqnQyS2yHqjBuwo5SkqCftIs2D3n9JE/mthZ6vWg9T1XrUP+cTyM4F7zGpEA3JeTHfTo28lhdFSP20d+HnfQxgwz6TkntGtlFELu21AVWqH1I8Nu75kS0Fo+Q9hWJIhEkfYq5zUdDkShJY2825lfCzz1qktPnpu7zIzvVoJ6IvpOG14kPPDdo91AWpC6U6FwA8x/xgwauUtrJ5dHoUV3IXYVLCFyAfe9Nhz1reXZKJ+IS0SKboO5iezxM1D+dPixuKzBNLOk2NZ+zfNiDcQuVf4B12Ok/21aiyg/j0S9eWckA085XQ33WhuW8lJ6oI93ZosPhSDQr7S5sfjsZeIuDUsyhIr20xgmmx7+klerY=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: orolia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4f4650fd-12d6-4992-4556-08d644e5b571
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Nov 2018 19:17:49.9661 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a263030c-9c1b-421f-9471-1dec0b29c664
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR0602MB3750
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/ba2u8xDHnUt4DRXWHNo4sZJksOQ>
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: Wed, 07 Nov 2018 19:17:57 -0000

Thomas and Martin,

On doing my own research into this for the BCP, I found that the Time Zone database maintenance procedures are documented in BCP 175 / RFC 6557.

However, after the discussion during the WG meeting, I think it's better to remove the mention of the leap second file hosted by the IETF in the BCP. As Martin notes, there are better places to get it.

--
Denis Reilly  |  Technical Lead  |  denis.reilly@orolia.com  (585)321-5837

-----Original Message-----
From: ntp <ntp-bounces@ietf.org> On Behalf Of Martin Burnicki
Sent: Wednesday, November 07, 2018 1:00 PM
To: Thomas Peterson <hidinginthebbc@gmail.com>; ntp@ietf.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [Ntp] Finding leap-seconds.list

Thomas Peterson wrote:
> As was discussed at the working group meeting at IETF 103 [0], I have decided to do some research on the leap-seconds.list file that the IETF appears to be hosting at https://www.ietf.org/timezones/data/leap-seconds.list, but for some participants of this working group appear unclear about.

During the IETF NTP WG session I posted a link in the chat which points to a PDF I wrote some time ago:
https://www.meinbergglobal.com/download/burnicki/the_ntp_leap_second_file.pdf

There are several "original" versions of that file published by the IERS, NIST, and USNO.

One of those original files (usually the version from NIST) is used to update the TZDB records, and the original file is also included in the TZDB distribution/tar ball, which is then unpacked and made available at the IETF web site.

The problem here is that first an update of the original leap second file appears, and only whenever the next TZDB version is released after that the file appears on the IETF web site.

So for most users it's better to pick up a file from one of the original sites.

> Where is this referenced in an RFC or other IETF document?
> I ran a search of “leap-seconds.list” across the spread of draft and RFC documents. No RFC that I have found makes direct reference. However, the current NTP BCP draft Section 4.6 [1] contains:
>
> ... SNIP ...
>
> The IETF maintains a leap second list [[7]] for NTP users who are not
>    receiving leap second information through an automatic source.
>
>    Files are also available from other sources:
>
> ... SNIP ...
>
> With [[7]] holding reference to the file hosted at, and a list of links to sources.
>
> What else is www.ietf.org hosting of a similar nature?
> This file alone is not the only thing hosted under www.ietf.org, in fact https://www.ietf.org/timezones/ directory listings show that all recent versions of the tzdb (including 2018g the most recent) which suggests a human maintaining the hosting of it, or automated process. Versions only go back to 2016. These files are also available over FTP [2].
>

Yes, and since the leap seconds file is part of the TZDB, it also becomes available via the IETF web site.

> How long have these files been hosted on www.ietf.org?
> Internet archive's Wayback Machine [3] shows it appearing back in 2015.
>
> Who is using the file?
> ntpd does depend on it as was discussed at the WG meeting, [4]. FreeBSD [5] holds reference to it and users have reported issues when being unable to access it in the past. In addition, at least one library [6] make use of it outside of ntpd, however I don't believe this is heavily used or cause non-developers or system administrators any pain if it went missing.

I'm sure the file *is* heavily used, but maybe not directly from the IETF web site.

It's a good source to become aware of an upcoming leap second, and it's a good source to be able to determine the current UTC/TAI offset, as e.g. required when using PTP which uses TAI timestamps by default.

Anyway, I think the file is mostly used by NTP or PTP servers since for most applications the information interesting for clients can be passed via the individual protocols.


Regards,

Martin
--
Martin Burnicki

Senior Software Engineer

MEINBERG Funkuhren GmbH & Co. KG
Email: martin.burnicki@meinberg.de
Phone: +49 5281 9309-414
Linkedin: https://www.linkedin.com/in/martinburnicki/

Lange Wand 9, 31812 Bad Pyrmont, Germany Amtsgericht Hannover 17HRA 100322 Geschäftsführer/Managing Directors: Günter Meinberg, Werner Meinberg, Andre Hartmann, Heiko Gerstung
Websites: https://www.meinberg.de  https://www.meinbergglobal.com
Training: https://www.meinberg.academy

_______________________________________________
ntp mailing list
ntp@ietf.org
https://www.ietf.org/mailman/listinfo/ntp
ATTENTION: This email came from an external source.
Do not open attachments or click on links from unknown senders or unexpected emails.