HOME About At Large FAQ Find Members Only News
 
Related Links
  Nominees
  Schedule
  Rules
  Membership Statistics
  ICANN Home Page
 
AT LARGE Q&A TOPICS
 
Topic: Default rootzone
Date: 2000-09-20 17:07:27
Author: Leah Gallegos <jandl@jandl.com>

Question: Would you support inclusion of other roots' TLD's in the ICANN default rootzone as are ccTLD's so that all non-colliding TLD's could be easily accessed? Do you support cooperating root systems?

Nominee Replies
Karl Auerbach - posted on 2000-09-24 22:07:41

I have not used the Department of Commerce DNS root for several years. And I have been using an extended suite of TLDs for that time.

I believe that ICANN/Dept o' Commerce are but one root system operator among root system operators. ICANN/DoC are simply one among many and are entitled to no intrinsic superior position.

As for cooperating root systems - it's a nice idea, but since every kid with a Linux or Bsd box can set up a root without asking anybody's permission, its more a dream than a reality that one can rely upon.

Consequently, I prefer to recognize right up front that multiple root systems can exist with not only different contents but even identically named TLDs that are different.

I leave it to the users (and their agents, i.e their ISP's or corporate DNS administrators) to use a root system that gives the kind of results that they expect.

There are many people who today publish phone books - those that don't have accurate numbers end up in the trash heap pretty quickly. The same kind of user choice will determine which root systems are use and which are rjected.

Emerson Tiller, J.D., Ph.D. - posted on 2000-09-20 19:47:25
To the extent that competition is enhanced, and stability ensured, my answer is yes to both.

Lawrence Lessig - posted on 2000-09-20 17:27:27
In principle, yes to both. I believe ICANN's role should be to facilitate a reduction in the architected monopoly power of the system. Build it so monopolies can't grow -- that was the net's original insight.


© 2000 ICANN. All rights reserved.

Privacy Policy     Terms of Service     Cookies Policy