Skip to main content
Resources

Public Participation Committee (PPC) Minutes

PPC Attendees: Mike Silber – Chair; Sébastien Bachollet; Thomas Narten; Gonzalo Navarro; Katim Touray; and Kuo-Wei Wu

Invited Attendees: Chris Disspain

Staff Attendees: Akram Atallah – Chief Operating Officer; Elise Gerich – Vice President, IANA; David Olive – Vice President, Policy Development Support; Alina Syunkova; Ken Shiu; Nick Tomasso and Filiz Yilmaz


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

  1. ATRT Implementation Work: Staff presented an update to the PPC on the ongoing work to implement the ATRT recommendations regarding improvements to the public comment process.

    • Action:

      • In advance of broader circulation, staff to provide the PPC with a draft process flow overview of the proposed public comment process and the related work to implement the recommendations in a timely fashion.

  2. Reports on Newcomers Activities and Remote Participation during ICANN 40: Staff provided a brief summary of successful newcomers' activities at the San Francisco/Silicon Valley ICANN meeting, as well as remote participation services. The PPC discussed potential ways that both programs could be improved and the types of metrics that may assist in evaluating the success of each program.

    • Action:

      • Staff to provide information to PPC regarding feasibility of the implementation of local networks for participants on site at the meeting location to reduce strain on external networks.

  3. Meetings for the Next Decade: Staff briefed the PPC on the prior work on the community consultation on the Meetings for the Next Decade project, and the status of recommendations arising out of that work.

    • Action:

      • Staff to advise the PPC on required resources for staff to recommence the community consultation on the Meetings for the Next Decade project.

  4. Community update in Singapore: The PPC discussed the potential for a community update session during the upcoming Singapore meeting and potential agenda items. The Chair noted that he would be working with staff in the coming weeks to identify agenda items.

  5. Workplan review: The PPC noted that staff was in the process of revising the PPC workplan and this would be discussed more fully after the new version is released.

  6. Discussion session in Singapore for proposed Summit on Developing Countries: The PPC briefly discussed the arrangements and invitations for an initial planning session for a proposed summit on developing countries.

    • Action:

      • PPC members to advise the leaders of the SOs and ACs, as well as the review teams formed under the Affirmation of Commitments, of the preparatory meeting as well as anticipated topics for discussion.

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