Skip to main content

Minutes - Risk Committee Meeting

Committee Attendees: Bruce Tonkin – Chair, Steve Crocker, Steve Goldstein, Ray Plzak, and Rajasekhar Ramaraj

Apologies: Wendy Seltzer

Other Board attendees: Peter Dengate Thrush and Suzanne Woolf

Staff members present: Doug Brent, Samantha Eisner, Dan Halloran, Greg Rattray, Theresa Swinehart, and Kevin Wilson

Invited attendee: Jim Negus, KPMG

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

  • Received update on and discussed ongoing efforts to formalize a successful risk management process within the organization and the risk identification process, including:
    • Staff engaged KPMG to assist staff to create an enterprise risk assessment;
    • ICANN established a common risk framework and nomenclature to guide future risk assessments;
    • Risks were divided into five primary categories with a total of 26 risks assessed. The risk categories were: credit, legal, market/pricing, strategic, and reputation;
    • Each risk was assessed via graph, with the Y axis representing severity to ICANN if the risk occurs (minor, moderate, major, severe, catastrophic) and X Axis representing the likelihood of the risk occurring (highly unlikely, unlikely, likely, probably, nearly certain).  A risk score for each risk was then determined for each risk as a combination of severity and likelihood.

The Risk Committee gave some feedback on the risk categories and also terminology to ensure an understanding of the impact of a risk is clear from its description.

    • Actions:
      • Staff to continue to refine work.
      • Staff to provide draft charter for proposed institution of a management committee overseeing enterprise risk management processes.
      • Staff to draft proposed enterprise risk management policy for organization.
      • For Seoul, Staff to present Risk Committee with remediation recommendations for 12-month forecast items and proposals for threshold setting, and with risk assessments for a three-year timeframe to align with strategic plan periods.
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."