Skip to main content

Minutes | Board Governance Committee (BGC) Meeting

BGC Attendees: Chris Disspain – Chair, Erika Mann, Gonzalo Navarro, Mike Silber, and Bruce Tonkin

BGC Member Apologies: Cherine Chalaby and Suzanne Woolf

Invited Guests: Ron da Silva

Executive and Staff Attendees: Megan Bishop (Board Support Coordinator), Michelle Bright (Board Support Content Manager), John Jeffrey (General Counsel & Secretary), Vinciane Koenigsfeld (Board Support Content Manager), Liz Le (Senior Counsel), and Amy Stathos (Deputy General Counsel)

The following is a summary of discussions, actions taken, and actions identified:

  1. Minutes – The BGC approved the minutes from the 24 August 2015 meeting.

  2. Reconsideration Request 15-11 – Chris Disspain abstained from participation in this matter noting a potential conflict. Staff briefed the BGC regarding the request submitted by Motion Picture Domain Registry Pty Ltd. ("MPDR"), the registry operator for .FILM gTLD, seeking reconsideration of ICANN's response to MPDR's Request For Release Of Letter/Letter Two-Character ASCII Labels ("two-letter labels"). Specifically, MPDR seeks reconsideration of ICANN's decision pursuant to the Process for Requesting Authorization for Release of Letter/Letter Two-Character Labels ("Process") to withhold authorization of release for the two-letter labels that were subject to objections, most of which were comprised of governmental entities' concerns that those two-letter labels could interfere with certain two-letter country code TLDs. After discussion, the BGC concluded that MPDR has not demonstrated any conduct inconsistent with any established policy or procedure. The Process explicitly states that only the "non-objected" two-letter labels will be released within 7-10 days of the close of the comment period, which is exactly what ICANN did. Neither the Process nor any other established ICANN policy or procedure currently prescribes whether, or how, objected-to two-letter labels are to be further evaluated. With respect to the objected to two-letter labels, as ICANN has publicly stated, ICANN is currently developing a process pursuant to which it can determine whether, and under what circumstances, ICANN might authorize release of objected-to two-letter labels. As such, ICANN has not yet evaluated or fully considered the merits of the governmental objections. ICANN's lack of action to date in that regard, however, is not inconsistent with any established policy or procedure. The BGC therefore concludes that Request 15-11 should be denied. The Bylaws authorize the BGC to make a final determination on reconsideration requests brought regarding staff action or inaction. Request 15-11 seeks reconsideration of a staff action or inaction. As such, the BGC concludes that this determination is final and that no further consideration by the Board is warranted. The BGC notates that it will continue to monitor the development of the criteria and process for evaluating objections to the release of certain two-letter labels, and will continue to urge staff to proceed as expeditiously as practicable.

  3. Reconsideration Request 15-14 – Staff briefed the BGC regarding the request submitted by Foggy Sunset, LLC seeking reconsideration of the Community Priority Evaluation panel's report ("CPE Report"), and ICANN's acceptance of the CPE Report, finding that Asia Spa and Wellness Promotion Council Limited's ("ASWPC's") application for .SPA prevailed in Community Priority Evaluation ("CPE") for that string. In light of the CPE results, the contention set for .SPA has been resolved and only ASWPC's application will proceed. Specifically, the Requester claims that the CPE panel evaluating ASWPC's Application ("CPE Panel") violated established policy or procedure by considering letters of support for the Application that were submitted more than 14 days after the Application was invited to CPE. After discussion, the BGC sought additional information and clarification from Staff regarding the CPE process and agreed to continue its discussion regarding Request 15-14 at the next BGC meeting.

    • Action: Staff to revise materials for further consideration by the BGC at its next meeting.

  4. Nominating Committee (NomCom) Chair and Chair-Elect – The BGC discussed the Expressions of Interest for the 2016 NomCom Chair and Chair-Elect.

Published 1 October 2015

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"""" is not an IDN."