Skip to main content
Resources

Minutes | Board Accountability Mechanisms Committee (BAMC) Meeting

BAMC Attendees: Alan Barrett, Becky Burr, Edmon Chung, Patricio Poblete, León Sánchez, and Katrina Sataki

BAMC Member Appologies: Sarah Deutsch

ICANN organization Attendees: Franco Carrasco (Board Operations Specialist), Casandra Furey (Associate General Counsel), John Jeffrey (General Counsel and Secretary), Elizabeth Le (Associate General Counsel), Wendy Profit (Board Operations Senior Manager), and Amy Stathos (Deputy General Counsel)


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

  1. Consideration of the Afilias Domains No. 3 Ltd. (Afilias) v. ICANN Independent Review Process (.WEB IRP) Final Declaration – Edmon Chung recused himself from the discussion noting potential conflicts of interest. At its 16 January 2022 meeting, the Board requested that the BAMC review, consider, and evaluate the .WEB IRP Final Declaration and recommendation, and provide the Board with its findings to consider and act upon before the organization takes any further action toward contracting for or delegation of .WEB. The Committee reviewed and discussed the background of the .WEB contention set as well as the .WEB IRP Final Declaration and the recommendation in that declaration. The Committee discussed that in light of the Panel's determinations and recommendation in the Final Declaration, as well as the claims raised in the IRP and in additional correspondence, it seems appropriate for ICANN to undertake an analysis of the allegations regarding the Domain Acquisition Agreement (DAA) between Nu Dotco, LLC (NDC) and Verisign, Inc. regarding .WEB, as well as the allegations regarding Afilias' conduct during the Auction Blackout Period in order to determine if any consequences are warranted with respect to any of the .WEB applications before moving forward with .WEB. Following discussion, the BAMC agreed to recommend that the Board: (a) ask the BAMC to review, consider and evaluate the claims relating to the DAA and the claims relating to Afilias' conduct during the Auction Blackout Period; (b) ask the BAMC to provide the Board with its findings and recommendations as to whether the alleged actions of NDC and/or Afilias warrant disqualification or other consequences, if any, related to any relevant .WEB application; and (c) direct ICANN to continue refraining from contracting for or delegation of .WEB until ICANN has made its determination regarding the .WEB application(s).

    • Actions: ICANN org to prepare relevant Board materials.
  2. Update re IRP Standing Panel Selection Process – The BAMC received an status update on the composition of the omnibus IRP Standing Panel. The org reported that on 17 February 2022, the names of the IRP Community Representatives Group were announced (Group). The Group members, which were empowered by Supporting Organizations and Advisory Committtees, are responsible for proposing a slate of nominees, for confirmation by the ICANN Board of Directors, to constitute the omnibus Standing Panel that will hear and resolve disputes filed under the IRP described in the ICANN Bylaws. The IRP Standing Panel candidates (Candidates) have been informed of the Group membership and have been asked to identify if they know any of the Group members. The Rules of Engagement, which govern how the parties involved in the selection process should conduct themselves, have been finalized and shared with the Candidates and the Group members. A first meeting of Group is being organized for immediately after ICANN73.

Published on 7 April 2022

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