Skip to main content
Resources

Minutes – Board Risk Committee (BRC) Meeting

BRC Attendees: Maarten Botterman, Rafael Lito Ibarra, Ram Mohan (Co-Chair), Mike Silber (Co-Chair), and Akinori Maemura, Kaveh Ranjbar, and Jonne Soininen

Other Board Member Attendees: Becky Burr, Chris Disspain, and Asha Hemrajani

ICANN Executives and Staff Attendees: Xavier Calvez (Chief Financial Officer), Samantha Eisner (Deputy General Counsel), Elizabeth Le (Senior Counsel), Melissa King (VP, Board Operations), Lisa Saulino (Board Operations Sr. Coordinator), Wendy Profit (Board Operations Specialist), and Ashwin Rangan (Sr. VP, Engineering & Chief Information Officer)


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

  1. Minutes – The BRC approved the minutes of the 4 November 2016 meeting.

  2. Approval of Revised BRC Charter – The BRC considered and agreed the proposed amendments to the BRC Charter. The revised Charter will be submitted to the Board Governance Committee (BGC) next for its consideration and further recommendation for adoption by the Board.

    • Action:

      • Materials to be prepared for BGC consideration.
  3. Feedback on Harvard Business School (HBS) Risk Management Seminar – The BRC received a briefing on the HBS Risk Management Seminar from the Co-Chairs and ICANN's Chief Financial Officer, who attended the seminar. The seminar was informative with three major takeaways: (1) categorizing risk will help to tailor monitoring, identification, and mitigation as well as oversight to the various categories of risk; (2) aligning the risk categories to the strategy of the Organization will help to keep track of the risks that are being monitored and make sure they are relevant to the organization, its mission and strategy; and (3) assessing risk by way of a heat map will help retain visibility on the risks that are most important, significant or impactful. The BRC discussed the importance of the notion of emerging or novel types of risks in categorizing risks. The BRC discussed developing a workshop to using an iterative voting method ("bouncecasting" method) with the framework from the seminar to assess emerging risks as well as the measures currently in place to address those risks and the effectiveness of such measures.

    • Action:

      • ICANN Organization to provide a timetable to BRC regarding a risk assessment workshop.
  4. Quarterly Risk Assessment Update – The BRC received an update on the assessment of the risk in the risk register for the period of Q4 FY16 to Q1 FY17. Since Q4 FY16, some new inherent risks have been identified relative to review effectiveness, and control effectiveness improved for the top three risks (largely driven by the IANA Stewardship Transition and progresses of the Work Stream 1 and Work Stream 2, which improvement reduced the overall residual risk rating.

    • Actions:

      • ICANN Organization to provide BRC with the process in place for addressing emerging risks that result from changes in geopolitical climate.
      • ICANN Organization to research how to classify risks related to activities driven by the community that require ICANN funds or manpower (like legal fees spend on the transition)

Published on 27 April 2017

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