Skip to main content

Board Governance Committee (BGC) Minutes

BGC Attendees: Dennis Jennings – chair; Rita Rodin Johnston, Ram Mohan, and Raymond Plzak

Staff Attendees: Rod Beckstrom – ICANN President and CEO, John Jeffrey – ICANN General Counsel; Samantha Eisner, Diane Schroeder, and Amy Stathos

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

  1. Discussed and approved minutes from prior meeting.
  2. Discussed process for making recommendation to the Board that the CEO be directed to have staff undertake additional work, research and analysis as appropriate to provide briefing to the Board to allow for formal consideration of the issue of remuneration of the Chair of the Board.
    • Action:
      • Staff to revise and circulate to the BGC a proposed resolution for presentation to the Board of Directors.
  3. Discussed revisions needed for Committee Standard Operating Procedures, including enhancing transition between old and new committee membership and the assignment of staff to support committee work.
    • Action:
      • Staff to revise Committee Standard Operating Procedures to address BGC members comments.
  4. Reviewed the BGC Charter and discussed need to address BGC work in assisting other Board committees in enhancing performance.
    • Action:
      • Staff to revised BGC Charter to reflect BGC member comments.
  5. Discussed the BGC work plan.
    • Actions:
      • Staff to work with Chair to provide information on guidelines for BGC self-assessment.
      • Staff to prepare a legend for document.
      • Staff to add the creation of a historical knowledge base to work plan.
  6. Discussed proposed draft of the Board Executive Committee Charter. The BGC discussed that while many companies do not require Executive Committees to have a charter, it could be helpful within ICANN to have a document clearly stating the scope Executive Committee’s powers. BGC members raised questions on appropriate placement for enumerated powers, as well as the need to have a dissolution clause within every Board committee charter.
    • Action:
      • Staff to revise proposed Charter to address BGC member comments.
  7. Discussed proposed processes for the Board’s establishment of working groups, including selection of chairs, expectations for the roles of chairs and co-chairs, establishment of terms of reference and setting out expected deliverables, deadlines, an expectation for interim reporting to the Board, and the need to set a defined time for the existence of a working group.
    • Action:
      • Staff to revise the working group process document to reflect BGC member comments.
  8. Received update from staff on the work for identifying a uniform package of software necessary for the performance of Board member responsibilities.
    • Action:
      • BGC members to review the proposed list of software and provide further comments in time to reach a final recommendation in March.
  9. Discussed the framework provided by BGC member regarding the creation of training programs.
    • Action:
      • Staff to prepare draft of overall statement of goals for the Board training program.
      • Staff to work with member of BGC to use the framework provided to develop a Board-specific training program.
  10. Received request from President to consider issues regarding Board travel to non-ICANN meetings.
    • Action:
      • Staff to place issue on work plan for future BGC meeting.
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."