Skip to main content

Minutes - Risk Committee (RC) Meeting

RC Attendees: Bruce Tonkin – Chair; Steve Crocker, and Rajasekhar Ramaraj

RC Apologies: Mike Silber, Suzanne Woolf

Other Board Member Board Attendee: Dennis Jennings

Staff Attendees: Doug Brent – Chief Operating Officer; Samantha Eisner, Patrick Jones, Greg Rattray, Michael Salazar, Diane Schroeder , and Amy Stathos

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

  1. Reviewed the proposed RC work plan for future meetings.
    • Actions:
      • Staff to produce a draft Enterprise Risk Management (“ERM”) Policy (or alternatively a framework for a draft ERM Policy) prior to the Nairobi meeting.
      • Staff to create risk strategy for the evaluation of meeting venues for ICANN’s international meetings.
  2. Staff provided an update on the current risk management activities within ICANN, including the drafting of a charter for a risk oversight management team, and the ongoing work on a formal risk management process, including efforts to build risk management activities into the FY11 budget, and mitigation planning.
    • Action:
      • Staff to revise ERM process and risk factors to address committee member comments, and provide to RC for feedback.
  3. Received project level risk management updates on the New gTLD program and business continuity efforts, with a discussion of risks identified within the program.
    • Actions:
      • Staff to revise the New gTLD risk assessment to reflect RC comments.
      • Staff to facilitate communications with the root server community on root scaling activities.
      • Staff to provide an update to the RC at the meeting in Nairobi.
      • Staff to include project level risk evaluation on DNSSEC and IDNs at next committee meetings.
      • Staff to make best efforts to prepare a brief paper on risks in New gTLD program for posting, in advance of Nairobi, if time permits.
      • Staff to include project level risk evaluation for Affirmation of Commitments review process into risk factors.
      • Staff to identify availability of objective standards for auditing risk management activities.
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."