Skip to main content
Resources

Structural Improvements Committee (SIC) Meeting - Minutes

SIC Members: Ray Plzak – Chair; Sébastien Bachollet; Judith Duavit Vazquez; Bertrand de La Chapelle; and Francisco da Silva

Other Board attendees: George Sadowsky and Jonne Soininen

Staff Attendees: David Olive – Vice President, Policy Development Support, Rob Hoggarth, Megan Bishop, Michelle Bright, Samantha Eisner, Alice Jansen, and Larisa Gurnick


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

The Meeting was called to order at 12:00 pm local time in Amsterdam, The Netherlands.

  1. Minutes: The SIC approved the minutes of its prior meeting.
  2. ASO Review: The SIC Chair reported on communications with the NRO/ASO regarding the closing of the review. The ASO is in the process of preparing a report of the items that require ICANN resources or action, particularly items raised in the ICANN Board/ASO interaction at the Beijing meeting.
  3. GNSO Charter Amendment Procedure: The SIC revisited its discussion from the prior meeting regarding the Board's role in the GNSO Charter Amendment Process. The SIC focused its conversation towards the protections defined in the process in the event the Board objects to the charter changes, and the Board's accountability role in the process. The SIC requested a change to the document prior to posting, to reference the Board's recognition of the Charter, as opposed to approval. The SIC approved a recommendation that the GNSO Charter Amendment Procedure be posted for public comment.

    • Actions:
      • Staff to revise procedure in line with SIC direction.
      • Staff to post procedure for public comment.
  4. Future Organizational Reviews: The SIC Chair noted that work is still ongoing with staff on this topic. This will be on the SIC's agenda for its next meeting.
  5. NomCom Review: The SIC agreed that this item will be discussed at the SIC's meeting in Durban, South Africa.
  6. Impact of New gTLDs on ICANN Structure and Processes: The SIC continued its discussion of the impact of new gTLDs on ICANN structure and processes, and how to continue this conversation to allow for broader community discussion at the ICANN meeting in Durban, South Africa. The community has already started engaging on this topic, and it could be interesting to take stock of how this issue is being addressed. The SIC noted that this conversation is very important for inclusion with the full Board's strategic planning over the next few days at the Board workshop. The SIC agreed that it is important to have a public session on this topic in Durban, including receiving information on the strategic planning component of this work, and integrating these two conversations.

    • Action:

      • Bertrand de La Chapelle to lead, on behalf of the SIC, the effort to have this topic integrated into the strategic planning discussion.
      • Staff to meet with SIC Chair and Bertrand de La Chapelle to continue planning on this session;

The meeting was adjourned at 12:47 pm local time in Amsterdam, The Netherlands.

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