Skip to main content
Resources

Minutes – Board Risk Committee (BRC) Meeting

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

BRC Member Apologies: Matthew Shears.

ICANN org Attendees: Xavier Calvez (Chief Financial Officer), James Caulfield (Vice President, Enterprise Risk Management), Ashwin Rangan (Sr. VP Engineering & Chief Information Officer), and Amy Stathos (Deputy General Counsel).


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

  1. Risk Management Implementation Timelines – The BRC received an update about the revised timelines for the two major projects taking place this year: an updated functional and organizational level risk identification process and an operational resiliency planning exercise. With respect to the functional risk identification process, ICANN organization is currently engaged in this process, which is on target as scheduled. The risk identification process will create an updated functional risk register. The functional risk register will then feed into an organizational level risk register. The organizational risk register will them inform the risk appetite statement that will be created. The risk appetite statement will describe the types of risk that we have at ICANN and our level of appetite for each of the risks or groups of risks. The BRC engaged in a discussion regarding the adding of certain additional risks to the organizational level risk register. With respect to the operational resiliency planning project, that is on schedule for the second half of the year.
  2. Quarterly Risk Register Update – The BRC received an update on the quarterly risk register. Across the top ten risks, inherent risk went up slightly, but control effectiveness associated with some new risks is better than it was previously, and as a result, residual risk went up. The BRC then discussed the changes made to the organizational level risk register since last quarter.
  3. Draft Risk Report to the Board – The BRC discussed the draft Risk Report to the Board. The BRC discussed presenting the Risk Report and accompanying presentation to the full Board during the May Board Workshop.
    • Action(s):
      • ICANN org to provide draft Risk Report to the ICANN org President and CEO for review.
      • BRC members to provide further comments to the Risk Report via email.
  4. IT – New Cybersecurity Framework – The BRC was presented with some general knowledge about the value of cybersecurity frameworks and received a brief introduction to the various available cybersecurity frameworks.

Published on 22 May, 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."