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.
    Salon interviews John Gilmore | Log in/Create an Account | Top | 36 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.
    Restricted TLDs are fine, but Gilmore talks of unr
    by edelman@law.harvard. on Tuesday July 02 2002, @01:28PM (#7575)
    User #884 Info | http://cyber.law.harvard.edu/edelman.html
    Agreed that .AERO and .MUSEUM represent an interesting concept that certainly isn't likely to cause much defensive registration and that's also likely to provide a certain value & quality precisely along the lines you describe. 100 more such TLDs make a certain amount of sense, and I wouldn't be surprised to find a growing consensus around such an approach.

    But that's just not what Gilmore was talking about & advocating in his interview. He says: "thousands of top-level domains, in which anyone could register a name" (emphasis added). And he subsequently contemplates registrants using one TLD rather than another if a desired domain isn't available in the first TLD attempted. So, as I read the interview, I take Gilmore to be advocating more unrestricted TLDs.

    The point I intended to make in my first paragraph is that new unrestricted TLDs seem to tend to have certain problems. fnord is right to point out that restricted TLDs don't seem to have these problems is true, but I don't think this fact gets at the core of my response to Gilmore. If Gilmore wants more uTLDs, and if uTLDs have the problems I flagged, then it seems to me that fnord's listing of the features & benefits of sTLDs (rTLDs? what do we call these? I'm not sure this precisely matches ICANN's sponsored/unsponsored sTLD/uTLD division) doesn't obviously settle the question of whether Gilmore's "1000 new unrestricted TLD" proposal is or is not a good idea.
    [ Reply to This | Parent ]
    Restricted TLDs are fine, but Gilmore talks of unr by edelman@law.harvard.
    Re: Restricted TLDs are fine, but Gilmore talks of
    by RFassett on Tuesday July 02 2002, @04:13PM (#7579)
    User #3226 Info | http://www.enum.info
    "The point I intended to make in my first paragraph is that new unrestricted TLDs seem to tend to have certain problems."

    "If Gilmore wants more uTLDs, and if uTLDs have the problems I flagged....."

    Ben, please "flag the certain problems that new unrestricted TLD's [would] seem to have" under the assumption that a 1,000 would be in existence. Since your research really can not conclude this because the parameters would be entirely different than the basis of your research, I would be curious to know how it is you are formulating this opinon. Please flag what these problems would seem to be - and the basis for such - given you have provided your opinion correlated to your research.
    [ Reply to This | Parent ]
    • Confused by BenEdelman Wednesday July 03 2002, @05:11PM
    Re: Restricted TLDs are fine, but Gilmore talks of
    by fnord (groy2kNO@SPAMyahoo.com) on Tuesday July 02 2002, @05:53PM (#7581)
    User #2810 Info
    I quite agree that 100's of new uTLDs, even if halfways mnemonically sensible (egs: .web, .shop, .www, .firm), and even if they include speculators and defensive registrations, aren't sustainable. But I'm not sure that that was what Gilmore was advocating. He's been around long enough to remember when comnetorg actually distinguished between entities, that is, when it was a directory system. From my reading he's not talking about 100 .com clones, and if he is, my long time respect for him as a voice of sanity just fell through the floor.

    rTLDs (which is as good a term as any, and I agree they may not precisely fit ICANN's definition because they would more properly fit on a continuum, it's not black and white) strike me as a win-win for everyone, or at least as close as we will get. If apple.computers doesn't sell books they have no reason to do a defensive registration in apple.books (and wouldn't be allowed to do so). If they do, they have to convince the booksellers association charged with policing the TLD that they have primary rights over some apple grower who sells books. If the booksellers association pays too much attention to IP interests then someone else comes along with .book and that becomes the TLD that people trust. I suspect just about everyone but squatters and big league IP interests would be happy with this, and frankly, those are the two interests now driving DNS policy, and together they are a tiny fraction of those the DNS should serve. But they both wave money, so ICANN listens. That, probably more than anything else, is why ICANN is irretrievably broken, -g

    [ Reply to This | Parent ]
    • 1 reply beneath your current threshold.


    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