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: Akram Atallah, Bertrand de La Chapelle and George Sadowsky

Staff Attendees: Michelle Bright, Samantha Eisner, Tanzanica King, David Olive, Christina Rodriguez, Marc Salvatierra, Alina Syunkova, Nick Tomasso, and Filiz Yilmaz


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

  1. Planning for Future ICANN Meetings: The PPC discussed the schedule development process for ICANN public meetings, including the application of this process to the Toronto Meeting. The PPC received an update on planning for the Latin American meeting in November 2013, as well as proposals for other meetings in 2014. On the hub cities proposal, staff reported on the small number of responses to the request for proposal that was issued, and then engaged in a discussion regarding the operation of the hub city concept. The PPC requested updates to the proposal document that is being prepared for community input, to identify ways to encourage hosting, as well as explanation of the capacity issues. The PPC asked staff to develop a new name for the program before publication for public comment. The PPC also raised the issue of continuing to assess risks associated with a meeting location after selected, to assure continuity of ICANN meetings.
    • Action:
      • After revising to meet PPC comments, the staff to post hub meeting document for public comment.
      • Hub meeting topic to be on agenda for PPC consultation with the community in Toronto.
  2. Minutes of Prior Meeting: The PPC approved the minutes of its prior meeting in August 2012.
  3. Review of Action Items: The PPC reviewed the action items identified at prior meetings. The PPC identified items that still required follow up and were not expected to be discussed during this meeting:
    • Action:
      • PPC agreed to close item regarding members providing comment on public comment proposal from staff.
  4. Overview of Web Content Accessibility at ICANN: The PPC discussed issues relating to supporting a variety of standards for content, and received a report on the support available on the different sites supported by ICANN.
  5. Public Session of PPC in Toronto: The PPC discussed a proposed agenda for the public consultation in Toronto, focusing on the hub city concept. The PPC also discussed ideas of trying a new structure of the meeting to encourage participation, and agreed to move that experimentation to the ICANN meeting in Beijing.
  6. Public Forum Session at the ICANN Meetings: The PPC discussed the purpose of the public forum session at ICANN meetings, noting that the public forum is separate from the public comment periods. The PPC received an update on the process for selection of topics for the public forum.
    • Action:
      • Staff to prepare some introductory remarks for the Chair of Board to open the next public forum, highlighting the difference between the public forum and the public comment processes.
  7. Language Services Update: Staff provided an update to the PPC on the status of the Language Services Policy and Procedure document that was posted for public comment. Staff provided a detailed review of the public comments received.
    • Action:
      • Staff to provide detailed, written summary of public comments, noting if there are specific actions arising out of those comments that will be addressed in further iteration of the policy and procedure document.
      • The PPC to consider the policy and recommend to the Board for adoption.
  8. Pilot SO/AC Training and Orientation Program Update: Staff provided an update on the high-level training program included in the FY13 budget. There has been a request from the community working group to postpone the implementation of the training, previously to be scheduled in Toronto, and staff agreed with that request.
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."