Skip to main content
Resources

Board Global Relationships Committee (BGRC) Minutes

BGRC Attendees:  Peter Dengate Thrush – Chair; Cherine Chalaby; Erika Mann; Gonzalo Navarro; George Sadowsky; Katim Touray and Kuo-Wei Wu.

Other Board Attendees:  Sebastien Bachollet; Rod Beckstrom – President and CEO; Bertrand de La Chapelle; Steve Crocker; Thomas Narten; and Suzanne Woolf.

Staff Attendees:  Akram Atallah – Chief Operating Officer; Jamie Hedlund – VP, Government Affairs, Americas; John Jeffrey – General Counsel and Secretary; Kurt Pritz – SVP, Stakeholder Relations; Rodrigo de la Parra; Diane Schroeder; Amy Stathos; and Ken Shiu.


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

  1. Latin America Strategy and Relationships Overview – Staff gave an overview on activities in the Latin American region, including a general economic overview, as well as an overview of the registry and registrar community in Latin America and their activities, such as the launch of DNSSEC in LACTLD registries.  Staff also provided an overview of the At-Large Community representation in Latin America and relationships with governments, as well as governmental involvement with the IGF and other Internet-related initiatives.  The BGRC discussed the need ensure that cultural and linguistic sensitivities are incorporated in regional communication and outreach activities, and the opportunity to coordinate with other regional stakeholders in performing this outreach.

    • Action:

      • Staff to prepare draft strategic plan (including priority objectives and an action plan) for the region to present at the next BGRC meeting.

      • Staff to provide update to BGRC regarding the non-contracted registry and registrar landscape in the region.

  2. IETF/ITU-T Multiprotocol Label Switching (MPLS) Operations Administration and Maintenance – BGRC was briefed on the status of the joint initiative between IETF and ITU-T on the MPLS standard.

  3. Department of Commerce Notice of Inquiry – Discussed community response to the Notice of Inquiry.

  4. IDN ccTLD Fast Track request Update – The BGRC received a briefing on the ccTLD IDN Fast Track process.

  5. BGRC Workplan – Discussed the drafting and finalization of the BGRC workplan for the year inclusion in the BGRC presentation report to the Board at the Silicon Valley/San Francisco meeting.

    • Action:

      • Staff to prepare a draft report for the BGRC’s review regarding the BGRC’s work since Cartagena for presentation to the community at the Friday session at the Silicon Valley Meeting.

  6. ISOC’s IPv6 Promotion and Awareness – The BGRC agreed that it supports ISOC’s IPv6 endeavors and means of partnering in these efforts should be explored.

    • Action:

      • Staff to provide any requests for resources or specific BGRC actions as necessary to facilitate this partnership work.

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