![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
They are still a problem whether you think they should exist
or not. The problem is that they are added unilaterally
and people using them expect everyone else to be able to
resolve them as well. The method of adding them was wrong
as it does not scale. If every language added the equivalent
you would have hundreds of sets of nameservers that you
roblems:
1) They are to quite some extent language-specific,
which is significantly different from .com and .net
(much more like .company and .network). .com and .net,
although having language-related origins, are codes
used across languages.
2) It may be the first time that a country is creating/takeing over a gTLD. While I think that ultimately (and hopefully sooner rather than later), we need equivalents of gTLDs in other scripts, and while the question of "who gets to run a gTLD" is probably the most difficult for ICANN to decide, I don't think that it would be such a good idea to allocate gTLDs to countries.
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.