Skip to main content

Welcome to the new ICANN.org! Learn more, and send us your feedback. Dismiss

Resources

Preliminary Report | Special Meeting of the ICANN Board

[Formal Minutes are still to be approved by the ICANN Board]

Note: This has not been approved by the Board and does not constitute minutes but does provide a preliminary attempt setting forth the unapproved reporting of the resolutions from that meeting. Details on voting and abstentions will be provided in the Board's Minutes, when approved by the Board at a future meeting.

NOTE ON ADDITIONAL INFORMATION INCLUDED WITHIN PRELIMINARY REPORT — ON RATIONALES — Where available, a draft Rationale for each of the Board's actions is presented under the associated Resolution. A draft Rationale is not final until approved with the minutes of the Board meeting.

A Special Meeting of the ICANN Board of Directors was held on 14 March 2012 at 6:00 pm local time in San Jose, Costa Rica.

Acting Chairman Cherine Chalaby promptly called the meeting to order.

In addition to the Acting Chair the following Directors participated in all or part of the meeting: Rod Beckstrom (President and CEO), Chris Disspain, Bill Graham, Erika Mann, Gonzalo Navarro, Ray Plzak, R. Ramaraj, George Sadowsky, Mike Silber, and Kuo-Wei Wu

The following Board Liaisons participated in all or part of the meeting: Thomas Roessler, TLG Liaison.

Sébastien Bachollet; Bertrand de La Chapelle; Steve Crocker; Heather Dryden, GAC Liaison; Ram Mohan, SSAC Liaison; Thomas Narten, IETF Liaison; Bruce Tonkin; Judith Vazquez; and Suzanne Woolf, RSSAC Liaison sent apologies

This is a preliminary report of the approved resolutions resulting from the Special Meeting of the ICANN Board of Directors, which took place on 14 2012

  1. Approval of New gTLD Service Providers

 

  1. Approval of New gTLD Service Providers

    The Board took the following action:

    Whereas, on 25 September 2010, the Board approved the New gTLD Application Processing budget <http://www.icann.org/en/minutes/resolutions-25sep10-en.htm#1>.

    Whereas, on 20 June 2011, the Board authorized the President and CEO to implement the new gTLD Program and approved the expenditures related to the New gTLD Program as detailed in section 7 of the Draft FY12 Operating Plan and Budget <http://www.icann.org/en/minutes/resolutions-20jun11-en.htm>.

    Whereas, on 9 August 2011, the Board formally adopted the FY12 Operating Plan and Budget, which included the details of anticipated expenditures related to the New gTLD Program in section 7 <http://www.icann.org/en/financials/adopted-opplan-budget-fy12-09sep11-en.pdf> [PDF, 1.53 MB].

    Whereas, to date ICANN has approved the entities to serve as gTLD Service Providers to process all of the new gTLD Applications and is still working out specific contractual obligations with those entities.

    Whereas, one or more gTLD Service Providers could provide millions of dollars worth of application processing services in any given billing cycle and ICANN must be prepared to timely pay for those services.

    Resolved (2012.03.14.02), the CEO or his designee is authorized to enter all contracts or statements of work with, and make all disbursements to, all gTLD Service Providers so long as the contract and disbursement amounts are contemplated in the approved budget for such expenditures.

    Eleven Board members voted in favor of Resolution 2012.03.14.02. Five Board members were unavailable to vote. The resolution carried.

    Rationale for Resolution 2012.03.16.02

    ICANN’s Disbursement Policy limits ICANN officers from contracting for or disbursing more than US $500,000.00 per obligation. ICANN is therefore adhering to its policy in seeking the Board’s approval to enter into these contractual obligations that exceed the $500,000 per obligation item. With the finite number of approved new gTLD service providers (“Service Providers”) and the potential level of application processing expenses that ICANN might incur with any one or more of the Service Providers, the contracting and disbursement limits of the Disbursement Policy could be exceeded every billing cycle during the new gTLD evaluation phase.

    Accordingly, to ensure that timely obligations are made and satisfied with the Service Providers, it is appropriate to take this action now and have the Board’s approval to undertake these contractual obligations. The CEO is being authorized to enter into all required contracts and make all required disbursements, with the Service Providers, subject to budgetary limits and based on the budget model that the Board approved on 9 August 2011, which included details of anticipated expenditures related to the New gTLD Program <http://www.icann.org/en/financials/adopted-opplan-budget-fy12-09sep11-en.pdf> [PDF, 1.53 MB].

    The Board’s approval of entering into these contractual obligations will have a positive impact on the community because it will allow ICANN to timely contract with and pay the gTLD Service Providers that are evaluating the new gTLD applications. There are fiscal impacts on ICANN but all of those impacts have been anticipated in the approved FY 2012 and draft FY 2013 budgets. There will not be any security, stability or resiliency issues relating to the domain names system.

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."