Skip to main content

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: Ray Plzak, Bertrand de La Chapelle

Invited Attendee: Olivier Crépin-Leblond

Staff Attendees: Akram Atallah – Chief Operating Officer; David Olive – Vice President, Policy Development Support; Kurt Pritz – Senior Vice President, Stakeholder Relations; Samantha Eisner, Janice Douma Lange, Wendy Profit, Christina Rodriguez, Alina Syunkova, Nick Tomasso 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 January 2011.
  2. ICANN Meetings Review: The PPC received an update of the work ongoing regarding the change of structure of ICANN meetings, and coordination with the Board Governance Committee on this topic. The PPC also discussed the budgeting process for meetings, including assessments for growths in attendance. Finally, the PPC discussed work towards the "hub city" concept with multiple year bookings, including the criteria necessary for the meeting sites.
    • Action:
      • 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.
      • PPC members to convene to discuss restructuring of meeting schedules if the Friday is removed from the public meetings, to assure that all expected activities are moved to a different time slot or are identified to proceed in a different way.
      • Staff to provide budgeting information to the PPC for its meeting in Prague.
      • Staff to provide updated information to the PPC regarding work on volume discounts and proposals towards the "hub city" concept, including criteria for desirable meeting sites.
      • PPC Subcommittee to circulate letter for SO and AC chairs regarding public meeting design.
  3. Language Services Review: The PPC received an update from staff on the status of the language services policy document, as well as forecasts for increasing the language services budget to meet the future demand for high-quality translation and interpretation services. The PPC also began a discussion regarding facilitating additional language communities accessing translations, as well as creating metrics for evaluating the usage of translated material.
    • Action:
      • PPC members to review the draft policy document and provide comments to staff.
  4. PPC Community Consultation in Costa Rica: The PPC discussed the agenda for its session with the community in Costa Rica, including an update on the ATRT work, an update on the future of ICANN meetings, and a new framework for advancing ICANN outreach, including an ICANN academy proposal to train those coming into ICANN leadership positions.
  5. Schedule for Future PPC Meetings: The PPC briefly discussed scheduling of meetings throughout 2012, including the addition of telephonic meetings.
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"""" is not an IDN."