IETF Logo Mail Archive

Re: [Ntp] Resending: Thoughts on draft-ietf-ntp-refid-updates

Tony Finch <dot@dotat.at> Fri, 20 July 2018 17:27 UTC

Return-Path: <dot@dotat.at>
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 88EF0130F4A for <ntp@ietfa.amsl.com>; Fri, 20 Jul 2018 10:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=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 tUWhYuS3byCm for <ntp@ietfa.amsl.com>; Fri, 20 Jul 2018 10:27:23 -0700 (PDT)
Received: from ppsw-31.csi.cam.ac.uk (ppsw-31.csi.cam.ac.uk [131.111.8.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 602C3131041 for <ntp@ietf.org>; Fri, 20 Jul 2018 10:27:23 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:44418) by ppsw-31.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.137]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1fgZBX-000u4A-JY (Exim 4.91) (return-path <dot@dotat.at>); Fri, 20 Jul 2018 18:27:19 +0100
Date: Fri, 20 Jul 2018 18:27:18 +0100
From: Tony Finch <dot@dotat.at>
To: Martin Burnicki <martin.burnicki@meinberg.de>
cc: ntp@ietf.org, Ask Bjørn Hansen <ask@develooper.com>
In-Reply-To: <b20d6802-e4fc-8af0-332f-9759652e9cde@meinberg.de>
Message-ID: <alpine.DEB.2.20.1807201816480.5965@grey.csi.cam.ac.uk>
References: <5B2795C6-F78E-40FB-8B98-790E50228808@redfish-solutions.com> <5EB0F348-AC75-4C29-A576-FA590305EA2E@netnod.se> <C7C5AC86-1488-452B-8C1D-05F5151D2AFB@develooper.com> <8e0a4de9-71b3-04ec-59fb-4431ea0a2d2d@meinberg.de> <alpine.DEB.2.20.1807201450450.3596@grey.csi.cam.ac.uk> <b20d6802-e4fc-8af0-332f-9759652e9cde@meinberg.de>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/P90HK_1f4BTSQUD1Gn5meVAQiBc>
Subject: Re: [Ntp] Resending: Thoughts on draft-ietf-ntp-refid-updates
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.27
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, 20 Jul 2018 17:27:28 -0000

Martin Burnicki <martin.burnicki@meinberg.de> wrote:
>
> If something like this should become a well accepted feature, there's
> also the question who runs and maintains the top level DNS entry in a
> reliable way? It must be made sure that the DNS entries are well
> maintained and updated over a long time, not only for the next 2 years
> or so, as long as some volunteers are interested in this topic.

Yes, it's a problem. The best I can do is write a maintenance script that
is mostly automated, and verifies that the IERS, USNO, and NIST leapsecond
tables agree before it will update the DNS. But, as you correctly observe,
I'm just an easily distracted volunteer :-)

(warning: symbiosisware ahead, danger will robinson!)
http://dotat.at/cgi/git/leapseconds.git/blob/HEAD:/leapseconds.pl

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty, Forth, Tyne, Dogger: Variable 3 or 4. Slight. Occasional
rain or showers. Good, occasionally moderate.

v2.23.0 | Report a Bug | By Email