Skip to main content

Minutes – Board Risk Committee (BRC) Meeting

BRC Attendees: Bruce Tonkin – Chair; Steve Crocker, Rajasekhar Ramaraj, Mike Silber, and Suzanne Woolf

Other Board Attendees: Peter Dengate Thrush

Staff Attendees: Akram Atallah, Chief Operating Officer; John Jeffrey, General Counsel and Secretary; Tina Dam, Daniel Halloran, Patrick Jones, Rick Lamb, and Diane Schroeder.

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

  1. Minutes: Reviewed and approved minutes from previous BRC meeting.

  2. Matter arising from the minutes: communications between ICANN, RSSAC and root operators regarding root scaling.

    • Action:

      • BRC Chair will formalize communications with RSSAC Chair, Vice-Chair, and RSSAC Board Liaison on this topic.

  3. Action Items: Staff provided an update on pending action items, including reporting thresholds for Risk Oversight Management Team and availability of incident reports.

  4. IPv4 Address Depletion: Discussed communications with RIRs on risks relating to IPv4 address depletion issues. IANA staff are reaching out to RIRs and should have more information after the next IETF meeting.

  5. IDN Program: Reviewed IDN program risks and mitigation measures, including staffing, relationship between fast-track and new gTLD programs, review of fast track, IDNA protocol revision, variant management, and general compliance with IDN requirements such as the guidelines, for both top and second level IDNs.

  6. DNSSEC Program: Reviewed DNSSEC program risks and mitigation measures, including operational risks, and lack of up-take at the application level.

    • Action:

      • Staff to provide an update on operational risks and mitigation responses in light of the past .ARPA DNSSEC issue.

  7. Discussed the possibility of a brief BRC discussion in Cartagena, for purposes including a review of the proposed BRC workplan.

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