Skip to main content

Board Governance Committee (BGC) Minutes

BGC Attendees:  Steve Crocker, Cherine Chalaby, Rita Rodin Johnston, Ram Mohan, Raymond Plzak, and Bruce Tonkin – Chair

Other Board attendees:  Rod Beckstrom – President and CEO; Peter Dengate Thrush – Chair of the Board; Rajasekhar Ramaraj

Staff Attendees:  Akram Atallah – Chief Operating Officer and Interim Chief Financial Officer; John Jeffrey – General Counsel and Secretary; Samantha Eisner, Diane Schroeder, and Ken Shiu and Amy Stathos

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

  1. Approval of Minutes:  The committee approved the minutes from last BGC meeting.

  2. Workplan:  The BGC discussed revised BGC workplan and explained the changes that have been made since the last time the BGC reviewed the workplan.  The BGC also briefly discussed the process for allocation of implementation responsibility for the ATRT recommendations..

  3. Guidelines for Improved Board Effectiveness:  BGC discussed draft Guidelines for handling motions and resolutions during Public Meetings.  The BGC also discussed the concept of having one member of the committee supporting the resolution be responsible for working with staff to prepare resolutions, and compile suggested edits.  The BGC also discussed the merits of including the Guidelines with the induction materials for new Board members and as a reference tool for Committee Chairs to guide new committee members.
    • Actions:

      • Staff to revise Guidelines to permit more flexible processes and to ensure that at least one Board member is responsible for a resolution.

      • Staff to circulate revised Guidelines for further feedback from the BGC prior to finalizing for submission for discussion at the next Board workshop or meeting.

      • The topic of the Board’s focus on strategic and operational decisions to be placed on the May board retreat agenda.

  4. Conflicts of Interest Disclosure Process:  The BGC discussed the equal application of the conflicts of interest disclosure requirements for all Directors and Liaisons.  The BGC also discussed the detailed and full conflicts of interest disclosure process and the submission of those disclosures for BGC review.  The BGC further discussed the need for some guidance on conflicts of interest disclosure statements.

    • Actions:  Office of General Counsel to reassert confidentiality requirements on a regular basis.

  5. BGC Review of other Committees:  Staff discussed the existing process for BGC’s review of each committee.  The matter was deferred to a future meeting.

  6. Confidentiality and Code of Conduct:  The BGC discussed the nature of confidentiality requirements for Directors and Liaisons.  The BGC further discussed minor revisions to the Code of Conduct, as well as the formalization of Guidelines for dealing with the Code of Conduct, as it relates to confidentiality. 

    • Staff to submit revised Code of Conduct to Board for approval

  7. Responding to GAC Communiqués:  The BGC discussed the need to track Communiqués or other written advice received from supporting organizations (SOs) and advisory committees (ACs) and to ensure that draft responses to these communiqués be included as agenda items for next Board meeting.

    • Action:  Staff to prepare a uniform process for the handling of SO and AC Communiqués or other written advice.

  8. Mid-term Slating:  The BGC discussed the need to consider the committee slating of the new incoming Director(s), as well as the need to select a new Chair, in June.

    • Action:  Staff to place on the next BGC agenda a discussion of the manner of selecting the Board Chair and Board Vice Chair.

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