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)


     
    gTLDs hoping to enter the legacy root The fix is still in on .travel
    posted by michael on Tuesday November 04 2003, @11:18AM

    ehasbrouck writes "At its annual business meeting, the day after its public forum (not), ICANN announced "an expedited process for a round of new sponsored generic top level domains (sTLDs), which will result in new sTLD's in 2004. sTLD serve specific communities. Examples of current sTLDs (include .museum, .coop, and .aero) "ICANN is working hard to listen and be responsive to the Internet community's needs and they have asked for us to address the issues regarding new sTLDs" stated [ICANN's CEOand President] Dr. [Paul] Twomey, who introduced the resolutions to the Board." (text of ICANN resolution)

    Such are the depths of ICANN doublespeak: "working hard to listen" by adjourning before the start of the open mike for public comments.

    Apparently some comments were taken earlier in the day, from those in the room in Tunisia or who had found out the comment e-mail address and submitted comments in advance, without waiting to see what proposals would be introduced at the last minute (usually, in ICANN's usual modus operandi , the most important ones). But those who actually wanted to respond to the staff and board proposals, and couldn't afford to be in Carthage, were SOL."



    "Anyway, ICANN's decision was exactly what IATA and its current front groups for its .travel scheme, Tralliance Corp. and the Travel Partnership Corp., had requested (demanded?) in a letter to the ICANN Board of Directors after the Board's last telephone conference, when the Board indicated that it might not approve a request for TLD sponsorship proposals at the Carthage meeting.

    IATA wanted to make sure that its designee would be awarded .travel, ASAP, to manage for the benefit of the travel industry (and without regard for any conflicting interests of travellers, travel consumers, NGO's concerned with travel, or Internet users at large). Delivering .travel to IATA required the following, and this is exactly what IATA approved:

    1. IATA wants .travel approved, ASAP, since IATA and its friends have already been taking ICANN approval for granted and spending money on .travel plans accordingly. IATA got what they wanted: the ICANN board voted to direct ICANN's president to publish an RFP for new TLD's by 31 December 2003, not waiting for the evaluation -- only just begun -- of the (failure of the) previous round of TLD's including .aero . Interestingly, the Travel Partnership Corp. based its appeal for hasty action by ICANN on the cost to the TPC and its "constituents" of "delay" in approving .travel. This argument would make sense only if ICANN had already promised .travel to the TPC; if the only remaining issue was when -- not whether -- .travel would be awarded to the TPC and its partners; and if the TPC had invested in its plans on the basis of such a promise by ICANN. But the TPC didn't even exist when IATA's original application for .travel was passed over in 2000 -- on the appropriate grounds that IATA airlines don't represent the diversity of travel constituencies. And ICANN has never made any public statement whatsoever to the TPC, or promising to award .travel to anyone at all. The TPC's letter and its arguments are an implicit admission that there was a secret promise by ICANN that .travel would be awarded to IATA -- which there was, specifically through former ICANN staff person (and de facto manging director) Louis Touton), as I've written previously and described directly to the ICANN Board in my comments to previous ICANN meetings . The TPC's letter was a thinly-veiled demand to ICANN to honor ICANN's secret promise, and apparently ICANN got the message and acted accordingly.
    2. IATA needed a "sponsored" rather than an "unsponsored" domain: airlines and the rest of the travel industry weren't interested in the existence of a TLD for travel, open to all constituencies with an interest in travel. No, the whole point was to get control of the Internet travel namespace (IATA is a cartel , remember), which is only permitted with a sponsored TLD. IATA and the TPC got what they wanted: ICANN will only consider applications for new sponsored
    3. IATA had originally argued for limiting the next round of TLD's to failed applications from the 2000 TLD application round (to rule out any potential competitors for .travel) by non-profit sponsors (IATA is, in theory, a non-profit orgnaization, although that's a bit of a stretch since all its members are for-profit or government-owned airlines). But ICANN passed over IATA's .travel application in 2000 because IATA couldn't represent all travel interests, and IATA had to create a new "non-profit" corporation, the TPC, to give the appearance of broader representation in the sponsoring body for .travel. Having done so, IATA realized that they couldn't necessarily "transfer" the original application to the new entity (without making apparent that it was a captive front for IATA, and that even if they did, the TPC as a new shell corporation couldn't meet the qualifications to actually operate a TLD. Tralliance Corp. might meet those qualifications, and has close ties to ICANN insiders, but it's a for-profit corporation. So IATA & Co. reversed themselves, and asked ICANN to eliminate the limitation to nonprofit sponsors passed over in 2000 . ICANN dutifully did so: the new RFP will allow applications for sponsored TLD's by any nonprofit or for-profit entity.
    4. Especially with applications theoretically open to all comers, IATA needed some way to ensure itself preferential treatment. ICANN delivered: the new round of TLD applications will be conducted so quickly as to heavily favor those who've already prepared their applications, and will lead to approval of only the top few applicants, probably 3, no matter how many worthy applications are submitted.

    The fix is still in. Unless something major happens to derail it, ICANN will award sponsorship of a .travel TLD to the Tralliance Corp. (with a nominal role for the TPC -- which will be forgotten as soon as the sponsorship agreement is signed -- as "policy making" body) as a front for IATA and the travel industry -- to the exclusion of the interests of travellers, travel consumers, consumer advocates, and Internet users at large -- at the next ICANN Board of Directors meeting, in Rome in March 2004."

     
      ICANNWatch Login  
    Nickname:

    Password:

    [ Don't have an account yet? Please create one. It's not required, but as a registered user you can customize the site, post comments with your name, and accumulate reputation points ("karma") that will make your comments more visible. ]

     
      Related Links  
    · Dr. Paul Twomey
    · ICANN
    · Tralliance Corp.
    · Travel Partnership Corp.
    · letter to the ICANN Board of Directors
    · .aero
    · written previously
    · my comments to previous ICANN meetings
    · asked ICANN to eliminate the limitation to nonprofit sponsors passed over in 2000
    · ehasbrouck
    · public forum (not)
    · announced
    · text of ICANN resolution
    · More gTLDs hoping to enter the legacy root stories
    · Also by michael
     
    This discussion has been archived. No new comments can be posted.
    The fix is still in on .travel | Log in/Create an Account | Top | 28 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.
    Re:New.net deserves .Travel
    by ldg on Wednesday November 05 2003, @03:13AM (#12601)
    User #2935 Info | http://example.com/
    I'm curious. Just how did New.Net screw their customers. I just successfully surfed to the asta.travel website by adding .new.net. I choose to not use their plug-in, so I use the extension instead. The website and domain both work just fine.

    I'm not a new.net fan by any means, but I don't see how they screwed customers if their domains resolve, they have TLD servers and a working registry.
    [ Reply to This | Parent ]
    Re:New.net deserves .Travel
    by cambler (chris@ambler.net) on Wednesday November 05 2003, @07:56AM (#12603)
    User #36 Info | http://onthenet.ambler.net/
    The difference, I think, is that I fully expect to see our .Web in the roots, and that waiting and participation will pay off.

    At that time, New.net will still be trying to get customers to download their plug-in.

    I like our plan of being patient and working within the system better. But perhaps that's just me.

    --
    Ambler On The Net [ambler.net]

    [ Reply to This | Parent ]
    Re:New.net deserves .Travel
    by simon on Wednesday November 05 2003, @11:57AM (#12608)
    User #2982 Info | http://www.nic.pro/
    I do making money with my New.net domain names.
    You may have a look at http://www.sex.shop or http://www.health.shop or at one of my other sites.

    nic.PRO will be back online soon with FREE sub-domains. Dowload the FREE plug-in at
    www.name-space.com/software
    [ Reply to This | Parent ]
  • 2 replies 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