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.
    ICANN Chair Admits "Stupid Mistake" | Log in/Create an Account | Top | 10 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.
    You misrepresent
    by WIPOorgUK on Thursday February 20 2003, @04:03PM (#11208)
    User #3146 Info | http://wipo.org.uk/
    > Haven't you realized that DNS is ambiguous - that a given DNS name can resolve to many many types of records, each with many intances.

    I have sussed that.

    And why can it not be aided - made less ambiguous - by adding a directory system to that which causes the most conflict - trademarks?

    Exactly whose purpose does it help - by being ambiguous?

    It only helps the major corporations to steal dictionary words that belong to everybody - small business and individuals alike.

    It only helps the major corporations to unlawfully overreach their trademark.

    > And even in the simple minded world that thinks of the net as being nothing more than the world wide web and in which a domain name leads only to a single A record the IP address in that A record points to an interface on a computer that may serve up a plethora of services of many types.

    I am personally aware that of the history of the Internet and the development of WWW.

    I object to the theft of the DNS by big business - primarily aided and abetted by ICANN, US DoC and UN WIPO.

    > And even if one is so limited as to conceive only of web pages, a single web site often consists of many types of content - look at sony.com - what is it? A movie company, a record company, an electronics company? What's ge.com - a builder of turbines, a finanancial services company, a leasing company...?

    Simple - multiple entries for multiple classifications.

    sony.electronic.us.reg
    sony.record.us.rg
    etc.

    > Now, if we had decent directory tools we would specify something about what we were looking for, usually via the context or the tool we were using - a phone would look for another telephone service, a calendaring program would look for a remote scheduling service interface, etc.

    I have not knocked other ideas in this respect.

    > Your view of the world is too unimaginate

    "unimaginate" - you cheeky scamp.

    How come the lawyers have not come up with the idea of name.class.country.reg?

    None can deny that it would not identify ALL registered trademark words - without 'consumer confusion', 'trademark conflict' and 'passing off' problems.

    You would think the lawyers are quite happy making all that money from the conflict and ambiguity.

    > and informed solely by search engines that are poor substitutes for real directories,

    It is not informed solely by search engines.

    WE AGREE SEARCH ENGINES ARE POOR SUBSTITUTES FOR REAL DIRECTORIES.

    > but, as measured by their popularity, clearly are much better at the job than the tool you want to impose on us, DNS.

    You misrepresent me - this registered trademark TLD is IN ADDITION to search engines.

    INTELLIGENT PEOPLE WILL AGREE SEARCH ENGINES ARE POOR SUBSTITUTES FOR REAL DIRECTORIES.

    Can anybody here give reasoned argument to counter this statement?

    Surely my favourite critic will argue against it.
    [ Reply to This | Parent ]
    You misrepresent by WIPOorgUK
    Go build it and see if anybody uses it
    by Anonymous on Friday February 21 2003, @09:37AM (#11209)
    You are entirely free to build your taxonomic naming system - If you want to engender user confusion you are free to make it look exactly like DNS. In fact you can use DNS protocols if you want. I suggest that you use TXT records to hold some sort of handle - I suggest a URI for the handle - for the resource you want. ENUM works sort of this way - ENUM is really a directory that is layered upon DNS and uses DNS protocols in a recursive fashion. However, your name space will be a name space distinct and separate from that of DNS, your name space willl followsyour rules, DNS will follow its own. And you will have to accept that many people not only will not use your name space but may establish what they believe are better designs. One thing you will need to make clear to your customers - the names that you would be pushing are not DNS names. As for the real DNS underpinnings - attempts such as you are pushing will always crash and burn on the hard rocks of the reality that there is no way to form, much less to enforce, a semantic relationship between a domain name hierarchy and the large number of things that that domain name can lead to. After your smashing sucess in this endevour I suggest that you move on, using your same logic, and force telephone number assignments to follow SIC codes representing the service you expect from the person who answers the phone.
    [ 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