Skip to main content
Resources

Board Risk Committee (RC) – Minutes

RC Attendees: Steve Crocker, Ray Plzak, Mike Silber - Chair, Bruce Tonkin, R. Ramaraj, Suzanne Woolf, and Judith Vazquez

Other Board Attendees: Akram Atallah, Erika Mann, Ram Mohan, Thomas Narten, and Thomas Narten

RC Apologies: Thomas Roessler

Other Invited Attendees: Olga Madruga-Forti

Staff Attendees: Xavier Calvez – Chief Financial Officer; John Jeffrey – General Counsel and Secretary; Jeff Moss – Chief Security Officer; Kurt Pritz – Senior Vice President, Stakeholder Relations; Edward Beck, Michelle Bright, Samantha Eisner, Daniel Halloran, Patrick Jones, and Amy Stathos


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. Software Process Review: The RC was introduced to Ed Beck, the new Vice President for IT, and staff confirmed that with Ed's introduction, improvements are being made to internal coordination on risk identification and mitigation efforts.
  3. TAS and New gTLD Update: The RC received a presentation on the risk-related efforts performed since Prague. A revised identification of the risks and mitigation efforts associated with the New gTLD Program will be provided to the RC prior to Toronto. The RC also had a high-level discussion of some of the emerging risk areas.
  4. Planning for Next Meeting: Staff provided proposed topics for discussion at the RC's next meeting, including strategic risks, new gTLDs, and the Risk Management Process overview. The RC requested an overview of the historical risk-related work performed on the New gTLD Program.
    • Action:
      • Staff to prepare a summary-level document on the New gTLD Program risk review to aid in RC discussion.
      • Staff and RC to determine if a telephonic meeting is required prior to Toronto.
      • Staff to implement improvements to meeting materials as requested by RC.
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."