[LEAPSECS] stale leap second information

Poul-Henning Kamp phk at phk.freebsd.dk
Wed Jan 14 10:06:54 EST 2015

In message <20150114115758.gvGCdclG%sdaoden at yandex.com>, Steffen Nurpmeso write
>"Poul-Henning Kamp" <phk at phk.freebsd.dk> wrote:
> |--------
> |In message <54B621B5.1080909 at rubidium.dyndns.org>, Magnus Danielson writes:
> |
> |>> About one year ago I contacted the folks at IERS and asked them to put
> |>> an expiration date into their leap second file since the existing one
> |>> didn't have one.
> |
> |What would be really useful would be if they provided the current
> |leapsecond count and the date of the next (if known) via DNS.
> |
> |DNS because it has built in caching and works almost everywhere.
>Or a new NTP protocol, that would only require a software update
>of NTP servers.

NTP is a much more specialized protocol than DNS and it is blocked
a lot of places.

>The current one is obsolete anyway in ~20 years,

The new one is called PTP, but there's probably 30 years of life
left in NTP still.

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

More information about the LEAPSECS mailing list