The traditional way in which time zone information has been transported to client machines has been the IANA tzdata/tzcode distribution. For Unix systems this usually relies on the patch or update mechanisms for operating systems. Microsoft produces its own version of that information, and Apple relies on a third party distribution which repackages the tzdata.
The IETF Time Zone Data Distribution Service is moving toward closure on its tzdist draft. The mechanism will provide a way to transport time zone information to clients via network protocols that can request only the bits relevant to a particular client device. The tzdata/tzcode have long had a set of "right" zones which can be used on systems which actually do count the leap seconds. Because the new tzdist mechanism is rooted in the tzdata ideas it is also capable of transmitting the leap second information as if it were a time zone. Last week I submitted a few examples of how that could work http://www.ietf.org/mail-archive/web/tzdist/current/msg01215.html -- 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
