Skip to main content

Minutes | Board Governance Committee (BGC) Meeting

BGC Attendees: Becky Burr, Ron da Silva, Sarah Deutsch, Ihab Osman, León Sánchez, Matthew Shears, and Tripti Sinha (Chair)

Other Board Member Attendees: Avri Doria, Lito Ibarra, and Patricio Poblete

ICANN org Attendees: Franco Carrasco (Board Operations Specialist), John Jeffrey (General Counsel and Secretary), Liz Le (Associate General Counsel), David Olive (SVP, Policy Development Support), Lisa Saulino (Board Operations Specialist), Amy Stathos (Deputy General Counsel), and Theresa Swinehart (SVP, Global Domains and Strategy)

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

  1. Agenda review and request to add to Any Other Business (AOB) – The Chair reviewed the meeting agenda, and proposed changes to the order of the agenda. The Committee agreed with the proposed change.
  2. Review of Prior Action Items – The BGC Chair noted there were no action items from the prior meeting.
  3. Board Members Serving as Liaisons to Community Groups Guidelines - The BGC received a briefing on revisions to the guidelines to address the Committee's feedback from its last meeting. The BGC discussed a few additional revisions. Following discussion, the BGC agreed to submit the final guidelines to the Board (subject to final revisions being made). The BGC also noted that this will be a living document subject to revision as needed and as practice dictates.

    • Action:
      • ICANN org to update the guidelines document to reflect the BGC's discussions and provide to the Board.
  4. Board Meeting Process Discussion – The BGC continued its discussion regarding the scope and purpose of Board minutes. The BGC agreed and understood that minutes are the official and legal record of a Board meeting, and the purpose of minutes is to accurately summarize what transpired during the meeting. The Committee noted that the ICANN Bylaws permit the Board to exclude some things from being published in the approved resolutions and/or minutes that the Board determines are not appropriate for disclosure. The BGC also discussed whether voting statements should be included as attachments to Board meeting minutes and discussed the scope and process for submitting voting statements. The discussion included when voting statements should be submitted, and how voting statements that are submitted after the close of a meeting should be treated. The BGC agreed that voting statements should accurately reflect statements and actions taken by the voting director during a Board meeting and should not contain new statements, new facts, or new information. The BGC determined that the current practice with respect to meeting minutes, including voting statements, is appropriate and consistent with the Bylaws and other corporate laws and regulation, and therefore should remain as is.
  5. Board Caucus on DNS Abuse – The BGC reviewed the process for establishing a Board caucus pursuant to the framework that the Committee established last year. The framework requires the chair of the sponsoring committee to submit to the BGC for review a recommendation to establish a caucus. The recommendation must include the name of the proposed caucus, the purpose of the proposed caucus, and membership criteria. Thereafter, the BGC will then evaluate the recommendation. If approved, then the recommendation will require approval by the Chair of the Board and ICANN President and CEO as to whether it should be created and whether ICANN org has sufficient and necessary resources to support the group. The BGC engaged in a discussion regarding how to determine which Board committee would be the appropriate sponsoring committee and whether the membership criteria of no less than three and no more than seven members should be addressed. The BGC agreed to continue the discussion at its next meeting.

Published on 07 July 2021

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"""" is not an IDN."