[tz] [PATCH] Updates for Chile 2013

[Bennett Todd]

It sure would be nice if we could always ship zoneinfo db updates in good
time for orderly deployment, but so far in my career, I've found ways to
partition the apps that urgently need accurate daylight savings rules
(often in the region of billing or accounts) from those which are
disruptive to update (in my specialty, infrastructure servers like
firewalls, routers, DNS, email, and the like). The latter can often
disagree with the former, as long as they agree with each other.

E.g. Email spam blockers that insist on strong coherence among all the
Received headers' timestamps are too fragile.

And for another example, KDCs must be updated in pretty good unison, with
only an hour slop among them, but clients using Kerberos auth must tolerate
a couple of hours skew between the KDC clock and their own, as long as each
is marching monotonically forward in coarse agreement.

Late updates are reprehensible, but alas, we can only do so much better
than the legislatures.

Can you meet your window by processing the update from github, or are you
dependent on a vendor who cannot or will not?

I've met employers' demands for validation and review of zoneinfo db
updates by ogling, and offering to others, diff(1) output on the output of
zdump(1) against the old and new databases.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mm.icann.org/pipermail/tz/attachments/20130301/c047827a/attachment.html