Skip to main content

Preliminary Report - Public Participation Committee (PPC) Meeting

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

Staff Attendees: Rod Beckstrom – President and CEO; Nick Ashton Hart, Samantha Eisner, Diane Schroeder, Amy Stathos and Nick Tomasso

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

  1. The PPC Chair received comments on the proposed agenda and accepted the CEO’s suggestion that the PPC add to its agenda today remote participation tools for use at the upcoming ICANN International Meeting in Nairobi.
  2. Reviewed the minutes from the prior PPC meeting, and all voting members in attendance unanimously approved the minutes.
  3. Discussed the proposed questionnaire prepared by Staff relating to ICANN’s meetings, which is the first of a three-part consultation. The survey will be posted for public response in sufficient time to gather some feedback to allow for a robust discussion in Nairobi. Additional consultation will occur prior to the ICANN meeting in Brussels, and sufficient information should be collected by September to allow for a recommendation of proposals to the PPC and Board regarding the future format and features of ICANN’s International Public Meetings. The PPC provided substantive guidance and comments to Staff to consider and revise, and requested a pre-launch testing to confirm the usability of the survey.
    • Actions:
      • Staff to incorporate PPC member suggestions and comments and revise proposed questionnaire, and circulate to the PPC. If PPC members have comments on revised survey, PPC members to provide input by email to Staff.
      • General Counsel’s office to provide guidance on requested protection of personal data points identified for collection.
      • Staff to provide PPC and other testers with pre-launch version of survey as soon as possible, for testing in advance of anticipated launch in mid-February 2010.
  4. Discussed Staff work to date on preparing a standardized remote participation toolset for use at the Nairobi International Public Meeting. This work includes options for use by persons with varying levels of bandwidth, and innovations in use of current tools to allow for better access. Discussed the need for a formation of operational practices for remote participation, such as a user’s guide and timing of audio file availability to make sure the postings are done in a timely fashion. The PPC Chair suggested that Staff create short, user-friendly how-to videos on the more widely-used remote participation tools, in advance of the Nairobi meeting, along with written documentation.
    • Actions:
      • By the end of the week, staff to provide the PPC Chair with a write up of the potential resources required for the creation of the requested videos and documentation, for presentation to the ICANN CEO and Chief Operating Officer.
      • Staff to begin work on identifying proper content for the requested videos.
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."