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.
    Tralliance in talks with New.net on .travel | Log in/Create an Account | Top | 42 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.
    collisions?
    by fnord (groy2kNO@SPAMyahoo.com) on Thursday August 14 2003, @07:17PM (#12071)
    User #2810 Info
    More to the point of the article, when new.net first released its plugin I managed to capture it (it was relatively simple so I don't know why newnetters were complaining they couldn't get a copy to provide for download) and take it apart.

    The way it worked then (I don't know about now) was that it contained all the existing legacy gTLD strings and all existing ccTLD strings. If one typed unregistered-name.travel, or even unregistered-name.foo one was served up with the new.net site. That is, it worked by a system of exclusion along the lines of:

    If TLD string = ICANN TLD string
    Then goto ICANN root
    Else goto new.net

    Interestingly the plugin included the then recently okayed but not yet functional .info, .biz etc. I find it hard to believe that if .travel was okayed by ICANN that new.net wouldn't similarily recognize it. Let's look at the possibilities.

    1. new.net recognizes only it's own travel. That would make it less useful.

    2. new.net recognizes only ICANN .travel. That would make its registrants howl (and perhaps, though I doubt, it even sue).

    3. new.net recognizes both and where there is a collision it chooses either itself or ICANN (or even serves up a page which points to both).

    It will be interesting to see where they go with this, but I can't see ICANN losing much sleep over it. -g

    [ Reply to This | Parent ]
    Re:collisions?
    by fnord (groy2kNO@SPAMyahoo.com) on Tuesday August 19 2003, @11:15AM (#12093)
    User #2810 Info
    I'm no ICANN fan but they are not introducing collision if they enter .travel in the root. Who are they colliding with, travel.new.net. And I suppose they couldn't create .mail as there are already mail subdomains out there, EG mail.yahoo.com [yahoo.com]. Get serious. As for new.net determining which extensions to add in the future, they haven't added any for quite awhile (probably the law of diminishing returns at work), and their internationalized domain names they promised almost from day one (which might have been successful for both registrants and new.net) are still nowhere to be found. -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