On Sat 2015-01-17T14:55:09 -0700, Rob Seaman hath writ: > However the data are encoded, stored or retrieved, there will be a > concept of operation that supports a variety of timekeeping / calendar > use cases. These surely include historical / retroactive > requirements. Any implementation should support the entire table of > leap seconds.
I am pleased to see the DNS mechanism details being worked out. In addition, version 05 of the tzdist draft was published today. https://tools.ietf.org/html/draft-ietf-tzdist-service-05 It includes explicit text defining the transfer of the entire table of leap seconds. -- Steve Allen <[email protected]> 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 _______________________________________________ LEAPSECS mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/leapsecs
