The whole alternate-root ${STATE}horse

Valdis.Kletnieks at vt.edu Valdis.Kletnieks at vt.edu
Sat Jul 9 20:51:24 UTC 2005


On Sat, 09 Jul 2005 14:52:23 CDT, "John Palmer (NANOG Acct)" said:

> No public RSN that cares about its credibility will create collisions. 

Ergo, ICANN doesn't care about its credibility, because it created a .BIZ.

Except that at the time, the people who had the .BIZ that got collided with
had no reason (a MoU, contract, or even a deal over beer) to expect that
ICANN wouldn't do such a thing.  If you're asserting that the "big players"
need be careful of colliding with a TLD in some tiny root you've never heard of,
you're opening a *really* nice extortion business model - just start up your own
root, cybersquat the first few million likely TLDs, and yell foul and demand
a license fee or other damages each time somebody else tries to create that TLD.

Either that, or you need to demonstrate that all the roots are cooperating in
some clearinghouse a la the way .COM is run - such an arrangement would in fact
be a reasonable way to follow RFC2826, as one clearinghouse would maintain the
root.  Of course, such a clearinghouse isn't actually in evidence, nor is there
any obvious reason to believe that one will be creatable...

And keep in mind as well that some things aren't done maliciously or even
intentionally - things like AS7007 or the time a third of .COM dissapeared
because of a disk-full error during the build *just* *happen*.  So what happens
if the following goes down:

Company A in Beijing decides it wants tld .qn--e4r34ew, and goes to Roots-R-Us
to register it.  Meanwhile, company B in Hong Kong goes to TLDs-for-cheap and
registers the same domain.  Both roots push their respective updates at 8AM
Monday, and hilarity ensues.  Discuss the conflict resolution process, citing
the aggreements that will be followed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20050709/d98ac450/attachment.sig>


More information about the NANOG mailing list