[LEAPSECS] stale leap second information
magnus at rubidium.dyndns.org
Wed Jan 14 03:59:03 EST 2015
On 01/14/2015 09:11 AM, Poul-Henning Kamp 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.
That would be one of many ways that it should be distributed.
We want a multi-protocol way of distributing this.
DNSSEC should be part of a DNS solution for instance.
Webpage with certificats and signed files is another aspect.
More information about the LEAPSECS