Skip to main content

Minutes | Board Risk Committee (BRC) Meeting

BRC Attendees: Harald Alvestrand (Chair), James Galvin, Danko Jevtović, Mandla Msimang, Patricio Poblete, Kaveh Ranjbar, and Matthew Shears

Other Board Member Attendees: Avri Doria, Manal Ismail, and Katrina Sataki

ICANN Organization Attendees: Xavier Calvez (SVP, Planning and Chief Financial Officer), Franco Carrasco (Board Operations Specialist), James Caulfield (Vice President, Risk Management), John Jeffrey (General Counsel and Secretary), Matt Larson (VP, Research), and Amy Stathos (Deputy General Counsel)

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

  1. Introduction from the Chair and Committee Charter Review – The Chair opened the meeting and summarized the purpose and scope of responsibilities of the Risk Committee, which is set forth in the Committee's charter.
  2. Review of Risk Committee Workplan – The Committee reviewed its workplan for calendar year 2022.
  3. Organization Risk Register Update – The Committee discussed the most recent updates to the Risk Register and reviewed the controls and mitigation in place for the updated risks. The updates are a result of a periodic validation of the Risk Register and the Risk Controls Assurance process. The Risk Register and a process change regarding the timing of updating the Risk Register was reviewed by the org's CEO Risk Management Committee and approved by the ICANN President and CEO.
  4. Risk Controls Assessment – The Committee received a briefing on the Risk Controls Assuarance process. The Risk Management Target Model specifies the maturity for risk controls assurance. The Risk Controls Assessment process was enhanced for more formality and rigor around assessment of control effectiveness for risks in the Risk Register. Every risk in the Risk Register was reviewed with its respective executive owner and all material controls in the existing controls sections of the Risk Register were deemed to be effective in reducing the residual risk. The Risk Controls Assessment was reviewed by the org's CEO Risk Management Committee and approved by the President and CEO.

Published on 6 May 2022

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