Five years is not enough. Think in terms of 20 to 50 years.
Oh, of course. I was thinking of five years as the review cycle for
names that people might want to reconsider.
Mark wrote:
If .BELKIN is reserved then it is not available to *anyone* including
Belkin. The simplist fix for .BELKIN is for the vendor to request
registration of the name through ICANN. It becomes a expensive
mea-culpa. The IETF should leave this to ICANN processes.
It occurs to me that a lot of this would be less painful if the ICANN new
TLD process were clearer about dealing with collisions with informal use.
AGB section 2.2.1.3 is about the DNS stability review, but it says "There
is a very low probability that extended analysis will be necessary for a
string that fully complies with the string requirements in subsection
2.2.1.3.2 of this module." where those requirements basically say it has
to be a valid ASCII or IDN DNS label.
For .BELKIN, the answer would depend on the details of the application,
which is unlike any other new TLD string review I can think of.
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
