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.
    Auerbach Weighs in for gTLD Lotteries | Log in/Create an Account | Top | 49 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:A question re less market, more community
    by KarlAuerbach on Wednesday April 09 2003, @09:43AM (#11473)
    User #3243 Info | http://www.cavebear.com/
    I have always disagreed with the ICANN's usually implicit policy that it will not allow any TLD that could ever possibly have a chance of ever failing. (Of course, it does seem that some of the super-seven that it picked two+ years ago may go under, perhaps as the result of boredom if not from financial failure.)

    Why shouldn't a TLD be allowed to fail? Who is harmed? Stale URL's and stale e-mail addresses happen all the time even with ICANN's propped up system. (By the way, take a peek at my presentation on the real meaning of "stability" at http://www.cavebear.com/rw/nrc_presentation_july_1 1_2001.ppt [cavebear.com])

    The customers of TLDs ought to be able to know beforehand enough information to decide whether they want to build their brand on the foundation provided by a particular TLD. (I am excepting from this those people who were compelled to use the legacy .com, .net, .org TLDs because those were the only ones available.)

    If there is reason for a rock-solid TLD, that stability ought to come at a cost to its customers. If there is a need for a TLD that offers fewer guarantees - perhaps for transient events like movie web sites - then who cares if it is financially and lasts only for a while?

    Why not treat TLDs like securities? Why not make the information about factors relevant to long term stability of a TLD available to potential customers - a kind of TLD prospectus - and let the customers decide whether they want to build on that TLD?

    Another aspect of this is that ICANN or, better yet, an independent body, could periodically audit TLD operations and issue an opinion letter indicating whether that TLD engages in adequate business asset protection procedures (such procedures would enable the hulk of a failed TLD to be picked up by a successor.) Having that kind of mechanism gives the customers the protection of knowing that at least their registration data won't be lost and that if all else fails they can pick up the relic and resume service.
    [ 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