Skip to main content
Resources

Structural Improvements Committee (SIC) Meeting - Minutes

SIC Members: Ray Plzak – Chair; Sébastien Bachollet; Bertrand de La Chappelle; Thomas Roessler; Judith Duavit Vazquez

Staff Attendees: Akram Atallah, Chief Operating Officer; David Olive, Vice President, Policy Development Support; Samantha Eisner, Rob Hoggarth, Alice Jansen, Olof Nordling, and Alina Syunkova

Invited Observer: Fadi Chehadé


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

The meeting was called to order at 8:32 am local time in Prague, Czech Republic.

  1. Minutes: The SIC approved the minutes of its prior meeting in May 2012

  2. ALAC Review Implementation: The SIC discussed the Final Report of the ALAC Review Implementation, and noted the need for formal Board action to acknowledge the completion of review.

    • Action:

      • Staff to prepare proposed resolution for Board consideration to recognize the finalization of the implementation of recommendations arising out of the ALAC Review.

  3. ccNSO Review Implementation: The SIC received an update on the ccNSO activities in implementing the recommendations arising out of the review of the ccNSO. A final report is anticipated in October 2012.

  4. ASO Review: The SIC reviewed the status of the review of the ASO, noting that discussions with the ASO regarding establishment of milestones will proceed.

  5. RSSAC Review: The Chair provided an update on the discussions with the RSSAC regarding the implementation of the RSSAC review, and noted that further conversations would occur at meetings at the upcoming IETF Meeting in July/August 2012. The Chair invited members of the SIC to join a working group to further this effort.

    • Action:

      • SIC member to confirm ability to attend upcoming meeting and join working group.

  6. Organizational Review Framework: The SIC discussed a proposed model for a framework for running the new cycle of organizational reviews as required under the Bylaws, with a focus on organizational effectiveness and establishing a set of objective criteria to be used across the organizational reviews. The SIC also discussed ways to look more broadly across the organization within the organizational reviews, as well as the need to make sure that items such as governance and fiscal responsibility are incorporated into the objective criteria used.

    • Actions:

      • Hold a session at the ICANN meeting in Toronto regarding planning for future structure of the GNSO, for inclusion on a Monday meeting agenda if possible.

      • SIC member to provide proposed format for the suggested meeting in Toronto.

      • SIC member to provide proposed set of criteria to staff.

      • Stakeholder Group review criteria to be placed on agenda for the next regular meeting of the SIC.

  7. Advice Framework: The SIC briefly discussed considerations in creating an advice framework to consider how the Board can obtain advice that it identifies as necessary, including the function of liaisons to the Board. The SIC also noted the need to consider informal advice collection from existing SOs and ACs.

    • Action:

      • This item should be staged for discussion at the next regular meeting of the SIC.

  8. Any other business: The SIC discussed the need to assure that any organizational reviews that have completed the implementation stage require formal recognition by the Board to acknowledge the completed status. The SIC also discussed the work within ALAC on future challenges within ICANN, and requested that this be considered by the Board at its upcoming workshop in September.

    • Action:

      • Staff to prepare proposed resolutions for Board consideration

The meeting adjourned at 9:50 am local time.

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