> On 13 Mar 2017, at 07:05, Stéphane Bortzmeyer <[email protected]> wrote: > > This is relevant to the Special-Use registry discussion. (Which is mentioned, > in a negative way.)
Meh. I fail to understand how the problems that the applicants for these strings made for themselves could be in scope for this WG or the IETF more generally. If these applicants want these strings to go into the root, they first need to convince ICANN that this won't cause significant problems and/or come up with viable risk mitigation strategies. Once they do that, ICANN may well turn to the IETF or other groups of experts -- SSAC? -- for advice on what to do. How those damage limitation approaches get developed is not something that should concern this WG. Personally, I think putting .home in the root is doomed forever. This string *still* accounts for 3-4% of the queries in the root server DITL datasets: higher than the queries for almost every existing TLD and the root. (Only .com and .net had higher numbers than .home in the 2016 root server pcaps.) Last time I looked, traffic for .home in the DITL data has increased every year since the 2013 name collision study, both in absolute and relative terms. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
