I'm pretty sure that I didn't want it to come to this, and I'm not entirely convinced that anyone should be doing it. But personal reservations aside, its happening. And I intend to see that its done as well as possible.
Then why did you and David ignore my plea to cooperate with the extant TLD managers, with whom the new.net TLDs now collide? You could have launched the new.net TLDs with a bunch of in-place registrants already hosting sites under the TLDs you have collided with. You could have built a shared registration system that could have encompassed all the non-ICANN TLDs, and helped create something that would have really given serious challenge to ICANN. But instead, you chose to ignore me, and the others. Now we have a mess on our hands, for example, who is really the registrant of warren.family, the one who has held the Pacificroot warren.family for 4 years, or the one who just got warren.family from new.net on Monday? What will new.net say to their customer when one of Pacficroot's registrants sends a C&D to a new.net registrant who has collided with their SLD? Is new.net's indemnity clause sufficient to protect you from liability to your customers, after you sold them something which subsequently got the new.net customer into a lawsuit? Maybe you want to run that one by David Hernand, see what he thinks. What a can of worms you have opened. I wish you had listened to me. And no, I'm not interested in a job at new.net anymore, in case you were wondering.
Aaron Hopkins Systems Engineer, idealab! Acting VP of Engineering, new.net
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org
iQCVAwUBOqXvPEfJWHAEvsjBAQFgAQQAmtREC7ZCYLVrA2biCzriM1z07Jrk7oAc fG9znSGC7gtHrcsad2N7SR+wFsWP2v8I546zYMvpcfHDClRFyS11tohi85W/CfEQ 9kaWfe01Jzqri37v+jHfAyX7k7OrSz+9wRJoh72rTItMWgaLECA1wync//EJ7EYc o+zS2KTe2P4= =kJXu -----END PGP SIGNATURE-----