Skip to main content

Board Risk Committee (RC) Meeting – Minutes

RC Attendees:  Steve Crocker (Chair), Rajasekhar Ramaraj, Mike Silber, Bruce Tonkin and Suzanne Woolf
Other Board attendees: Erika Mann and Thomas Narten

Staff Attendees:  Akram Atallah – Chief Operating Officer; Elise Gerich – Vice President, IANA; John Jeffrey – General Counsel and Secretary; Jeff Moss – Chief Security Officer; Samantha Eisner, Patrick Jones, Amy Stathos, and Alina Syunkova

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

  1. Minutes: The Committee reviewed and approved minutes of the prior RC meeting.

  2. New gTLD Program: Staff provided a briefing to the RC on the updated risk analysis report, including risk analysis, planning and mitigation measures.  The RC discussed additional items for inclusion in the plan, and noted that it has looked closely and provided commentary to staff and continues to work through assessing risks and mitigation.  The RC approved forwarding revised risk analysis to the Board.

    • Actions:

      • Staff to include note of the RC’s work in this area in the report to the community at the Singapore meeting.

      • Staff to forward risk assessment to Board, noting changes in the new version.

      • Staff to conduct scoring and rating over identified risks, for presentation at a later RC meeting.

  3. Affirmation of Commitments: The RC briefly discussed monitoring the progress of meeting the responsibilities under the Affirmation of Commitments.

    • Action:

      • Staff to confirm that a project-level presentation on risk analysis for meeting the Affirmation of Commitments be placed on the agenda for the next RC meeting.

  4. DNS Systemic Risk Efforts: The RC received a briefing from staff on DNS Systemic Risk Efforts, including the revisions to the SSAC-related Bylaws, the work to create a working group to address responsibility for security issues removed from the SSAC-related Bylaws, and the work of the community DSSA group.

    • Action:

      • The new Chief Security Officer to meet with RC at a future face-to-face meeting to discuss a plan to address DNS Systemic risks.

  5. Enterprise Risk Reassessment: The RC received an update from staff on the enterprise risk reassessment work.  The RC discussed the need to include a risk mediation strategy as well as reporting on completion of mitigation efforts.

  6. Agenda Planning: The RC discussed the next meeting, including scheduling and agenda setting.

    • Actions:

      • Staff to schedule the next RC meeting.

      • Staff to include a project-level risk management presentation on ICANN’s IDN work, including IDN variants.  Staff is also to brief on IANA department as well as internal IT and business continuity/contingency risk planning, and an update on new gTLDs.

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