Skip to main content
Resources

Minutes | Board Governance Committee (BGC) Meeting

BGC Attendees: Cherine Chalaby, Chris Disspain (Chair), Markus Kummer, Ram Mohan, and Mike Silber

BGC Member Apologies: Rinalia Abdul Rahim and Asha Hemrajani

Other Board Member Attendees: Becky Burr, Steve Crocker, and Ron da Silva

ICANN Organization Attendees: Michelle Bright (Board Content Senior Manager), John Jeffrey (General Counsel and Secretary), Vinciane Koenigsfeld (Board Training & Content Senior Manager), Elizabeth Le (Associate General Counsel), Wendy Profit (Manager, Board Operations), and Amy Stathos (Deputy General Counsel)


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

  • Update on Community Priority Evaluation Process Review (Review) - The BGC received a briefing on the status of the CPE process review. The second track of the Review, which focuses on gathering information and materials from the CPE provider, is still ongoing. This is in large part because, despite repeated requests from ICANN beginning in March 2017, the CPE provider failed to produce a single document until just very recently – four months and numerous discussions after FTI's initial request. Thus far, not all documents requested have been produced. FTI is in the process of reviewing the documents that have been produced. The BGC discussed the importance of bring the work on the second track to a closure within a definitive time period so that the FTI can conclude their work.
    • Action
      • ICANN organization to follow up with FTI on what documents are outstanding from the CPE provider in response to FTI's document request.
      • ICANN organization to continue providing the BGC with updates on the status of the review, and publish update(s) as appropriate.
  • Board Committee and Leadership Selection Procedures - The BGC reviewed and discussed proposed revisions to the Board Committee and Leadership Selection Procedures (Procedures). The BGC agreed that Committee members should review revisions and provide further edits, if any, by the next BGC meeting, whereupon the Committee will revisit the issue.
    • Action:
      • BGC members to provide comments and further edits to the Procedures via email by the next BGC meeting.
  • Discussion of Board Committees and Working Groups Slate – The BGC discussed the Board Committees and Working Group slates based upon the preferences indicated by the Board members. The BGC also discussed standardizing the Committee charters to specify a minimum and maximum number of Committee members but allow flexibility for the composition of Committee within that range.
    • Action:
      • ICANN organization to revise the Committee charters in accordance with the discussion regarding composition of the Committees for consideration by the BGC at its next meeting.
  • Any Other Business
    • Nominating Committee (NomCom) 2018 Chair and Chair-Elect Leadership– The BGC noted that it is anticipated that the interview process for the NomCom 2018 Chair and Chair-Elect Leadership will be completed by the next BGC meeting and that the BGC will discuss its recommendations at the meeting.

Published on 24 August 2017.

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