Skip to main content

Minutes | Board Accountability Mechanisms Committee (BAMC) Meeting

Board Accountability Mechanisms Committee (BAMC) Attendees: Becky Burr, Sarah Deutsch, Chris Disspain, Nigel Roberts, and León Sanchez (Chair)

Other Board Member Attendees: Khaled Koubaa, and Tripti Sinha

ICANN Organization Attendees: Susanna Bennett (SVP, Chief Operating Officer), Franco Carrasco (Board Operations Specialist), Samantha Eisner (Deputy General Counsel), John Jeffrey (General Counsel and Secretary), Vinciane Koenigsfeld (Director, Board Operations), Elizabeth Le (Associate General Counsel), and Amy Stathos (Deputy General Counsel)

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

  1. Independent Review Process (IRP) Implementation Oversight Team's (IOT) composition - The Committee discussed the status of the work on recomposing the IOT. The BAMC noted that pursuant to Article 4, Section 4.3(n) of the ICANN Bylaws, the establishment of the IOT is ICANN's responsibility in consultation with the Supporting Organizations (SOs) and Advisory Committees (ACs). As the Board committee with oversight role of ICANN's accountability mechanisms, the BAMC considers the work of the IOT to be paramount to ICANN's accountability and is committed to ensuring that, in fulfilling its responsibility, the work of the IOT is completed in a timely and efficient manner. The BAMC acknowledged that while ICANN org previously issued a call for more volunteers to join as members of the IOT, more detail should be provided to the SOs and ACs to assist in helping ICANN achieve a broader and active membership. The BAMC noted that it will ask the SOs and ACs, in their consultation role on the membership of the IOT, to assist with circulating the call for expressions of interest to their membership and engage with those people in their membership and network that meet the skills and availability, and encourage them to apply. The BAMC noted that the SOs and ACs have requested additional information, particularly in the skills and experience required, targeted size of the recomposed IOT, and the deadline by which expressions of interests should be submitted. In terms of the skills and experience required, the BAMC agreed that interested members should have the necessary legal or judicial skills and experience in disputes such as IRPs, arbitrations, or other alternate dispute resolution processes. Specific familiarity with ICANN's accountability mechanisms is another important skill. The members must also have the time and availability to attend at least a one hour call each week to participate in on IOT telephonic meetings, as well as sufficient availability to contribute to the work online. The BAMC agreed that the targeted size of the recomposed IOT is an additional six to ten new active members would be ideal to increase participation and diversity of the group, in addition to the existing IOT members, if they wish to remain. The BAMC agreed that small, focused, dedicated group is appropriate for this specialty work, and potentially doubling the size of the currently active membership is expected to result in a group that can meet quorum while bringing skilled new voices to the table.

    • Action(s): ICANN org to draft letter from BAMC to SO and AC leadership to provide more information on the skills and experience required and the targeted size of the recomposed IOT.

  2. Litigation Update - The BAMC received a litigation update.

Published on 11 July 2019

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