Skip to main content
Resources

Public Participation Committee (PPC) Minutes

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

Staff Attendees:  John Jeffrey – General Counsel and Secretary; David Olive – Vice President, Policy Development Support; Janice Douma Lange, Robby Markowicz, Amy Stathos, and Nick Tomasso

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 from Staff on the Meetings for the Next Decade consultation that is ongoing, and discussed ideas for achieving broader input and participation into the first phase of the consultation, including the hosting of a webinar and the exploration of tools outside of online surveys.  The PPC also discussed planning for the next phase of the consultation and the need to simplify the proposed process.
    • Actions:
      • Staff to prepare note for the PPC suggesting the organization and timing of a webinar, to address PPC member comments.
      • Staff to present a more simplified process and timeline for the second phase of the meetings consultation, and circulate within week to the PPC members.
  3. Received an update from Staff on the Public Participation Review project outline, and the proposal to seek expertise from outside sources.  The PPC agreed that further reflection was required to evaluate the potential contributions to the organization, and Staff shall proceed with work to achieve consultations.
    • Actions:
      • Staff to prepare note for the PPC with overall reflections of the contributions anticipated from each of the two sources identified to date, and guidance on the approach to the potential service providers.
      • PPC member Katim Touray volunteered to help draft interchange with International Public Participation Association.  Draft expected in a few days.
  4. Received an update from Staff on the selection process of venues for upcoming ICANN international meetings, and the results of the public comment period on the revision of the selection process.  Staff also provided an update on the recent opening of a call for meeting selection sites for upcoming meetings.  Staff confirmed that a recommendation would be made prioritizing potential meeting locations, with a reminder of criteria.
    • Action:
      • Staff to prepare a note for PPC members, which could then be shared with the full Board on the progress made on the selection process to date. 
  5. Received an update from Staff on the status of hiring a new manager of public participation and engagement.
  6. The Chair requested that the items identified at the previous PPC meeting regarding ICANN’s linguistic policy and programme be carried over for action.
    • Actions:
      • Staff to perform test of remote simultaneous interpretation including the use of video.  The Chair invited Staff to provide suggestions for this testing.
      • Staff to review the usage of requested linguistic services at the ICANN international meetings and the needs justifying those requests, to allow for the creation of an operational process, including cost-based information.  This should include updates made between the Nairobi meeting and the Brussels meeting, and planning for Cartagena.
      • PPC to provide guidance to Staff on useful metrics for evaluation of usage of linguistic services.
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."