> On 21 Mar 2017, at 17:30, Suzanne Woolf <suzworldw...@gmail.com> wrote: > > Jim, > > In the interests of preserving a distinction here that I believe is > important: > >> On Mar 21, 2017, at 10:01 AM, Jim Reid <j...@rfc1035.com> wrote: >> >> >>> On 21 Mar 2017, at 13:54, Paul Wouters <p...@nohats.ca> wrote: >>> >>> Suggesting we postpone .homenet while figuring out a new IETF/ICANN >>> process, something that can take years, would basically doom this rename >>> and install .home as the defacto standard. >> >> At the risk of pouring petrol on the fire, .home *is* the defacto standard. >> Queries for this TLD account for ~4% of the 2016 DITL root server traffic. >> That's more than every delegated TLD except .com and .net. And the traffic >> for .home has been increasing in both absolute and relative terms in recent >> years. 3-4 years ago, it was ~3% of the DITL data set. > > “Lots of queries for .home” doesn’t imply that it’s a “defacto standard” for > anything in particular. > > Is there any evidence connecting the use of the string “.home” in queries to > the DNS with any particular protocol, type of equipment, network > configuration, or software?
In the UK, I believe the largest residential ISP has used the .home suffix on millions of its CPEs for several years. How much of that leaks is another question. Tim _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
