Skip to main content
Resources

Minutes – Board Risk Committee (BRC) Meeting

BRC Attendees: Rafael Lito Ibarra, Ram Mohan (Co-Chair), George Sadowsky, Mike Silber (Co-Chair), Jonne Soininen, Kuo-Wei Wu, and Suzanne Woolf

Other Board Member Attendees: Asha Hemrajani

Board Member Elect Observing: Maartern Botterman, Akinori Maemura,

ICANN Organization Attendees: Susanna Bennett (Chief Operating Officer), Xavier Calvez (Chief Financial Officer), David Conrad (Chief Technology Officer), Samantha Eisner (Deputy General Counsel), John Jeffrey (General Counsel & Secretary), Melissa King (VP, Board Operations), Elizabeth Le (Senior Counsel), Wendy Profit (Board Operations Specialist), and Amy Stathos (Deputy General Counsel)


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

  1. Minutes – The BRC approved the minutes of the 26 June 2016 meeting.

  2. Overview of BRC Charter – The Committee reviewed and discussed its Charter as approved by the Board on 6 March 2009, and whether any refinements or revisions would be appropriate to capture the scope and purpose of the Committee.

    • Actions:

      • BRC members to review the current Charter and provide any suggested refinements or revisions by 18 November 2016.
      • Prepare draft Charter incorporating proposed revisions for approval by the BRC and then submitting to the Board Governance Committee.
  3. Community Engagement Strategy – The Committee continued its discussion regarding the strategy for community engagement relative to risk assessment. Specifically, the BRC focused on two facets: (1) what need is the BRC trying to address (such as accountability, transparency, and community engagement); and (2) how the BRC can address these needs. The BRC noted the positive community feedback with prior engagement efforts of an ad hoc working group for the budget and discussed whether a similar approach would be appropriate relative to risk assessment. Participation to the ad hoc working group would be open to any community member with interest. The BRC agreed to launch the community engagement strategy at ICANN 58.

    • Actions:

      • Provide invitation to BRC Co-Chairs to send to the community to join the working group.
      • Prepare to launch working group at ICANN 58.
  4. Communication Between the BRC and the Board – The BRC reviewed and discussed its efforts to support Board members' exercise of their responsibility in managing risk. In June 2016, the BRC initiated a BRC activity report that will be submitted to the Board semi-annually. The BRC has conducted two risk workshops in the past year. One of the Co-Chairs noted that a risk workshop at every meeting could be an on-going approach to exchanging on risk assessment and mitigation within the Board.

    • Actions:

      • Prepare additional presentation materials for workshop setting forth the objectives of the session.
      • Consider including a stress test process of the mitigation plan in the next workshop.
  5. AOB - BRC Member Position Description – The BRC addressed the question that the BGC has asked, which is what attributes do the BRC believe are appropriate for a BRC member to have. The BRC noted that the Committee deals with technical, legal, policy, operational, and financial risks. The BRC identified some general skills and qualities it believes a BRC member should have, and agreed to draft a BRC member position description to provide to the BGC.

    • Action:

      • Document a position description for Risk Committee members.

Published on 1 February 2017

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