Is there any concern for the IETF in a policy that says “If you start
using an arbitrary name that isn’t currently in the root zone, you can
just get the IETF to protect it for you”?
It's a reasonable question, but I think a reasonable answer in some
circimstances is "yes".
Let's say we found that there's some online thing we never heard of
before, but it turns out that 100,000,000 people in India and China use
it, it uses private names in .SECRET, and people looking at DNS logs
confirm that they're seeing leakage of .SECRET names. Beyond rolling our
eyes and saying we wish they hadn't done that, what else should we do?
Why shouldn't we reserve it? The number of possible TLDs is effectively
unlimited, striking one more off the list that might be sold in the future
doesn't matter. This is engineering, not ideally what we might have done
with a blank slate, but the best we can do under the circumstances.
Furthermore, given that ICANN has already said they won’t delegate these
names in particular, how is it helpful for the IETF to also add them to
the Special Use Names registry?
I believe that they're currently blocked in the current new gTLD round,
but not necessarily beyond that. I don't see any evidence that the six
applicants who paid $185,000 to apply for .CORP or the ten remaining
applicants for .HOME or the five remaining applicants for .MAIL have given
up. They certainly haven't gotten their money back.
Regards,
John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
