Skip to main content
Resources

Minutes – Board Risk Committee (BRC) Meeting

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

Invited Board Attendees: Ray Plzak and Kuo-Wei Wu

Staff Attendees: Greg Rattray – Chief Internet Security Advisor; Doug Brent – Chief Operating Officer; Elise Gerich – Vice President, IANA; Kevin Wilson – Chief Financial Officer; Joe Abley, Samantha Eisner, Patrick Jones, Olof Nordling, Diane Schroeder and Leo Vegoda.


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

  1. Staff provided an update on the status of the Risk Oversight Management Team and the Enterprise Risk Management Guidelines, which are near completion.

    • Actions:
      • Staff to ensure incorporation of risk management incident review process into Guidelines.
      • Staff to confirm that a discussion of proper reporting thresholds is on the RC’s September 2010 meeting agenda.
  2. Staff provided a report on risks relating to IPv4 depletion issues, and held a discussion regarding engaging in discussions with the Regional Internet Registries regarding those issues.

    • Action:
      • In coordination with the ROMT, staff to coordinate outreach to the Numbers Resource Organization executive committee.
  3. Staff provided an initial report regarding identification of key risk areas related to the Affirmation of Commitments, and the RC discussed additional items for consideration, including identification of key risks in performance and outcomes.

    • Action:
      • Staff to identify risk areas related to outcomes and performance measurements related to the Affirmation of Commitments.
  4. Staff provided a brief report regarding key risk areas identified in the operation of L-Root and mitigation work

  5. Prior to closing the meeting, the Chair noted that a workplan had been circulated and invited online discussion

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