Skip to main content
Resources

Minutes | Board Accountability Mechanisms Committee (BAMC) Meeting

Board Accountability Mechanisms Committee (BAMC) Attendees: Cherine Chalaby, Chris Disspain (Chair), Asha Hemrajani, Markus Kummer, Ram Mohan, and Mike Silber

BAMC Member Apologies: Rinalia Abdul Rahim

Other Board Member Attendees: Maarten Botterman, Becky Burr, and Louswies van der Laan

Invited Observers: Sarah Deutsch and Léon Sanchez

ICANN Organization Attendees: Akram Atallah, (President, Global Domains Division), Susanna Bennett (Chief Operating Officer), Michelle Bright (Board Content Senior Manager), John Jeffrey (General Counsel and Secretary), 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. Reconsideration Request 17-4 – Becky Burr abstained from the discussion noting potential conflicts. The BAMC received a briefing on Reconsideration Request 17-4 (Request 17-4), submitted by DotMusic Limited and dotgay LLC (Requestors), seeking reconsideration of ICANN organization's response to the Requestors' request for documents, pursuant to ICANN's Documentary Information Disclosure Policy (DIDP), relating to the Community Priority Evaluation process review. Upon evaluation, the BAMC found that Request 17-4 does not set forth a proper basis for reconsideration because ICANN organization adhered to established policies and procedures in its response to the joint DIDP Request. The BAMC concluded that ICANN organization did not violate ICANN's Mission, Commitments and Core Values or established ICANN policy(ies) in its response to the joint DIDP Request. Further, the BAMC found that the Requestors do not claim that the response to the joint DIDP Request is contrary to the DIDP Response process, nor do the Requestors provide any information to show how ICANN organization's Response violates ICANN's Mission, Commitments, or Core Values.
    • Actions:
      • ICANN organization to prepare materials for Board consideration.
  2. Any Other Business
    • Amazon Independent Review Process Final Declaration - Becky Burr abstained from the discussion noting potential conflicts. The BAMC noted that at its 23 September 2017 meeting, the ICANN Board directed "the Board Accountability Mechanisms Committee (BAMC) to review and consider the [IRP] Panel's recommendation that the Board 'promptly re-evaluate Amazon's applications' and 'make an objective and independent judgment regarding whether there are, in fact, well-founded, merits-based public policy reasons for denying Amazon's applications,' and to provide options for the Board to consider in addressing the Panel's recommendation." (https://www.icann.org/resources/board-material/resolutions-2017-09-23-en#2.e) Upon discussion, the BAMC approved a recommendation that the Board ask the Governmental Advisory Committee (GAC) to provide the Board, within a set time, any new or additional information to provide to the Board as it relates to: (i) the merits-based public policy reasons, regarding the GAC's advice that the Amazon Applications should not proceed; or (ii) any other new or additional information regarding the GAC's advice that the Amazon Applications should not proceed.
      • Actions:
        • ICANN organization to prepare materials for Board consideration.

Published on 30 October 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."