Skip to main content
Resources

Minutes | Board Governance Committee (BGC) Meeting

Published 16 June 2016

BGC Attendees: Rinalia Abdul Rahim, Cherine Chalaby, Chris Disspain (Chair), Erika Mann Mike Silber, and Bruce Tonkin

BGC Apologies: Suzanne Woolf

Other Board Member Attendees: Rafael Lito Ibarra, Asha Hemrajani, and Markus Kummer

ICANN Executive and Staff Attendees: Akram Atallah (President and CEO; President, Global Domains Division), Samantha Eisner (Associate General Counsel), John Jeffrey (General Counsel and Secretary), Melissa King (VP, Board Operations), David Olive (Sr. VP, Policy Development Support; General Manager, ICANN Regional Headquarters –Istanbul), Wendy Profit (Board Operations Specialist), Amy Stathos (Deputy General Counsel), Theresa Swinehart (Sr. VP, Multistakeholder Strategy and Strategic Initiatives), and Christine Willett (VP of gTLD Operations)

Invited Guests: J. Beckwith Burr; representatives on behalf of Dotgay LLC


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

  1. Minutes – The BGC approved the minutes from the meeting on 12 April 2016.
  2. Dotgay LLC’s Oral Presentation to the BGC re Reconsideration Request 16-3 – Dotgay LLC made a presentation to the BGC regarding Reconsideration Request 16-3. Dotgay LLC’s presentation materials and written summary of its presentation have been published at https://www.icann.org/resources/pages/reconsideration-16-3-dotgay-request-2016-02-18-en.
    • Action:
      • BGC to consider additional information provided and then consider Request 16-3.
  3. Expected Standards of Behavior – Staff provided an overview of the proposed enhancements to the current Expected Standards of Behavior, as well as the parallel efforts with respect to developing a community anti-harassment policy/procedure. The BGC discussed the proposed revisions and agreed to recommend that the Board authorize the posting for public comment of the proposed revisions to the Expected Standards of Behavior. The BGC also discussed the input from the community requesting that ICANN work with an expert, as needed and appropriate, to help develop a proposed community anti-harassment policy/procedure to be followed at ICANN Public meetings. The BGC agreed to recommend that the Board direct the President and CEO, or his designee(s), to retain an expert, as appropriate, with experience in drafting and implementing relevant anti-harassment policies to assist in the development of a community anti-harassment policy/procedure to be followed at ICANN Public meetings, which could include items such as complaints handling and resolution, and enforcement processes.
    • Action:
      • Staff to engage expert and work up proposals for discussion with the community.
  4. Board Working Group on Internet Governance – The BGC discussed the establishment of a Board Working Group on Internet Governance (BWG-IG) to provide consultation and advice on ICANN’s efforts related to involvement in Internet governance work, as appropriate within ICANN’s mission and in service of ICANN’s strategic plan. The following Board members have volunteered to be members of the BWG-IG: Rinalia Abdul Rahim, Ron da Silva, Chris Disspain, Markus Kummer (Chair), Erika Mann, George Sadowsky, and Lousewies Van der Laan. The BGC agreed to recommend that the Board form the BWG-IG and appoint the above-named Board members to the BWG-IG. The BGC further noted that additional Board members may be added to the BWG-IG membership, if other Board members subsequently express an interest.
    • Action:
      • Staff to add the BWG-IG formation and membership to the Board meeting agenda for approval.
  5. Call for Expressions of Interest for 2017 Nominating Committee Chair and Chair-Elect – Staff provided an overview of the draft Call for Expressions of Interest (EOIs) for 2017 Nominating Committee (NomCom) Chair and Chair-Elect positions. The Call for EOIs explains that, while it is anticipated that the 2016 Chair-Elect position will be elevated to the 2017 Chair position, such is not necessarily the case and EOIs may be submitted through 10 June 2016. Staff further explained that 360-degree reviews of the current NomCom leadership will take place, which will help inform the BGC in making its recommendation to the Board regarding the 2017 NomCom Chair and Chair-Elect. The BGC agreed to post the Call for EOIs for 2017 NomCom Chair and Chair-Elect.
    • Actions:
      • Staff to post Call for EOIs.
      • Staff to gather EOIs and present to BGC for consideration.
  6. Board 360-Degree Evaluation – Staff provided an overview of the 360-degree evaluation conducted by the Board. The BGC agreed to forward the Board self-evaluation report to the Board and recommend that the Board post the scores, which is consistent with the process that has been followed in past years.
  7. Update on Reconsideration Request 16-4 – Staff briefed the BGC on Reconsideration Request 16-4, which seeks reconsideration of the Contractual Compliance department’s response to the Requester’s complaint regarding a dispute about a domain name between the Requester and the relevant domain name registrar. At the 12 April 2016 BGC meeting, the BGC requested that staff obtain additional information regarding the nature and basis of the dispute between the registrant and registrar. Staff provided an overview of the efforts to obtain the additional information and explained that the Contractual Compliance department is in the process of concluding its further investigation. The BGC continued its consideration of Request 16-4 until the further information has been provided.
    • Action:
      • Staff to finalize the investigation and then re-submit Request 16-4 to the BGC for consideration.
  8. AOB
    Committee and Board Chair 360-Degree Evaluations
    – The BGC discussed having each of the Board committees, and the Board, conduct a 360-degree evaluation of their respective Chair or Co-Chairs (or vice chair). The BGC discussed the need to tailor the Board 360-degree evaluation questionnaire to Chair positions.
    • Action:
      • Staff to draft a 360-degree evaluation questionnaire tailored to Board and Committee Chair positions, and then distribute it to the BGC for review.
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."