Skip to main content
Resources

Minutes – Public Participation Committee (PPC) Meeting

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

PPC Apologies: Thomas Narten

Staff Attendees: Doug Brent – Chief Operating Officer; 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. PPC chair provided an update to the PPC on recent conversations with staff regarding suggestions on improving PPC working methods.
  2. Reviewed the proposed agenda for the meeting, and received a suggestion that the PPC should consider the public report, due in advance of the ICANN International Meeting in Nairobi.
  3. Reviewed and voting members unanimously approved minutes of prior PPC meeting, with modification noted during review.
  4. Discussed the formation of an agenda for the PPC’s session with the public in Nairobi. The PPC members agreed that use of remote participation, reminders on the document deadline policy, and an introduction to the PPC’s work to create a holistic approach to public participation within ICANN, are all appropriate topics for inclusion. The PPC also agreed that Nairobi is an appropriate venue to focus on the particular needs of participants from developing countries. The PPC agreed that ICANN’s advisory committees and sponsoring organizations, particularly the ALAC, have valuable experience and knowledge in fostering participation, and their input and participation in the PPC public session should be actively invited and encouraged. Staff confirmed that the session would be scheduled to minimize agenda conflicts.
    • Actions:
      • Staff to create theme for the public session in line with the PPC directives, to include the identification of available remote participation tools as one method of organizing the session. Staff to circulate proposal to PPC membership.
      • Staff to work with PPC member for specific suggestions on how to better allow ICANN’s advisory committees and sponsoring organizations to participate in the session, and to seek contributions of ideas for the real-time participation in ICANN meetings.
      • Staff to suggest ways of having community members actively present for a portion of the PPC public session in Nairobi.
  5. Received an update from Staff on the introduction of a matrix of remote participation services available at the Nairobi meeting, and provide the public with an identification of the types of tools that will be available in advance of the Nairobi meeting. The PPC discussed suggestions of how to balance interjections from participants who are physically present with interjections made by participants that are participating remotely, and recognized that some of this is dependent upon the judgment of the chair of each session.
    • Actions:
      • Staff to provide update to PPC on remote participation tools after completing internal confirmations on the availability of the tools.
  6. Discussed items that the PPC must complete before Nairobi, including a report to the President and Chair of the Board on what the PPC is trying to achieve in Nairobi; completion of the PPC report to the public; the preparation of tutorials on remote participation tools available in Nairobi; and continued work on the public participation portion of the ICANN website.
    • Actions:
      • Staff to provide PPC with draft of note to the President and Chair of the Board.
      • Staff to provide PPC with draft of PPC report to the public.
      • Staff to provide update to PPC on the remote participation tutorial in advance of public posting.
  7. Received request from PPC member for a summarization on action items from prior PPC meeting.
    • Action:
      • Staff to provide action item updates in advance of every PPC meeting.
  8. Received request from PPC member to change timing of next PPC meeting.
    • Action:
      • Staff to coordinate PPC member schedules to accommodate change in timing.
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."