Skip to main content

Board Risk Committee (RC) – Minutes

RC Attendees: Steve Crocker, Ray Plzak, Thomas Roessler, Mike Silber - Chair, Bruce Tonkin, Suzanne Woolf, and Judith Vazquez

Other Board Attendees: Erika Mann, Ram Mohan, Thomas Narten, Gonzalo Navarro Sébastien Bachollet, Chris Disspain, Bertrand de La Chapelle, Thomas Narten, and George Sadowsky

RC Apologies: R. Ramaraj

Staff Attendees: Akram Atallah – Chief Operating Officer; John Jeffrey – General Counsel and Secretary; Jeff Moss – Chief Security Officer; Kurt Pritz – Senior Vice President, Stakeholder Relations; Samantha Eisner, Patrick Jones, Amy Stathos, and Alina Syunkova

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

  1. Minutes of Previous Meeting: The RC approved the minutes of its previous meeting.
  2. DNS Resiliency Efforts: The RC received a report from staff regarding ongoing efforts regarding enhancements to DNS resiliency, including collaboration among root operators. The RC discussed possible Board communications regarding contacts and collaboration among root operators. The RC also discussed deployment of anycast instances of root servers and development of a strategy for future deployment. The RC agreed to form a small work party of three Board members to consider coordination and collaboration issues.
    • Action
      • Work party of RC members to provide update on coordination and collaboration issues at upcoming RC meeting.
  3. Update on Key Program Identification for Risk Committee Tracking: The RC received a report on the work to identify key program areas for RC tracking and reporting in FY13.
  4. New gTLD Program Update: The RC discussed the issues surrounding various technology systems and the identification of best practices that could inform systemic improvements going forward.  The RC also discussed efforts for assuring operational readiness for continued progress through the roll out of new gTLDs, and the need to update the identified risks and mitigation efforts for the New gTLD Program. The RC discussed the need for publicly documenting its attention to this issue, and the possibility for recommending a Board resolution on this matter.
    • Actions:
      • Staff to give RC members an opportunity to review terms of reference for program review work undertaken.
      • Staff to update the identification of risks and mitigation efforts for the New gTLD Program.
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."