ICANNWatch
 
  Inside ICANNWatch  
Submit Story
Home
Lost Password
Preferences
Site Messages
Top 10 Lists
Latest Comments
Search by topic

Our Mission
ICANN for Beginners
About Us
How To Use This Site
ICANNWatch FAQ
Slash Tech Info
Link to Us
Write to Us

  Useful ICANN sites  
  • ICANN itself
  • Bret Fausett's ICANN Blog
  • Internet Governance Project
  • UN Working Group on Internet Governance
  • Karl Auerbach web site
  • Müller-Maguhn home
  • UDRPinfo.com;
  • UDRPlaw.net;
  • CircleID;
  • LatinoamerICANN Project
  • ICB Tollfree News

  •   At Large Membership and Civil Society Participation in ICANN  
  • icannatlarge.com;
  • Noncommercial Users Constituency of ICANN
  • NAIS Project
  • ICANN At Large Study Committee Final Report
  • ICANN (non)Members page
  • ICANN Membership Election site

  • ICANN-Related Reading
    Browse ICANNWatch by Subject

    Ted Byfied
    - ICANN: Defending Our Precious Bodily Fluids
    - Ushering in Banality
    - ICANN! No U CANN't!
    - roving_reporter
    - DNS: A Short History and a Short Future

    David Farber
    - Overcoming ICANN (PFIR statement)

    A. Michael Froomkin
    - When We Say US™, We Mean It!
    - ICANN 2.0: Meet The New Boss
    - Habermas@ discourse.net: Toward a Critical Theory of Cyberspace
    - ICANN and Anti-Trust (with Mark Lemley)
    - Wrong Turn in Cyberspace: Using ICANN to Route Around the APA & the Constitution (html)
    - Form and Substance in Cyberspace
    - ICANN's "Uniform Dispute Resolution Policy"-- Causes and (Partial) Cures

    Milton Mueller
    - Ruling the Root
    - Success by Default: A New Profile of Domain Name Trademark Disputes under ICANN's UDRP
    - Dancing the Quango: ICANN as International Regulatory Regime
    - Goverments and Country Names: ICANN's Transformation into an Intergovernmental Regime
    - Competing DNS Roots: Creative Destruction or Just Plain Destruction?
    - Rough Justice: A Statistical Assessment of the UDRP
    - ICANN and Internet Governance

    David Post
    - Governing Cyberspace, or Where is James Madison When We Need Him?
    - The 'Unsettled Paradox': The Internet, the State, and the Consent of the Governed

    Jonathan Weinberg
    - Sitefinder and Internet Governance
    - ICANN, Internet Stability, and New Top Level Domains
    - Geeks and Greeks
    - ICANN and the Problem of Legitimacy

    Highlights of the ICANNWatch Archive
    (June 1999 - March 2001)


     
    This discussion has been archived. No new comments can be posted.
    RIPE Ready to Anycast Too | Log in/Create an Account | Top | 5 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Threshold:
    Check box to change your default comment view
    The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
    Re:Root server operator independence
    by KarlAuerbach on Tuesday February 18 2003, @11:00AM (#11186)
    User #3243 Info | http://www.cavebear.com/
    I'm not sure that we are saying different things.

    I agree, it is prudent to test that root servers (and the procedures used to operate them) will work should there is reason to get a copy of a root zone from a different place than normal. That was my interpretation of what Jon did and I thought then, and I think now, that such a test was warranted and proper.

    But the question that I am asking is who has the ultimate authority to decide whether to hold such a test or, more importantly, to decide whether a situation has evolved to the degree that the tested procedure is to be put into real practice?

    If really bad things were to happen and root server operators (individually or as a group) felt that a change should be made, and be made immediately, would they feel that they had to ask for outside approval or would they feel safe in acting on their own? Might they refrain from doing what needs to be done because they feel a chill of uncertainty about whether they have the final authority?

    Do ICANN and the Dept of Commerce believe that they are "in charge" of the root servers in the same way that a person may think that he/she is "in charge" of a herd of cats just because they fortuitiously happen to be walking in the same direction?

    If so, then two things need to be done:

    First, the non-authoritative position of ICANN/Dept of Commerce should be clearly enunciated by all concerned.

    Second, the question of the precise scope of the root server operator's role needs to be raised. This question necessarily involves asking about means to ensure that the root server operators remain within that scope. This question also necessarily involves asking about the performance of those jobs that are placed outside of that scope - such as perhaps the decision as to who operates a ccTLD or even the broader question of who gets to decide what is in the root zone file that the root operators might commit themselves to use no matter how dire the circumstances.
    [ Reply to This | Parent ]


    Search ICANNWatch.org:


    Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
    You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com