Skip to main content
Resources

Public Participation Committee (PPC) Minutes

PPC Attendees: Jean-Jacques Subrenat – Chair; Thomas Narten, Gonzalo Navarro, Vanda Scartezini, and Katim Touray

Other Board Attendee: Kuo-Wei Wu

Staff Attendees: Doug Brent – Chief Operating Officer; Rob Hoggarth, Janice Douma Lange, Christina Rodriguez, Diane Schroeder, and Amy Stathos

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

  1. Reviewed the minutes from the prior PPC meeting, and all voting members in attendance approved the minutes.

  2. Received an update on remote participation at the Brussels meetings, including the advance staff and community trainings, as well as improvements made in light of the remote participation experiences in Brussels. This also includes the formation of a late-session addition approval process to provide more certainty for the scheduled meeting arrangements and allow for all attendees – remote and on-site – to plan meeting attendance. Staff noted that given unexpected issues that arose in the application of the process, staff recommends a further consideration of the process and of the implementation.

    • Action:
      • At next meeting of PPC, staff to give full report on the 15 day advance deadline on session posting and requests for late additions, including topics raised and criteria imposed. After PPC consideration of the report, it should be posted publicly.
  3. Received an update from staff on interpretation services, including the work of staff to identify a common team of interpretation providers to use at every ICANN International Meeting, and the work being done to identify the languages that ICANN will provide interpretation services for at the international meetings, determined by meeting location and based upon research and resource availability. The PPC discussed the challenges inherent in attempting to perform remote interpretation of a live meeting. The PPC also briefly discussed the potential for involvement of community members in translation of materials.

    • Action:
      • Staff to perform test of remote simultaneous interpretation including the use of video.
      • Staff to review the usage of requested translation services at the ICANN international meetings and the needs behind those requests, to allow for the creation of an operational process on this, including cost-based information.
      • PPC to provide staff guidance on useful metrics for evaluation of usage of translation services.
  4. Received an update on the status of the ongoing consultation for the Meetings for the Next Decade, noting that community members participating in the survey have already demonstrated that they hold definitive opinions on the issues raised within the survey, including numbers of meetings per year, meeting locations, and travel support.

    • Action:
      • Staff to determine if they can provide information about the regions from which survey responses are received.
      • Staff to work to increase the number of respondents to the survey.
  5. Received an update from staff on the status of hiring a new manager of public participation and engagement.

  6. Received an update from staff on a proposed process for selection of the North American meeting site for March 2011.

    • Action:
      • Staff to post the meeting selection process for notice to the community with a note regarding the change in approach, and invite community input on the same.
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."