Skip to main content
Resources

Board Risk Committee (RC) – Minutes

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

Other Board Member Attendees: Bruce Tonkin

ICANN Executives and Staff Attendees: Akram Atallah (President, Global Domains Division), Susanna Bennett (Chief Operating Officer), Megan Bishop (Board Support Coordinator), John Jeffrey (General Counsel and Secretary), Patrick Jones (Global Stakeholder Engagement Senior Director), Jacks Khawaja (Enterprise Risk Director), Elizabeth Le (Senior Counsel), Ashwin Rangan (Chief Innovation & Information Officer), Amy Stathos (Deputy General Counsel), and Teresa Swinehart (Sr. Advisor to the President on Strategy)

Board Member Elect: Rinalia Abdul Rahim (observing)


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

  • Minutes – The RC approved the minutes from the previous meeting.

  • DNS Risk Assessment Status Update – Staff provided an update on the DNS Risk Assessment. Since the last update, DNS risks have been identified and classified within a clear taxonomy and communicated in ICANN 49. There was a meeting with SSAC Chair, RSSAC Chair, and BRC members to discuss the current DNS Risk Assessment and next steps. The RC discussed the next steps including publication of the DNS Narrative, Framework and Risks so that there can be a dialogue with the community.

  • New gTLD Risk Assessment – The RC received a report from staff regarding the status of New gTLD Program risk assessment efforts. The RFP has closed and a vendor has been selected to perform the assessment. The RC discussed the timeline of the assessment.

  • TLD Universal Acceptance Update – Staff provided an update on TLD Universal Acceptance. The RC discussed the next steps which includes the publication of a road map for the TLD Universal Acceptance Initiative. The RC noted the importance of establishing a timeline of a path forward. The RC further noted that the Committee previously requested an analysis from staff as to what should be the scope for consideration by the RC on the TLD Universal Acceptance Initiative.

    • Action: Staff to prepare an analysis as to how universal acceptance risks should be addressed by the RC, and whether there are other risks or concerns that should be referred to other Board Committees.

  • Name Collision Mitigation Status – Staff presented the RC with a status update on the name collision mitigation status. The Name Collision Occurrence Management Framework was put out for public comment. The public comment period recently closed. Staff is the process of finalizing the analysis of the public comment, which will be published along with the updated proposal. Thereafter, the updated proposal will be submitted to the NGPC for consideration. The RC also noted that the committee is aware that the SSAC intends to issue a statement on this issue, which will be taken into account in the updated proposal.

  • Enterprise Risk Management Status Update – Staff provided an update on the ERM status and the progress that the ERM Team has made toward identifying key enterprise risks, risk interactions, and risk mitigation efforts. The RC discussed the scope of the key enterprise risks identified and the proposed remediation efforts.

Published on 9 July 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."