Skip to main content
Resources

Minutes | Regular Meeting of the ICANN Board

A Regular Meeting of the ICANN Board of Directors was held in Helsinki, Finland on 27 June 2016 at 12:30 local time. Each Director waived notice of holding the meeting.

Steve Crocker, Chair, promptly called the meeting to order.

In addition to the Chair, the following Directors participated in all or part of the meeting: Chris Disspain, Asha Hemrajani, Rafael Lito Ibarra, Markus Kummer, Bruno Lanvin, Erika Mann, Göran Marby (President and CEO), George Sadowsky, Mike Silber (telephonically), Bruce Tonkin, Lousewies van der Laan, and Kuo-Wei Wu.

The following Directors sent their apologies: Rinalia Abdul Rahim, Cherine Chalaby (Vice Chair), and Ron da Silva.

The following Board Liaisons participated in all or part of the meeting: Ram Mohan (SSAC Liaison), Jonne Soininen (IETF Liaison), and Suzanne Woolf (RSSAC Liaison).

The following Board Liaisons sent their apologies: Thomas Schneider (GAC Liaison).

Secretary: John Jeffrey (General Counsel and Secretary).

The following ICANN Executives and Staff participated in all or part of the meeting: Akram Atallah (President, Global Domains Division); Susanna Bennett (Chief Operating Officer); Duncan Burns (Vice President, Global Communications); and Xavier Calvez (Chief Financial Officer).

These are the Minutes of the Regular Meeting of the ICANN Board, which took place on 27 June 2016.

  1. Main Agenda:
    1. FY17 Update to the Five-Year Operating Plan

 

  1. Main Agenda:

    1. FY17 Update to the Five-Year Operating Plan

      Asha Hemrajani, the Co-Chair of the Board Finance Committee, introduced the item, noting that approval of the update to the Five-Year Operating Plan was a companion action to the Board's recent approval of the FY17 Operating Plan and Budget. Asha informed the Board that the Board Finance Committee reviewed the updates to the Operating Plan and recommended their approval by the full Board.

      Xavier Calvez provided the Board with an overview of the community input received on the version of the update to the Five-Year Operating Plan posted for public comment. He also highlighted the changes and the clarifications that were made in response to public comments. Xavier reported that the changes included clarifications on the IANA stewardship transition within the Five-Year Operating Plan and reorganization of some of the portfolios for the nine goals.

      Asha Hemrajani moved and Steve Crocker seconded the resolution. The Board took the following action:

      Whereas, the draft FY17 Update to the Five-Year Operating Plan was based upon community consultations, and consultations with ICANN staff and the Board Finance Committee (BFC), during the current fiscal year and was posted for public comment on 05 March 2016.

      Whereas, comments received from the public comment forum were discussed during several calls with Board members, staff members, and representatives of the ICANN bodies that submitted those comments, to help ensure the comments were adequately understood and appropriate consideration was given to them.

      Whereas, the public comments received, as well as other solicited community feedback through conference calls, meetings in Marrakech and email communications, were taken into account to determine required revisions to the draft FY17 Update to the Five-Year Operating Plan.

      Whereas, the BFC has discussed, and guided staff on, the development of the FY17 Update to the Five-Year Operating Plan at each of its recent regularly scheduled meetings.

      Whereas, the BFC met on 09 June 2016 to review and discuss the suggested changes resulting from public comment, and the final FY7 Budget and Operating Plan was approved by the Board on 26 June 2016. As a complement to the approval of the FY17 Operating Plan and Budget, the Five-Year Operating Plan has been updated as part of the FY17 planning cycle, including through the public comment process, and the BFC recommends that the Board adopts the FY17 Update to the Five-Year Operating Plan.

      Resolved (2016.06.27.01), the Board adopts the FY17 Update to the Five-Year Operating Plan [PDF, 680 KB].

      All members of the Board present voted in favor of Resolution 2016.06.27.01. Rinalia Abdul Rahim, Cherine Chalaby, and Ron da Silva were unavailable to vote on the Resolution. The Resolution carried.

      Rationale for Resolution 2016.06.27.01

      On 05 March 2016, a draft of the FY17 Update to the Five-Year Operating Plan was posted for public comment. This version was based on numerous discussions with members of the senior ICANN Management, and extensive consultations with ICANN Supporting Organizations, Advisory Committees, and other stakeholder groups throughout the prior several months.

      This FY17 Update to the Five-Year Operating Plan will have a positive impact in that it provides a proper framework pursuant to which ICANN will be operated. It also provides the basis for the organization to be held accountable in a transparent manner. This will have a fiscal impact on ICANN and the community as is intended. This should not have anything but a positive impact on the security, stability and resiliency of the domain name system (DNS) with respect to any funding that is dedicated to those aspects of the DNS.

      This is an Organizational Administrative Function that has already been subject to public comment as noted above.

Published on 10 August 2016

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