Inside ICANNWatch  
Submit Story
Lost Password
Site Messages
Top 10 Lists
Latest Comments
Search by topic

Our Mission
ICANN for Beginners
About Us
How To Use This Site
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.
    Domain Names Once Again Fetch Top Dollar | Log in/Create an Account | Top | 46 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    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.
    Why destroy the best DNS system?
    by Anonymous on Tuesday December 30 2003, @07:43PM (#12805)
    Intentional Fracture of internet identies with new overlapping TLDs only leads to errors, and no benefit. The persons who created DNS many years ago did it right. .gov, .edu, .mil, .uk, .au, these top levels all have meaning. Destroying that meaning would be stupid. The information related by these top levels is beneficial to everyone. Furthermore, People understand this and they can organize destinations and particular hosts in their minds as a result of the structure. This original design takes advantage of the way that human memory works, specifically with regard to association.

    People do understand this (if this is what you mean by directory), it is not nearly dead. It is what people understand. Your attempts to "drive the final spike into the heart" of what it is that works is ignorant. Adding generic, overlapping new top level domains helps noone except for lawyers, and domain sellers, and breaks a beneficial pattern that works to benefit everyone for no good reason.

    delta.com should belong to one registrant. Creating new TLDs (that overlap in purpose) with the TLDs that already exist, will not change this. You solve nothing. But what it will do is create confusion.

    Going from (icannwatch.com = icannwatch.net = icannwatch.org) to (icannwatch.com = icannwatch.net = icannwatch.org = icannwatch.web) benefits only the seller of the new domain. Basically the domain owner is forced to compete with another iteration of its own identity or pony up the dough. This is harmful to the domain owner and the internet user.

    I think that icannwatch.info is advertising godaddy at this time. I am not sure how the .info .com .web situation currenty plays out for Godaddy, I do not have the time to research, however I will just try the .com by default and hopefully I will get the same Godaddy and not some other domain related website.

    The confusion that is created can be easily identified by the review of the log files of any major email server. A common error is one generated when someone ads the wrong tld to the end of the hostname, of an email address. The mail bounces, the internet user often cannot recognize the problem and thinks that email is down or does not realize that the mail was not delivered. A review of the address with the wrong tld, by the original sender that has now received a bounce only confirms the wrong tld in writing back to the users mind. User fails to recognize the problem. The user calls tech support etc etc.

    Having domain with other char sets or gibberish is no justification for destroying the ability for domain to be easily remembered. gibberis is gibberish, everyone recognizes it and it will not affect someone who stumbles across some. This is not what we are talking about.

    The DNS works like a directory tree. Creating many entries at the top will only make the system less useful, like a desktop with a thousand meaningless overlapping folders. And with where we are heading duplicate data inconsistantly in different places wihin the tree.

    You have it backwards, opening many overlapping entries at the very top will flatten out the DNS hierarchy.

    You want to create competition for ever domain owner to compete with themselves or someone else as the user try and keep up.

    More overlapping TLDs is bad for domain owners and surfers period. However, more overlapping TLDs are good for lawyers and lottery ticket salespeople.

    [ 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