Skip to main content
Resources

Minutes | Board Governance Committee (BGC) Meeting

Board Governance Committee (BGC) Attendees: Rinalia Abdul Rahim, Cherine Chalaby, Chris Disspain (Chair), Asha Hemrajani, Markus Kummer, Ram Mohan, and Mike Silber

Other Board Member Attendees:  Maarten Botterman, Becky Burr, Ron da Silva, Khaled Koubaa, George Sadowsky, and Lousewies van der Laan

Invited Observers: Sarah Deutsch, Avri Doria, and Matthew Shears

ICANN Organization Attendees: Susanna Bennett (SVP & Chief Operating Officer), Michelle Bright (Board Content Senior Manager), Duncan Burns (SVP, Global Communications & Managing Director), John Jeffrey (General Counsel and Secretary), Vinciane Koenigsfeld (Board Training & Content Senior Manager), Elizabeth Le (Associate General Counsel), Wendy Profit (Manager, Board Operations), Lisa Saulino (Board Operations Senior Coordinator), and Amy Stathos (Deputy General Counsel)


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

  1. Approval of Minutes – The BGC discussed the draft minutes of the 11 October 2017 meeting. The BGC noted questions from some of the members regarding the capture of the BGC's discussion on the uniform integrity screening.

    • Action: ICANN organization to revise draft minutes and redistribute to the BGC for approval online during ICANN 60.

  2. Board Member Skillsets Guidance to the Nominating Committee (NomCom) – The BGC reviewed the draft Board member skillsets guidance to the NomCom for the NomCom's use during the its 2018 Board member selection process. The BGC discussed that the guidance document is updated and sent to the NomCom annually. The BGC agreed to review the draft and provide suggested changes via email, to allow both the departing and new BGC members an opportunity to provide their input before the BGC approves the guidance document after ICANN60 and send it to the NomCom soon after ICANN 60.

    • Actions

      • BGC members to provide any suggested revisions to draft Board member skillsets guidance to the NomCom via email.

      • BGC to approve Board member skillsets guidance to the NomCom online promptly after ICANN60.

  3. 2018 Work Plan – The BGC reviewed the draft work plan for 2018.  The BGC noted that the work plan needs to be updated to incorporate the BGC's newly added responsibility: Coordinating the dynamic development of the Board priorities and their associated deliverables, and monitoring progress against the set priorities. BGC agreed that the work plan should be published on the BGC's webpage. The published work plan will be a living document and as change are made, the old version of the work plan will be archived and the most current version will be accessible from the BGC webpage.

    • Actions:

      • ICANN organization to update the work plan to incorporate the activities associated with the responsibility of related to Board priorities and re-circulate to the BGC.

      • ICANN organization to publish work plan on the BGC webpage.

  4. CPE Process Review Update – The BGC received an update on the status of the CPE Process Review.  ICNAN organization reported that FTI has completed its investigative process of obtaining information and materials from the CPE Provider. FTI has provided the final draft report for scope 1 (review of the process by which ICANN organization interacted with the CPE Provider related to the CPE reports issued by the CPE Provider) to the BGC. FTI is in the process of drafting the report for scope 2 (evaluation of whether the CPE criteria were applied consistently in each CPE report) and anticipates that the final draft report will be completed by the end of the week or early next week. It is anticipated that the report for scope 3 (compilation of the reference materials relied upon by the CPE Provider to the extent such reference materials exist for the evaluations which are the subject of pending Reconsideration Requests) will be provided in the coming few weeks.

  5. Uniform Board Member Integrity Screening Communications Plan – The BGC discussed options for engaging with the community regarding the uniform integrity screening, including publication of a BGC blog followed by initiation of a public comment period to obtain community feedback regarding a proposed uniform integrity screening process, and perhaps engaging with the SOs and ACs leaders during their sessions with the Board at ICANN 60. The BGC noted that the Board Chair discussed the uniform integrity screening in the Chairman's blog of 20 October 2017, noting that this would be a topic of interest over the next year. The BGC discussed addressing this topic during ICANN 60 and whether the issue would get lost with all that is going on at ICANN 60, and whether it would make more sense to wait until additional questions, such as what is done with the integrity screening reports once completed, to begin a full discussion on this matter. The BGC agreed that before formal engagement efforts with the community are commenced, the process for how the screening reports will be handled once received should to be developed. The BGC requested ICANN organization to develop this process and revert to the BGC.

    • ActionICANN organization to develop the process for handling screening reports once received and revert to the BGC.

Published on 10 November 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."