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 Apologies: Sarah Deutsch

Other Board Member Attendees: Manal Ismail

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


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

  1. Legal Invoices for Dispute Matters and Status Report on Spending: Edmon Chung recused himself from discussing and voting on the matter, noting potential conflicts of interest. The BAMC reviewed and approved a recommendation to the Board to approve a tranche of money for payment of legal invoices and fees related to certain dispute matters. The BAMC also received a report on expenses incurred related to dispute matters for which the spend amount was previously approved by the Board.

    • Action: ICANN org to prepare relevant Board materials.
  2. Litigation Update – The BAMC received a litigation update.
  3. Update on the Independent Review Process Implementation (IRP) Oversight Team (IOT) Progress - The BAMC received a briefing on the progress on the work underway in the IRP-IOT. The IOT's scope of work includes: finalizing updated IRP Supplementary Procedures; developing rules for Cooperative Engagement Process (CEP); making recommendations of trainings for IRP Standing Panel; developing recall process for Standing Panel members; developing rules governing appeals from IRP panel decisions; developing procedures if ICANN elects not to respond to an IRP; considering developing additional independence requirements for panelists; considering designing specialized rules for PTI service complaints; and developments re Bylaws Sec. 4.3(y). The BAMC noted that the IRP-IOT has been focusing its work over the past two years on updating the IRP Supplementary Procedures, and that much of this work has centered on the time for filing an IRP rule. The IRP-IOT has also created subgroups to address the remaining areas of the Supplementary Procedures. The BAMC discussed the importance of moving the work on updating the Supplementary Procedures along and asked ICANN org for recommendations on how to move the work along. The BAMC noted that there is a vacancy on the IRP-IOT in one of the Board membership positions previously held by Nigel Roberts. The BAMC Chair noted that she will ask the Chair of the Board Governance Committee (BGC) to issue a call for interested Board members to serve as a member on the IRP-IOT.

    • Actions

      • BAMC Chair to ask BGC Chair to issue a call for expressions of interest to serve as a member on the IRP-IOT.
      • ICANN org to recommend ways to move the work of the IRP-IOT along.

Published on 04 February 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."