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)


     
    Country-Code Top Level Domains (ccTLDs) Whither the ccTLDs?
    posted by jon on Sunday September 15 2002, @05:10PM

    One of the three most important changes the Blueprint ended up making to the status quo was its offering the ccTLDs a Supporting Organization of their very own. (The other two were the replacement of at-large representation with NomCom directors, and the formal jettisoning of the idea that ICANN policymaking is supposed to be consensus-based and meaningfully bottom-up.) But the Blueprint's proposal for a ccNSO fell far short of the ccTLDs' demands: that ICANN should be able to impose no policy on ccTLDs without their consensus support (meaning a 2/3 vote of the ccTLDs voting in each region); that it must be part of the ccSO function to determine which issues are "global" and therefore within ICANN jurisdiction in the first place; and that the ccTLDs must be able to name all of the members of their own SO Council, without carpetbaggers inserted by the NomCom. The ccTLD Adcom had urged that ICANN enter into a dialog to bridge the gap between the two positions.

    We've now seen ICANN's response.



    ICANN has chosen its own committee to flesh out details for ccNSO implementation, requesting the participation of just two members of the ccTLD Adcom. Others whom ICANN sees as uncompliant, such as Peter Dengate-Thrush and Nigel Roberts, are not invited. And the invitation letter is insistent that the committee must deliberate "within the framework of the Blueprint": nobody will be allowed "to re-argue decisions already made by the ICANN Board as embodied in the Blueprint." The ccTLD Adcom's response: "You will understand the temptation for the Adcom to regard this group as a top down device, cynically designed to provide evidence of support for the Blueprint . . . ."

    ICANN is confident that it can get the MoU extended with or without the support of the ccTLDs. But if it wants to get the ccTLDs to sign contracts, it's going to have to find its way to adopting positions they'll actually support. So far, the cc's seem to be hanging tough. (Note also, in this regard, Elisabeth Porteneuve's proposed Names Council resolution declaring that ICANN's failure to properly update ccTLD name servers is endangering Internet stability.)

     
      ICANNWatch Login  
    Nickname:

    Password:

    [ Don't have an account yet? Please create one. It's not required, but as a registered user you can customize the site, post comments with your name, and accumulate reputation points ("karma") that will make your comments more visible. ]

     
      Related Links  
  • chosen its own committee
  • response
  • proposed Names Council resolution
  • demands
  •  
    This discussion has been archived. No new comments can be posted.
    Whither the ccTLDs? | Log in/Create an Account | Top | 1 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: Whither the ccTLDs?
    by fnord (groy2kNO@SPAMyahoo.com) on Monday September 16 2002, @02:16PM (#9266)
    User #2810 Info
    Regarding the last paragraph above, ICANN CEO M. Stuart Lynn has now responded on the GA list to a question regarding Elisabeth Porteneuve's concerns as put forward by Danny Younger. Lynn denies that there is any cause for concern, then goes on to say
    Three of the ccTLD requests for migration have not yet been completed because the ccTLD operators have (despite repeated requests) failed to cooperate in allowing the IANA to perform technical checks as provided by longstanding IANA policy. See the FAQs at http://www.iana.org/faqs/tld-zone-access-faq.htm for a description that we recently posted summarizing for ccTLD managers the policy, its longstanding basis (documented back to RFC 1591 in March 1994), and the means by which those seeking to change the policy should proceed.
    That supposed longstanding policy being used as a threat by ICANN has been covered before by ICANNWatch, first here, second here. -g
    [ 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