Skip to main content

Minutes | Board Accountability Mechanisms Committee (BAMC) Meeting

Board Accountability Mechanisms Committee (BAMC) Attendees: Becky Burr, Sarah Deutsch, Chris Disspain (Chair), Léon Sanchez, and Mike Silber

Other Board Member Attendees: Cherine Chalaby and Göran Marby  

ICANN Organization Attendees: Akram Atallah (President, Global Domains Division), Casandra Furey (Associate General Counsel), John Jeffrey (General Counsel and Secretary), Aaron Jimenez (Board Operations Senior Coordinator), Tarek Kamel (Sr. Advisor to President & SVP, Government and IGO Engagement), Vinciane Koenigsfeld (Board Training & Content Senior Manager), Elizabeth Le (Associate General Counsel), Wendy Profit (Manager, Board Operations), Lisa Saulino (Board Operations Senior Coordinator), and Amy Stathos (Deputy General Counsel)

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

  1. Further consideration of Gulf Corporation Council (GCC) v. ICANN Independent Review Process (IRP) Final Declaration (.PERSIANGULF) – The Committee considered and discussed some of IRP Panel's factual premises and conclusions in the Final Declaration. The Committee asked ICANN Org to conduct a further comprehensive evaluation of the Final Declaration to identify all the concerns and the evidentiary support for such concerns that were identified by the IRP Panel.
    • Action: ICANN Org to conduct a further comprehensive evaluation of the Final Declaration to identify all the concerns and the evidentiary support for such concerns that were identified by the IRP Panel.
  2. Consideration of the Asia Green IT System Bilgisayar San. ve Tic. Ltd. Sti. (AGIT) v. ICANN IRP Final Declaration (.HALAL/.ISLAM) – The  BAMC discussed AGIT IRP Final Declaration and approved recommendation to the Board to accept the finding by the IRP Panel that AGIT is the prevailing party; to direct ICANN Org to reimburse AGIT in the amount declared by the Panel; and to direct the BAMC to evaluate the findings in the Final Declaration and the GAC non-consensus advice as well as the subsequent communications from or with objecting and supporting parties, in light of the Final Declaration, and provide a recommendation to the Board as to whether or not the applications for .HALAL and .ISLAM should proceed.
    • Action: ICANN Org to prepare materials for Board consideration.
  3. Next Steps on Community Priority Evaluation (CPE) Process Review (Review) – Becky Burr abstained from consideration of this matter, noting potential conflicts. The Committee noted that the three reports on the CPE Process Review were published on 13 December 2017 and discussed the next steps in the Review. The BAMC also discussed the correspondence that have been received since the publication of the reports. The BAMC approved a recommendation to the Board to acknowledge and accept the findings in the three reports; that as a result of the findings, there will be no overhaul or change to the CPE process in the current New gTLD round; that the CPE Process Review has been completed; and that the BAMC should move forward with consideration of the remaining reconsideration requests relating to the CPE process that were placed on hold pending completion of the CPE Process Review and to take FTI's findings into consideration as part of the BAMC's review.
    • Actions:
      • ICANN Org to prepare materials for Board consideration.
  4. Update on the New IRP – The BAMC received an update on the community's work related to the revised IRP, including a status update on the Supplementary Rules of Procedure as well as the work relating to the establishment of the IRP standing panel. The BAMC was informed that the work related to the establishment of the standing panel has begun and that ICANN Org held a webinar earlier in the day with the leadership of the Supporting Organizations and Advisory Committees to begin the cross-community discussion concerning what processes are required to establish the standing panel.
  5. Update on the Status of .WEBS application – The Committee received an update on the .WEBS application.

Published on 12 February 2018

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