Skip to main content
Resources

Minutes – Board Risk Committee (BRC) Meeting

Published on 8 May 2016

BRC Attendees: Rafael Lito Ibarra, Ram Mohan (Co-Chair), George Sadowsky, Mike Silber (Co-Chair), Jonne Soininen, Kuo-Wei Wu, and Suzanne Woolf

Other Board Member Attendees: Asha Hemrajani and Rinalia Abdul Rahim

Invited Attendees: Göran Marby

ICANN Executives and Staff Attendees: Susanna Bennett (Chief Operating Officer), Megan Bishop (Board Operations Coordinator), Xavier Calvez (Chief Financial Officer), Vinciane Koenigsfeld (Board Operations Content Manager), Ashwin Rangan (Chief Innovation and Information Officer), and Amy Stathos (Deputy General Counsel)


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

  1. Minutes – The BRC approved the minutes of the 19 June 2015, 9 November 2015, and 1 February 2016 meetings.

  2. BRC Workplan – Staff provided an overview of the updated BRC Workplan for the 2016 calendar year and explained that it may be further updated based upon the finalized version of the three-year Enterprise Risk Management (ERM) strategy roadmap. The Workplan also includes reviews of ICANN's cybersecurity efforts every six months.

    • Action:

      • Staff to update BRC Workplan to include items regarding risk implications of the IANA stewardship transition and resulting accountability work, as well as further revisions based upon the finalized ERM strategy roadmap.

  3. Quarterly Risk Assessment Update – Staff provided an overview of the quarterly risk assessment of ICANN's risk matrix, which contains approximately 30-35 identified risks, and informed the BRC that no new top ten risks have been identified. Staff explained that the identified risks are monitored on an on-going basis, and the risks to be included in the top ten are re-assessed annually and/or on an as-needed basis.

    • Actions:

      • Staff to assess and discuss with the BRC members, and then provide a summary to the BRC regarding IANA Stewardship transition-related risk implications and whether any new risks should be included in the top ten risks.

      • Staff to assess and recommend to the BRC how to include and monitor potential risks, if any, associated with the DNSSEC key rollover.

  4. ERM Strategy Roadmap – Staff provided an overview of the ERM strategy and roadmap, as well as the current status and target positions for each of the seven types of risk management activities. Staff further explained that the ERM roadmap defines the risk management strategy at ICANN for the next three years. The BRC continued (from the last meeting) to discuss the categories of risk management activities, the appropriate target positions, the proposed timeline and objectives to reach each target position, as well as the key success factors used to measure progress.

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