On Tue, 21 Mar 2017, Jim Reid 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.
Can we tell from the queries or a timeline of query quantity if this
is generic .home pollution that predates the homenet protocol suite,
or actually the result the homenet protocol suite being deployed?
Although I fear sticking to .home would be a legal issue, even if it
would be the technical best solution.
Paul
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
