Skip to main content
Resources

Minutes | Board Audit Committee (AC) Meeting

BAC Attendees: Sarah Deutsch, Akinori Maemura and Lousewies van der Laan (Chair).

BAC Member Apologies: Mike Silber.

Other Board Member Attendees: Cherine Chalaby and Avri Doria.

ICANN Organization Attendees: Xavier Calvez (Chief Financial Officer), Becky Nash (VP, Finance), John Jeffrey (General Counsel & Secretary), and Amy Stathos (Deputy General Counsel).


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

  1. Recommendation for the Renewal of Independent Auditors – The BAC was presented with the recommendation to approve its current audit firm as ICANN's independent auditors for the FY18 audit. The current firm has been engaged as ICANN's independent auditor firm since FY14. The FY18 proposed audit work includes the ICANN consolidated financial statements, which includes Public Technical Identifiers costs. The Committee discussed the benefits of re-engaging the same firm for the FY18 audit. Specifically, the BAC discussed that the current firm is knowledgeable of PTI as they were the auditor firm last year for the independent audit and also for the consolidated results. The current firm is also very knowledgeable of the New gTLD Program. The BAC noted that having the current auditor firm for FY18 with the knowledge of the environment, the transactions, does improve the quality of the audit and minimize any risk. In addition, it does result in a more efficient audit process given their knowledge and experience. After discussion, the BAC agreed to recommend to the Board to authorize the President and CEO to take all steps necessary to engage the current audit firm as ICANN's annual independent auditor for the FY18 audit. The BAC engaged in a discussion regarding best practices in the selection of independent auditors. The Committee agreed that a paper should be developed after ICANN61 for the Board to look at the different options, changing firms, changing partner within the same firm or not changing for the future audits.
    • Actions:
      • ICANN organization to prepare the relevant materials for Board consideration.
      • ICANN organization to develop a paper after ICANN61 for the Board to look at the different options, changing firms, changing partner within the same firm or not changing for the future audits.
  2. Executive Interviews – The BAC agreed to that it would as a best practice it should to continue holding executive interviews, without other staff present, to allow the BAC to get direct input from ICANN organization executives on any issues they might have. The interviews allow executives to speak to the BAC about any topic in a less formal and unscripted manner. The BAC agreed to schedule the interviews at upcoming ICANN Public meetings. The Committee discussed that they should re-evaluate whether the right people are being interviewed, whether others should be interviewed, and the order of the interview sessions.
  3. AOB – The BAC discussed the agenda for its meeting during ICANN61.

Published on 26 April 2018

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