August 2019 - GNSO-PDP3Dot0-DT

Proposed Agenda GNSO PDP 3.0 - 3 September at 13:00 UTC
by Ariel Liang Aug. 30, 2019

Aug. 30, 2019

Dear All, Below, please find the proposed agenda for the PDP 3.0 Small Team Meeting on Tuesday, 3 September at 13:00 UTC. 1. Welcome and roll call 2. #12 Notification to Council of changes in work plan. Presentation of use case drafts & updates. (~45 minutes - Berry) 3. Staff Reminder & AOB Best, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 310 804 2761 Skype: ariel.liang.icann www.icann.org

1 0

Improvement #16 - Confirmation
by mail＠berrycobb.com Aug. 27, 2019

Aug. 27, 2019

Hi All, Per our meeting last week and discussion around Improvement #16, please find attached a rationale for how this improvement can be satisfied. >From GNSO PDP 3.0 Implementation Plan: #16. Criteria for PDP WG Updates Ensure standardized set of information provided by PDP WGs GNSO Council to provide criteria for information that needs to be provided by PDP WG leadership teams as part of their updates to be in a position to closely track progress and identify issues at an early stage. This would include a requirement for a PDP WG to provide early warning as well as identify potential risks that could hamper progress. Staff should develop a template for reporting with criteria and information to be shared in PDP WG updates such as issues, risks, progress against work plan See #11 - Adapt fact sheet that is being used for EPDP Team to template so it can also be used for other efforts Staff / May 2019 As presented in prior meetings for Improvement #11, multiple work products were created or updated to compliment the new feature of Status and Conditions codes being applied to our GNSO projects. The intent of those work products is to provide greater project management discipline. One such component of effective project management is project communications, which is what Improvement #16 mostly sets out to accomplish. Reviewing the work product descriptions (as attached in the catalog) achieves the #16 objectives by providing standard sets of information when WG leadership teams update the GNSO Council via the newly enhanced project list or other special updates as required. In its most common form, the Project Situation Report (also a part of the GNSO Project List) will be used as the authoritative work product to provide said updates. The other work products will be included the communications package as necessary based on the requirements of the update requested and as fulfilled by the WG Leadership team and staff support. The early warning component of the Improvement #16 objective listed above can also be satisfied by the soon to be completed escalation procedure as part of the Status/Condition feature presented under of Improvement #11. I will have a set of use cases for review by the PDP3.0 team to compliment the escalation procedure discussion shortly. Regarding implementation of Improvement #16, consistent use of these standard work products is also a requirement. However, it may not make sense to deploy these to all in-flight projects we have today, especially those that are nearing completion as it may disrupt continuity of previous communications on their work plans. It also may not make sense to devote time in developing fully developed Gantt chart project plans for these in-flight groups either. Thus, the deliverable here, also as a part of implementing #11, staff will commit to storing templates of these work products for use on newly formed working groups or other efforts launched by the GNSO Council. They will also be deployed for in-flight groups where it makes practical sense and as determined by the working group leadership team and staff support. At a minimum, the Project Situation Report is now deployed on the GNSO Council Project List (1st edition 22 August 2019). The EPDP Phase 2 will also continue to use the full spectrum of work products as recently submitted to the GNSO Council for its consideration. I've attached it here for in-use reference and convenience. One final note, the last work product published in the attached catalog is the Project Change Request form. This has yet to be discussed specifically by the PDP3.0 in regards to part of Improvement #12, but it is suggested as a part of the escalation procedure in Improvement #11. Perhaps this component can also be packaged together? Absent any objections, staff will include #16 and #12 as part of a consolidated package for Improvement #11. Thank you. B Berry Cobb @berrycobb GNSO Policy Consultant

2 1

Proposed Work Plan for PDP 3.0 Small Team
by Ariel Liang Aug. 27, 2019

Aug. 27, 2019

Dear All, Per action item, please see the proposed workplan (“Workplan” tab) presented during the Small Team call today. https://docs.google.com/spreadsheets/d/1iCi08gUMdwERcwwHT9C5DIYApz91SEU8Lrj…. Kindly note that in Table 3 (weekly meeting planning), staff have adjusted the draft agenda for the 10 Sep and 17 Sep meetings to accommodate those who will attend the EPDP F2F meeting in LA. As a result, the target delivery date for Package 2 improvements (#11, #12, #14, #16) has been moved to 17/18 Sep. Please feel free to share your addition comments/questions for the proposed workplan on list. If no objection, the planning for future meetings and the delivery of improvements will proceed according to this workplan. Thank you for your review! Best, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 310 804 2761 Skype: ariel.liang.icann www.icann.org

1 0

Post Call | PDP 3.0 Call | Tuesday, 27 August 2019 at 13:00 UTC
by Andrea Glandon Aug. 27, 2019

Aug. 27, 2019

Dear all, All recordings for the PDP 3.0 call held on Tuesday, 27 August 2019 at 13:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/H4vkBg> (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, Andrea

1 0

Actions & Notes: GNSO PDP 3.0 Small Team Meeting 27 August 13:00 UTC
by Ariel Liang Aug. 27, 2019

Aug. 27, 2019

Dear All, Please find below the action items and notes captured during the small team call on Tuesday, 27 August at 13: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/H4vkBg Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) == ACTION ITEMS: - Staff to work with Rafik and Pam to develop a proposal on how to solicit input from the wider GNSO community for PDP 3.0 improvement implementation - Staff to circulate the workplan with the Small Team for comments/input NOTES: 1. Welcome and roll call 2. Proposed workplan/timeline & ICANN66 planning - The Small Team needs to further discuss how to solicit input from the wider GNSO Community. PDP 3.0 may not be of great interest to all Councilors. - A point to consider: Doing the consultation before Montreal = current Council are up to speed. Doing if after = education & possible divergence in new Council?  - We need to be careful with messaging; input from community = good; re-litigating from point zero = not good.  - ACTION ITEM: Staff to work with Rafik and Pam to develop a proposal on how to solicit input from the wider GNSO community for PDP 3.0 improvement implementation - ACTION ITEM: Staff to circulate the workplan with the Small Team for comments/input 3. #11 & #12 & #16 - #16 has multiple work products feed into it (e.g., gantt chart, fact sheet, project situation report, etc.). - See Berry’s email to the Small Team last weekend regarding the suggestion for how to implement #16. Slowly introduce the work products without interruption of current work. Project situation report would be the main work product reflecting the progress in a WG. #16 will wrap up when #11 is completed. - #12 is related to #11. Staff is in process creating six use cases to complement the escalation procedure. - Project change request (#12) helps formalize the request process when a WG needs to change its delivery schedule: https://docs.google.com/document/d/1atq-97a4KlNixU7xkMqH-7l-pHLH5T5zQvP4YhZ… - Formalizing the change process at this stage is a huge leap for the Council as many Councilors may not have project management experience/training. Consider doing this in the future phase of PDP 3.0? It seems a lot of formality coming out of the gate, worried about how sustainable it is for the Council. - The Council needs to decide: 1) how many PDPs can be launched at the same time; 2) chartering; 3) when a WG misses the target, the process to change the delivery schedule needs to be managed, in addition to other important changes (e.g., shaving down the charter, change of WG leadership, terminate the PDP). - WGs doing a better job of informing the Council about issues cropping up in PDPs is critical. It is part of the concern around the project change request process, and how formal that seems? - Having a PCR will help the WG leadership understand they need to make request early on if they see target is slipping. This is about early intervention to mitigate a need for a PCR. But when it is invoked, it should be formal. - Implementing something sustainable with Council has to be considered. It’s a process to move from wishful thinking to pragmatic management. It can’t happen overnight.  4. AOB

1 0

Improvement #5 - Optimal use of GNSO Council liaisons to PDP WGs
by Darcy Southwell Aug. 27, 2019

Aug. 27, 2019

All, As a refresher, Improvement #5 is about ensuring optimal use of GNSO Council liaisons to PDP WGs, which identified as the need to “ensure that there is a clear understanding with regards to the role of the Council liaison and how he/she can assist the WG leadership. This may require PDP WG leadership teams to actively involve the liaison in leadership / preparatory meetings.” During the January 2019 SPS, we discussed the idea of coming up with a toolkit to provide to Council liaisons. As we look to build that, it seems like we should consult with current and prior PDP liaisons for some input. To facilitate those discussions, I’ve prepared the following discussion questions (see Google doc here<https://docs.google.com/document/d/1eh67kgqRsAFdn5WlwjjY_1OxWFp_Dl4MyOCpvzf…>). I’ve also included the questions below. The following questions are designed to facilitate discussion with past and present Council liaisons to various PDPs about what went well, what was a challenge, and identify possible improvements. Recognizing that each PDP operates differently based upon the PDP leadership, the PDP scope, the controversial nature (or lack thereof) of the PDP issue(s), and the timelines, we’re not seeking to normalize every PDP. Rather, these questions are designed to help inform the Council's PDP 3.0 Small Team on how to improve the Council liaison role. This may be with the development of new tools, new processes, training, etc. 1. Did you understand Council’s expectations of you as a liaison to a PDP? If not, what was the gap in understanding? 2. Do you believe the PDP leadership understood the Council’s expectations of your role as liaison to the PDP? If not, what do you believe the PDP leadership understood your role as liaison to be? 3. Do you believe the PDP working group understood the Council’s expectations of your role as liaison to the PDP? If not, what do you believe the PDP working group understood your role as liaison to be? 4. Did you attend PDP working group meetings? If so, how many (e.g., most, some, few)? If you missed meetings, did you have an alternative way to monitor the working group’s progress? 5. Were you engaged with the PDP working group email list? If not, did you have an alternative way to monitor the working group’s progress? 6. Did you attend PDP leadership meetings? If yes, was it beneficial? If not, do you feel that may have been helpful? 7. Did you feel empowered as the liaison to engage the PDP leadership, the PDP working group, and/or Council leadership about challenges? 8. What went well as a liaison? 9. What was your greatest challenge as a liaison? 10. What would you have found helpful to perform your liaison duties more effectively (e.g., tools, information, training, etc.)? Please review and provide your edits/suggestions/comments in the Google doc. Thanks, Darcy

3 3

Proposed Agenda GNSO PDP 3.0 - 27 August at 13:00 UTC
by Ariel Liang Aug. 23, 2019

Aug. 23, 2019

Dear All, Below, please find the proposed agenda for the PDP 3.0 Small Team Meeting on Tuesday, 27 August at 13:00 UTC. 1. Welcome and roll call 2. Proposed workplan/timeline & ICANN66 planning. (45 minutes – Rafik & Ariel ) 3. (time permitting) #11 Enforce Deadlines and Ensure Bite Size Pieces. Seek clarification and guidance. (~TBD minutes - Berry) 4. AOB Best, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 310 804 2761 Skype: ariel.liang.icann www.icann.org

1 0

Actions & Notes: GNSO PDP 3.0 Small Team Meeting 20 August 13:00 UTC
by Ariel Liang Aug. 20, 2019

Aug. 20, 2019

Dear All, Please find below the action items and notes captured during the small team call on Tuesday, 20 August at 13:00 UTC. Staff has post 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/FYfkBg Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) == ACTION ITEMS - Darcy to further refine the anonymous survey related to #13 and share with the Small Team an updated version to review. - Staff to proceed with finalization of the document(s) for #16 and post the relevant link(s) in the status tracking spreadsheet. Staff to assign final call/interim finalization date for #16. - Staff to work with Rafik in seeking Small Team’s direction on #11. NOTES 1. Welcome and roll call 2. #13 Anonymous Survey - Who receives the raw results? Who receives the aggregated results? What type of transparency we want? - Match the survey questions with the expected standards of leaders (Improvement #6). - 360 review for Nomcom is a similar effort. Maybe this survey can follow the practice of 360 review, as the survey results are public. Check whether the 360 review can be duplicated. - Assuming “raw” is still anonymized data – available to Council on request, but generally a summary. Provide the raw data to Council leadership & liaison AND WG leadership. Surely the goal is to be able to check & change course if appropriate? - What is the frequency of the survey? Regular, but hard to envision the exact frequency. It should correspond to the scope / timeline of the PDP. - We should not misuse the survey results for people to complain. It should not discourage leadership to leave a PDP. Survey is to provide the WG members’ view of PDP leadership. - It should have the name of a particular PDP on top of the survey so respondents don’t get mixed up. Have the survey period for at least one week. - If a PDP is only one year, the survey can be conducted at the end as a retrospective type of review. If a PDP lasts multiple years, the survey can be conducted in the middle of the PDP. Frequency is impacted by the length of a PDP. - We may need additional tools to review PDP leadership. - You could pick a fixed timeframe and determine which PDPs are ready for a leadership review? It could have a ‘needs to be in operation for a minimum of x months’? Minimum 6 months, but it remains flexible as if there is something seriously wrong, you don’t even need 6 months to figure that out. - The survey should not be the end of PDP evaluation, but an ongoing evaluation. - So maybe the question is about setting the conditions that can trigger survey before or ahead of scheduled time. The survey is just one input among others to review WG leadership. Regular schedule but with ability to trigger it if there is an indication that something might be amiss? You will also need to factor in the work load for Council leadership, liaison, staff as well as subsequently Council for managing and reviewing the surveys. - ACTION ITEM: Darcy to further refine the anonymous survey and share with the Small Team an updated version to review. 3. #16 Criteria for PDP WG Updates - Presentation of project status and condition procedure document, part of the “work product” - These products provide certain details to show the challenge the PDP is facing. - Budget, it ties with #17. Question about bandwidth. That is one of the main improvements related to #17. Costing of a group is different from its financial resources. - “Overall hours consumed” is not a perfect indicator on the overall resources spent on a PDP. It is a guestimate. Some of these tracking elements will be linked to CRM / Salesforce. -. Reluctant to minutely include/assess/... volunteer/community time; we need to make something out of that piece information, but it's not as if that were a pool of resources which can be shifted to other PDPs.  - We can spend more time on the resourcing of current and future groups. Staff and Community size is complicated. The end goal is that someday we can assign a number to a planned PDP and be able to assign a $$$$ number and the Council make a decision whether that is a PDP they want to launch and expend resources. - Even if it is not a PDP, just understanding how much the effort costs, it can better inform the Council whether the effort should be done or not. - Making rough estimations about how many people are needed from the community? - Can close #16 out based on the discussions today. The only question on #16 is how it gets deployed. Staff will need to make decisions on whether to move toward the same level of consistency across PDP WGs, especially as they have been ongoing with existing methods of providing WG updates. - In several "SDOs/regional organizations" (ITU, IETF, GSMA, ETSI...), none of them measure nor manage volunteer/membership/community time. - We should be conservative about community resources and so having thing in mind when planning activities. We can put some criteria like how much WIP we can cope with, determining the skills needed(from basic to advanced) to make decision. - The SSAC has implemented a max. # of working parties that can be active at the same time. If there are new topics to be dealt with, they are added to the pipeline and only start when another closes. It is trickier in a GNSO environment, but similarly there is a limit here of how many projects can be dealt with at the same time. - SSAC may be different, but in a way this is exactly what the Council has been discussing … we can’t do everything at once. We have to prioritize the work. Be conscious of workload and what we can do at one time. - ACTION ITEM: Staff to proceed with finalization of the document(s) for #16 and post the relevant link(s) in the status tracking spreadsheet. Staff to assign final call/interim finalization date for #16. 4. #11 - Get input on the first three bullet points in the implementation plan. - Create check-list for items that need to happen at the outset of PDP which includes Council / Council leadership to meet with the PDP WG to brief the PDP Team on the charter and its expectations. – This has already been done in certain degree. Need more direction for creating check list for stuff that has already been done. More about documenting these activities and checking whether there are related materials. - ACTION ITEM: Staff to work with Rafik in seeking Small Team’s direction on #11. 5. AOB

1 0

Post Call | PDP 3.0 Call | Tuesday, 20 August 2019 at 13:00 UTC
by Nathalie Peregrine Aug. 20, 2019

Aug. 20, 2019

Dear all, All recordings for the PDP 3.0 call held on Tuesday, 20 August 2019 at 13:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/FYfkBg> (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] FW: Action Items - GNSO PDP 3.0 Small Team Meeting 9 July 2019 at 13:00 UTC
by PAMELALITTLE Aug. 20, 2019

Aug. 20, 2019

Hi Flip, Thank you very much for the memo and the proposed new texts. I like your proposed distinction between a Complaint (3.6) and a Challenge (3.7). I also like the idea of creating a permanent Appeals Committee within the GNSO Council for a number of reasons. To this end, the Council may need to formally charter the Appeals Committee (like the Standing Section Committee and the Standing Committee on [ICANN] Budget and Operations). If so, we will need to consider the appropriate composition, taking into account representativeness, expertise, impartiality, etc. I am also wondering whether such a permanent Appeals Committee: 1. could/should handle both 3.6 and 3.7; 2. could be a substitute for a panel of volunteer mediators (Improvement #15). Or we can consider deferring implementation of Improvement #15 pending trialling a permanent Appeals Committee and see how it works out (or not). Look forward to yo and others' thoughts. Kind regards, Pam ------------------------------------------------------------------ Sender:Flip Petillion <fpetillion(a)petillion.law> Sent At:2019 Jul. 19 (Fri.) 06:43 Recipient:gnso-pdp3dot0-dt@icann.org <gnso-pdp3dot0-dt(a)icann.org> Subject:[GNSO-PDP3Dot0-DT] FW: Action Items - GNSO PDP 3.0 Small Team Meeting 9 July 2019 at 13:00 UTC Flip Petillion fpetillion(a)petillion.law +32484652653 www.petillion.law [signature_1038369082] Attorneys – Advocaten - Avocats From: Flip Petillion <fpetillion(a)petillion.law> Date: Thursday, 18 July 2019 at 11:07 To: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces(a)icann.org> Subject: FW: [GNSO-PDP3Dot0-DT] Action Items - GNSO PDP 3.0 Small Team Meeting 9 July 2019 at 13:00 UTC All, Please find attached an updated memo I have made on the basis of our discussions and the comments that were made in the Google doc. The new memo contains some proposed language for Sections 3.6 and 3.7. Feel free to convert the memo in a Google doc and please share your comments. Best regards, Flip Flip Petillion fpetillion(a)petillion.law +32484652653 www.petillion.law Attorneys – Advocaten – Avocats From: GNSO-PDP3Dot0-DTOn Behalf OfFlip Petillion Sent: 11 July 2019 21:24:21 (UTC+01:00) Brussels, Copenhagen, Madrid, Paris To: Darcy Southwell; Pam Little Cc: GNSO-PDP3Dot0-DT; gnso-pdp3dot0-dt(a)icann.org Subject: Re: [GNSO-PDP3Dot0-DT] Action Items - GNSO PDP 3.0 Small Team Meeting 9 July 2019 at 13:00 UTC I concur Flip Petillion fpetillion(a)petillion.law +32484652653 www.petillion.law [signature_1793451646] Attorneys – Advocaten - Avocats From: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces(a)icann.org> on behalf of Darcy Southwell <darcy.southwell(a)endurance.com> Date: Thursday, 11 July 2019 at 16:20 To: Pam Little <pam.little(a)alibaba-inc.com> Cc: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces(a)icann.org>, "gnso-pdp3dot0-dt(a)icann.org" <gnso-pdp3dot0-dt(a)icann.org> Subject: Re: [GNSO-PDP3Dot0-DT] Action Items - GNSO PDP 3.0 Small Team Meeting 9 July 2019 at 13:00 UTC Agree with Pam here. This is the same idea we discussed in Marrakech. On Wed, Jul 10, 2019 at 10:04 PM Pam Little <pam.little(a)alibaba-inc.com> wrote: Hi Stev & Team The process you described below makes sense to me. Based on your proposed process and our call early this week and to keep us on track, I think it would be helpful to have a simple table set out at least the following: Improvement # Description of Implementation Step Interim Finalization Target Date Final Call Target Date Small Team Lead Thoughts? Kind regards, Pam ------------------------------------------------------------------ Sender:Steve Chan <steve.chan(a)icann.org> Sent At:2019 Jul. 11 (Thu.) 08:47 Recipient:gnso-pdp3dot0-dt@icann.org <gnso-pdp3dot0-dt(a)icann.org> Subject:Re: [GNSO-PDP3Dot0-DT] Action Items - GNSO PDP 3.0 Small Team Meeting 9 July 2019 at 13:00 UTC Dear All, For the following action item, please find the staff understanding: “Staff to send note about process for finalization of implementation items” The process is connected to two of the other action items identified below. Firstly, Rafik and staff will seek to identify which implementation items appear ready for at least interim finalization within this small group. Secondly, Rafik, the relevant small team lead, and staff will package up the relevant materials and send an email to his list for a final call and will operate by non-objection. Once signed off, the implementation plan will be updated the reflect the status change. Rafik, others, if you believe this process is incorrect or needs to be more robust, please let us know. This simple process is envisioned for finalization on an implementation item by implementation item basis. There will still remain an overall validation of the larger package of PDP 3.0 materials, testing with the PDP leadership, and of course Council approval. Best, Steve From: GNSO-PDP3Dot0-DT <gnso-pdp3dot0-dt-bounces(a)icann.org> on behalf of Steve Chan <steve.chan(a)icann.org> Date: Tuesday, July 9, 2019 at 6:22 PM To: "gnso-pdp3dot0-dt(a)icann.org" <gnso-pdp3dot0-dt(a)icann.org> Subject: [GNSO-PDP3Dot0-DT] Action Items - GNSO PDP 3.0 Small Team Meeting 9 July 2019 at 13:00 UTC Dear All, Below, please find the action items captured on the small team call held on Tuesday, 9 July 2019 at 13:00 UTC. The action items have been added to the Wiki (https://community.icann.org/x/B56jBg) and are captured here: Staff to send note about process for finalization of implementation items Rafik/staff to review list of implementation items and determine which are ready for finalization by the PDP 3.0 team. Per action item above, Rafik/staff/lead to package up relevant materials and send to list for final review. Staff to review and ensure that Google documents are available for #4 and #16 Need business process to determine how conditions are set/changed and when intervention by Council is needed. Berry to send a draft business process to team for their consideration. Best, Steve Steven Chan Policy Director, GNSO Support Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Email: steve.chan(a)icann.org Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar See All SO and AC events on the ICANN Global calendar [features.icann.org] _______________________________________________ GNSO-PDP3Dot0-DT mailing list GNSO-PDP3Dot0-DT(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-pdp3dot0-dt _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

2 2