Skip to main content
Resources

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)

Invited Observers: Ihab Osman

ICANN Organization Attendees: Samantha Eisner (Deputy General Counsel), John Jeffrey (General Counsel and Secretary), Aaron Jimenez (Board Operations Sr. Coordinator), Elizabeth Le (Associate General Counsel), and Amy Stathos (Deputy General Counsel)


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

  1. Recomposition of Independent Review Process Implementation Oversight Team (IRP-IOT) – The BAMC discussed the expressions of interests to join the IRP-IOT that were submitted. The BAMC also discussed the results of the follow up for additional information from some candidates that did not provide sufficient information for the BAMC to determine their substantive qualifications and/or time availability. ICANN org also reported on the responses received from the current IRP-IOT members who have actively participated in the IRP-IOT since January 2018, noting their interests in continuing with the IRP-IOT. The BAMC agreed to recommend that the Board affirm the work of the BAMC on the recomposition of the IRP-IOT.

    • Action(s):

      • ICANN Org to prepare relevant materials for Board consideration online.
  2. Update on Status of Establishment of IRP Standing Panel The BAMC was provided with a briefing on the status of establishment of IRP standing panel. The BAMC agreed with the recommendation to issue the Call for Expressions of Interest accompanied by a blog.

    • Action(s):

      • ICANN org to draft blog and circulate online for BAMC feedback.
      • Once blog is approved, ICANN org to issue Call of Expressions of Interest.
  3. Litigation Update - The BAMC received a litigation update.

Published on 21 November 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""icann.org"" is not an IDN."