Skip to main content

Audit Committee (AC) Meeting Minutes

AC Attendees: Bill Graham, Olga Madruga-Forti, Erika Mann – Chair, and Ray Plzak

Other Board Attendees: Cherine Chalaby, Steve Crocker, George Sadowsky

ICANN Executives and Staff Attendees: Susanna Bennett (Chief Operating Officer), Megan Bishop (Board Support Coordinator), Michelle Bright (Board Support Manager), Xavier Calvez (Chief Financial Officer), John Jeffrey (General Counsel and Secretary), Jacks Khawaja (Enterprise Risk Director), Elizabeth Le (Senior Counsel), and Amy Stathos (Deputy General Counsel).

Apologies: Gonzalo Navarro

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

  1. Minutes – The AC approved the minutes from the 16 November 2013 meeting.

  2. Auditors Renewal Process – Staff provided an update of the auditor selection process for FY14 audit. The AC previously agreed that ICANN would engage in a more comprehensive selection process for the FY14 auditors to accommodate for the growth and internationalization of ICANN, and that the engagement would be conducted through a Request for Proposal (RFP) process. Staff reported on the various issues that need to be considered with respect to the RFP, including whether or not we will receive responses from the firms that we hope to engage. The AC agreed that the RFP process should include international firms and national firms that have affiliation with international networks. The AC revisited the timeline for the process. The plan is to select the independent auditor for FY14 by the end of March 2014. The AC discussed the need for a criteria list for the selection process. The AC will approve the criteria list prior to the launch of the RFP.

    • Action: Staff to prepare list of criteria for RFP selection process for AC approval

  3. Cross Committees Review – The AC engaged in a discussion on whether the right structure currently exists to address various risks within the organization. The AC suggested having a discussion with the Chairs of the Audit, Finance, Risk Committees and the NPGC to further discuss this issue. The purpose of the cross-Committees review is to identify risks, assess potential gaps, mitigating risks, and oversight.

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