November 2019 - GNSO-PDP3Dot0-DT

FW: ALAC Feedback: Invitation to Provide Input for PDP 3.0 Implementation
by Ariel Liang Dec. 3, 2019

Dec. 3, 2019

Dear All, For Small Team’s record, please see ALAC’s input for PDP 3.0 implementation attached. Thank you! Ariel From: Evin Erdogdu <evin.erdogdu(a)icann.org> Date: Wednesday, November 27, 2019 at 4:27 PM To: Ariel Liang <ariel.liang(a)icann.org>, ICANN At-Large Staff <staff(a)atlarge.icann.org>, Steve Chan <steve.chan(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, Maureen Hilyard, Alan Greenberg, Holly Raiche, Justine Chew Subject: Update: ALAC Feedback: Invitation to Provide Input for PDP 3.0 Implementation Dear Ariel and All, There is one revision added to the statement (attached) in the second paragraph on the first page: The ALAC appreciates proposed reforms to the PDP process that may make the process more effective and efficient in achieving outcomes. However, concern was expressed that the “reforms” suggested by the PDP 3.0 could be used to actually limit the participation by the ALAC / At-Large Community. In striving for timely, inclusive, productive and broad-based participation in PDP 3.0, the ALAC wish to share some feedback with the GNSO Council. Please share this final, revised statement with the GNSO Council Small Team. Thank you for confirmation of receipt - and Happy Thanksgiving to you as well! Cheers, Evin

2 1

Proposed Agenda & Materials GNSO PDP 3.0 - 3 December at 21:00 UTC
by Ariel Liang Nov. 27, 2019

Nov. 27, 2019

Dear All, Please find below the proposed agenda for the PDP 3.0 Small Team meeting on Tuesday, 3 December at 21:00 UTC (please note the new rotation time based on the doodle result): 1. Welcome & roll call 2. Review input to PDP 3.0 improvements: https://community.icann.org/x/_ZgzBw 3. Webinar preparation & slide review: https://docs.google.com/presentation/d/1cKpme0QFIkCBWxCngIAio4Vqs80dOVq2UsD… 4. (time permitting) Charter template revision: https://docs.google.com/document/d/1c69yMieH-9MCfhSelpb5vc8dxvIY_IzN/edit 5. AOB Please note: Re 2: The GAC has provided input (thanks Maxim for commenting on list) and the ALAC/At-Large is expected to provide input as well. Re 3: * Staff attempted to summarize the most important takeaways for each improvement, so the slide deck is a bit long. However, this may be necessary to ensure that Councilors/audience are aware of the details. * For slide no. 19, please see attached the Package 2 examples for display. * If you have input/suggestion for slides, please feel free to insert comments on the Google Slides (click “insert” from the top menu). * Per discussion with Rafik & Pam, one proposal is to divide the presentation by two people (Rafik & Ariel), and other Small Team members and staff can chime in during Q&A following the presentation of each package of improvements. The specific approach can be further discussed/confirmed during the Small Team meeting next Tuesday. Re 4: Staff haven’t made new edits, but if time permits, Small Team can start identifying sections that need revision during the meeting. Subsequently, Staff will follow up and make suggested revisions. Have a great Thanksgiving holiday for those celebrating and talk to you soon. Best Regards, Ariel

1 0

FW: [council] GAC Member Feedback to GNSO on GNSO PDP 3.0 Implementation Documents
by Ariel Liang Nov. 27, 2019

Nov. 27, 2019

Dear all, For Small Team record -- please find the GAC input to PDP 3.0 improvements attached. Thank you, Ariel From: council <council-bounces(a)gnso.icann.org> on behalf of Terri Agnew <terri.agnew(a)icann.org> Date: Tuesday, November 26, 2019 at 9:24 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] GAC Member Feedback to GNSO on GNSO PDP 3.0 Implementation Documents Dear Council, Please find attached a transmittal letter and accompanying document providing feedback from GAC Members on the GNSO PDP 3.0 implementation documents. Thank you. Kind regards, Terri

2 1

Re: [GNSO-PDP3Dot0-DT] [Ext] Re: Finalized Package 4 Improvements (#9 & #15) - Delivered to the GNSO Council
by Ariel Liang Nov. 22, 2019

Nov. 22, 2019

Will do, Flip. Thank you! Best, Ariel From: Flip Petillion <fpetillion(a)petillion.law> Date: Friday, November 22, 2019 at 4:11 AM To: Ariel Liang <ariel.liang(a)icann.org>, "gnso-pdp3dot0-dt(a)icann.org" <gnso-pdp3dot0-dt(a)icann.org> Subject: [Ext] Re: [GNSO-PDP3Dot0-DT] Finalized Package 4 Improvements (#9 & #15) - Delivered to the GNSO Council Thank you Ariel ! Please let us know when / if ICANN Legal profides feedback. Best regards, Flip Flip Petillion fpetillion(a)petillion.law +32484652653 www.petillion.law [signature_262312119][petillion.law]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.petillion.law_&d=Dw…> Attorneys – Advocaten - Avocats From: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces(a)icann.org> on behalf of Ariel Liang <ariel.liang(a)icann.org> Date: Thursday, 21 November 2019 at 23:39 To: "gnso-pdp3dot0-dt(a)icann.org" <gnso-pdp3dot0-dt(a)icann.org> Subject: [GNSO-PDP3Dot0-DT] Finalized Package 4 Improvements (#9 & #15) - Delivered to the GNSO Council Dear all, For the record on the mailing list – the finalized documents for Improvements #9 and #15 have been delivered to the Council. Thanks very much for the Super Small Team (Flip, Rafik, Pam, Heather)’s effort in shaping the implementation of these two improvements, and thanks to all Small Team members for your input/contribution! Best Regards, Ariel P.S. ICANN Legal has not provided any feedback for the proposed language concerning their roles in WG complaint proceedings. Should they provide any input, staff will incorporate their suggested revision (if any) in redline to facilitate the review. From: council <council-bounces(a)gnso.icann.org> on behalf of Ariel Liang <ariel.liang(a)icann.org> Date: Thursday, November 21, 2019 at 5:27 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] PDP 3.0 Package 4: Proposed Documents for Improvements 9 & 15 Dear GNSO Councilors, On behalf of the PDP 3.0 Small Team, staff would like to inform you that the Small Team has completed proposed documents for implementing twelve (12) out of fourteen (14) PDP 3.0 improvements so far. Previously, the Small Team sent to the GNSO Council proposed implementation documents for: · Improvements #1, #2, #3 & #6 on 22 August<https://mm.icann.org/pipermail/council/2019-August/022965.html>; · Improvements #11, #12, #14, and #16 on 25 September<https://mm.icann.org/pipermail/council/2019-September/023075.html>; · Improvements #5 & #13 on 22 October<https://mm.icann.org/pipermail/council/2019-October/023185.html>. The Small Team is now sending the proposed implementation documents for improvements #9 & #15. They are packaged together as they are concerned with consensus building and conflict resolution within GNSO working groups. #4 and #17 are the two improvements remaining in the pipeline. The Small Team invites the GNSO Council to review these documents and welcomes your questions and feedback. All delivered PDP 3.0 implementation documents can be found here: https://community.icann.org/x/v4rkBg *** Improvements #9 (Provide further guidance for section 3.6 and clarification of section 3.7 of the GNSO working group guidelines) · A guideline document that suggests detailed improvements to the complaint process within a GNSO working group, as well as proposed revisions to Section 3.7 of the GNSO Working Group Guidelines: https://docs.google.com/document/d/1pIHFupCdXoH3BSgRfu6KbzUm2jt1AQ-_MEk0JeM… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> · A briefing document that explains the concept of “consensus” and references experience with consensus building in the Internet Engineering Taskforce (IETF): https://drive.google.com/a/icann.org/file/d/1o8732tPyRh6PnER76VlT984HCLfovn… [drive.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_a_ica…> – NOTE: Since this document will be absorbed by the consensus playbook to be developed under Improvement #4, it does not require further deliberation by the GNSO Council at this time. Improvement #15 (Independent Conflict Resolution) · A reference guide to existing conflict resolution resources available to the ICANN community: https://docs.google.com/document/d/1yq__EGRYmicTGEOoZPqh6FdsXWNzFblqWwZkXhP… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Re: [GNSO-PDP3Dot0-DT] Finalized Package 4 Improvements (#9 & #15) - Delivered to the GNSO Council
by Flip Petillion Nov. 22, 2019

Nov. 22, 2019

Thank you Ariel ! Please let us know when / if ICANN Legal profides feedback. Best regards, Flip Flip Petillion fpetillion(a)petillion.law +32484652653 www.petillion.law [signature_262312119]<http://www.petillion.law/> Attorneys – Advocaten - Avocats From: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces(a)icann.org> on behalf of Ariel Liang <ariel.liang(a)icann.org> Date: Thursday, 21 November 2019 at 23:39 To: "gnso-pdp3dot0-dt(a)icann.org" <gnso-pdp3dot0-dt(a)icann.org> Subject: [GNSO-PDP3Dot0-DT] Finalized Package 4 Improvements (#9 & #15) - Delivered to the GNSO Council Dear all, For the record on the mailing list – the finalized documents for Improvements #9 and #15 have been delivered to the Council. Thanks very much for the Super Small Team (Flip, Rafik, Pam, Heather)’s effort in shaping the implementation of these two improvements, and thanks to all Small Team members for your input/contribution! Best Regards, Ariel P.S. ICANN Legal has not provided any feedback for the proposed language concerning their roles in WG complaint proceedings. Should they provide any input, staff will incorporate their suggested revision (if any) in redline to facilitate the review. From: council <council-bounces(a)gnso.icann.org> on behalf of Ariel Liang <ariel.liang(a)icann.org> Date: Thursday, November 21, 2019 at 5:27 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] PDP 3.0 Package 4: Proposed Documents for Improvements 9 & 15 Dear GNSO Councilors, On behalf of the PDP 3.0 Small Team, staff would like to inform you that the Small Team has completed proposed documents for implementing twelve (12) out of fourteen (14) PDP 3.0 improvements so far. Previously, the Small Team sent to the GNSO Council proposed implementation documents for: · Improvements #1, #2, #3 & #6 on 22 August<https://mm.icann.org/pipermail/council/2019-August/022965.html>; · Improvements #11, #12, #14, and #16 on 25 September<https://mm.icann.org/pipermail/council/2019-September/023075.html>; · Improvements #5 & #13 on 22 October<https://mm.icann.org/pipermail/council/2019-October/023185.html>. The Small Team is now sending the proposed implementation documents for improvements #9 & #15. They are packaged together as they are concerned with consensus building and conflict resolution within GNSO working groups. #4 and #17 are the two improvements remaining in the pipeline. The Small Team invites the GNSO Council to review these documents and welcomes your questions and feedback. All delivered PDP 3.0 implementation documents can be found here: https://community.icann.org/x/v4rkBg *** Improvements #9 (Provide further guidance for section 3.6 and clarification of section 3.7 of the GNSO working group guidelines) · A guideline document that suggests detailed improvements to the complaint process within a GNSO working group, as well as proposed revisions to Section 3.7 of the GNSO Working Group Guidelines: https://docs.google.com/document/d/1pIHFupCdXoH3BSgRfu6KbzUm2jt1AQ-_MEk0JeM… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> · A briefing document that explains the concept of “consensus” and references experience with consensus building in the Internet Engineering Taskforce (IETF): https://drive.google.com/a/icann.org/file/d/1o8732tPyRh6PnER76VlT984HCLfovn… [drive.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_a_ica…> – NOTE: Since this document will be absorbed by the consensus playbook to be developed under Improvement #4, it does not require further deliberation by the GNSO Council at this time. Improvement #15 (Independent Conflict Resolution) · A reference guide to existing conflict resolution resources available to the ICANN community: https://docs.google.com/document/d/1yq__EGRYmicTGEOoZPqh6FdsXWNzFblqWwZkXhP… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Finalized Package 4 Improvements (#9 & #15) - Delivered to the GNSO Council
by Ariel Liang Nov. 21, 2019

Nov. 21, 2019

Dear all, For the record on the mailing list – the finalized documents for Improvements #9 and #15 have been delivered to the Council. Thanks very much for the Super Small Team (Flip, Rafik, Pam, Heather)’s effort in shaping the implementation of these two improvements, and thanks to all Small Team members for your input/contribution! Best Regards, Ariel P.S. ICANN Legal has not provided any feedback for the proposed language concerning their roles in WG complaint proceedings. Should they provide any input, staff will incorporate their suggested revision (if any) in redline to facilitate the review. From: council <council-bounces(a)gnso.icann.org> on behalf of Ariel Liang <ariel.liang(a)icann.org> Date: Thursday, November 21, 2019 at 5:27 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] PDP 3.0 Package 4: Proposed Documents for Improvements 9 & 15 Dear GNSO Councilors, On behalf of the PDP 3.0 Small Team, staff would like to inform you that the Small Team has completed proposed documents for implementing twelve (12) out of fourteen (14) PDP 3.0 improvements so far. Previously, the Small Team sent to the GNSO Council proposed implementation documents for: · Improvements #1, #2, #3 & #6 on 22 August<https://mm.icann.org/pipermail/council/2019-August/022965.html>; · Improvements #11, #12, #14, and #16 on 25 September<https://mm.icann.org/pipermail/council/2019-September/023075.html>; · Improvements #5 & #13 on 22 October<https://mm.icann.org/pipermail/council/2019-October/023185.html>. The Small Team is now sending the proposed implementation documents for improvements #9 & #15. They are packaged together as they are concerned with consensus building and conflict resolution within GNSO working groups. #4 and #17 are the two improvements remaining in the pipeline. The Small Team invites the GNSO Council to review these documents and welcomes your questions and feedback. All delivered PDP 3.0 implementation documents can be found here: https://community.icann.org/x/v4rkBg *** Improvements #9 (Provide further guidance for section 3.6 and clarification of section 3.7 of the GNSO working group guidelines) · A guideline document that suggests detailed improvements to the complaint process within a GNSO working group, as well as proposed revisions to Section 3.7 of the GNSO Working Group Guidelines: https://docs.google.com/document/d/1pIHFupCdXoH3BSgRfu6KbzUm2jt1AQ-_MEk0JeM… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> · A briefing document that explains the concept of “consensus” and references experience with consensus building in the Internet Engineering Taskforce (IETF): https://drive.google.com/a/icann.org/file/d/1o8732tPyRh6PnER76VlT984HCLfovn… [drive.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_a_ica…> – NOTE: Since this document will be absorbed by the consensus playbook to be developed under Improvement #4, it does not require further deliberation by the GNSO Council at this time. Improvement #15 (Independent Conflict Resolution) · A reference guide to existing conflict resolution resources available to the ICANN community: https://docs.google.com/document/d/1yq__EGRYmicTGEOoZPqh6FdsXWNzFblqWwZkXhP… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Actions & Notes: GNSO PDP 3.0 Small Team Meeting 19 November 13:00 UTC
by Ariel Liang Nov. 19, 2019

Nov. 19, 2019

Dear All, Please find below the action items and notes captured during the PDP 3.0 Small Team meeting on Tuesday, 19 November at 13:00-14:00 UTC. Staff has posted to the wiki space the action items and notes. Please note that these are high-level notes and are not meant as a substitute for the recording and chat room records, which are posted on the wiki at: https://community.icann.org/x/QpIzBw Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) == ACTIONS: - Staff to start developing relevant documents for Improvement #17 based on small team input. - Small Team/Staff to coordinate on the leads for presentation during the PDP 3.0 webinar. NOTES: 1. Welcome and roll call 2. Improvement #17 ~Initial Discussion - page 1 is an abstract of the work plan. Initial take away is that there are some broad/yet defined terms, e.g., “resources” can be multiple things, such as warm bodies that do the work, financial resources. It can imply tracking components. Question is about the “oversight” and who is doing the oversight. - With the exception of EPDP, we don’t do any of the regular update of WG resources, as there are no existing resources allocated to the other working groups. Need better definition of who is doing the reporting and how the report is being consumed. - No understand how much money has been allocated to each working group. No specific budget is trickled down to individual working group, and exception is the EPDP. The driving component of the dedicated fund for EPDP is that it comes from the ICANN contingency fund/slush fund. - Possible implementation steps need more clarity. “Resource” is vague. Chartering phase needs to take into consideration the resources. - The fact sheet is not a panacea that fixes everything. Only EPDP uses it. It has some aspects to track warm body resources, doing an FTE estimation plus using attendance and other data to guestimate how much time the community has spent on the EPDP efforts. - Improvement #11 tries to address problems when they come to the way of a working group. - Need to understand what the expected deliverables are for the “resource and bandwidth analysis”. - Page 2 includes the Council action items related to improvement #17. Two items from SPS2019 are related the scary spreadsheet to get a comprehensive picture of ongoing activities. - Engaging working group leadership on the financial resources in an action item in the next fiscal year. This action item is not workable in the current form, as all GNSO PDP WGs are set to conclude their work in FY2020. - There is another action item to understand the capacity of the Council. - PDFs attached are draft working progress, trying to quantify the amount of efforts/participation in GNSO working groups. These PDFs are out of date now. Very time consuming to put together these PDFs. All the data that we collect is in decentralized places (e.g., wiki, spreadsheet). It is hard to report against the data. - A graphic shows the growth of WG participation over time. Participation grows due to advertisement through engagement efforts and importance of the subjects. - A graphic that calculates the number of dates/overall duration of each WG. Once the board adopts the recommendations, there is time needed to implement the policies. - Scary spreadsheet: either update/create another version or convert it into some other format to facilitate more regular update. Create a larger time scale to reflect how these projects affect us. Action items on the right-hand side are to introduce the prioritization of the projects. - Do we need to guard against an expectation that there will always be funds? Asking a general question could lead to a presupposition that there is money available, which in turn could become a spend on nice-but-unnecessary. - High contributor does not equate to useful contributions. - Another spreadsheet that reflects our pipeline of inflight projects. The aim is to understand how many FTEs are required to get some outcome. The idea is to take a snapshot of how people review/respond to mailing list. Within the working group there are different levels of contributors. Assign some kind of hours to those different levels of contributors. Took a long time to put together the data. - Resourcing and budgeting are just puzzle pieces to a larger puzzle. We need better definition of what the Council really wants to accomplish. - Page 3 is a starter list of things that need to be done. - Improvement #17 is really about the resource, so defining it is a good place to start. - The idea of pipeline is important. The rest of the improvement is related to project management, and it is centered around pipeline. - In terms of resources, it should start from the chartering phase. EPDP starts to do that but it wasn’t very advanced. Maybe involve planning work at the beginning. How to adjust the way that we plan our work to align with the timeline. How to synchronize/coordinate the work. - Prioritization of GNSO projects should be done in SPS2020. Should have one PDP no longer than one/two years? - Reflect more in the charter template, to specify what kind of resources are needed. - Community hours are hard to track/require. No SGs/Cs have the ability to know specifically how many of their members can participate in a WG. - Struggle to figure out what deliverable is required for this improvement. The point about community resource is that it is difficult to measure, and it varies. But ICANN financial resources and staff resources should be fixed for a given year/time. The purpose is not just about reporting/recording the number of hours. It is more meaningful if we have a view of the resources from ICANN Org side in order to decide whether the Council can take on another project. Need to understand how to prioritize. - Is it possible to use the data regarding staff resources? If policy staff are already stretched, then maybe we cannot have staff to support another policy effort. - The pain and scream come from the community resources. FTE allocation remains relatively flat. 7/34 out of policy department supports the GNSO PDPs. The growth of the number of WG has increased. Staff is overworked, but we are not going to say that. It is up to community to say what needs to come along. - We are running at 130-140% out of the 100% utilization availability. Staff will make it work. The real issue is the number of balls being juggled at the same time from the community perspective. - 3 or 4 WGs are launched and wrapping up at around the same time. - Each WG has attendance record in separate tabs in one of Berry’s spreadsheet. At the individual level, you can see who is participating and how often he/she is participating. It took a very long time to compile the information but it hasn’t been used much. Get a better picture of who are the community’s key performers by how much they are participating. It does not address the elephant in the room – how to decide which WG can be launched. - The only method to ensure we have resources is to limit the number of projects. We have three types of resources: ICANN staff, WG members. A good indicator is when active members stop participating in certain WG. They may be fed up. - Start with something basic to help the community understand their capacity. - Community resources will vary depending on topics. For example, IGO Curative Rights will have more GAC members and IGOs while Transfer Policy review will have more from registrars. - Not concerned about getting accuracy for estimating resources at the first go. It may take several iterations. - ACTION ITEM: Staff to start developing relevant documents for Improvement #17 based on small team input. 3. PDP 3.0 Webinar Prep - Webinar is scheduled on 27 November at 21:00 UTC. Concerns about conflict with IGF 2019 in Berlin. Several small team members are unable to attend. - Webinar is to focus on key takeaway from the proposed implementation for each improvement. Following presentation of each package of improvements is the Q&A. Scheduled for 90 min but may wrap up early. - ACTION ITEM: Small Team/Staff to coordinate on the leads for presentation during the PDP 3.0 webinar. 4. AOB

1 0

Re: [GNSO-PDP3Dot0-DT] [Ext] RE: Final Call: Review Improvements $9 & #15 by Wednesday, 20 November
by Ariel Liang Nov. 19, 2019

Nov. 19, 2019

Thanks Flip, Marie, and Philippe for your feedback! Staff will plan to incorporate these redline edits after the final call deadline by COB tomorrow (Wed, 20 November). In the meantime, the Complaints Officer just added one short phrase in the paragraph on page 9 about her mandate (e.g., she may handle complaints about the “ICANN Org providing an inadequate level of staff support”). She has no other suggested edits. Best Regards, Ariel From: "philippe.fouquart(a)orange.com" <philippe.fouquart(a)orange.com> Date: Tuesday, November 19, 2019 at 9:30 AM To: Flip Petillion <fpetillion(a)petillion.law>, Marie Pattullo <marie.pattullo(a)aim.be>, Ariel Liang <ariel.liang(a)icann.org>, "gnso-pdp3dot0-dt(a)icann.org" <gnso-pdp3dot0-dt(a)icann.org> Subject: [Ext] RE: [GNSO-PDP3Dot0-DT] Final Call: Review Improvements $9 & #15 by Wednesday, 20 November Thanks Ariel. I agree too, this makes sense, and I’d think they know better (as a rule :). Re 2, I understand the point as the need not to put too much emphasis on what was done to deal with one past contentious case; as it may be done differently for future ones - point well taken. Apologies for missing this afternoon’s call. Regards, Philippe From: GNSO-PDP3Dot0-DT [mailto:gnso-pdp3dot0-dt-bounces@icann.org] On Behalf Of Flip Petillion Sent: Tuesday, November 19, 2019 2:57 PM To: Marie Pattullo; Ariel Liang; gnso-pdp3dot0-dt(a)icann.org Subject: Re: [GNSO-PDP3Dot0-DT] Final Call: Review Improvements $9 & #15 by Wednesday, 20 November I agree Flip Petillion fpetillion(a)petillion.law +32484652653 www.petillion.law [signature_1295071146][petillion.law]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.petillion.law_&d=Dw…> Attorneys – Advocaten - Avocats From: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces(a)icann.org> on behalf of Marie Pattullo <marie.pattullo(a)aim.be> Date: Tuesday, 19 November 2019 at 13:46 To: Ariel Liang <ariel.liang(a)icann.org>, "gnso-pdp3dot0-dt(a)icann.org" <gnso-pdp3dot0-dt(a)icann.org> Subject: Re: [GNSO-PDP3Dot0-DT] Final Call: Review Improvements $9 & #15 by Wednesday, 20 November Thanks Ariel; I see no reason why we should not simply accept all of the Ombudsman’s proposals – they make complete sense. M From: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces(a)icann.org> On Behalf Of Ariel Liang Sent: Monday, November 18, 2019 6:57 PM To: gnso-pdp3dot0-dt(a)icann.org Subject: Re: [GNSO-PDP3Dot0-DT] Final Call: Review Improvements $9 & #15 by Wednesday, 20 November Dear all, This is to let you know that the Ombudsman provided some input to the language concerning his potential involvement when a disagreement / conflict happens in a GNSO WG. Per his input, the implementation documents for Improvements #9 & #15 have been updated. You can see the redline edits on #9 document as follows: 1. Added the sentence “Elements of confidentiality may be invoked when the Ombudsman is involved in a proceeding” at the end of the first paragraph about the Ombudsman (Section 3.3 on page 10). 2. Deleted the reference to a previous case when the Ombudsman was involved in a GNSO WG matter (second paragraph in Section 3.3 on pages 10-11). 3. Replaced “lodge a complaint with the Ombudsman” and “bring in the Ombudsman” with “lodge the issue and engage with the Ombudsman” consistently throughout the document. #15 document reflects the same changes per points 1) & 2) above. We are waiting for input from ICANN Legal and ICANN Complaints Officer, if any. Thank you, Ariel From: Ariel Liang <ariel.liang(a)icann.org<mailto:ariel.liang@icann.org>> Date: Wednesday, November 13, 2019 at 5:31 PM To: "gnso-pdp3dot0-dt(a)icann.org<mailto:gnso-pdp3dot0-dt@icann.org>" <gnso-pdp3dot0-dt(a)icann.org<mailto:gnso-pdp3dot0-dt@icann.org>> Subject: Final Call: Review Improvements $9 & #15 by Wednesday, 20 November Dear all, We hope this message finds you well, and hope those who have traveled back home from Montreal had an uneventful trip! Following the working session on Monday, 4 November, staff have updated the documents for Package 4 Improvements #9 and #15, incorporating input and suggestions received from the Small Team: #9 Clarification to Complaint Process in GNSO Working Group Guidelines: https://docs.google.com/document/d/1pIHFupCdXoH3BSgRfu6KbzUm2jt1AQ-_MEk0JeM… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> #15 Independent Conflict Resolution: https://docs.google.com/document/d/1yq__EGRYmicTGEOoZPqh6FdsXWNzFblqWwZkXhP… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> Please provide your final input by COB Wednesday, 20 November. In absence of concerns/objections, staff will coordinate with the Small Team lead to finalize the Package 4 documents and send to the GNSO Council no later than Friday, 22 November. == Please note: Improvement #15 has incorporated all Pam’s suggested edits and the document is now in clean format. Improvement #9: * You should be able to see all substantive updates in redline; editorial suggestions have already been accepted directly (e.g., replacing “dispute” with “disagreement” throughout the document). * Per action items<https://community.icann.org/x/vIEzBw> from the 22 October meeting, staff also shared the draft document with the Ombudsman, ICANN Legal, Conflict Resolution Specialist, and Complaints Officer, seeking feedback (if any) for the proposed language about their potential roles in Section 3.7 complaint proceedings. The Conflict Resolution Specialist already provided updated/approved language regarding her job duty/mandate, which has been incorporated in redline. Any further feedback received from the Ombudsman, ICANN Legal, and Complaints Officer should be reflected in the documents for both #9 and #15 for consistency purpose. * Improvement #9 also includes a briefing document [drive.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_a_ica…> on the concept of consensus in PDP. This briefing document does not require additional work/review by the Small Team, as it will be absorbed by the consensus playbook to be developed by the external vendor for Improvement #4. Thank you, Julie & Ariel _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

Post Call | PDP 3.0 Call | Tuesday, 19 November 2019 at 13:00 UTC
by Nathalie Peregrine Nov. 19, 2019

Nov. 19, 2019

Dear all, All recordings for the PDP 3.0 call held on Tuesday, 19 November 2019 at 13:00 UTC can be found on the agenda wiki page <https://community.icann.org/display/GCP/2019-11-19+PDP3.0> (attendance included). These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-pdp3dot0-dt/> and the main wiki page<https://community.icann.org/x/3hhIBg>. Thank you. Kind regards, Nathalie

1 0

Re: [GNSO-PDP3Dot0-DT] Final Call: Review Improvements $9 & #15 by Wednesday, 20 November
by Flip Petillion Nov. 19, 2019

Nov. 19, 2019

I agree Flip Petillion fpetillion(a)petillion.law +32484652653 www.petillion.law [signature_1295071146]<http://www.petillion.law/> Attorneys – Advocaten - Avocats From: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces(a)icann.org> on behalf of Marie Pattullo <marie.pattullo(a)aim.be> Date: Tuesday, 19 November 2019 at 13:46 To: Ariel Liang <ariel.liang(a)icann.org>, "gnso-pdp3dot0-dt(a)icann.org" <gnso-pdp3dot0-dt(a)icann.org> Subject: Re: [GNSO-PDP3Dot0-DT] Final Call: Review Improvements $9 & #15 by Wednesday, 20 November Thanks Ariel; I see no reason why we should not simply accept all of the Ombudsman’s proposals – they make complete sense. M From: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces(a)icann.org> On Behalf Of Ariel Liang Sent: Monday, November 18, 2019 6:57 PM To: gnso-pdp3dot0-dt(a)icann.org Subject: Re: [GNSO-PDP3Dot0-DT] Final Call: Review Improvements $9 & #15 by Wednesday, 20 November Dear all, This is to let you know that the Ombudsman provided some input to the language concerning his potential involvement when a disagreement / conflict happens in a GNSO WG. Per his input, the implementation documents for Improvements #9 & #15 have been updated. You can see the redline edits on #9 document as follows: 1. Added the sentence “Elements of confidentiality may be invoked when the Ombudsman is involved in a proceeding” at the end of the first paragraph about the Ombudsman (Section 3.3 on page 10). 2. Deleted the reference to a previous case when the Ombudsman was involved in a GNSO WG matter (second paragraph in Section 3.3 on pages 10-11). 3. Replaced “lodge a complaint with the Ombudsman” and “bring in the Ombudsman” with “lodge the issue and engage with the Ombudsman” consistently throughout the document. #15 document reflects the same changes per points 1) & 2) above. We are waiting for input from ICANN Legal and ICANN Complaints Officer, if any. Thank you, Ariel From: Ariel Liang <ariel.liang(a)icann.org<mailto:ariel.liang@icann.org>> Date: Wednesday, November 13, 2019 at 5:31 PM To: "gnso-pdp3dot0-dt(a)icann.org<mailto:gnso-pdp3dot0-dt@icann.org>" <gnso-pdp3dot0-dt(a)icann.org<mailto:gnso-pdp3dot0-dt@icann.org>> Subject: Final Call: Review Improvements $9 & #15 by Wednesday, 20 November Dear all, We hope this message finds you well, and hope those who have traveled back home from Montreal had an uneventful trip! Following the working session on Monday, 4 November, staff have updated the documents for Package 4 Improvements #9 and #15, incorporating input and suggestions received from the Small Team: #9 Clarification to Complaint Process in GNSO Working Group Guidelines: https://docs.google.com/document/d/1pIHFupCdXoH3BSgRfu6KbzUm2jt1AQ-_MEk0JeM… #15 Independent Conflict Resolution: https://docs.google.com/document/d/1yq__EGRYmicTGEOoZPqh6FdsXWNzFblqWwZkXhP… Please provide your final input by COB Wednesday, 20 November. In absence of concerns/objections, staff will coordinate with the Small Team lead to finalize the Package 4 documents and send to the GNSO Council no later than Friday, 22 November. == Please note: Improvement #15 has incorporated all Pam’s suggested edits and the document is now in clean format. Improvement #9: * You should be able to see all substantive updates in redline; editorial suggestions have already been accepted directly (e.g., replacing “dispute” with “disagreement” throughout the document). * Per action items<https://community.icann.org/x/vIEzBw> from the 22 October meeting, staff also shared the draft document with the Ombudsman, ICANN Legal, Conflict Resolution Specialist, and Complaints Officer, seeking feedback (if any) for the proposed language about their potential roles in Section 3.7 complaint proceedings. The Conflict Resolution Specialist already provided updated/approved language regarding her job duty/mandate, which has been incorporated in redline. Any further feedback received from the Ombudsman, ICANN Legal, and Complaints Officer should be reflected in the documents for both #9 and #15 for consistency purpose. * Improvement #9 also includes a briefing document<https://drive.google.com/a/icann.org/file/d/1o8732tPyRh6PnER76VlT984HCLfovn…> on the concept of consensus in PDP. This briefing document does not require additional work/review by the Small Team, as it will be absorbed by the consensus playbook to be developed by the external vendor for Improvement #4. Thank you, Julie & Ariel

2 1