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.
    Lynn's sTLD Limit (3), DNS Taxonomy Bashed in Amsterdam | Log in/Create an Account | Top | 11 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: Lynn's sTLD Limit (3), DNS Taxonomy Bashed in
    by Anonymous on Monday December 16 2002, @03:15PM (#10576)
    Given that ICANN's staff has spent about $2,500,000 to $3,000,000 deploying all of seven new TLDs over two years, they ought to know how to do it by now.

    Virtually all of the reports and other contractual baggage that ICANN has larded onto those seven TLDs has proved to be worthless featherbedding not worth carrying forward. And the one item that is important, data escrow, seems to have been lost in the ICANN morass.

    I would suggest a target rate of one new TLD per week - with time off for holidays - 50 new TLDs in 2003!

    And those ought to be without restriction so that we can see what kind of ideas will crop out of fertile DNS soil that has not been salted by the ICANN mentality of asphyxiating regulation.
    [ Reply to This | Parent ]
    Re: Lynn's sTLD Limit (3), DNS Taxonomy Bashed in
    by fnord (groy2kNO@SPAMyahoo.com) on Tuesday December 17 2002, @09:53AM (#10585)
    User #2810 Info
    The TLD space was originally designed to be taxonomized, either by content (.com, .edu, .int) or geopolitical entity (.us, .ie, .cc). Veri$ign broke the former, and .tv et al broke the latter, in the name of profit. One cannot put Humpty Dumpty together again, but if we're going to have more new gTLD's, and I support the 50 per year idea, there has to be some sanity employed or the vast majority of end-users (who weren't there to speak or be represented) will shun most all of them due to confusion. I know a number of reasonably tech savvy people who are still surprised to learn that there is now an .info TLD.

    If there is no taxonomy one might as well hand out random strings (eg: .0d7z) for all the good it will do. We still do have a taxonomy of sorts, .name or .museum or .biz at least make some sort of semi-intuitive sense, as will .health or .travel. The issue to me is whether this should be left to ICANN or some committee appointed by them, or whether it should be left to the magical forces of the free market. Much as I appreciate the benefits of the latter, what if there is an applicant for .book and an applicant for .books and an applicant for .lit? That decision will still come down to an ICANN call and they're unlikely to allow competitors in a similar namespace due to a fear that both will fail, so there is no true free market anyway. In addition, at what level does one differentiate? Should it be at the level of .food or at the level of .chips or at the level of .fritos? If that is left entirely to the free market to sort out then we will have entries at all levels, leaving a further counter-intuitive mess for years.

    I'd personally like to see someone like the ITU handling this as they have a wealth of experience and resources in similar areas. I fail to see what is so hard to understand about using the telephone book model as a reasonable starting point for a taxonomy. I've been told over the years by many who pay attention to such things that the DNS is not intended as a directory system, I always ask why not? and have never received an answer, even a poor one. Paul Mockapetris has said he intended it as a directory system and that's good enough for me. Some wisdom, even some sanity, is sorely needed.

    With regards to Ken Fockler's rumored involvement, I really think ICANN needs something in its bylaws saying that former BoD members (to say nothing of sitting ones for that matter, eg: Rob Blokzijl) cannot become ICANN lobbyists for a set period of time as is common with some elected/appointed/employed government positions, as well as in some private enterprises with non-disclosure/non-competition agreements. I would like to see a similar proviso for ICANN staff. Of course I rarely see what I'd like to see from ICANN, but perhaps some successor body could... -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