Skip to main content
Resources

Board Risk Committee (RC) Meeting – Minutes

RC Attendees: Steve Crocker (Chair), Rajasekhar Ramaraj and Bruce Tonkin

Apologies: Mike Silber and Suzanne Woolf

Staff Attendees: Patrick Jones, Denise Michel, Diane Schroeder, Ken Shiu and Amy Stathos


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

  1. The Committee reviewed and approved minutes of the prior BRC meeting held on 13 March 2011.

  2. The Committee discussed the need to ensure the Board has been provided with a final risk review, including staff's risk analysis, planning and risk mitigation measures, in relation to the New gTLD Program. The committee noted the final briefing as a necessary due diligence step to be performed by the Board prior to any voting decision on the New gTLD Program.

    • Actions:

      • Staff to update the risk analysis report for the new gTLD program and circulate to the Committee

      • The Committee to schedule a briefing session for the Board at the board workshop during the Singapore meeting

  3. Staff provided the Committee with an update on the current status and internal monitoring of progress on ICANN's various responsibilities under the Affirmation of Commitments (AoC) reviews and the status of the preliminary implementation plans, which have been published.

    • Action: Staff to provide the committee with a risk and impact analysis of contingency scenarios in the event of implementation delays due to external resources.

  4. Staff discussed strategic and long-term scenario planning issues. The Committee noted that the issues discussed should already be captured in the current enterprise risk management framework and subject to regular assessment under the framework. The Committee instructed staff to verify the inclusion of these issues in the framework.

    • Action: Staff to ensure and verify issues are reflected in the current framework.

  5. At Committee Chair's request, staff provided briefing to committee on third party paper relating to insider theft of intellectual property or assets.

    • Action: Staff to determine if applicable to organization.

  6. Staff discussed proposed agenda items for the next committee meeting in Singapore.

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