Skip to main content
Resources

Minutes | Board Risk Committee (RC)

RC Attendees: Steve Crocker, Bill Graham, Ram Mohan, Mike Silber – Chair, Jonne Soininen, Kuo-Wei Wu, Gonzalo Navarro, and Suzanne Woolf

Other Board Member Attendees: Erika Mann

Executive and Staff Attendees: Susanna Bennett (Chief Operating Officer), Megan Bishop (Board Support Coordinator), Xavier Calvez (Chief Financial Officer), John Jeffrey (General Counsel and Secretary), Jacks Khawaja (Enterprise Risk Director), Cyrus Namazi (Vice President, DNS Industry Engagement), Francisco Arias (Director, Technical Services), Akram Atallah (President, Global Domains Division), Ashwin Rangan (Chief Innovation & Information Officer), and Amy Stathos (Deputy General Counsel)

Invited Attendees: Rinalia Abdul Rahim, Markus Kummer, and Asha Hemrajani


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

  1. Action items – Staff provided a recap of the action items stemming from ICANN 50 in London and indicated that most of the noted action items will be addressed in this RC meeting.

  2. New gTLD Risk Quantification Update – Staff provided the RC with a status update on the new gTLD risk quantification project. There are several objectives of the risk quantification. They are to: (i) identify key risks of the New gTLD Program; (ii) quantify the cost of the risks to ICANN associated with the New gTLD Program; (iii) review the risks for mitigation efforts and existing controls; and (iv) then create a communications plan.

    • Action: Staff to prepare a summary of the new gTLD risk quantification update to share with the community, with the goal being ICANN 51 in Los Angeles.

  3. Name Collision Update – Staff provided an update on: (i) the Name Collision Occurrence Management Framework; (ii) the action items stemming from ICANN 50 in London; (iii) issues that have been identified to date.

  4. Universal Acceptance Roadmap and Communications Plan – Staff provided an update on the status of the Universal Acceptance Roadmap, informed the RC that there were no major changes suggested by the community through the public comment period, and indicated that the final Roadmap will be published soon. Staff provided an update on the status of the Communications Plan, informed the RC that staff is incorporating suggestions from the community provided through the public comment period, and indicated that the Communications Plan should be ready by the end of the month.

  5. Enterprise Risk Management Dashboard – Staff provided an update on the progress of the ERM Dashboard, which includes prioritization of risks and refinement of the KPIs. The RC discussed issues regarding prioritization, application of KPIs, and timing of the presentation of the ERM Dashboard data. Staff provided an overview of next steps, which include: (i) gathering the 2015 risk ratings; (ii) ranking the risks according to likelihood and severity of that risk; and (iii) creating a summary of the most critical risks affecting ICANN.

  6. DNS Risk Assessment – Staff provided a brief update on the DNS Risk Assessment. Staff will provide documentation regarding the top DNS-related risks for ICANN 51 in Los Angeles.

    • Action: Staff to prepare materials regarding top DNS-related risks for ICANN 51 in Los Angeles.

Published on 18 September 2014

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