<html><head></head><body>What is that a checksum of? The zone name?<br>
<br>
If we're moving away from zone names like that, I don't see any point in hashing an identifier just to obscure it. Better to just use an incrementing counter (Asia/009, America/010) or an algorithm that generates pronouncable names when fed an incrementing counter (Asia/009 -> Asia/Kasoma, America/010 -> America/Fureso).<br><br><div class="gmail_quote">On December 1, 2016 4:46:39 PM EST, Paul Eggert <eggert@cs.ucla.edu> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On 12/01/2016 01:30 PM, Guy Harris wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> It would have been nice if there had been some form of ID that we could have used for tzdb zones that*didn't* involve city names<br /></blockquote><br />How about SHA-256 checksums? Instead of "Europe/Kiev" the zone name <br />would be <br />"099d2adb7f9a187c25224cd49364de6d510d6e89924584c0b97d88d3f801e551", <br />which would make users less likely to raise political objections. <br />SHA3-512 is also a possibility, although SHA3 software isn't as mature <br />and the names would be a bit long. (:-)<br /><br /></pre></blockquote></div></body></html>