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

Warner Losh <imp@bsdimp.com> Mon, 12 November 2018 17:33 UTC

Return-Path: <wlosh@bsdimp.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 57BCE130E51 for <ntp@ietfa.amsl.com>; Mon, 12 Nov 2018 09:33:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bsdimp-com.20150623.gappssmtp.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 C54pByfYqTgk for <ntp@ietfa.amsl.com>; Mon, 12 Nov 2018 09:33:08 -0800 (PST)
Received: from mail-it1-x132.google.com (mail-it1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BA89130E53 for <ntp@ietf.org>; Mon, 12 Nov 2018 09:33:08 -0800 (PST)
Received: by mail-it1-x132.google.com with SMTP id e11so14331448itl.5 for <ntp@ietf.org>; Mon, 12 Nov 2018 09:33:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Yt8ySxwBz5gEZNZIJCuTf9nJ34DNNBeKhxNPB/TAqzQ=; b=dmYmUBjYt3iHrYGAzV/TvcEay5z7JJnxoOq/41Qs3ZHHun3usybJJWZzTkDIvRYFZu qM5xbc0uPk8X4Rog1HBtgQzc0fKrKzCKJaV1uqmNpXIVZhZ2ChBml8TgAE9BbL5FjCjD /0v9hKZ76YalnpCSSjW16GewrLAY/qgYZX4d9AmEQ/kJq+8WDr+QOFd03wZ5XVGvDe5f YiBdGIdqEacJD8Y4us4ljUA5x0mJyUQc033Z1hJXTS/WC9UH+vafVHuwB0MQw5G0qWNr DQ4sXns0BQQoWm0mowQ8u993bpSNNyYh3RXSlUekfVw4qJ/GSt8qtwZXdObj04ZbrJ15 TtSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Yt8ySxwBz5gEZNZIJCuTf9nJ34DNNBeKhxNPB/TAqzQ=; b=BqPLOnOz4DG3iVC/4MFNH41Hli1QYYQS55ndM9UMU/OcTnNEPdOqtqui0F4JYtLCZP xlkyVPr74Fd01aTAsmONObmkZb6TW8QWrjEfM2peQ3Prw4TkFuWXUKWeZjRf8cB8sG3y vbnIUFXaTv9wKtCD9aUpM4+G0tUDAn36PlaT8UXo+XjnkPBNV2F0w2LyjUCxsfFDOoTR e7+98cRrgTdNxsGCZzw0f+DRZbenAA8XgONpmq8zzaL5AYDZeUQ+z9W+MVTAkt/lkpmT JLfFj0J96/TAnYhjduR0bxIGNL1EjZJjZFs/tzMnBXPYP/+mSQAEgMdfHE6HdUIEwZqi 4Nrw==
X-Gm-Message-State: AGRZ1gJjeVlyPhpfoKQcy32l6wb51OCgjT50lUtQOvHo1Y6QVmNugCgF qUAsvHxVkG6oxMIA9bBzLHYx219ce/g/psxEwFil9g==
X-Google-Smtp-Source: AJdET5fCO5ov4ubu1dxp+eGCcXZgLORfaTNl6egeghmLRqZ0N2WWVhD1g4ejtyEcOfKu7Vr4cqv42c0HVH5nnmQFJr0=
X-Received: by 2002:a02:9951:: with SMTP id d17-v6mr1508684jak.78.1542043987348; Mon, 12 Nov 2018 09:33:07 -0800 (PST)
MIME-Version: 1.0
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> <5BE96529020000A10002E079@gwsmtp1.uni-regensburg.de>
In-Reply-To: <5BE96529020000A10002E079@gwsmtp1.uni-regensburg.de>
From: Warner Losh <imp@bsdimp.com>
Date: Mon, 12 Nov 2018 10:32:55 -0700
Message-ID: <CANCZdfpB_zbFNyS3H14Z96h2MpHs3=9cWUkwvAyKZV6Xi0vMuA@mail.gmail.com>
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
Cc: eggert@cs.ucla.edu, dsibold.ietf@gmail.com, Thomas Peterson <hidinginthebbc@gmail.com>, denis.reilly@orolia.com, ntp@ietf.org, Martin Burnicki <martin.burnicki@meinberg.de>
Content-Type: multipart/alternative; boundary="00000000000018dbbe057a7b18aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/gJX5hvGyw0PhVSbDwSKee5ydMG8>
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 17:33:11 -0000

On Mon, Nov 12, 2018 at 4:34 AM Ulrich Windl <
Ulrich.Windl@rz.uni-regensburg.de> wrote:

> >>> Paul Eggert <eggert@cs.ucla.edu> schrieb am 08.11.2018 um 22:39 in
> Nachricht
> <a7d8d58b-7370-1b4c-0c70-fd775dfbf854@cs.ucla.edu>:
> > On 11/7/18 6:49 PM, Thomas Peterson wrote:
> >> * The IETF ceases to host unpacked versions of tzdb
> >
> > I'm not sure exactly what is being proposed here. That being said, the
> > tzdb distribution <https://www.iana.org/time‑zones> is not going to
> > remove the leap‑seconds.list file. That file is used by tzdb itself and
> > (like it or not) many downstream packages depend on it. Whatever problem
> > you're trying to solve, removing leap‑seconds.list can't be part of the
> > solution.
>
> So if TZ data depend on the leapsecond list, the previous discussion on
> whether the TZ data wil be updated frequently enough should be solved: In
> my
> view of things new TZ data should be made availale whenever a new
> leapsecond
> file is available (or at least significantly before the last one expires).
>

I think the probability of that is approaching 1.0

Let's look at the timeline...

First week or so in January Bulletin C comes out
By Feb 1 new leap file that expires December-ish (it's technically valid
until Dec 31 23:59:58, but the practice has been to expire a bit before
then, IIRC, December 1st).
Then July comes around and we do it again: by august 1st a new leap file is
available, expiring June 1.

So worst case we have a 4 month window. If a TZDB release were done the day
before a new leap file, you'd have 4 months to do another release to be
"just in time".

Going back to 2010, I see the following releases: 2018g, 2012j, 2011n,
2010o (based on a quick grep of the FreeBSD vendor imports, which is
imperfect data). Each of these years shows at least monthly releases based
on the letter suffix... So there's approximately monthly releases. Worst
case, there's a 4 month window. I think we're good, and if there were a 3
month period where there were no tz changes, a special one for the new leap
file could be made either in early May or November.

Warner