Skip to main content
Resources

Public Participation Committee (PPC) Meeting Minutes

PPC Attendees: Sébastien Bachollet – Chair, Chris Disspain, Thomas Narten, Gonzalo Navarro, Mike Silber and Kuo-Wei Wu

Other Board Attendees: Bertrand de La Chapelle

Invited Observer: Fadi Chehadé

Staff Attendees: David Olive – Vice President, Policy Development Support; Kurt Pritz – Senior Vice President, Stakeholder Relations; David Closson; Carole Cornell, Samantha Eisner, Christina Rodriguez, Amy Stathos, Alina Syunkova, Nick Tomasso, Jim Trengrove, and Filiz Yilmaz


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

  1. Minutes of Prior Meeting: The PPC approved the minutes of its prior meeting in May 2012.

  2. Review of Action Items: The PPC reviewed the action items identified at the prior meeting. The PPC identified items that still required follow up and were not expected to be discussed during this meeting:

    • PPC subcommittee, in coordination with staff, to form agreed-upon series of principles for scheduling Mondays and Thursdays at the public meetings, as well as a process for managing scheduling, and report back to the PPC.

  3. Update on PPC-related activities: Staff provided a review of the PPC-related activities since the prior meeting, including: update on meeting scheduling for the public meeting in Prague; public comment processes; items planned for the PPC community session in Prague; continuation of the work on planning for ICANN outreach activities; ongoing discussion of the implementation of an AC/SO Leadership Training Program; Newcomers activities at the Prague meeting; the provision of remote participation services in Prague; and increased focus on the post-meeting reporting.

  4. Update on Public Comment Process: Staff provided an update on the public comments process and issues identified within the community as we gain further experience with the new cycle. It was noted that the reply periods are not being utilized in the expected manner, and that some groups within ICANN have expressed concern that the minimum comment period of 21 days is too short, while other groups express that the comment period is too long. Staff also provided some proposals to modification to the process to better achieve the desired results. The PPC then discussed some proposals of how to make the reply period achieve the results it was anticipated to reach, such as a more interactive reply format separate from the comment box, or a type of “public hearing” on certain topics.

    • Actions:

      • PPC members to provide notes to staff regarding suggestions for modifications to the public comment process.

      • Staff to provide a summary of the proposals (including the one expected from the Prague Public meeting of the PPC) under discussion for the modification of the public comment process, including anticipated scheduling for the proposed processes.

  5. Planning for Future ICANN Meetings: Staff provided a review of some of the criteria for meeting venues for ICANN’s public meeting, such as meeting room facilities, room capacity, and location and size of hotels. Staff also identified some example proposals for “hub” meeting locations.

    • Action:

      • PPC Member to coordinate with staff to provide proposal for PPC consideration regarding consultation on the hub meeting idea.

  6. Update on ICANN.org redesign: Staff provided a review of the ICANN.org website in the few months after the redesign was launched in early 2012. The Committee discussed ways to seek community input.

    • Actions:

      • Staff to consider a process for seeking community input on the new look of icann.org.

      • Staff to continue to analyze the application of W3C standards for the website for people with disabilities.

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