[tz] NIST leap-second file not yet updated

[Arthur David Olson]

Paul Eggert in...
    http://www.ietf.org/mail-archive/web/tzdist/current/msg01135.html
... from 2014-12-17 notes that "...the IERS file is copyrighted. That is
why the tz database reproduces the NIST file (the NIST file is public domain).
Other distributors of the IERS file might want to keep this in mind."

Unless the copyright situation has changed since then...

    @dashdashado

On Mon, Feb 15, 2016 at 1:20 PM, <Paul_Koning at dell.com> wrote:

>
> > On Feb 15, 2016, at 12:49 PM, Steve Allen <sla at ucolick.org> wrote:
> >
> > On Mon 2016-02-15T12:14:52 -0500, Tim Parenti hath writ:
> >> I prepared the attached patch which uses the file from IERS shortly
> >> after the 2016-01-11 announcement, but was sitting on it while we
> >> waited for NIST, since the conversation at the time seemed to indicate
> >> that NIST was our preferred source.  I think, though, that since IERS
> >> actually decides the leap seconds and seems to be updating their file
> >> more promptly, it might be worthwhile to consider switching to IERS as
> >> our canonical source for this file.
> >
> > That makes sense.  Announcing the leap seconds is part of the charter
> > of the IERS, and staff there are on public record as having interest
> > in disseminating the information.  It is not part of the charter of
> > NIST, and staff there are on public record as not wanting leap seconds
> > to exist.
>
> I'll second that.  And even if it were part of the NIST charter, NIST
> would only be a secondary source, not the primary source.  IERS is the
> originator of the data; why use a middleman?
>
> If we currently have anything saying that we use any source other than
> IERS as the supplier of leap second data, we should fix that.
>
>         paul
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/tz/attachments/20160215/4772c47f/attachment.html>