[LEAPSECS] stale leap second information

Poul-Henning Kamp phk at phk.freebsd.dk
Wed Jan 14 05:25:53 EST 2015

In message <54B62FD7.4000300 at rubidium.dyndns.org>, Magnus Danielson writes:

>> 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.
>That would be one of many ways that it should be distributed.


But the reason why DNS would be nice is that it's lightweight.

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