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.
    XTNS offers new gTLDs (sort of) | Log in/Create an Account | Top | 127 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.
    Re: Show me one working name ? ? ?
    by dtobias (dan@tobias.name) on Saturday September 01 2001, @02:17AM (#2098)
    User #2967 Info | http://domains.dan.info/
    This "XTNS" thing is just yet another example of what's rampant on the Internet these days. First, the techie geeks create a system (DNS in this case) capable of expressing complex hierarchical structures. Then, the clueless newbies and the marketing types who pander to them fail to understand or appreciate this structure, so they treat DNS like it's a flat namespace ending in .com. Finally, in the third act of this play, some other marketing type comes in with a "revolutionary" new scheme that does just what the original system did, only in a greatly inferior way -- but, unlike the open standards-based method developed by the geeks in Act 1, this way is proprietary and involves everybody sending lots of money to the marketing type in charge of it. "Reinventing the wheel" can be profitable if it lets you get a patent on it...

    I've run into many examples of this sort of "three-act play", in areas ranging from domain names to Web browser features. After Web designers succeeded in disabling or overriding practically every feature of HTML , HTTP, or browsers, originally designed to make Web pages able to flexibly adapt to the user's needs, a market then developed for proprietary "solutions" that reinvented, in a much clumsier and more awkward way, some of the features that were there in the first place but were ignored or disabled.

    [ Reply to This | Parent ]
    Re: Show me one working name ? ? ? by dtobias
    Re: Show me one working name ? ? ?
    by Anonymous on Saturday September 01 2001, @05:16AM (#2099)
    First of all the guys at XTNS are anything but clueless. They are seasoned veterans who know as much if not more about the DNS than most techies involved with Internet infrastructure. DNS as it stands is rigid and counter-intuitive, and unforgiving. XTNS's namespaces are well thoughtout to address these issues in a methodical manner.

    The namespaces are entirely logical and really only ever read one direction (if you think about it ...) THe core aim of the company is to launch corporate and brand namespaces such as "anything.corpname". However, those are costly spaces, and the launch of their recent "Open" spaces addresses this issue -- they only look like reverse TLDs. Take a name space "anything.corpname" and sell parts of it and you get (using the most common 3LDs as your guide) "store.corpname", "corp.corpname" and I would guess coming up would be the likes of "web.corpname", "news.corpname" and so forth. In this way an entity can buy either is entire own domain, or some part of it.

    This system sits on top of DNS without breaking it. The design is meant to take away the unforgiving and confusing aspects of DNS without endangering existing stability. Thus, lengthy impossible to recall URLs are replaced with simple alterates such as "camry.toyota" that in a real sense are like Windows sitting on top of DOS (believe me, in 5 years time the current DNS will be "DOS" to what we will then call the "Windows" of the Internet and will be seen as overly techie and clunky). And rigid unforgiving URLs (one character wrong and you get a 404 error etc) with extremely forgiving namespaces -- if your customer makes a typing error in an XTNS namespace then they still reach your web server and you can try to help them reach their intended destination. Hence "camry.toyota" and "camery.toyota" and "thatnewcaryouadvertised.toyota" can all get to the same page -- impossible with regular (unenhanced) DNS. And yes I know they have to be able to spell what is to the right of the dot, but hey I bet XTNS are working on that too!

    As to ftp, email, etc they have stated they even have solutions for those in the works to. Give them a chance, they are only a couple of weeks old in terms of their first public appearance!
    [ 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