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)


     
    New gTLDs Why the draft .aero sponsorship agreement should be rejected
    posted by michael on Saturday November 17 2001, @01:39PM

    Anonymous writes "by Edward Hasbrouck, "The Practical Nomad"; http://hasbrouck.org/icann

    Recommendations to the ICANN Board of Directors and the ICANN At-Large Study Committee (15 November 2001)

    1. Request for action by members of the ICANN Board of Directors

    I am writing to you as members of the ICANN Board of Directors (and the ICANN At-Large Study Committee) concerning the latest sections of the draft sponsorship agreement for the ".aero" global top-level domain (gTLD) posted 9 November 2001 to the ICANN web site.

    I believe that the terms of the most recently posted sections of the draft agreement, the ".aero Charter" (Attachment 1) and the "Description of the Sponsored TLD Community" (Attachment 5) :

    1. Are inconsistent in important respects with the proposal on the basis of which the .aero agreement was supposed to be negotiated, and with the general terms of the "TLD Sponsorship Agreement";
    2. Are inconsistent with principles of transparency, public participation, and content neutrality in the administration of the Internet namespace;
    3. Fail to represent the diversity of the sponsored gTLD community and its stakeholders, including failing to allow for registration by many members of the originally-defined community or to provide for at- large participation in the governance or administration of the .aero domain;
    4. Are contrary to the interests of public safety in aviation and air transportation;
    5. Are especially significant as precedents, and would set inappropriate precedents, for other sector- specific gTLD's; and for all these reasons
    6. Should not be approved by ICANN, and certainly should not be approved without full consideration by the Board of Directors.
    "




    Under the procedure established by ICANN Resolutions 01.83-01.86 , ICANN's President is authorized to sign the .aero sponsorship agreement unless a member of the ICANN Board of Directors requests otherwise within seven days of the completion of posting of the draft agreement. Affirmative action by you is required to prevent the signing and implementation of the draft agreement.

    Some sections of the draft .aero sponsorship agreement have not yet been posted as of this writing (15 November 2001), so the seven-day comment and objection period has not yet begun. However, since the portions of the agreement already posted are clearly contrary to ICANN principles and the public interest, I urge you to record your request that the draft .aero agreement not be signed, without delay. Once that request has been recorded, the Board of Directors can schedule the .aero agreement for full consideration at a future board meeting.

    2. How the draft "aero" agreement differs from SITA's original proposal

    The .aero gTLD was proposed by the "Société Internationale de Télécommunications Aéronautiques" (SITA) as "a Top Level Domain for the entire Air Transport Community (ATC)"... In this... proposal, the definition of ATC is: 'All companies and organizations for which the main activity is related to Air Transport.'"

    The inclusiveness of this proposal for a domain for all stakeholders in the air transport community was a significant factor in ICANN's selection of this proposal, from among many others, for negotiation towards a sponsorship agreement.

    The draft .aero sponsorship agreement continues to refer to the "Air Transport Community", but defines it very differently: "The .aero TLD is restricted to people, entities and government agencies which: (1) provide for and support the efficient, safe, and secure transport of people and cargo by air; and (2) facilitate or perform the necessary transactions to transport people and cargo by air."

    There are three material changes from the proposal to the draft agreement:

    1. The proposal included all those whose activities are "related to" air transport, while the draft agreement would include only those who "provide for and support" or "facilitate or perform... transactions to support" air transport." That would exclude those whose relationship to air transport is as users or purchasers rather than as providers of air transport services. These excluded members of the community and stakeholders in the domain include airline passengers, air cargo shippers, and their organizations. The draft agreement also excludes those whose activities are "related to" air transport, but who are neither providers nor users of services. These air transport community members and stakeholders include air transport consumer, safety, and security advocates and advocacy organizations, and organizations and individuals impacted by the air transport industry through airport noise, environmental damage, security measures, etc. (affected homeowners, neighborhood organizations, civil liberties organizations, etc.).
    2. The draft agreement would limit the .aero domain to those who "support... transport... by air", implicitly excluding those who oppose air transport or, perhaps more importantly, those whose criticisms of others in the air transport community might be considered by SITA or others in the community to constitute opposition to air transport. Under the draft agreement, eligibility for registration and participation in administration of the .aero domain depends on whether the registrant's opinions constitute "support" or "opposition" to a particular point of view. This will require SITA to implement content-based procedures for inquiries into, and determinations of, prospective registrant's opinions. This would be administratively complex, costly, and fraught with potential for abuse. There is no evidence that SITA has the least competence to make such determinations, or to represent the full diversity of the air transport community and its stakeholders in doing so. (SITA may claim that it has no intention to actually impose such conditions for .aero registration. That may be true, but if so, the sponsorship agreement should not grant SITA authority to do so, as the draft does.) SITA has given no public explanation as to why the .aero domain should be open to the industry's boosters but closed to its critics.
    3. Perhaps most dangerously, the requirement for "support" of air transport as a condition of continued eligibility for .aero registration could serve as a powerful deterrent to whistle-blowing or the raising of criticisms from within the air transport industry, out of fear that those criticisms could be used as grounds for an allegation of lack of "support", and thus for revocation of a .aero registration. Many safety and security hazards to air transport have become known, and been addressed, only as a result of whistle-blowing from within the industry. That should be encouraged and protected, not discouraged. SITA itself said in its proposal, "This industry needs a TLD that it can manage to the same safety and security standards that prevail in the legacy world today." Those legacy industry standards include explicit protections for whistle-blowers, standards for transparency (especially with respect to safety concerns) and encouragement of criticism and debate -- none of which are included in the draft .aero agreement. It's ironic that the draft .aero agreement, with its potential disincentives for whistle-blowing on safety and security, was posted to the ICANN Web site less than a week before an ICANN Board of Directors meeting devoted primarily to safety and security. Moreover, for ICANN to enter into an agreement creating a disincentive -- fear of disqualification from eligibility for .aero registration -- to whistle-blowing and public airing of safety and security concerns by members of the air transport community would give substantial cause for the Department of Commerce of the USA to exercise it's oversight authority over ICANN, and to intervene in the public interest. This, I assume, is an outcome ICANN, SITA, and most stakeholders (including myself) would much prefer to avoid.

    3. The ".aero" application and ICANN principles

    ICANN general terms for all gTLD Sponsorship Agreements include the following: "3.1. Obligation to Maintain Representative Characteristics Justifying Original Selection of Sponsor. During the Term of this Agreement, Sponsor (a) agrees to ensure it remains at least as representative of the Sponsored TLD Community as it was at the time of its selection, and (b) shall be responsible for developing policies for, and providing for the operation of, the Sponsored TLD in the interest of the Sponsored TLD Community."

    As described above, the draft .aero sponsorship agreement with SITA clearly fails to meet this requirement. SITA has failed to represent the diversity of the community as it was represented in the SITA proposal for .aero, excluding significant segments of the community (particularly users and purchasers of air transport services, and those critical of air transport). SITA has proposed no policies whatsoever, in the draft agreement, providing any mechanism for accountability to those stakeholders. Indeed, SITA's conduct in negotiating a draft agreement excluding large and significant segments of the community calls into serious question its ability or commitment to administering the .aero gTLD in their interests. At a minimum, since the draft agreement makes clear that SITA is no longer as representative of the air transport community as it claims to be in its initial proposal and at the time of its selection, ICANN should requires SITA to resubmit its application for .aero for de novo, clean-slate consideration on the basis of a narrower and more accurate description of how inclusive a community SITA really is capable and committed to represent.

    SITA's failure to fulfill its responsibility to represent the community of stakeholders in the .aero gTLD, and its failure to ensure that it exercises its delegated authority in the interest of the community, is an almost inevitable outcome of ICANN's failure to include mandatory provisions for transparency and at-large participation in the exercise of delegated authority. On this issue, I recommend to your attention my testimony and comments to the ICANN At- Large Study Committee, with particular reference to the example of SITA and .aero, available at . The Delegation of Authority for .aero (Attachment 2 of the sponsorship agreement) has not yet been posted for public comment, but I urge you not to approve it unless it is conditioned on transparency and at-large participation.

    4. The importance of ".aero" as a precedent

    The defects in the .aero draft agreement, and the closed procedure by which was negotiated, are significant not just for themselves but because, as SITA itself correctly states, "This is the first time any specific industry grouping would be allowed to adopt its own TLD." There are likely to be many more gTLD's for specific economic sectors, and the .aero application warrants particular care because it is setting precedents. The handling of .aero is the test case for you as the ICANN Board of Directors as to how ICANN will deal with the balancing of corporate boosters and critics, at-large stakeholders, and public interests in the establishment of new domains for specific economic sectors that are already largely dominated by corporate interests. This precedent-setting importance makes it particularly inappropriate for the .aero sponsorship agreement to be signed without full opportunity for public and at-large input and full consideration by the ICANN Board of Directors.

    Accordingly, I urge that -- in addition to recording your request to ICANN's President that the draft .aero agreement not be signed -- you schedule a public hearing and full consideration of the .aero agreement for a future ICANN Board of Directors meeting.

    Edward Hasbrouck
    edward@hasbrouck.org
    http://hasbrouck.org

  • Passenger air travel and travel e-commerce consumer advocate, author, and FAQ-maintainer
  • Member-at-large of the Air Transport Community and the ".aero" gTLD constituency
  • Click here to comment on this story

     
      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  
  • ICANNWatch.org
  • edward@hasbrouck.org
  • http://hasbrouck.org
  • Click here to comment on this story
  • http://hasbrouck.org/icann
  •  
    This discussion has been archived. No new comments can be posted.
    Why the draft .aero sponsorship agreement should be rejected | Log in/Create an Account | Top | 2 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: Why the draft .aero sponsorship agreement shou
    by dtobias (dan@tobias.name) on Tuesday November 20 2001, @03:00AM (#3798)
    User #2967 Info | http://domains.dan.info/
    I can't really agree with all of these criticisms. .aero is intended as a narrowly restricted TLD for a particular industry, and it is a sponsored TLD, meaning that the sponsoring organization has been granted the power of deciding most of the issues of its management rather than having every detail micromanaged by ICANN. In fact, others on this site would rake ICANN over the coals any time they tried to micromanage a sponsored domain. Thus, criticizing the agreement because it potentially lets the sponsor make broad decisions about who does or doesn't "support" the industry's objectives, and thus should or shouldn't be eligible for a domain, is in effect saying that ICANN ought to be imposing more conditions on the sponsors, which seems to go against the general belief here.

    If some hypothetical organization (radical environmentalists, perhaps) wants to ban all air travel, why should they be entitled to a .aero domain? They're not part of the air travel industry, and in fact if they succeeded in their aims there wouldn't be any industry any more, and thus no need for a TLD for it. Not allowing them a domain in this restricted TLD isn't "suppressing dissent" any more than not allowing the Taliban to set up a site in the .us domain to criticize the United States, when they don't have a U.S. presence as required by that domain's rules. An anti-air-travel organization is free to set up their site in .org or .info.

    As for internal critics within the industry, who otherwise qualify for .aero domains but express views that the rest of the industry dislikes, I hope the rules aren't used against them to deny or revoke .aero domains for political purposes, but that's an internal matter within that industry, possibly subject to appeal under the various dispute policies or in court, but not necessarily something that ICANN should be making rules about to cover every hypothetical possibility.

    I don't see how individual air passengers should have any entitlement to a .aero domain, any more than individual museum visitors have an entitlement to a .museum domain, or individual college students have a right to a .edu domain.
    [ 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