[LEAPSECS] stale leap second information

[Steve Allen]

On Wed 2015-01-14T19:53:52 +0000, Poul-Henning Kamp hath writ:
> Plenty of space for the data we need in an IPv4 'A' record, and
> a human readable TXT record could supplement that.

All of the leap second information thru history is already
demonstrated via HTTP transport in Ken Murchison's test server for
the IETF tzdist protocol.  The data come from these URLs

Leap second information as RFC 5545 (iCalendar) VTIMEZONE
(this is human-readable text, but many modern e-mail user agents will
interpret it as a calendar to add to a scheduling agent)

https://cyrus-test.andrew.cmu.edu/tzdist/zones/Etc/TAI

Leap second information as json
(this is also human-readable text)

https://cyrus-test.andrew.cmu.edu/tzdist/zones/Etc/TAI/observances?start=1970-01-01T00:00:00Z&end=2038-01-01T00:00:00Z

These same tzdist services will be providing the time zone information
that any client of NTP will need in order to convert to local time.
That makes the tzdist protocol into one-stop shopping for info about
the offset from "UTC" as stored by whatever operating system.

--
Steve Allen                 <sla at ucolick.org>                WGS-84 (GPS)
UCO/Lick Observatory--ISB   Natural Sciences II, Room 165    Lat  +36.99855
1156 High Street            Voice: +1 831 459 3046           Lng -122.06015
Santa Cruz, CA 95064        http://www.ucolick.org/~sla/     Hgt +250 m