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.
    Survey of Usage of the .BIZ TLD | Log in/Create an Account | Top | 20 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: Survey of Usage of the .BIZ TLD
    by fnord (groy2kNO@SPAMyahoo.com) on Monday June 24 2002, @06:25PM (#7433)
    User #2810 Info
    My first point was followed by a smiley :) It wasn't to be taken entirely seriously (though if we have substantially the same ICANN deciding which entities are ready to run a registry, we shouldn't be surprised if we get substantially the same result, ICANN not only doesn't learn from its mistakes, it won't even admit to them). Who gets .org, and how and why, will be the next test in this regard, and probably the last for some years, barring deciding which registry takes over another failing registry (which I think is a distinct possibility).

    As for my second point, I suspect it will never be proved or disproved as we are unlikely to see such a scenario as more open gTLDs under ICANN. If we see any new TLDs, they will need more than a sunrise, or ineffective and largely unpoliced restrictions, as Ben has documented with .biz and .name (though see here regarding NeuLevel apparently cancelling some 7500 registrations). The only nearly foolproof way to ensure that a namespace isn't gamed and filled with drek is to make it restricted and manually review each potential registration. This gets us very close to restricted domains like .museum and .aero, who together have less than 10,000 registrations to date (they'd have to average $10 net profit per name just to return their investment in ICANN's application fee).

    Probably few speculators or defensive registrations live there, but that means not much income either, for the registry, or ICANN. Even assuming such TLDs don't fail due to funding problems, they don't make for much of a revenue source for ICANN so creating a few more restricted TLDs probably isn't worth the bother to them.

    So I predict if ICANN or a similar successor is in place we'll either see no new gTLDs for quite a few years, or a situation where a registry is given a number of restricted ones, probably farming out the policing to somewhat relevant entities. In some cases those entities might even be willing to operate at a loss (to themselves, not the registry) simply so that their members have a defined and controlled namespace through which other benefits would accrue (this is the model I suggested before the first rollout). In the latter case, my first point still halfways applies. If there is a way to mismanage it, ICANN probably will. -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