Skip to main content
Resources

Minutes | Board Organizational Effectiveness Committee (OEC) Meeting

OEC Attendees: Avri Doria – Chair, Becky Burr, Danko Jevtovic, Lito Ibarra, Ihab Osman and Matthew Shears

OEC Apologies: Mandla Msimang

Executive and Staff Attendees: Susanna Bennett, Franco Carrasco, Steve Conte, Amy Creamer, Jean-Baptiste Deroulez, Samantha Eisner, Negar Farzinnia, Larisa Gurnick, Vinciane Koenigsfeld, Laena Rahim and Theresa Swinehart


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

The Meeting was called to order at 15:00 UTC.

  1. Agenda – The Chair established the agenda for the meeting and gave an overview of items to be discussed.
  2. Review of Board Paper for the Second Organizational Review of the Security and Stability Advisory Committee Review (SSAC2) Detailed Implementation Plan (the "Plan") – ICANN organization circulated the Board Paper to the OEC for its review prior to the meeting, and the OEC's input has been incorporated therein.

    In connection with the Plan, the OEC noted that the Plan contains several recommendations which relate to the roles and responsibilities of the SSAC Board Liaison. ICANN organization will update the OEC in due course, should the OEC be required to take any action on this item.

    The OEC concluded its discussion on this topic, and approved the recommendation to the Board that it is appropriate for the Board to accept the Plan, and for the Board to instruct the SSAC2 Review Implementation Work Party to continue the implementation process.

    • Action Item:

      • The OEC to forward its recommendation to the Board for its consideration.
  3. Review of Board Paper for the Second Organizational Review of the Root Server System Advisory Committee Review (RSSAC2) Detailed Implementation Plan (the "Plan") – ICANN organization circulated the Board Paper to the OEC for its review prior to the meeting.

    The OEC concluded its discussion on this topic, and approved the recommendation to the Board that it is appropriate for the Board to accept the Plan, and for the Board to instruct the RSSAC2 Review Implementation Work Party to continue the implementation process.

    • Action Item:

      • The OEC to forward its recommendation to the Board for its consideration.
  4. Streamlining of Reviews

    1. Discussion on Streamlining of Reviews - ICANN organization provided an update on this topic, within the context of public comment input on the ATRT3 Draft Report which closed on 31 January 2020.

      Over the last few years, there has been ongoing discussion surrounding this topic. The paper on "Timing and Streamlining of Reviews" sets out the issues that could be addressed through streamlining efforts including items such as duration; cadence; review team member skills; role of the ICANN Board, ICANN organization and the community; and potential to focus on issuing findings. The ICANN Board submitted a public comment to the ATRT3 that included some of these streamlining ideas.

      ICANN organization provided the OEC with a high-level summary of the community feedback received on streamlining in response to the ATRT3's draft report. ICANN organization also provided a brief update on the outcome of the ATRT3's face-to-face meeting in Brussels in early February 2020, during which the ATRT3 had the opportunity to analyze the comments received and discuss the way forward.

      The OEC Chair commented that it would be worthwhile to have an informal discussion with the ATRT3 after ICANN67, to enable the OEC and the ATRT3 Board Caucus Group to discuss the ongoing work of the ATRT3 as it works towards submitting its final report to the Board.

      • Action Item:

        • ICANN organization to propose to the ATRT3 to have an informal engagement among the ATRT3, the OEC and the ATRT3 Board Caucus Group to discuss the streamlining and prioritization work tracks prior to finalizing its report.
    2. Upcoming Board Workshop Session at ICANN67 - The OEC agreed that the purpose of the Board Workshop session is to assess the goals and the desired outcome for two work tracks to ensure that the Board is aligned in its efforts to address critical issues: (1) the streamlining of reviews; and (2) the prioritization of review recommendations.

      • Action Items:

        • ICANN organization and the OEC to consider ways to re-focus the discussion on streamlining and prioritization on the original problem statement and the desired outcome.
        • ICANN organization to organize a call with the OEC Chair, Becky Burr and Leon Sanchez and ICANN organization to discuss the presentation materials for the Board Workshop session.
  5. Any Other Business

    • Update on the IANA Naming Function Review (IFR) – ICANN organization provided a brief update on the status of the IFR. The IFR Team finalized its initial scoping document. Although Board approval is not required for the IFR's scoping document, the OEC reviewed the IFR scoping documents before forwarding to the Board. ICANN organization circulated a Board Informational Paper on "IFR Founding Scoping Documents Completed" to the OEC prior to the meeting.

      • Action Item:

        • The OEC to forward the Board Informational Paper to the Board as recommended reading.
    • Roles & Responsibilities for Specific Reviews - ICANN organization reiterated that the procedural document on the "Roles & Responsibilities for Specific Reviews" provides sufficient guidance on the different roles and responsibilities of the OEC, Board Caucus Group, Board Liaisons, etc.

      • Action Item:

        • ICANN organization to include this as an agenda item for a future OEC meeting to discuss the different roles and responsibilities for specific reviews.

The Chair called the meeting to a close.

Published on 03 April 2020

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