Skip to main content
Resources

Secretary's Notice | Secretary's Notice of the ICANN Board Action Without a Meeting

EFFECTIVE DATE: 12 JUNE 2017

THE ICANN BOARD PASSED THE FOLLOWING RESOLUTION EFFECTIVE 12 JUNE 2017 BY UNANIMOUS CONSENT, WITHOUT A MEETING, PURSUANT TO THE ICANN BYLAWS AT:

Section 19. ACTION WITHOUT MEETING

Any action required or permitted to be taken by the Board or a Committee of the Board may be taken without a meeting if all of the Directors entitled to vote thereat shall individually or collectively consent in writing to such action. Such written consent shall have the same force and effect as the unanimous vote of such Directors. Such written consent or consents shall be filed with the minutes of the proceedings of the Board.

ALL VOTING MEMBERS RESPONDED AND CONSENTED TO THE FOLLOWING RESOLUTION BY ELECTRONIC MEANS:

GAC Advice: Copenhagen Communiqué (March 2017)

Whereas, the Governmental Advisory Committee (GAC) met during the ICANN58 meeting in Copenhagen, Denmark and issued advice to the ICANN Board in a communiqué [PDF, 190 KB] on 15 March 2017 ("Copenhagen Communiqué").

Whereas, the Copenhagen Communiqué was the subject of an exchange between the Board and the GAC on 27 April 2017.

Whereas, in a 25 April 2017 letter [PDF, 637 KB], the GNSO Council provided its draft feedback to the Board concerning advice in the Copenhagen Communiqué relevant to generic top-level domains to inform the Board and the community of gTLD policy activities that may relate to advice provided by the GAC. The comments were formally adopted by the GNSO on 18 May 2017 and provided to the Board in a 2 June 2017 letter [PDF, 778 KB].

Whereas, the Board developed an iteration of the scorecard to respond to the GAC's advice in the Copenhagen Communiqué, taking into account the exchange between the Board and the GAC and the information provided by the GNSO Council.

Resolved (2017.06.12.01), the Board adopts the scorecard [PDF, 321 KB] titled "GAC Advice – Copenhagen Communiqué: Actions and Updates (12 June 2017)" in response to items of GAC advice in the Copenhagen Communiqué.

Rationale for Resolution 2017.06.12.01

Article 12, Section 12.2(a)(ix) of the ICANN Bylaws permits the GAC to "put issues to the Board directly, either by way of comment or prior advice, or by way of specifically recommending action or new policy development or revision to existing policies." In its Copenhagen Communiqué (15 March 2017), the GAC issued advice to the Board on various matters including: (1) protection of identifiers of the Red Cross/Red Crescent in gTLDs; (2) protection of names and acronyms of Intergovernmental Organizations (IGOs) in gTLDs; (3) mitigation of domain name abuse; and (4) two-character domain names at the second level that correspond to country/territory codes. The ICANN Bylaws require the Board to take into account the GAC's advice on public policy matters in the formulation and adoption of the polices. If the Board decides to take an action that is not consistent with the GAC advice, it must inform the GAC and state the reasons why it decided not to follow the advice. Any GAC advice approved by a full consensus of the GAC (as defined in the Bylaws) may only be rejected by a vote of no less than 60% of the Board, and the GAC and the Board will then try, in good faith and in a timely and efficient manner, to find a mutually acceptable solution.

At this time, the Board is taking action to address the advice from the GAC in the Copenhagen Communiqué. The Board's actions are described in the scorecard [PDF, 321 KB] dated 12 June 2017.

In adopting its response to the GAC advice in the Copenhagen Communiqué, the Board reviewed various materials, including, but not limited to, the following materials and documents:

https://www.icann.org/en/system/files/correspondence/bladel-et-al-to-crocker-02jun17-en.pdf [PDF, 778 KB]

The adoption of the GAC advice as provided in the scorecard will have a positive impact on the community because it will assist with resolving the advice from the GAC concerning gTLDs and other matters. There are no foreseen fiscal impacts associated with the adoption of this resolution. Approval of the resolution will not impact security, stability or resiliency issues relating to the DNS.

This is an Organizational Administrative function that does not require public comment.

Published on 14 June 2017

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