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.

    --ado


On Mon, Aug 12, 2013 at 3:20 PM, Paul Eggert <eggert@cs.ucla.edu> wrote:
Martin Burnicki wrote:
> My proposal is to use some sort of network protocol to deploy the contents
> of the tz DB, either for a single time zone used on a system, or even for all
> time zones supported by the tz database.
>
> In my opinion this is similar to DNS or DHCP, or even NTP services.

Have you looked at Internet RFC 4833?  It specifies a DHCP
option for disseminating TZ settings.  It's not exactly what
you're asking for, but it should help you get started on how
to add that sort of thing to DHCP.

> My proposal is to change the TZ code and DB in a first step
> so that they also use the NIST leap second file format.

Sure, you could add an option ('-S file', say) to zic.c, with
documentation in zic.8.