Skip to main content
Resources

Public Participation Committee (PPC) Meeting Minutes

PPC Attendees: Sébastien Bachollet – Chair, Chris Disspain, Thomas Narten, and Kuo-Wei Wu

Other Board Attendees: Bertrand de La Chapelle, George Sadowsky, Olga Madruga-Forti

Staff Attendees: Megan Bishop, Michelle Bright, Mandy Carver, Sally Costerton, Renate De Wulf, Chris Gift, Elizabeth Le, Denise Michel, Amy Stathos, Nick Tomasso, Jim Trengrove and Heidi Ullrich

Invited Guests: Olivier Crepin-Leblond and Matthew Shears


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

  1. Adoption of Minutes – The PPC approved the minutes of the previous meeting,
  2. Preparation of the Co-Branded GSE/PPC Public Meeting – The PPC discussed the structure and organization of the joint public meeting that the PPC will be hosting with the ICANN Global Stakeholder Engagement (GSE) group on Thursday, 11 April 2013. The open session will focus on global engagement strategy for the existing community and new stakeholders outreach, and will include a presentation from the community outreach group. The meeting will include a breakout session into the following four sub-topic groups relating to global engagement strategy: (1) production of collateral; (2) conferences, events, and speaker panels; (3) digital engagement, online platforms and tools; and (4) assessment of the community engagement model. Each group will be co-facilitated by a GSE team member and a PPC member.
  3. Atlas 2 (At Large Summit 2) – The PPC received a presentation from the Chair of the At-Large Advisory Committee (ALAC) about a proposed summit in London in 2014, at the same time as the ICANN meeting. Following the presentation, the PPC discussed questions posed by the Board Finance Committee, particularly as to whether the proposed travel costs are intended to cover just the people who do not otherwise travel to the ICANN meeting or attendees whose expenses are already normally covered for the ICANN meeting. The PPC then discussed the process for seeking Board approval of the proposal.
    • Action:
      • PPC Chair to draft motion for PPC consideration.
  4. Publication and Posting Procedures – The PPC discussed standardizing a set of policies and procedures for the posting, re-posting, and tagging of documents to different online platforms, including what sort of notice should be provided to the community of changes to documents. The PPC agreed to consider this topic in further detail at the meeting in May.
  5. Meeting Strategy Working Group – The PPC reported that the preparation for the first meeting strategy working group is on track for Thursday in Beijing. The group will provide a report to the PPC at the next PPC meeting.
  6. ATRT – The PPC discussed the 2012 Implementation Summary Report for ATRT 1 recommendations and the five Recommendations for which it is responsible –15, 16, 17, 18, and 21. For Rec. No. 21, the PPC will assess at the May workshop whether the online tools exist to restructure the format of the public comment period to allow a direct reply to a comment. For Rec. No. 7 regarding training and capacity building, the PPC received a briefing on the Online Education Platform (OEP), which is an engagement and development tool for the ICANN community relating to ICANN's function and role in the Internet ecosystem. The platform will build a common and coherent understanding among stakeholders about ICANN and will be globally scalable. Staff advised the PPC that the plan is to launch a limited pilot beta at the next ICANN meeting in July 2013 in Durban. The PPC also received an update on ICANN Academy, which is being developed through a multistakeholder working group that will meet in Beijing. The PPC anticipates that the group is working on face-to-face leader training for the Buenos Aires meeting.
  7. MyICANN – The PPC discussed the update on the new functionality and capabilities for MyICANN. The update includes localization, navigation in the six UN languages, and the integration of AtTask and a meeting calendar. MyICANN meetings and the online learning platform will be integrated with MyICANN by the next meeting in Durban. The PPC was also informed that the community wiki and two other operations tools, including the registry/registrar on boarding tool, AROS, will be migrated into MyICANN.
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."