Rafik Dammak Pam Little k drazek Philippe Fouquart Maarten Simon

Marika Konings Steve Chan

PDP updates

10 Mar 2019

18 Jul 2019  

•  Council leadership to propose path forward to obtain clarification / provide view concerning intersection between the Name Collisions Analysis Project and SubPro PDP
•  ICANN Staff to consider timing for GNSO Policy webinar (e.g., two weeks prior). ICANN Staff to consider suggested changes to slide format raised during meeting.
•  Council leadership to provide guidance to SubPro PDP on how to navigate interdependent topics (e.g., assumptions doc, Name Collisions Analysis Project, string similarity, IDNs) and potentially dependent PDPs (e.g., RPMs).
•  Council leadership to draft a note to the ICANN Board on NCAP.
•  Council leadership to draft a note to the ccNSO on string similarity and IDNs (together or separate).
•  Input for future updates, Council to suggest one presenter.  Also, focus on post-ICANN meeting updates.

Rafik Dammak Pam Little k drazek

Marika Konings Steve Chan

•  Council to consider if they would like to provide a written response to ICANN Org, to be delivered by the end of September. Councilors to inform their respective SG/Cs of the timeline for providing input.

Rafik Dammak k drazek Pam Little

Marika Konings

• Small team to prepare draft RPMs charter amendments (which will likely include engagement with the IGOs/GAC afterwards) (Volunteers, Paul McGrady as lead, Martin Silva Valent, Elsa Saade, Keith Drazek)

•  Council to convene small team to consider CCT-RT recommendations referred to the GNSO and GNSO PDPs and determine next steps (Volunteers: Pam Little to lead, Carlos Gutierrez, Michele Neylon)
•  Small team to provide proposed approach to GNSO Council
•  ICANN staff to add CCT-RT to the August Council meeting agenda planning document
•  Councilors to review draft text and provide input, if applicable, prior to the September 2019 Council meeting, 13 September 2019 at the latest.

Pam Little Carlos Raul Gutierrez Michele Neylon

Steve Chan Emily Barabas

EPDP Phase 2 Work plan package

•  Councilors to review EPDP Phase 2 work plan package and share any comments or questions with the mailing list

k drazek Pam Little Rafik Dammak

Marika Konings Steve Chan Berry Cobb

18 Jul 2019 

•  Staff to investigate the anticipated timing, funding and expected deliverables for the Evolution of the Multi stakeholder Model of Governance project.
•  ccNSO and GNSO to form joint team to identify any commonalities or differences. Also look at budget and 5 year strategic plan. 
•  ICANN staff to reach out to Maarten Simon and Philippe Fouquart to determine if they are willing to lead action item above.
•  ICANN staff to invite Brian Cute to a future Council meeting
•  Rafik Dammak to invite Brian Cute to future PDP 3.0 meeting to make sure to not create overlapping work on the Evolution of the MSM
•  Continue discussion on list and future next meeting
•  Council to establish a small team to develop a public comment and/or further feedback to Brian concerning review of his document and questions about what comes next.  Consider inviting Brian to the August or September GNSO Council meeting.

•  Council’s liaison to the EPDP, Rafik Dammak to forward letter to EPDP Phase 2 Team and coordinate with them to determine what will be included in the response.

•  Council leadership to propose path forward to obtain clarification / provide view concerning intersection between the Name Collisions Analysis Project and SubPro PDP
•  ICANN Staff to consider timing for GNSO Policy webinar (e.g., two weeks prior). ICANN Staff to consider suggested changes to slide format raised during meeting.
•  Council leadership to provide guidance to SubPro PDP on how to navigate interdependent topics (e.g., assumptions doc, Name Collisions Analysis Project, string similarity, IDNs) and potentially dependent PDPs (e.g., RPMs).
•  Council leadership to draft a note to the ICANN Board on NCAP

• .
•  Council leadership to draft a note to the ccNSO on string similarity and IDNs (together or separate).
•  Input for future updates, Council to suggest one presenter.  Also, focus on post-ICANN meeting updates.

•  Council to consider if they would like to provide a written response to ICANN Org, to be delivered by the end of September. Councilors to inform their respective SG/Cs of the timeline for providing input.

•  ICANN staff to include an agenda item on the September Council meeting, inviting ICANN Org to speak on the impact of GDPR as well as the EPDP 1 recommendations on the enforcement and implementation of existing policies, procedures, and contractual provisions related to accuracy (including ARS).

•  Council to convene a small group to draft a substantive response on data accuracy for Council review to send to ICANN Org in response to 21 June letter (https://gnso.icann.org/en/correspondence/marby-to-drazek-21jun19-en.pdf) (volunteers: Marie, Darcy, Flip)

•  Council leadership and staff to schedule an extraordinary Council meeting to discuss the Board adoption of the EPDP policy recommendations.
•  Staff to provide Board voting results
•  Council leadership to prepare an action plan for engaging with the Board. This includes documenting the options available to the Council, collecting questions/comments/concerns from Stakeholder Groups/Constituencies and the EPDP Team, timeline for engagement with the EPDP Team, and timeline for engagement with the Board.
•  Council to, in consultation with the EPDP team, write communication to ICANN Board and seek to secure board support for Rec #12.
•  Councilors to reach out to their respective SG/Cs to help inform the drafting of the letter to the Board; seek to finalize by 29 July 2019. If the need arises, Council leadership to convene small team to help further develop the letter.
•  Councilors to work to complete the letter, which may include integrating elements such as:
•  When the letter references that some Councilors having dissenting views, that the group holding those dissenting views are identified.
•  Add clarity about the ask of the ICANN Board (e.g., confirm that the Board and Council have a common understanding).
•  Rafik Dammak to confirm when recommendation one, purpose 2 will be expected to be discussed by the EPDP phase 2

k drazek Pam Little Rafik Dammak

Marika Konings Nathalie Peregrine

• to convene small team to consider CCT-RT recommendations referred to the GNSO and GNSO PDPs and determine next steps (Volunteers: Pam Little to lead, Carlos Gutierrez, Michele Neylon)
•  Small team to provide proposed approach to GNSO Council
•  ICANN staff to add CCT-RT to the August Council meeting agenda planning document
•  Councilors to review draft text and provide input, if applicable, prior to the September 2019 Council meeting, 13 September 2019 at the latest.

•  Councilors to review EPDP Phase 2 work plan package and share any comments or questions with the mailing list

Marika Konings Steve Chan Berry Cobb

•  Council leadership to draft response to ICANN org, acknowledging receipt of the letter, acknowledgment of the underlying issue, and committing to determine next steps as a Council.
•  ICANN staff to include an agenda item on the September Council meeting, inviting ICANN Org to speak on the impact of GDPR as well as the EPDP 1 recommendations on the enforcement and implementation of existing policies, procedures, and contractual provisions related to accuracy (including ARS).
•  Council to convene a small group to draft a substantive response on data accuracy for Council review to send to ICANN Org in response to 21 June letter (

• https://gnso.icann.org/en/correspondence/

• marby-to-

• drazek-21jun19-en.pdf)

• (volunteers: Marie, Darcy, Flip)

Mary Wong Julie Hedlund Ariel Liang

•  ICANN Staff to send travel reminders to councilors

•  Council to, in consultation with the EPDP team, write communication to ICANN Board and seek to secure board support for Rec #12.
•  Councilors to reach out to their respective SG/Cs to help inform the drafting of the letter to the Board; seek to finalize by 29 July 2019. If the need arises, Council leadership to convene small team to help further develop the letter.
•  Councilors to work to complete the letter, which may include integrating elements such as: When the letter references that some Councilors having dissenting views, that the group holding those dissenting views are identified. Add clarity about the ask of the ICANN Board (e.g., confirm that the Board and Council have a common understanding).
•  Rafik Dammak to confirm when recommendation one, purpose 2 will be expected to be discussed by the EPDP phase 2

Marika Konings Nathalie Peregrine

•  GNSO Chair to remind SG/Cs to discuss within its respective groups and respond directly (and/or inform Council if there is something within its purview) to the ATRT3 with a response to the following question: what types of improvements would the Community want to see implemented?

Rafik Dammak Pam Little k drazek

Marika Konings Steve Chan

•  ICANN staff to update relevant documentation to note change of liaison from Keith Drazek to Tatiana Tropina (IGO Red Cross)
•  ICANN staff to review existing liaisons, determine who is termed out at the upcoming AGM, seek replacements and perform handover beforehand.

•  Councilors to review Council leadership response to RPM leadership (see https://gnso.icann.org/en/correspondence/gnso-council-to-rpm-pdp-co-chairs-22aug19-en.pdf) and advise Council leadership of any questions, comments or concerns in relation to the response.

Mary Wong Julie Hedlund Ariel Liang

• ICANN Staff to send travel reminders to councilors

k drazek Rafik Dammak Pam Little