<div dir="ltr"><div>Since it's useful to leave in placesupport for the current way of specifying leap seconds, a NIST-to-current conversion script may be in order.<br><br></div> --ado<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Aug 12, 2013 at 3:20 PM, Paul Eggert <span dir="ltr"><<a href="mailto:eggert@cs.ucla.edu" target="_blank">eggert@cs.ucla.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">Martin Burnicki wrote:<br>
> My proposal is to use some sort of network protocol to deploy the contents<br>
> of the tz DB, either for a single time zone used on a system, or even for all<br>
> time zones supported by the tz database.<br>
><br>
> In my opinion this is similar to DNS or DHCP, or even NTP services.<br>
<br>
</div>Have you looked at Internet RFC 4833? It specifies a DHCP<br>
option for disseminating TZ settings. It's not exactly what<br>
you're asking for, but it should help you get started on how<br>
to add that sort of thing to DHCP.<br>
<div class="im"><br>
> My proposal is to change the TZ code and DB in a first step<br>
> so that they also use the NIST leap second file format.<br>
<br>
</div>Sure, you could add an option ('-S file', say) to zic.c, with<br>
documentation in zic.8.<br>
</blockquote></div><br></div>