Re: [Ntp] Antw: Re: Finding leap-seconds.list

Hal Murray <hmurray@megapathdsl.net> Mon, 12 November 2018 20:41 UTC

Return-Path: <hmurray@megapathdsl.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 79E40130E68 for <ntp@ietfa.amsl.com>; Mon, 12 Nov 2018 12:41:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.044
X-Spam-Level: *
X-Spam-Status: No, score=1.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_DYNAMIC_IPADDR=1.951, RDNS_DYNAMIC=0.982, T_HDRS_LCASE=0.01, 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 lGj0EaczzOGQ for <ntp@ietfa.amsl.com>; Mon, 12 Nov 2018 12:41:10 -0800 (PST)
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by ietfa.amsl.com (Postfix) with ESMTP id 92843130E4B for <ntp@ietf.org>; Mon, 12 Nov 2018 12:41:09 -0800 (PST)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 7383F40605C; Mon, 12 Nov 2018 12:41:09 -0800 (PST)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Warner Losh <imp@bsdimp.com>
cc: Hal Murray <hmurray@megapathdsl.net>, ntp@ietf.org
From: Hal Murray <hmurray@megapathdsl.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 12 Nov 2018 12:41:09 -0800
Message-Id: <20181112204109.7383F40605C@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/c1HNnHyKGpCWruRoalvxLGoRUeA>
Subject: Re: [Ntp] Antw: Re: 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: Mon, 12 Nov 2018 20:41:12 -0000

imp@bsdimp.com said:
> The deadline for #6 is leap-second day, correct? ntpd only announces an
> impending leap second in the last 24 hours before the leap second. Or is that
> just a reference implementation detail. When there's no leap second the
> deadline is a few days before since that's the expiration of the previous
> file. 

The ntpd-kernel API is "leap tonight".
The ntpd-ntpd API is "leap at the end of this month".

A valid local leap-seconds file overrides the results from upstream servers.

I'm not sure what happens if ntpd has a valid leap-seconds file after it 
expires.

The early announcement on the wire gives humans a chance to verify that the servers are announcing as expected and/or maybe time to correct things if something is not right.

>>   3 TZDB releases updated copy from NIST
>>   4  distro releases update to TZDB
>>   5  end system picks up new TZDB from distro
> Also, to be clear, as far as ntpd is concerned, steps 3, 4, 5 are all
> *optional* if there's another mechanism to pull in a new leap-second.txt file
> from elsewhere. #5 implies an upgrade of at least some of the packages on the
> system. While that's *A* way to do it, there are other equally valid ways. We
> should allow for the extra time, of course, for this to happen. 

Correct.

I think the timing on alternatives will be similar so I haven't explored them.  In many cases, step 3 goes away.


> P.S. Sorry if I'm being too nit-picky here, but traditionally there's been a
> wide diversity of methods for obtaining leap-seconds.txt, and it would be
> premature to standardize on the above list. 

Doesn't look nit-picky to me.  Not even mildly so, much less "too".  Thanks for pointing it out so it gets archived.

My main goal is to avoid having every end-user workstation running a cron job pointed at some server that can't do anything about it if some distro ships a buggy version that turns into a DoS.

If your users get it from your servers, I'll be happy.



-- 
These are my opinions.  I hate spam.