Skip to main content
Resources

Preliminary Report | Regular 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 2 February 2013 at 5:30 pm local time in Los Angeles, California.

Bruce Tonkin, Vice Chair promptly called the meeting to order.

In addition to the Vice Chair the following Directors participated in all or part of the meeting: Sébastien Bachollet, Fadi Chehadé (President and CEO), Bertrand de La Chapelle, Chris Disspain, Bill Graham, Olga Madruga-Forti, Erika Mann, Gonzalo Navarro, Ray Plzak, George Sadowsky, Mike Silber, Judith Vazquez and Kuo-Wei Wu. Steve Crocker (Chair) sent apologies.

The following Board Liaisons participated in all or part of the meeting: Francisco da Silva (TLG Liaison), Heather Dryden (GAC Liaison), Ram Mohan (SSAC Liaison); Thomas Narten (IETF Liaison); and Suzanne Woolf (RSSAC Liaison).

The following ICANN staff participated in all or part of the meeting: Akram Atallah, Chief Operating Officer; John Jeffrey, General Counsel and Secretary; Michelle Bright, Sally Costerton, Samantha Eisner, David Olive, Diane Schroeder, and Amy Stathos.

This is a preliminary report of the approved resolutions resulting from the Special Meeting of the ICANN Board of Directors, which took place on 2 February 2013.

  1. Consent Agenda:
    1. Approval of Board Meeting Minutes
    2. Registry Stakeholder Group Charter Amendments
      1. Rationale for Resolution 2013.02.02.02
    3. Southern California Office Space Lease
      1. Rationale for Resolution 2013.02.02.03
    4. Engagement of Independent Auditor
      1. Rationale for Resolution 2013.02.02.05
    5. Officer Appointment and related document revision
  2. Main Agenda:
    1. Multi-Stakeholder Meeting Strategy Working Group
      1. Rationale for Resolutions 2013.02.02.08 - 2013.02.02.11

 

  1. Consent Agenda:

    The Vice Chair introduced the items on the consent agenda and called for a vote. The Board then took the following action:

    Resolved, the following resolutions in this Consent Agenda are approved:

    1. Approval of Board Meeting Minutes

      Resolved (2013.02.02.01), the Board approves the minutes of the 20 December 2012 Special Meeting of the ICANN Board.

    2. Registry Stakeholder Group Charter Amendments

      Whereas, The ICANN Bylaws (Article X, Section 5.3) state, "Each [GNSO] Stakeholder Group shall maintain recognition with the ICANN Board."

      Whereas, the GNSO Registry Stakeholder Group (RySG) has alerted ICANN Staff and the Board to a set of changes to its Charter including expanding the activities of its internal Observers Group, simplifying the process for assessment of annual dues and adding the immediate past Chair of the RySG to its Executive Committee.

      Whereas, the community had the opportunity to review and comment on the RySG Charter amendments and there were no objections to the changes.

      Whereas, the Structural Improvements Committee recommends the Board approve the RySG Charter changes as presented.

      Resolved (2013.02.02.02) the proposed amendments to the Registry Stakeholder Group Charter are approved by the Board.

      Rationale for Resolution 2013.02.02.02

      In July 2009, as part of the comprehensive GNSO Improvements program, the ICANN Board approved the formal Charters of four new GNSO Stakeholder Groups (see ICANN Board Resolution 2009.30.07.09).

      The ICANN Bylaws (Article X, Section 5.3) state, "Each Stakeholder Group shall maintain recognition with the ICANN Board." The review of SG charter changes is an important part of ICANN's obligation to maintain recognition of the GNSO Stakeholder Groups and Constituencies and to preserve the operating principles articulated in the ICANN Bylaws. Community review and comments on SG charter changes can assist the Board in its evaluation process. This process is key to ICANN's accountability and transparency efforts. During the comment on this process, there were no comments received in objection to the proposed changes. Comments were received noting how the proposed amendments could be incorporated into other Stakeholder Group charters, and that will be considered as a more formalized evaluation process is developed.

      This action will have a limited impact on ICANN's resources. Increased activities by RySG Observer Groups require meetings and secretariat support, but so far that support is within the parameters of existing ICANN Budgets and staff resources. This action is not expected to have any impact on the security, stability or resiliency of the DNS.

      This action is an Organizational Administrative Function for which public comment was received.

    3. Southern California Office Space Lease

      Whereas, ICANN's current lease in Los Angeles expires 30 June 2022.

      Whereas, ICANN's primary operations and staff are located in the greater Los Angeles area.

      Whereas, current and future office space needs for primary operations will be at least 35,000 square feet.

      Whereas, the Board Finance Committee has recommended that the Board approve this resolution.

      RESOLUTION 2013.02.02.04 REDACTED PURSUANT TO RESOLUTION 2013.02.02.03

      Resolved (2013.02.02.04), the Board approves the redaction of the details of Resolution (2013.02.02.03), and corresponding rationale pending completion of negotiations.

      Rationale for Resolution 2013.02.02.03

      Although ICANN is pursuing an aggressive internationalization plan, ICANN has no plans to relocate its headquarters in Los Angeles. The Los Angeles office has been designed to be multi-functional. It is both a central office for support operations and serves as a host location for small to mid-size meetings (e.g., Board workshops). Staffing requirements to support the New the gTLD Program has caused the existing space to reach capacity.

      While most future staffing will be in hub offices and other locations outside the U.S., the long term staffing plans would require seating for approximately 35 additional staff in Los Angeles. There is one parcel of space remaining in the building in Los Angeles. The space is approximately 5,800 square feet and sits directly above ICANN's existing space. Given the convenience of the location and the existing good working relationship with the current landlord, the Board has determined that entering into a lease amendment is appropriate.

      While there will be a fiscal impact, it will not take effect during this fiscal year and it will be addressed in the FY14 budgeting process. This decision will have no impact on the security, stability or resiliency of the domain name system.

      This is an Organizational Administrative Function not requiring public comment.

    4. Engagement of Independent Auditor

      Whereas, Article XVI of the ICANN Bylaws (http://www.icann.org/general/bylaws.htm) requires that after the end of the fiscal year, the books of ICANN must be audited by certified public accountants, which shall be appointed by the Board.

      Whereas, the Board Audit Committee has discussed the engagement of the independent auditor for the fiscal year ending 30 June 2013, and has recommended that the Board engage Moss Adams LLP.

      Whereas, the Board Audit Committee has recommended that the Board direct the President and CEO or his designees to negotiate and execute a professional services agreement with Moss Adams.

      Resolved (2013.02.02.05), the Board authorizes the President and CEO to engage Moss Adams LLP as the auditors for the financial statements for the fiscal year ending 30 June 2013.

      Rationale for Resolution 2013.02.02.05

      The engagement of an independent auditor is in fulfillment of ICANN's obligations to undertake an audit of ICANN's financial books. This furthers ICANN's accountability to its Bylaws and processes, and the results of the independent auditors work will be publicly available. There is a fiscal impact to the engagement that has already been budgeted. There is no impact on the security or the stability of the DNS as a result of this appointment.

      This is an Organizational Administrative Function not requiring public comment.

    5. Officer Appointment and related document revision

      Resolved (2013.02.02.06), David Olive is elected as an Officer of ICANN with the title of Vice President, Policy Development Support.

      Resolved (2013.02.02.07), Paragraph 4 of ICANN's Contracting and Disbursement Policy shall be revised to read as follows: ICANN Officers include: (i) President and Chief Executive Officer (CEO); (ii) Chief Operating Officer (COO); (iii) Chief Financial Officer (CFO); (iv) General Counsel and Secretary; and (v) Vice President, Policy Development Support.

    Fifteen members of the Board voted in favor of Resolutions 2013.02.02.01, 2013.02.02.02, 2013.02.02.03, 2013.02.02.04, 2013.02.02.05, 2013.02.02.06, and 2013.02.02.07. One member of the Board was unavailable to vote on the resolutions. The resolutions carried.

  2. Main Agenda:

    1. Multi-Stakeholder Meeting Strategy Working Group

      The Vice Chair introduced this agenda item and the Board had a brief discussion about the anticipated goal of the working group. The Board also briefly discussed the mechanism through which the members of the Working Group would be selected, as well as the need to include a provision within the Working Group charter to dissolve the group after its work is concluded.

      The Board then took the following action:

      Whereas, ICANN has committed to identifying ICANN Meeting locations two years in advance.

      Whereas, after consideration that adoption of a prior Consolidated Meetings Strategy proposal was not timely, the Public Participation Committee (PPC) initiated work to create a working group to address the meeting location strategy.

      Whereas, the PPC has developed a proposed charter for a multistakeholder Meetings Strategy Working Group (MSWG) and recommends that the Board adopt the charter and approve the creation of the MSWG.

      Resolved (2013.02.02.08), the Board approves of the creation of the MSWG and adopts the Charter of the MSWG. The MSWG is expected to provide its report to the Board no later than ICANN's 2013 Annual General Meeting.

      Resolved (2013.02.02.09), the original members of the MSWG from the ICANN Board are: Sébastien Bachollet, Chair and Chris Disspain.

      Resolved (2013.02.02.10), the MSWG, working with the PPC, is directed to proceed with the identification of community members pursuant to the Charter. Community member appointments do not require the approval of the full Board.

      Resolved (2013.02.02.11), the President and CEO is directed to provide the MSWG with the staff support necessary to enable the MSWG to undertake and complete its work.

      Fourteen members of the Board approved of Resolutions 2013.02.02.08, 2013.02.02.09, 2013.02.02.10, and 2013.02.02.11. One Board member voted against the resolutions.  One Board member was unavailable to vote on the resolutions. The resolutions carried.

      Rationale for Resolutions 2013.02.02.08 - 2013.02.02.11

      The successful operation of ICANN's public meetings in all of the geographic regions is an important part of ICANN's accountability and transparency efforts. The action today will allow community members to serve alongside Board members in helping to develop a meetings strategy that will align with community needs, while taking into account the fiscal and facility requirements for these meetings.

      The creation of this MSWG is expected to have a minimum fiscal impact on ICANN, mostly in the resources to support the new WG. The development of the MSWG is anticipated to have a positive impact on the public interest, as ICANN is working to meet its goals for long-term planning of the meeting while considering community input. This resolution is not expected to have any impact on the security or the stability of the DNS.

      This is an Operational Administrative Function of ICANN for which public comment was not required prior to decision. The work of the MSWG is likely to be subject to public comment.

      The Vice Chair called the meeting to a close.

Published on 12 February 2013

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."