Skip to main content

Minutes | Board Audit Committee (BAC) Meeting

BAC Attendees: Alan Barrett, Sarah Deutsch (Chair), Mandla Msimang, Ihab Osman, Kaveh Ranjbar, and Katrina Sataki

BAC Member Apologies: Akinori Maemura

Other Board Member Attendees: Avri Doria and Patricio Poblete

ICANN Organization Attendees: Xavier Calvez (SVP, Planning and Chief Financial Officer), Franco Carrasco (Board Operations Specialist), Liz Le (Associate General Counsel), Becky Nash (VP of Planning), Brett Peterson (Director Accounting), Shani Quidwai (Sr. Director Finance), and Amy Stathos (Deputy General Counsel)

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

  1. Opening Remarks The Chair opened the meeting and reviewed the meeting agenda.
  2. BAC Work Plan – The Committee reviewed its work plan which is currently on track.

  3. Request for Proposal (RFP) for Independent Audit Services – The BAC previously recommended that ICANN org perform a Request for Proposal (RFP) for the independent audit services for both ICANN and its wholly owned subsidiary, Public Technical Identifiers (PTI), for FY22, considering that the most recent audit firm has performed such services for the past eight years. The BAC received a briefing on the RFP that was conducted from 1 December 2021 to 5 January 2022. ICANN issued the direct RFP to 11 audit firms. Five of the 11 firms participated in the RFP. The BAC reviewed and discussed the vetting process that carried out by the org, which included a 75-part questionnaire and oral presentations from all five candidates. The BAC reviewed and discussed firms' qualifications and costs proposals, and ICANN org's recommendation. Following discussion, the BAC agreed to recommend that the Board approve the engagement of the firm recommended by ICANN org to provide independent audit services for the fiscal year ending 30 June 2022. The BAC noted that the reporting of this matter at the Committee and Board level will remain at a high level, and, where necessary, certain confidential information will be withheld from disclosure for negotiation purposes.
    • Actions: ICANN org to prepare relevant Board materials.

Published on 3 May 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"""" is not an IDN."