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)


     
    New gTLDs The Registry double standard
    posted by tbyfield on Sunday May 25 2008, @09:16PM

    Anonymous writes: "ICANN is maintaining two standards, one for its customers and one for itself. First off, we will clarify the two types of TLDS that exist, those with specific use constraints and those that are generic. In the first category, we find TLDs like; .GOV, .EDU, .SB, .BR, .ARPA, .INT and others. These TLDS have specific rules; e.g. only treaty organizations, only infrastructure, only institutions approved by GAO, EDUCAUSE, etc. The second category of TLDS are the generics, such as .COM, .ORG, and others, where the rule is essentially, you pay your money and you get your domain.

    In this second category, there was serious concern about market capture and dominant position where the registry had direct business relationships with the registrants. The USG forced ICANN to develop a method to decouple the monopoly position of the registry by creating the construct of a registrar to act as the intermediary between the registrant and the registry. This was hailed as a solution to fostering growth and competition in the domain marketplace. Indeed ICANN insists that this “thick” registry model be adopted for generic TLDS and includes such stipulations in the contracts the registry operator must sign before being approved to run the delegation.

    So in what category does one place the root zone?




    Is it a zone that has specific rules regarding entries, such as .GOV, or .ARPA, or is it a generic? Historically, the root zone was considered in the first camp, where specific constraints were placed on entry into the zone. Indeed, for the first decade of ICANN’s existence, the Board grappled with how to evaluate new TLD requests. Recent events, mostly from the gTLD constituents, have argued that ICANN should relax their TLD evaluation process and fundamentally change the nature of the root zone, from one that had constraints on entry to a generic model. The gNSO estimates that once the rules are relaxed, that thousands of TLD’s will be injected into the root zone – if you pay your money, you can have a TLD.

    To date, ICANN argues that the root is “special” and therefore even when it changes into a generic delegation, ICANN will maintain direct relationships with the root zone registrants. This is at odds with the rules under which all other generic delegations are maintained. Once standard for ICANN, one for everyone else.

    Monetizing the Stewardship

    ICANN has a contractual obligation to encourage competition, while maintaining security and stability. The gNSO proposal changes the root zone into a generic delegation and thus changes the stewardship role ICANN played. To fully support competition, it seems reasonable to insist on the adoption of the registry/registrar model for the root in its new status as a generic. If that premise is adopted, ICANN should have to choose which role it wishes to play, either the root registry –OR- one of many root registrars. To do otherwise places the whole registry/registrar model in question. If competition is good for other generic delegations, why is it not good here?

    In the absence of competition, ICANN can and does dictate pricing. If the gNSO numbers are to be believed and the TLD non-refundable application fees apply, ICANN could see an increase in revenue in the tens of millions per year. One might argue that ICANN is abandoning rigor and discipline over root zone management as a means to ensure stability in favor of a “get rich quick” scheme. Monetization of the root zone should NOT accrue only to the benefit of ICANN. The principles of market and competition should apply here as well."

     
      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  
    · ICANN
    · More New gTLDs stories
    · Also by tbyfield
     
    This discussion has been archived. No new comments can be posted.
    The Registry double standard | Log in/Create an Account | Top | 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.


    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