<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Have long thought there would be merit for some sort of on demand updates.   This could be implemented in a system more similar to/if not DNS.  If you need the rules for a location/zone/city/place you would query for that and in the first place, the DNS servers provided by your ISP or company and if they have that info you get it from them if not they request off the next level up and so on and so on.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">In DNS the rules could be published in TXT records in much the same way as Google publishes all its net-blocks in DNS so that anybody can query what public addresses they use.   Google publish a TXT record with the names of other TXT records which list the netblocks they use (wish Amazon and MS Azure were so internet application friendly).    For a time zone, a TXT record could be published giving the number of records (lines) for that zone and then TXT records published with an index suffix on the zone.   <br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">IANA could maintain these TXT records under their domain with maybe a subdomain per time zone (OMG in a zone file),  OR, they could actually delegate this out to designated authorities for geo-political areas.... OK, yep, that would be a political <span>quagmire for some regions of the world so perhaps not.<br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span>All of this could be done within the existing internet infrastructure and without it impacting IANA systems.   The starting point being an RFC to describe it all including the format meanings of the rules themselves.  That format would likely need to be less dependent on the definition of and interpretation of white-space; some sort of single delimiter would be nice.   "|" would be a candidate.   The records would be free of the commentary, that would remain in the current full download from IANA.<br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span>DNSSEC....   Definitely.  Much mischief possible without.<br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span>Oh and Java / JodaTime, which I have just patched for the Norfolk Island and Fiji changes not yet released by IANA on a couple of hundred JVMs.  Neither Java nor JodaTime would need to embed their timezone info any more (when updated to just use DNS) which would save me from that chore.   <br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span>Wishful thinking ?   Must have been suggested before.<br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span>David Wade<br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span><b>Traversing Googles cloud netblocks (thanks Google).</b><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span>waded@darkhorse:~$ dig +short TXT _<a href="http://cloud-netblocks.googleusercontent.com">cloud-netblocks.googleusercontent.com</a><br>"v=spf1 include:_<a href="http://cloud-netblocks1.googleusercontent.com">cloud-netblocks1.googleusercontent.com</a> include:_<a href="http://cloud-netblocks2.googleusercontent.com">cloud-netblocks2.googleusercontent.com</a> include:_<a href="http://cloud-netblocks3.googleusercontent.com">cloud-netblocks3.googleusercontent.com</a> include:_<a href="http://cloud-netblocks4.googleusercontent.com">cloud-netblocks4.googleusercontent.com</a> include:_<a href="http://cloud-netblocks5.googleusercontent.com">cloud-netblocks5.googleusercontent.com</a> ?all"<br>waded@darkhorse:~$ dig +short TXT _<a href="http://cloud-netblocks1.googleusercontent.com">cloud-netblocks1.googleusercontent.com</a><br>"v=spf1 include:_<a href="http://cloud-netblocks6.googleusercontent.com">cloud-netblocks6.googleusercontent.com</a> include:_<a href="http://cloud-netblocks7.googleusercontent.com">cloud-netblocks7.googleusercontent.com</a> ip4:<a href="http://8.34.208.0/20">8.34.208.0/20</a> ip4:<a href="http://8.35.192.0/21">8.35.192.0/21</a> ip4:<a href="http://8.35.200.0/23">8.35.200.0/23</a> ip4:<a href="http://108.59.80.0/20">108.59.80.0/20</a> ip4:<a href="http://108.170.192.0/20">108.170.192.0/20</a> ip4:<a href="http://108.170.208.0/21">108.170.208.0/21</a> ?all"<br>waded@darkhorse:~$ dig +short TXT _<a href="http://cloud-netblocks1.googleusercontent.com">cloud-netblocks1.googleusercontent.com</a><br>"v=spf1 include:_<a href="http://cloud-netblocks6.googleusercontent.com">cloud-netblocks6.googleusercontent.com</a> include:_<a href="http://cloud-netblocks7.googleusercontent.com">cloud-netblocks7.googleusercontent.com</a> ip4:<a href="http://8.34.208.0/20">8.34.208.0/20</a> ip4:<a href="http://8.35.192.0/21">8.35.192.0/21</a> ip4:<a href="http://8.35.200.0/23">8.35.200.0/23</a> ip4:<a href="http://108.59.80.0/20">108.59.80.0/20</a> ip4:<a href="http://108.170.192.0/20">108.170.192.0/20</a> ip4:<a href="http://108.170.208.0/21">108.170.208.0/21</a> ?all"<br>waded@darkhorse:~$ dig +short TXT _<a href="http://cloud-netblocks2.googleusercontent.com">cloud-netblocks2.googleusercontent.com</a><br>"v=spf1 ip4:<a href="http://162.216.148.0/22">162.216.148.0/22</a> ip4:<a href="http://162.222.176.0/21">162.222.176.0/21</a> ip4:<a href="http://173.255.112.0/20">173.255.112.0/20</a> ip4:<a href="http://192.158.28.0/22">192.158.28.0/22</a> ip4:<a href="http://199.192.112.0/22">199.192.112.0/22</a> ip4:<a href="http://199.223.232.0/22">199.223.232.0/22</a> ip4:<a href="http://199.223.236.0/23">199.223.236.0/23</a> ip4:<a href="http://23.236.48.0/20">23.236.48.0/20</a> ip4:<a href="http://23.251.128.0/19">23.251.128.0/19</a> ip4:<a href="http://35.204.0.0/14">35.204.0.0/14</a> ip4:<a href="http://35.208.0.0/13">35.208.0.0/13</a> ?all"<br>waded@darkhorse:~$ dig +short TXT _<a href="http://cloud-netblocks3.googleusercontent.com">cloud-netblocks3.googleusercontent.com</a><br>"v=spf1 ip4:<a href="http://107.167.160.0/19">107.167.160.0/19</a> ip4:<a href="http://107.178.192.0/18">107.178.192.0/18</a> ip4:<a href="http://146.148.2.0/23">146.148.2.0/23</a> ip4:<a href="http://146.148.4.0/22">146.148.4.0/22</a> ip4:<a href="http://146.148.8.0/21">146.148.8.0/21</a> ip4:<a href="http://146.148.16.0/20">146.148.16.0/20</a> ip4:<a href="http://146.148.32.0/19">146.148.32.0/19</a> ip4:<a href="http://146.148.64.0/18">146.148.64.0/18</a> ip4:<a href="http://34.104.0.0/22">34.104.0.0/22</a> ?all"<br>waded@darkhorse:~$ dig +short TXT _<a href="http://cloud-netblocks4.googleusercontent.com">cloud-netblocks4.googleusercontent.com</a><br>"v=spf1 ip4:<a href="http://130.211.8.0/21">130.211.8.0/21</a> ip4:<a href="http://130.211.16.0/20">130.211.16.0/20</a> ip4:<a href="http://130.211.32.0/19">130.211.32.0/19</a> ip4:<a href="http://130.211.64.0/18">130.211.64.0/18</a> ip4:<a href="http://130.211.128.0/17">130.211.128.0/17</a> ip4:<a href="http://104.154.0.0/15">104.154.0.0/15</a> ip4:<a href="http://104.196.0.0/14">104.196.0.0/14</a> ip4:<a href="http://208.68.108.0/23">208.68.108.0/23</a> ip4:<a href="http://35.184.0.0/14">35.184.0.0/14</a> ip4:<a href="http://35.188.0.0/15">35.188.0.0/15</a> ip4:<a href="http://35.216.0.0/15">35.216.0.0/15</a> ?all"<br>waded@darkhorse:~$ dig +short TXT _<a href="http://cloud-netblocks5.googleusercontent.com">cloud-netblocks5.googleusercontent.com</a><br>"v=spf1 ip4:<a href="http://35.190.0.0/17">35.190.0.0/17</a> ip4:<a href="http://35.190.128.0/18">35.190.128.0/18</a> ip4:<a href="http://35.190.192.0/19">35.190.192.0/19</a> ip4:<a href="http://35.235.224.0/20">35.235.224.0/20</a> ip4:<a href="http://35.192.0.0/14">35.192.0.0/14</a> ip4:<a href="http://35.196.0.0/15">35.196.0.0/15</a> ip4:<a href="http://35.198.0.0/16">35.198.0.0/16</a> ip4:<a href="http://35.199.0.0/17">35.199.0.0/17</a> ip4:<a href="http://35.199.128.0/18">35.199.128.0/18</a> ip4:<a href="http://35.200.0.0/14">35.200.0.0/14</a> ip4:<a href="http://35.235.216.0/21">35.235.216.0/21</a> ip6:2600:1900::/35 ?all"<br>waded@darkhorse:~$ dig +short TXT _<a href="http://cloud-netblocks6.googleusercontent.com">cloud-netblocks6.googleusercontent.com</a><br>"v=spf1 ip4:<a href="http://35.190.224.0/20">35.190.224.0/20</a> ip4:<a href="http://35.232.0.0/15">35.232.0.0/15</a> ip4:<a href="http://35.234.0.0/16">35.234.0.0/16</a> ip4:<a href="http://35.235.0.0/17">35.235.0.0/17</a> ip4:<a href="http://35.235.192.0/20">35.235.192.0/20</a> ip4:<a href="http://35.236.0.0/14">35.236.0.0/14</a> ip4:<a href="http://35.240.0.0/15">35.240.0.0/15</a> ip4:<a href="http://35.203.232.0/21">35.203.232.0/21</a> ip4:<a href="http://130.211.4.0/22">130.211.4.0/22</a> ip4:<a href="http://35.220.0.0/14">35.220.0.0/14</a> ip4:<a href="http://35.242.0.0/15">35.242.0.0/15</a> ip4:<a href="http://35.244.0.0/14">35.244.0.0/14</a> ?all"<br>waded@darkhorse:~$ dig +short TXT _<a href="http://cloud-netblocks7.googleusercontent.com">cloud-netblocks7.googleusercontent.com</a><br>"v=spf1 ip4:<a href="http://34.64.0.0/11">34.64.0.0/11</a> ip4:<a href="http://34.96.0.0/14">34.96.0.0/14</a> ip4:<a href="http://34.100.0.0/16">34.100.0.0/16</a> ip4:<a href="http://34.102.0.0/15">34.102.0.0/15</a> ip4:<a href="http://108.170.216.0/22">108.170.216.0/22</a> ip4:<a href="http://108.170.220.0/23">108.170.220.0/23</a> ip4:<a href="http://108.170.222.0/24">108.170.222.0/24</a> ip4:<a href="http://35.224.0.0/13">35.224.0.0/13</a> ip4:<a href="http://35.190.240.0/22">35.190.240.0/22</a> ip4:<a href="http://35.190.242.0/23">35.190.242.0/23</a> ip4:<a href="http://35.206.0.0/15">35.206.0.0/15</a> ?all"</span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span><br></span></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 19 Jul 2019 at 08:53, Steve Crocker <<a href="mailto:steve@shinkuro.com">steve@shinkuro.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">:)<br>
<br>
Sent from my iPhone<br>
<br>
> On Jul 18, 2019, at 4:51 PM, Paul Eggert <<a href="mailto:eggert@cs.ucla.edu" target="_blank">eggert@cs.ucla.edu</a>> wrote:<br>
> <br>
> Steve Crocker wrote:<br>
>> It doesn’t seem to me the legal verbiage would be part of the regular download, so that would reduce the payload a bit.<br>
> <br>
> Sorry, I shouldn't have distracted the performance discussion by mentioning that verbiage. It's so small that eliminating it isn't worth the effort unless one is trying to win a compression contest. Here's a complete copy of the verbiage:<br>
> <br>
> # This zic input file is in the public domain.<br>
</blockquote></div>