- Gdd-gnso-ppsai-impl - lists.icann.org

7 May PPSAI IRT Meeting Recap
by Jason Kean May 8, 2026

May 8, 2026

Hello IRT, Thank you to all who participated in yesterday’s meeting. The Zoom recording is available on the PPSAI meeting Wiki space<https://icann-community.atlassian.net/wiki/x/AYBnOw>. Please find the meeting recap below. Meeting Topics Covered: * Reviewed updated P/P providers for the purpose of the PPSAI policy<https://docs.google.com/document/d/1zmSg19naS4LG9O0pLvz8u3dJV9Yl_v7q/edit> based on the 23 April discussion<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/996442113/Meeti…> and introduced non-affiliated entities for IRT discussion * Reviewed two updated flow of requirements diagrams - 1. Updated based on input<https://drive.google.com/file/d/1gm4aZaCWcpHIgtCHyuRMvutHgGWIFHm2/view> and 2. Updated based on input and revised to include non-affiliated entities<https://drive.google.com/file/d/1ekVRC2XQwhQdQgY3LsGJzRrW6Y36Hy0E/view> * Discussed IRT member proposal provided on the email list <https://lists.icann.org/hyperkitty/list/gdd-gnso-ppsai-impl@icann.org/threa…> In light of the differing IRT perspectives on who should be considered P/P providers for the purpose of this policy, the group will not finalize the P/P providers or Flow of Requirements diagram to allow for additional discussion. To further inform IRT discussion and drive the conversation towards resolution on these outstanding issues for alignment, ICANN org will develop and introduce a list of PPSAI Consensus Policy requirements for P/P Providers. ICANN org Task: * Develop list of PPSAI Consensus Policy requirements for P/P Providers and share with IRT in advance of the next meeting. Next IRT meeting: * The IRT’s next meeting will be on Thursday, 21 May at 15:30UTC. * Meeting Objective: Review and align on list of P/P Consensus Policy requirements. Thank you all for your continued engagement and contributions. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

REMINDER: PPSAI IRT Task
by Jessica Puccio May 7, 2026

May 7, 2026

Hello PPSAI IRT - A quick reminder to continue the conversation on the PPSAI email list regarding potential solutions to the outstanding issues for alignment. Your input is important to help better understand the IRT perspectives and further develop proposed next steps. Current materials for reference are listed below: * Review of Feedback on Outstanding Issues for Alignment<https://docs.google.com/document/d/182kwPsXtyjZ2zPrhlcdtdM1NWsyp0XKt/edit> * The Zoom recording and transcript are available here<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…>. Note: ICANN org is in the process of developing proposed next steps for resolving outstanding issues based on 23 April discussion and responses on list. Our upcoming session will be Thursday, 07 May at 15:30 UTC (timezone converter here<https://www.timeanddate.com/worldclock/converter.html>). Meeting Objective: Review proposed next steps and determine the path forward. Attached is the .ics file for your records. Kind Regards -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>)

5 5

PPSAI IRT: 23 APR Meeting Recap
by Jason Kean April 23, 2026

April 23, 2026

Hello IRT, Thank you to everyone who participated in today’s meeting. We greatly appreciate the thoughtful discussion and look forward to working through next steps. The Zoom recording is available on the PPSAI meeting Wiki space<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/996442113/Meeti…>. Please find the meeting recap below. Meeting Topics Covered: * IRT feedback on the Outstanding Issues for Alignment paper<https://docs.google.com/document/d/1CjiOdr8FfLPN_rS-18567PaWK0_Ir9Gh/edit#h…>. * Discussion on clarifying questions to better understand how IRT members believe the outstanding issues can be resolved. * Please find the document that guided the discussion here<https://urldefense.com/v3/__https:/docs.google.com/document/d/182kwPsXtyjZ2…>. IRT Task: * Continue discussing potential solutions to the outstanding issues for alignment on the PPSAI email list. ICANN org Tasks: * Develop proposed next steps for resolving outstanding issues based on 23 April discussion and contributions on the email list. * Share proposed next steps with IRT in advance of the next meeting. Next IRT meeting: * The IRT’s next meeting will be on Thursday, 07 May at 15:30UTC. * Meeting Objective: Review proposed next steps and determine the path forward. Please reach out with any questions. Thank you all for your continued engagement and contributions! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

PPSAI IRT document guiding today's discussion 23 April
by Jason Kean April 23, 2026

April 23, 2026

Hello IRT, In preparation for our discussion at 15:30 UTC, we are sharing the Review of Feedback on Outstanding Issues for Alignment document<https://docs.google.com/document/d/182kwPsXtyjZ2zPrhlcdtdM1NWsyp0XKt/edit?u…> which will review the input received on the Outstanding Issues for Alignment paper and introduce clarifying questions for IRT discussion. We look forward to seeing everyone at the meeting. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

2 1

23 April PPSAI IRT Meeting
by Jason Kean April 20, 2026

April 20, 2026

Hello IRT, Thank you to everyone who posted comments in the Outstanding Issues for Alignment paper<https://urldefense.com/v3/__https:/docs.google.com/document/d/1CjiOdr8FfLPN…>. Please find the agenda and objectives for this Thursday’s 23 April IRT meeting at 15:30 UTC below (.ics file attached). Agenda: · Welcome and Work Plan (5 min) · Session Objectives (2 min) · Input on Outstanding Issues for Alignment paper (20min) · Accounting for Resellers (55min) · AOB (8 min) Objective(s): · Review input on Outstanding Issues for Alignment paper · Review and discuss options for accounting for resellers · IRT understanding of task to review and comment on options for resellers Please reach out with any questions. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

REMINDER: PPSAI IRT: 9 APR Meeting Recap
by Jessica Puccio April 15, 2026

April 15, 2026

Hello IRT - A quick reminder that feedback on the Outstanding Issues for Alignment<https://urldefense.com/v3/__https:/docs.google.com/document/d/1CjiOdr8FfLPN…> paper is due by end of day tomorrow, 16 April. Please take a few minutes to provide input directly on the document (here<https://urldefense.com/v3/__https:/docs.google.com/document/d/1CjiOdr8FfLPN…>) so ICANN org can review prior to the next IRT meeting on Thursday, 23 April at 15:30 UTC (.ics file attached). As always, please feel free to reach out with any questions. Kind Regards -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>) On 4/9/26, 16:02, "Jason Kean via Gdd-gnso-ppsai-impl" <gdd-gnso-ppsai-impl(a)icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>> wrote: Hello IRT, Thanks to all who were able to participate in today’s meeting. We greatly appreciated the lively discussion. Please find a recap of the meeting, the current IRT task, and information on the next meeting below. The Zoom recording is available on the PPSAI meeting Wiki space [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…>. Meeting Topics Covered: * Outstanding Issues for Alignment * ICANN org’s proposed definition of “knowingly” * Who is and who may not be considered a privacy or proxy provider for purposes of the new P/P Consensus Policy * How to account for resellers IRT Task: * Review and provide comments on the Outstanding Issues for Alignment paper [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1CjiOdr8FfLPN…> by the end of day 16 April. * Please comment in the highlighted sections - links to these sections are bookmarked in the table at the top of page 2 under IRT Instructions. * Following receipt of IRT input, the IPT will review and respond to the IRT’s input in advance of the next IRT meeting. Next IRT meeting: * The IRT’s next meeting will be on Thursday, 23 April at 15:30UTC. * The goal of this meeting will be to review the IRT’s input, continue discussion as needed, and align on a path forward for the outstanding issues. Please don’t hesitate to reach out with any questions. Thank you all for your commitment and contributions to this work! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

PPSAI IRT: 9 APR Meeting Recap
by Jason Kean April 9, 2026

April 9, 2026

Hello IRT, Thanks to all who were able to participate in today’s meeting. We greatly appreciated the lively discussion. Please find a recap of the meeting, the current IRT task, and information on the next meeting below. The Zoom recording is available on the PPSAI meeting Wiki space<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/931102721/Meeti…>. Meeting Topics Covered: * Outstanding Issues for Alignment * ICANN org’s proposed definition of “knowingly” * Who is and who may not be considered a privacy or proxy provider for purposes of the new P/P Consensus Policy * How to account for resellers IRT Task: * Review and provide comments on the Outstanding Issues for Alignment paper<https://docs.google.com/document/d/1CjiOdr8FfLPN_rS-18567PaWK0_Ir9Gh/edit#h…> by the end of day 16 April. * Please comment in the highlighted sections - links to these sections are bookmarked in the table at the top of page 2 under IRT Instructions. * Following receipt of IRT input, the IPT will review and respond to the IRT’s input in advance of the next IRT meeting. Next IRT meeting: * The IRT’s next meeting will be on Thursday, 23 April at 15:30UTC. * The goal of this meeting will be to review the IRT’s input, continue discussion as needed, and align on a path forward for the outstanding issues. Please don’t hesitate to reach out with any questions. Thank you all for your commitment and contributions to this work! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

9 April PPSAI IRT Meeting
by Jason Kean March 31, 2026

March 31, 2026

Hello IRT, Thank you to all those who participated in the requirements flow wrap-up discussion and the robust dialogue on resellers, “knowingly” related issues, and existing policy and contractual related requirements related to privacy and proxy services at our ICANN85 meeting. I hope that everyone who attended in-person had an uneventful trip home. In response to IRT’s input, the ICANN org team has been working to, 1. develop a paper to align with the IRT on current thinking related to “knowingly,” including with regard to resellers, and 2. in parallel, streamline the initial Consensus Policy draft to make sure it leverages all relevant policies and existing contractual obligations, including but not limited to the Registration Data Policy and RAA. We believe it is critical to resolve both points to ensure the IRT’s input fully informs the initial policy draft before the language is finalized for IRT review. Following resolution, ICANN org will finalize the draft Consensus Policy and share with the IRT for review. Next IRT Meeting * The next IRT meeting will be on Thursday, 9 April at 15:30 UTC (.ics file attached). * The goal of this meeting is to review current thinking on knowingly and resellers and facilitate IRT discussion. Please don’t hesitate to reach out with any questions. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

ZOOM INFO: PPSAI IRT Meeting | #29 | Tuesday, 10 MAR | 3:30 UTC | 60 Mins
by Jessica Puccio March 9, 2026

March 9, 2026

Hello PPSAI IRT Members - Room information and Zoom links have been posted. Hope to see everyone there! Tuesday March 10, 2026 Room 301<https://icann85.sched.com/venue/Room+301> 09:00 IST (UTC+5.5), 10 March 2026 03:30 UTC, 10 March 2026. Participation Links To ensure transparency of participation in ICANN’s multistakeholder model, please remember to sign in to Zoom sessions using your full name (e.g. First Name + Last Name/Surname). • Zoom Meeting Link: https://icann.zoom.us/j/94007968859?pwd=gcOqASd2EeZbGzlAU3PNunaIvNJP1b.1 • Zoom Meeting ID: 940 0796 8859 • Zoom Meeting Passcode: wBX$A9JSn$ • Zoom International Dial-In Numbers: https://icann.zoom.us/u/abSYHfsjrQ • Zoom Phone Passcode: 733 726 6535 for today’s meeting. Kind Regards -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>)

1 0

REMINDER: PPSAI IRT Meeting | #29 | Tuesday, 10 MAR | 3:30 UTC | 60 Mins
by Jessica Puccio March 5, 2026

March 5, 2026

Hello PPSAI IRT - A quick reminder about our upcoming session at ICANN85 on Tuesday, 10 March at 3:30 UTC | 09:00 IST (timezone converter here<https://www.timeanddate.com/worldclock/converter.html>). Attached is the .ics file for your records. Zoom information will be sent no sooner than 24 hours in advance and can also be found on the schedule: GDS: PPSAI IRT Working Session<https://icann85.sched.com/my-schedule#:~:text=to%20My%20Schedule-,GDS%3A%20…>. The goal for this session is to finalize and accept the Draft Requirements Flow Visual as the basis for the Draft Consensus Policy. Note: this is a 60 minute session only. Next IRT Meeting: * The next IRT Meeting | #30 | is tentatively scheduled for Thursday, 09 April, to allow staff to develop a Draft Consensus Policy. Safe travels to those heading to Mumbai to join ICANN85 in person. Looking forward to seeing you soon! Kind Regards -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>)

1 0

FOLLOW-UP: PPSAI IRT Meeting | #28 | Thursday, 05 FEB | 15:30 UTC | 90 Mins
by Jessica Puccio Feb. 27, 2026

Feb. 27, 2026

Hello IRT - A quick reminder that feedback on the Draft Requirements Flow Visual is due end of day today, 27 February. Please take a few minutes to leave your comments directly on the document here<https://urldefense.com/v3/__https:/drive.google.com/file/d/1zcI63Yp8rEc5LLZ…> so ICANN org can review prior to the next IRT meeting at ICANN85 on Tuesday, 10 March at 3:30 UTC (.ics file attached). Next Step(s): * Register for ICANN85<https://meetings.icann.org/en/meetings/icann85/> and remember to book the GDS: PPSAI IRT Working Session<https://icann85.sched.com/my-schedule#:~:text=to%20My%20Schedule-,GDS%3A%20…> to your schedule. * The next meeting will be 10 MAR at ICANN85 (03:30 UTC | 09:00 IST (timezone converter here<https://www.timeanddate.com/worldclock/converter.html>)) - the goal will be to finalize and accept the Draft Requirements Flow Visual as the basis for the Draft Consensus Policy. As always, please feel free to reach out with any questions. Kind Regards -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>)

1 0

REMINDER: 19 FEB meeting cancelled - IRT input on Draft Requirements Flow Visual due 26 FEB
by Jessica Puccio Feb. 17, 2026

Feb. 17, 2026

This is a friendly reminder that the IRT session for Thursday, 19 February is cancelled. IRT members are asked to socialize the attached Draft Requirements Flow Visual PDF document with your respective groups. Please post all input either directly on the Draft Requirements Flow Visual<https://drive.google.com/file/d/1zcI63Yp8rEc5LLZJRk2VR-0MJCDVqRMs/view> or on-list by end of day, Thursday, 26 February. Following receipt of IRT input, ICANN org will review and respond to the comments ahead of our next discussion at ICANN85 on Tuesday, 10 March at 3:30 UTC<https://icann85.sched.com/event/2Gwnn/gds-ppsai-irt-working-session> (placeholder .ics file attached). The goal of this meeting is to finalize the Requirements Flow Visual. Please don’t hesitate to reach out with any questions. Best Regards, -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>)

1 0

PPSAI IRT: 5 Feb Meeting Recap
by Jason Kean Feb. 6, 2026

Feb. 6, 2026

Hello IRT, Thanks to all who were able to participate in yesterday's meeting. Please find a recap of the topics covered, the current IRT task, and information on the next meeting below. The Zoom recordings and slide deck are available on the PPSAI meeting Wiki space<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/776175617/Meeti…>. Topics covered: * Plan for Finalizing Requirements Flow * ICANN org and the IRT agreed to cancel the IRT’s 19 February meeting to allow members more time to socialize the Draft Requirements Flow Visual with their respective groups. * The new deadline for input on the Draft Requirements Flow is 27 February. * IRT input will be discussed at the IRT’s 10 March ICANN85 session with the goal of finalizing the Requirements Flow document. * Once the Requirements Flow finalized, ICANN org will develop draft Consensus Policy language for IRT discussion following the sequence of work outlined in the project Work Breakdown<https://icann-community.atlassian.net/wiki/pages/viewpageattachments.action…> for Deliverable #3: Draft Consensus Policy. * Review of IRT comments on Draft Requirements Flow Visual * ICANN org reviewed IRT comments, ICANN org responses, and facilitated an open discussion on the Draft Requirements Flow. * IRT comments and ICANN org responses on the Draft Requirements Flow Visual are still live in the document. * Current comments can also be found on page 3 of the attached Draft Requirements Flow Visual PDF for reference. IRT Task: * Socialize the attached Draft Requirements Flow Visual PDF document with your groups and interested community members. * Provide additional comments on the Draft Requirements Flow Visual<https://drive.google.com/file/d/1zcI63Yp8rEc5LLZJRk2VR-0MJCDVqRMs/view> (link to PPSAI IRT working folder - access is restricted to IRT members). * Input in the document is due by the end of day 27 February. Step-by-step instructions for posting comments in this file are attached to this email for reference. * Following receipt of IRT input, the ICANN org will review and respond to the IRT’s comments in advance of the next IRT meeting. Next IRT meeting: * The IRT’s next meeting will be at ICANN85 on Tuesday, 10 March at 3:30 UTC (a meeting invite and .ics file will be sent within the week). * The goal of this meeting will be to finalize the Requirements Flow Visual. Please don’t hesitate to reach out with any questions. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Feb. 3, 2026

Hello All, Please find the agenda and objectives for the IRT meeting, Thursday, 05 February, below: Agenda * Welcome and Work Plan (5 min) * Session Objectives (2 min) * Review of input on Draft Requirements Flow Visual (75 min) * AOB (8 min) Objectives 1. Review IRT input on Draft Requirements Flow Visual 2. IRT understanding of task to review, share, and comment on the Draft Requirements Flow Visual We look forward to seeing everyone on Thursday at 15:30 UTC. -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>)

1 0

REMINDER: Feedback Due 29 JAN - DRAFT Requirement Flow Visual
by Jessica Puccio Jan. 30, 2026

Jan. 30, 2026

Hello IRT - This is a friendly reminder to please take some time to review the Draft Requirements Flow<https://drive.google.com/file/d/1zcI63Yp8rEc5LLZJRk2VR-0MJCDVqRMs/view?usp=…> visual and share your comments ahead of our next discussion. As you view the graphic, please note the goal is to provide a visual means to understand the course of requirements to ultimately produce a draft Consensus Policy. Please have all feedback submitted directly on the graphic<https://drive.google.com/file/d/1zcI63Yp8rEc5LLZJRk2VR-0MJCDVqRMs/view?usp=…> by EOD, Thursday, 29 January; only highlighting the specific area of related text when making comments. Instructions attached. Thank you for your time and cooperation. Best Regards, -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>)

3 2

PPSAI IRT: 22 Jan Meeting Recap
by Jason Kean Jan. 23, 2026

Jan. 23, 2026

Hello IRT, Thanks to all who were able to participate in yesterday's meeting. Please find a recap of the topics covered, the current IRT task, and information on the next IRT meeting below. The Zoom recordings and slide deck are available on the PPSAI meeting wiki space [<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/668008449/Meeti…>icann-community.atlassian.net<http://icann-community.atlassian.net>]<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/668008449/Meeti…>. Recap of topics covered: * Review of IRT comments on Draft Implementation Plan * ICANN org reviewed an IRT question regarding the Human Rights Impact Assessment and two suggested edits to the Summary of Recommendations section. * All IRT comments were resolved, and the Implementation Plan was finalized. The Final Implementation Plan is located here<https://icann-community.atlassian.net/wiki/pages/viewpageattachments.action…>. * Introduction of Draft Requirements Flow Visual * ICANN org reviewed the recent history of the accreditation discussions: Threshold Question B > requested guidance from the GNSO Council<https://icann-community.atlassian.net/wiki/pages/viewpageattachments.action…> on whether the policy recommendations would preclude any of the 4 IRT discussed accreditation models > GNSO Council’s guidance<https://icann-community.atlassian.net/wiki/pages/viewpageattachments.action…>. * ICANN org introduced the Requirements Flow Visual (PDF attached) - noting that it is based on the guidance received from the GNSO Council and IRT discussions on potential accreditation models. * ICANN org clarified that the intent is to focus IRT discussions on the flow of requirements to reach alignment for the Consensus Policy. IRT Task: * Review the Requirements Flow Visual<https://drive.google.com/file/d/1zcI63Yp8rEc5LLZJRk2VR-0MJCDVqRMs/view> (link to PPSAI IRT working folder - access is restricted to IRT members) and post initial comments by the end of day 29 January. Please find instructions for posting comments in this file attached. * Following receipt of IRT input, the IPT will review and respond to the IRT’s comments in advance of the next IRT meeting. Next IRT meeting: * The IRT’s next meeting will be on Thursday, 5 February at 15:30 UTC (.ics attached). * The goal of this meeting is to review and discuss all comments posted on the Requirements Flow Visual and facilitate further discussion on the flow of requirements. Please don’t hesitate to reach out with any questions. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Re: [Invt-gdd-gnso-ppsai-impl] A question regarding today's PPSAI IRT meeting (Today | Thursday 22 2026 | 15:30 UTC) and going forward)
by Jessica Puccio Jan. 22, 2026

Jan. 22, 2026

Hi John – Happy New Year and thank you for reaching out. Yes, we plan to continue using a format similar to what was done previously. Post-meeting summaries will be shared 24 - 48 hours following each session. Appreciate your engagement and thank you for sharing these updates more broadly. Kind Regards -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>) On 1/22/26, 15:36, "John McCabe via Invt-gdd-gnso-ppsai-impl" <invt-gdd-gnso-ppsai-impl(a)icann.org<mailto:invt-gdd-gnso-ppsai-impl@icann.org>> wrote: Hi Jessica, and Happy New Year to you and the entire PPSAI IRT team! In the lead-up to presenting to the GNSO, Jason regularly sent out post-meeting follow-up summaries to the IRT membership. As the representative to the PPSAI IRT, I found these useful info to share with the RySG membership as well as the referenced link lists included. We are now in the post-GNSO guidance resumption of the IRT’s work, and I’m wondering if such a distribution will be forthcoming going forward, or if I should endeavor to pull them together in the weeks/months ahead on an ad hoc basis (they don’t burden recipients with zero interest, but hold out the potential for further discovery via the links for any and all.) Might you please enlighten me as to what I may expect going forward in the next phase of our work? Thank you for your guidance! John McCabe RySG representative PPSAI IRT 212-877-8943 On Jan 22, 2026, at 9:38 AM, Jessica Puccio via Invt-gdd-gnso-ppsai-impl <invt-gdd-gnso-ppsai-impl(a)icann.org> wrote: Hello PPSAI IRT, Reminder that the PPSAI IRT Meeting #27 will be starting in approximately 60 minutes. Join Zoom Meeting: https://icann.zoom.us/j/94751600178?pwd=aNskiz0YIpeYsFSecHXPIM2fYaFkcV.1 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/94751600178?pwd=aNskiz0Y…> Meeting ID: 947 5160 0178 Passcode: ^=51.zA?H5 Find your local number: https://icann.zoom.us/u/avV0Qo1vH [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/avV0Qo1vH__;!!PtGJab4!6i…> -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>) From: jessica.puccio(a)icann.org<mailto:jessica.puccio@icann.org> When: 10:30 - 12:00 January 22, 2026 Subject: PPSAI IRT Meeting | #27 | Thursday, 22 JAN | 15:30 UTC | 90 Mins Location: https://icann.zoom.us/j/94751600178?pwd=aNskiz0YIpeYsFSecHXPIM2fYaFkcV.1 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/94751600178?pwd=aNskiz0Y…> This invite is for the PPSAI IRT meeting, scheduled for Thursday, 22 JAN | 15:30 UTC | 90 minutes. Participation details are copied below and a static .ics file will be sent in a separate email for your convenience. Join Zoom Meeting: https://icann.zoom.us/j/94751600178?pwd=aNskiz0YIpeYsFSecHXPIM2fYaFkcV.1 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/94751600178?pwd=aNskiz0Y…> Meeting ID: 947 5160 0178 Passcode: ^=51.zA?H5 Find your local number: https://icann.zoom.us/u/avV0Qo1vH [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/avV0Qo1vH__;!!PtGJab4!6i…> -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>) <PPSAI IRT Meeting #27 Thursday, 22 JAN 15-30 UTC 90 Mins.ics>_______________________________________________ Invt-gdd-gnso-ppsai-impl mailing list -- invt-gdd-gnso-ppsai-impl(a)icann.org<mailto:invt-gdd-gnso-ppsai-impl@icann.org> To unsubscribe send an email to invt-gdd-gnso-ppsai-impl-leave(a)icann.org<mailto:invt-gdd-gnso-ppsai-impl-leave@icann.org>

2 1

Re: [Ext] Re: PPSAI IRT: 8 Jan Meeting Recap (Response to request for PP provider list)
by Jason Kean Jan. 21, 2026

Jan. 21, 2026

Hi Luc, Regarding your request for a list of PP providers, while registrars are required to provide information to ICANN in the RIS in re PP providers, this information is not currently made publicly available. We look forward to discussing ways to produce such a list with the IRT. Please let us know if you have any other questions. Thanks. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> From: Jason Kean via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Reply-To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org> Date: Tuesday, January 13, 2026 at 8:12 PM To: Luc SEUFER <lseufer(a)namespace.com>, "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org> Cc: Jason Kean <jason.kean(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] Re: [Ext] Re: PPSAI IRT: 8 Jan Meeting Recap Hi Luc, Thank you for your emails and your comments in the Implementation Plan document. Regarding your request for access to a list of affiliated P/P providers, we are looking into this and will get back to you as soon as possible. Regarding your inquiry about the participation of ICANN org’s Finance team, we do not view Finance as a core member of the ICANN org implementation team because we do not believe the recommendations will have a significant impact on Finance’s function or require its ongoing participation through the implementation phases. However, during the process of implementation, we will provide regular cross-functional updates and engage different functions as necessary as the work progresses. We are also not currently envisioning the type of accreditation program that was originally proposed by the 2016 IRT (Model 1 discussed last year by this IRT). During our next phase of work, following finalization of the Implementation Plan, the IPT will share a proposed flow of requirements based on the IRT’s input on previously discussed accreditation models [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/pages…>, consistent with the GNSO Council’s guidance [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/pages…>. These discussions will serve as the foundation for Consensus Policy drafting, as outlined in the work breakdown and Implementation Plan. We look forward to discussing further soon. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> From: Luc SEUFER <lseufer(a)namespace.com> Date: Tuesday, January 13, 2026 at 11:30 AM To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org>, Jason Kean <jason.kean(a)icann.org> Cc: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Ext] Re: PPSAI IRT: 8 Jan Meeting Recap Hi Jason, Me again. I was listening to the recordings and realised I may not have fully understood your reply to my question. Sorry about that. Could you please confirm that no member of the ICANN Finance team is involved because ICANN does not intend to turn this accreditation system into a revenue-generating mechanism, in particular by introducing a high accreditation fee, as was briefly envisaged by your predecessors? Thank you for your patience. Best regards, Luc On 12/01/2026 15:05, « Luc SEUFER via Gdd-gnso-ppsai-impl » <gdd-gnso-ppsai-impl(a)icann.org> said : Ji Jason et al, I have a somewhat related request for ICANN Org. To help us make an informed decision when implementing the plan, it would be useful to have access to a list of affiliated P/P providers. My understanding is that ICANN already maintains such a list, as registrars are required to disclose these providers in the RIRs. Having this information would allow us to assess actual, existing services rather than relying on theoretical models. I do not believe this information is subject to confidentiality obligations, so I assume there should be no obstacle to sharing it. Many thanks, Luc De : Jason Kean via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Date : vendredi, 9 janvier 2026 à 18:33 À : gdd-gnso-ppsai-impl(a)icann.org <gdd-gnso-ppsai-impl(a)icann.org> Cc : Jason Kean <jason.kean(a)icann.org> Objet : [Gdd-gnso-ppsai-impl] PPSAI IRT: 8 Jan Meeting Recap Hello IRT, Thanks to all who were able to participate in yesterday's meeting. Please find a recap of the meeting, the current IRT task, and information on the next meeting below. The Zoom recording is available on the PPSAI meeting Wiki space [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…>. Meeting topics covered: * High-level review of GNSO Council guidance * The IPT reviewed the Council’s guidance [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/pages…> to reorient IRT members. * The IPT and IRT will revisit the Council’s guidance in greater detail in future implementation discussions. * Introduction of Draft Implementation Plan * The Draft Implementation Plan [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/19v42_DCrNhR2…> was reviewed at a high-level to orient IRT members on the content and structure, and to highlight the inputs and considerations taken into account for planning, in accordance with the Consensus Policy Implementation Framework (CPIF)<https://www.icann.org/uploads/ckeditor/CPIF_v2.0_2019CLEAN.pdf> and the <https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug…> IRT Principles & Guidelines<https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug…>. * The IPT additionally shared a work breakdown [drive.google.com]<https://urldefense.com/v3/__https:/drive.google.com/file/d/1qrwH3I3i5F5o6KT…> to show how the work would be organized. IRT Task: * Review the Draft Implementation Plan [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/19v42_DCrNhR2…> by the end of day 15 January. Please highlight the appropriate area of text and add your comments accordingly. * Following receipt of IRT input, the IPT will review and respond to the IRT’s input in advance of the next IRT meeting. Next IRT meeting: * The IRT’s next meeting will be on Thursday, 22 January at 15:30UTC. * The goal of this meeting will be for the IRT and IPT to align on the Implementation Plan and finalize the document. Please don’t hesitate to reach out with any questions. Thank you all for your commitment and contributions to this important work! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org/>

1 0

PPSAI IRT Meeting 22 Jan 15:30 UTC : Agenda and Objectives
by Jason Kean Jan. 20, 2026

Jan. 20, 2026

Hello IRT, Please find the agenda and objectives for Thursday’s 22 January IRT meeting below: Agenda * Welcome and Work Plan (5 min) * Session Objectives (2 min) * Review of Implementation Plan and IRT comments (20 min) * Introduction of Draft Requirements Flow Visual (55 min) * AOB (8 min) Objectives * Review IRT input on Implementation Plan and finalize document * IRT understanding of the purpose and structure of the Draft Requirements Flow Visual * IRT understanding of task to review and comment on the Draft Requirements Flow Visual We look forward to seeing everyone on Thursday at 15:30 UTC. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Re: [Ext] Re: PPSAI IRT: 8 Jan Meeting Recap
by Jason Kean Jan. 15, 2026

Jan. 15, 2026

Hi Luc, Thank you for your emails and your comments in the Implementation Plan document. Regarding your request for access to a list of affiliated P/P providers, we are looking into this and will get back to you as soon as possible. Regarding your inquiry about the participation of ICANN org’s Finance team, we do not view Finance as a core member of the ICANN org implementation team because we do not believe the recommendations will have a significant impact on Finance’s function or require its ongoing participation through the implementation phases. However, during the process of implementation, we will provide regular cross-functional updates and engage different functions as necessary as the work progresses. We are also not currently envisioning the type of accreditation program that was originally proposed by the 2016 IRT (Model 1 discussed last year by this IRT). During our next phase of work, following finalization of the Implementation Plan, the IPT will share a proposed flow of requirements based on the IRT’s input on previously discussed accreditation models<https://icann-community.atlassian.net/wiki/pages/viewpageattachments.action…>, consistent with the GNSO Council’s guidance<https://icann-community.atlassian.net/wiki/pages/viewpageattachments.action…>. These discussions will serve as the foundation for Consensus Policy drafting, as outlined in the work breakdown and Implementation Plan. We look forward to discussing further soon. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> From: Luc SEUFER <lseufer(a)namespace.com> Date: Tuesday, January 13, 2026 at 11:30 AM To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org>, Jason Kean <jason.kean(a)icann.org> Cc: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Ext] Re: PPSAI IRT: 8 Jan Meeting Recap Hi Jason, Me again. I was listening to the recordings and realised I may not have fully understood your reply to my question. Sorry about that. Could you please confirm that no member of the ICANN Finance team is involved because ICANN does not intend to turn this accreditation system into a revenue-generating mechanism, in particular by introducing a high accreditation fee, as was briefly envisaged by your predecessors? Thank you for your patience. Best regards, Luc On 12/01/2026 15:05, « Luc SEUFER via Gdd-gnso-ppsai-impl » <gdd-gnso-ppsai-impl(a)icann.org> said : Ji Jason et al, I have a somewhat related request for ICANN Org. To help us make an informed decision when implementing the plan, it would be useful to have access to a list of affiliated P/P providers. My understanding is that ICANN already maintains such a list, as registrars are required to disclose these providers in the RIRs. Having this information would allow us to assess actual, existing services rather than relying on theoretical models. I do not believe this information is subject to confidentiality obligations, so I assume there should be no obstacle to sharing it. Many thanks, Luc De : Jason Kean via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Date : vendredi, 9 janvier 2026 à 18:33 À : gdd-gnso-ppsai-impl(a)icann.org <gdd-gnso-ppsai-impl(a)icann.org> Cc : Jason Kean <jason.kean(a)icann.org> Objet : [Gdd-gnso-ppsai-impl] PPSAI IRT: 8 Jan Meeting Recap Hello IRT, Thanks to all who were able to participate in yesterday's meeting. Please find a recap of the meeting, the current IRT task, and information on the next meeting below. The Zoom recording is available on the PPSAI meeting Wiki space [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/space…>. Meeting topics covered: * High-level review of GNSO Council guidance * The IPT reviewed the Council’s guidance [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/pages…> to reorient IRT members. * The IPT and IRT will revisit the Council’s guidance in greater detail in future implementation discussions. * Introduction of Draft Implementation Plan * The Draft Implementation Plan [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/19v42_DCrNhR2…> was reviewed at a high-level to orient IRT members on the content and structure, and to highlight the inputs and considerations taken into account for planning, in accordance with the Consensus Policy Implementation Framework (CPIF)<https://www.icann.org/uploads/ckeditor/CPIF_v2.0_2019CLEAN.pdf> and the <https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug…> IRT Principles & Guidelines<https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug…>. * The IPT additionally shared a work breakdown [drive.google.com]<https://urldefense.com/v3/__https:/drive.google.com/file/d/1qrwH3I3i5F5o6KT…> to show how the work would be organized. IRT Task: * Review the Draft Implementation Plan [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/19v42_DCrNhR2…> by the end of day 15 January. Please highlight the appropriate area of text and add your comments accordingly. * Following receipt of IRT input, the IPT will review and respond to the IRT’s input in advance of the next IRT meeting. Next IRT meeting: * The IRT’s next meeting will be on Thursday, 22 January at 15:30UTC. * The goal of this meeting will be for the IRT and IPT to align on the Implementation Plan and finalize the document. Please don’t hesitate to reach out with any questions. Thank you all for your commitment and contributions to this important work! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org/>

2 2

PPSAI IRT: 8 Jan Meeting Recap
by Jason Kean Jan. 13, 2026

Jan. 13, 2026

Hello IRT, Thanks to all who were able to participate in yesterday's meeting. Please find a recap of the meeting, the current IRT task, and information on the next meeting below. The Zoom recording is available on the PPSAI meeting Wiki space<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/581861377/Meeti…>. Meeting topics covered: * High-level review of GNSO Council guidance * The IPT reviewed the Council’s guidance<https://icann-community.atlassian.net/wiki/pages/viewpageattachments.action…> to reorient IRT members. * The IPT and IRT will revisit the Council’s guidance in greater detail in future implementation discussions. * Introduction of Draft Implementation Plan * The Draft Implementation Plan<https://docs.google.com/document/d/19v42_DCrNhR2hWt7otXxL3MzkG0mmMde/edit?u…> was reviewed at a high-level to orient IRT members on the content and structure, and to highlight the inputs and considerations taken into account for planning, in accordance with the Consensus Policy Implementation Framework (CPIF)<https://www.icann.org/uploads/ckeditor/CPIF_v2.0_2019CLEAN.pdf> and the IRT Principles & Guidelines<https://www.icann.org/en/system/files/files/irt-principles-guidelines-23aug…>. * The IPT additionally shared a work breakdown<https://drive.google.com/file/d/1qrwH3I3i5F5o6KTzI7MoySGo70esDgn2/view?usp=…> to show how the work would be organized. IRT Task: * Review the Draft Implementation Plan<https://docs.google.com/document/d/19v42_DCrNhR2hWt7otXxL3MzkG0mmMde/edit?u…> by the end of day 15 January. Please highlight the appropriate area of text and add your comments accordingly. * Following receipt of IRT input, the IPT will review and respond to the IRT’s input in advance of the next IRT meeting. Next IRT meeting: * The IRT’s next meeting will be on Thursday, 22 January at 15:30UTC. * The goal of this meeting will be for the IRT and IPT to align on the Implementation Plan and finalize the document. Please don’t hesitate to reach out with any questions. Thank you all for your commitment and contributions to this important work! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

2 2

REMINDER: Feedback Due 15 JAN - PPSAI IRT Implementation Plan
by Jessica Puccio Jan. 12, 2026

Jan. 12, 2026

Hello IRT - This is a friendly reminder to please take some time to review the Draft Implementation Plan<https://docs.google.com/document/d/19v42_DCrNhR2hWt7otXxL3MzkG0mmMde/edit> and share your comments ahead of our next discussion. As you read through the document<https://docs.google.com/document/d/19v42_DCrNhR2hWt7otXxL3MzkG0mmMde/edit>, please note the areas discussed in the 08 JAN meeting, including the role and participation expectations of an IRT member, along with the deliverables and a high-level timeline. The goal of this plan is to give us a shared roadmap for driving this project forward. Please have all feedback submitted directly on the document<https://docs.google.com/document/d/19v42_DCrNhR2hWt7otXxL3MzkG0mmMde/edit> by EOD, Thursday, 15 January; only highlighting the specific area of related text when making comments. Thank you for your time and cooperation. Best Regards, -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>)

1 0

PPSAI IRT will reconvene 8 January 2026
by Jason Kean Dec. 8, 2025

Dec. 8, 2025

Hello IRT, To avoid restarting IRT work right before the upcoming holiday season, the IRT will reconvene in the new year on Thursday 8 January 2026. The first session will focus on the review of the PPSAI Implementation Plan. The Implementation Plan will provide an overview of the project and a schedule for work activities, deliverables, and milestones. Following IRT alignment on the Implementation Plan, we will review the GNSO Council PPSAI Small Team’s guidance<https://icann-community.atlassian.net/wiki/pages/viewpageattachments.action…> and begin work on accreditation models / the flow of requirements. Meeting invitations for the first few sessions will be sent shortly. The IPT looks forward to working with the IRT on this next phase of work in the new year! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Update: Receipt of PPSAI Small Team Guidance and Next Steps
by Jason Kean Nov. 13, 2025

Nov. 13, 2025

Hello IRT, Congratulations on receiving GNSO Council guidance on PPSAI implementation (attached)! And congratulations to Ashley Heineman for being named Council Liaison to the PPSAI IRT! In response to the Council’s guidance, ICANN org has started working on an Implementation Plan to draft and implement Consensus Policy for PPSAI recommendations. We plan on reconvening the IRT in December to review and align on the Implementation Plan and resuming a regular cadence of IRT meetings in January. Please be on the lookout for meeting invitations in the coming weeks. The ICANN org team looks forward to working with the IRT on this next phase of work! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Re: [Ext] PPSAI IRT Answers to Threshold Questions from Council
by Jason Kean Nov. 13, 2025

Nov. 13, 2025

Dear Susan, Thank you for the Council’s responses to the IRT’s requested guidance. And many thanks to Paul for shepherding this work forward as Council Liaison to the PPSAI IRT. We look forward to working with Ashley Heineman as the new Council Liaison to the PPSAI IRT moving forward. The ICANN org team is excited to start the next phase of implementation work with the IRT. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> From: Susan Payne <susan.payne(a)comlaude.com> Date: Thursday, November 13, 2025 at 11:19 AM To: Jason Kean <jason.kean(a)icann.org> Cc: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org>, John Emery <john.emery(a)icann.org>, Caitlin Tubergen <caitlin.tubergen(a)icann.org>, Anne ICANN via council <council(a)icann.org> Subject: [Ext] PPSAI IRT Answers to Threshold Questions from Council Dear Jason, In response to your request, as PPSAI Project Manager, to Council on 1 August 2025 concerning the Privacy and Proxy Services Accreditation Issues (PPSAI) Threshold Questions (TQ), please find the attached responses from Council. The PPSAI Small Team, chaired by Paul McGrady worked diligently to provide helpful and consensus-driven responses, which were presented at the ICANN84 GNSO Council meeting and amended to updated language for TQ B. Having received no objections from Councilors by the deadline, I am pleased to send these responses on the PPSAI TQs from the GNSO Council to ICANN org and the PPSAI IRT. We look forward to the updates from our new Council Liaison to the PPSAI IRT, Ashley Heineman. Thank you, Susan Payne GNSO Council Chair ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com__;!!PtGJab4!5Tbwbtvllb03ifi…>

1 0

PPSAI IRT Answers to Threshold Questions from Council
by Susan Payne Nov. 13, 2025

Nov. 13, 2025

Dear Jason, In response to your request, as PPSAI Project Manager, to Council on 1 August 2025 concerning the Privacy and Proxy Services Accreditation Issues (PPSAI) Threshold Questions (TQ), please find the attached responses from Council. The PPSAI Small Team, chaired by Paul McGrady worked diligently to provide helpful and consensus-driven responses, which were presented at the ICANN84 GNSO Council meeting and amended to updated language for TQ B. Having received no objections from Councilors by the deadline, I am pleased to send these responses on the PPSAI TQs from the GNSO Council to ICANN org and the PPSAI IRT. We look forward to the updates from our new Council Liaison to the PPSAI IRT, Ashley Heineman. Thank you, Susan Payne GNSO Council Chair ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the "Com Laude Group") does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com<https://comlaude.com>

1 0

PPSAI Small Team presentation to Council tomorrow 29 October
by Jason Kean Oct. 28, 2025

Oct. 28, 2025

Hello IRT, Friendly reminder that GNSO Council will discuss the PPSAI Small Team’s proposed responses<https://gnso.icann.org/sites/default/files/policy/2025/draft/ppsai-small-te…> to the IRT’s requested guidance<https://gnso.icann.org/sites/default/files/policy/2025/draft/ppsai-irt-tq-r…> tomorrow, 29 October from 13:15 to 15:15<https://icann84.sched.com/event/29QND/gnso-council-meeting-part-1-of-2> Dublin local time. We will follow-up with the IRT to outline next steps following the Council’s discussion. I hope all those attending ICANN84 are having a productive meeting! Best, Jason From: Jason Kean <jason.kean(a)icann.org> Date: Thursday, October 9, 2025 at 7:04 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: Update: PPSAI Small Team work Hello IRT, The PPSAI Small Team recently completed its proposed responses<https://gnso.icann.org/sites/default/files/policy/2025/draft/ppsai-small-te…> to the IRT’s requested guidance<https://gnso.icann.org/sites/default/files/policy/2025/draft/ppsai-irt-tq-r…>. The proposed responses were distributed to the GNSO Council via its mailing list on 29 September. The GNSO Council will discuss the small team’s proposed responses at ICANN84 on Wednesday, 29 October from 13:15 to 15:15 Dublin local time. We will follow-up with the IRT to outline next steps following the Council’s discussion. Safe travels to all those attending ICANN84! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Update: PPSAI Small Team work
by Jason Kean Oct. 9, 2025

Oct. 9, 2025

Hello IRT, The PPSAI Small Team recently completed its proposed responses<https://gnso.icann.org/sites/default/files/policy/2025/draft/ppsai-small-te…> to the IRT’s requested guidance<https://gnso.icann.org/sites/default/files/policy/2025/draft/ppsai-irt-tq-r…>. The proposed responses were distributed to the GNSO Council via its mailing list on 29 September. The GNSO Council will discuss the small team’s proposed responses at ICANN84 on Wednesday, 29 October from 13:15 to 15:15 Dublin local time. We will follow-up with the IRT to outline next steps following the Council’s discussion. Safe travels to all those attending ICANN84! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Update: PPSAI Presentation to Council
by Jason Kean Aug. 18, 2025

Aug. 18, 2025

Hello IRT, Paul McGrady presented the PPSAI IRT Threshold Question Responses to the GNSO Council during its 14 August meeting<https://icann.zoom.us/rec/play/K75lmByKDxu_8YGJcF3pzOauMMj_y392Mt_fU0blGn5U…>. The Council agreed that a small team, under Paul’s leadership, would be the best mechanism to respond to the IRT’s requests for additional guidance. The PPSAI Small Team<https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages…> will meet weekly and aim to socialize its work in September. We will keep the IRT updated as the small team’s work progresses. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Solution for privacy and proxy registrations
by Steve Crocker Aug. 5, 2025

Aug. 5, 2025

PPSAI folks, I've given some thought to Privacy and Proxy Providers. 1. Privacy and Proxy providers are qualitatively different. Privacy providers provide alternative contact details -- email, phone, physical address -- but do not obscure the registrant's identity. The purpose is to route correspondence to people who are designated to accept and act on the registrant's behalf, and to avoid disclosing the registrant's direct contact details. In the normal physical world, this is accomplished by explicitly designating a correspondence address. In the current implementations of registration data, inserting the correspondence address into the data elements allocated to the registrant's contact is mistake that has two consequences. - It obscures the fact that the contact data is not related to the registrant but is, instead, contact data for a different role. - It makes it impossible to include registrant contact information in the database that may -- or should -- be available to authorized requestors. - The correct path forward is to define a new role, Correspondent. This role is optional. If it is included, it indicates where correspondence should be directed. This data should usually be public. In contrast, the registrant's address, etc. can be private and not disclosed in response to normal requests. 2. Proxy providers fall into two categories, known and unknown. Unknown proxy providers should be treated as ordinary registrants. That is, they should be presumed to be the actual registrant, with all of the rights, privileges, responsibilities and obligations as any other registrant. Known proxy providers should be identified as such. One possible way to do so is to extend the distinction between Natural and Legal Persons to include a third category, Known Proxy Provider. They are the legal registrants, with the full set of rights, privileges, responsiblities and obligations as other registrants, but it will be important to many requestors to know that the registrant is actually a proxy provider. The concept of Known Proxy Provider is not the same as an accredited proxy provider. Accreditation presumably implies an agreement with the proxy provider to adhere with some rules regarding disclosure to appropriate requestors. The concept of a Known Proxy Provider simply conveys to the requestor that the registration has been carried out by a proxy provider, but there is no implication as to what the proxy provider will do when asked to reveal the beneficial registrant. If it is desired to institute a process of accrediting Known Proxy Providers, we need a careful understanding of the intended purpose and a good argument as to why it will work. In the current environment, there are no rules barring someone from using a proxy provider and no rules requiring that proxy providers be identified. Registrars are likely to be able to identify well known proxy providers and add that detail to their registration data, but I do not see any reliable mechanism for identifying a proxy registration when the proxy provider does not want to be known as a proxy provider. 3. Proxy providers pose a potential policy conflict Registrars have obligations to collect accurate registration data, and they have an obligation to protect that data from inapprpriate disclosure. Where does a proxy provider fit into this picture? What service does it provide that is not in conflict with the registrar's role? Thanks, Steve -- Sent by a Verified sender

3 5

FW: [council] PPSAI IRT Threshold Question Responses for the Attention of the GNSO Council
by Caitlin Tubergen Aug. 1, 2025

Aug. 1, 2025

Dear IRT members, Below, please find the message sent to the GNSO Council today. Best regards, Caitlin -- Caitlin Tubergen Director, Policy Development Support (GNSO) From: Caitlin Tubergen via council <council(a)icann.org> Reply-To: Caitlin Tubergen <caitlin.tubergen(a)icann.org> Date: Friday, August 1, 2025 at 12:13 PM To: "council(a)icann.org" <council(a)icann.org> Subject: [council] PPSAI IRT Threshold Question Responses for the Attention of the GNSO Council SENT ON BEHALF OF JASON KEAN, PPSAI Project Owner Dear Councilors, ICANN org is pleased to share the Privacy and Proxy Services Accreditation Issues (PPSAI) Threshold Question Responses paper (attached) with the Council on behalf of the PPSAI Implementation Review Team (IRT). Paul McGrady, in his role as GNSO liaison to the PPSAI IRT, is scheduled to present the IRT’s work at the Council’s upcoming 14 August meeting. The PPSAI IRT has worked over the past 13 months in sessions, on-list, and within documents to develop responses to the following threshold questions: * Policy: Are there any policy questions or items the IRT already wants to bring to Council for guidance? (Threshold Question A) * Accreditation Model (Accreditation Program or Alternative Implementation): Can an implementation model without a new standalone accreditation program remain consistent with the policy recommendations? (Threshold Question B) * Disclosure Frameworks (Intellectual Property and Law Enforcement): Are there specific areas to revisit under new law/policy (ICANN org to share assessment for IRT review)? (Threshold Question C) * Alignment of Privacy/Proxy Policy with Related Work: Can these frameworks be aligned with existing work on the Registration Data Request Service (RDRS), Registration Data Policy, and other existing procedures and remain consistent with the policy recommendations? (Threshold Question K) The PPSAI IRT and ICANN org look forward to the Council’s decision on next steps for this work and are standing by to provide additional support as needed. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Final PPSAI IRT Threshold Question Responses for the Attention of the GNSO Council document
by Jason Kean July 30, 2025

July 30, 2025

Hello IRT, Thank you to all IRT members who contributed to the drafting of PPSAI Threshold Question responses in meetings, on-list, and within the documents over the past 13 months! ICANN org is happy to share the final clean version of the PPSAI IRT Threshold Question Responses for the Attention of the GNSO Council document (attached). IRT members can reference the highlighted text in the draft document<https://docs.google.com/document/d/1tyU2iLxwvvVJBTybUulXFnFCN600nMEu/edit> for updates made in response to recent IRT discussions on-list and during the 24 July session. Congratulations to the IRT on reaching this significant milestone! PPSAI IRT Threshold Question Responses will be presented to the GNSO Council during its 14 August meeting. ICANN org will update the IRT on-list regarding next steps following the Council’s discussion. Thank you again to the entire IRT for devoting your time and energy to this important work. Looking forward to next steps! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

24 July IRT Session Follow-up
by Jason Kean July 25, 2025

July 25, 2025

Hello IRT, Thank you to all those who attended and contributed to yesterday’s productive IRT discussion. To reflect the discussion on Volker’s proposal, ICANN org has included text (highlighted) in the draft PPSAI IRT Threshold Question document<https://docs.google.com/document/d/1tyU2iLxwvvVJBTybUulXFnFCN600nMEu/edit> under Note on Broader IRT PPSAI Discussion on top of page 6 and under TQ.B Initial Draft Language on page 11. Please provide any additional input by the end of the day today (Friday, 25 July). Thank you! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Request for clarification on proposal | 24 July IRT Meeting Reminder
by Jason Kean July 24, 2025

July 24, 2025

Hello IRT, Thank you to Volker for his proposed alternative implementation model (proposal in email below) and to all other IRT members who have contributed to this on-list discussion. Regarding this proposal, the ICANN org team wanted to clarify whether the proposed text is referring to proxy service providers rather than privacy service providers or both. Once this is clarified, subject to the group’s agreement, we suggest including this point as an alternative model for implementation under TQ.B. Reminder: In preparation for the IRT session on Thursday, 24 July at 15:30 UTC, please make comments within the draft PPSAI IRT Threshold Question document<https://docs.google.com/document/d/1tyU2iLxwvvVJBTybUulXFnFCN600nMEu/edit> on any aspect of the document that you cannot live with and provide text that you could support in your comment(s). Your comments will be used to guide the session’s discussion as we work to finalize the Threshold Question document for the GNSO Council. IRT input is needed by the end of the day Friday, 25 July. We look forward to seeing everyone on Thursday! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> From: Volker Greimann <volker.greimann(a)centralnic.com> Date: Thursday, July 17, 2025 at 7:41 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Cc: Jason Kean <jason.kean(a)icann.org> Subject: [Ext] Re: Meeting follow-up | Scheduling of 24 July Meeting Hi all, one thought: Would we not be able to circumvent all the issues with whether or not (and if so how) to accredit pp providers with one simple hack? The goal ultimately is to hold privacy providers accountable and ensure they fall (essentially) under the same rules for data disclosure as registrars do already, e.g ensuring that registrants are bound by terms that we understand pp providers should follow. This would cleanly avoid all bureaucratic overhead, avoid having to differentiate between affiliated or non-affiliated providers, etc. This can be done by a simple policy requirement that would require registrars to pass along certain terms to all registrants through their agreements, gTAC, policies or otherwise. Essentially it boils down to the essence of the matter that privacy service providers are just another type of registrants. "Registrars must ensure that registrants using their services who register domain names for the sole use of, on behalf of or for the benefit of third parties agree to... ." should do nicely as a starting point as there is already precedent for such requirements in other policies. Maybe this could also be brought to the GNSO as an option when they address our concerns regarding the issues with the non-community developed accreditation models proposed by ICANN staff. Yes, this may require a rewrite of the existing policy recommendations, but the general principles stated above that were mostly agreed would form a basis that would allow quick progress. Sincerely, Volker Greimann General Counsel & Head of Policy and Compliance - Online Division volker.greimann(a)centralnic.com Office: +49-172-6367025 Web: www.teaminternet.com Team Internet Group PLC (AIM:TIG). Registered Office: 4th Floor, Saddlers House, 44 Gutter Lane, London, United Kingdom, EC2V 6BR. Team Internet is a company registered in England and Wales with the company number 8576358. ________________________________ From: Jason Kean via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Sent: 17 July 2025 11:28 PM To: gdd-gnso-ppsai-impl(a)icann.org <gdd-gnso-ppsai-impl(a)icann.org> Cc: Jason Kean <jason.kean(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] Meeting follow-up | Scheduling of 24 July Meeting Hello IRT, Thank you all for the productive session earlier today on the draft PPSAI IRT Threshold Question document [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1tyU2iLxwvvVJ…>. As promised, we are sending out invitations for a meeting next Thursday, 24 July at 15:30 UTC to continue the discussion. Reminder: IRT input is needed by the end of the day Friday, 25 July. To help prepare for this meeting, we ask that you make comments on any aspect of the document that you cannot live with and provide text that you could support in your comment(s). We will use your comments to guide the discussion. We look forward to seeing everyone next Thursday! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

4 4

Meeting follow-up | Scheduling of 24 July Meeting
by Jason Kean July 18, 2025

July 18, 2025

Hello IRT, Thank you all for the productive session earlier today on the draft PPSAI IRT Threshold Question document<https://docs.google.com/document/d/1tyU2iLxwvvVJBTybUulXFnFCN600nMEu/edit>. As promised, we are sending out invitations for a meeting next Thursday, 24 July at 15:30 UTC to continue the discussion. Reminder: IRT input is needed by the end of the day Friday, 25 July. To help prepare for this meeting, we ask that you make comments on any aspect of the document that you cannot live with and provide text that you could support in your comment(s). We will use your comments to guide the discussion. We look forward to seeing everyone next Thursday! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

5 5

PPSAI IRT Task and Prep for 17 July 2025 @ 15:30 UTC Session
by Jason Kean July 14, 2025

July 14, 2025

Hello IRT, Please find the draft PPSAI IRT Threshold Question Answers document for the GNSO Council here<https://docs.google.com/document/d/1tyU2iLxwvvVJBTybUulXFnFCN600nMEu/edit> for your review. This document provides a brief background on the inception of the Privacy and Proxy Service Accreditation Issues recommendations, IRT work to date, and presents the current version of all IRT Threshold Question answers and requests for additional guidance. Note: Threshold Question answers have been updated since the last IRT discussion and are ready for IRT review. We will walk through this document during the upcoming IRT session on Thursday, 17 July at 15:30 UTC. IRT input on this document is due by the end of day Friday, 25 July. We look forward to seeing everyone on Thursday! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

PPSAI IRT Session Follow-Up
by Jason Kean June 26, 2025

June 26, 2025

Hello IRT, Thank you to those who participated in today’s recorded session<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/edit-v2/2263286…> on the draft language for Threshold Question B<https://docs.google.com/document/d/1pm5WCZK7RULtsflJROc-LUZvRwMSfFShTyHPxDI…>. As promised, please find a PDF version attached for further distribution. Final input is requested by the end of the day Friday, 4 July. Next IRT Session Calendar invitations have been sent for the next session on Thursday, 17 July at 15:30 UTC. Regards, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

REMINDER: PPSAI IRT Prep for 26 June Session
by Jason Kean June 24, 2025

June 24, 2025

Hello IRT, We look forward to the upcoming session this Thursday, 26 June at 15:30 UTC. Reminder: This session will focus on reviewing draft language for Threshold Question B<https://docs.google.com/document/d/1pm5WCZK7RULtsflJROc-LUZvRwMSfFShTyHPxDI…>. Final input on this language is requested by the end of the day Friday, 4 July. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

PPSAI IRT: ICANN83 Follow-up and TQ.B Task Assignment
by Jason Kean June 19, 2025

June 19, 2025

Hello IRT, Thanks to all who participated in the ICANN83 IRT session (#22) - the recordings are available here<https://icann83.sched.com/event/246XK/gds-ppsai-irt-working-session>. I hope all those that attended in-person had an uneventful trip home. Please find the new IRT task assignment and the next IRT session details below. IRT Task Assignment (#20250616) Please review the proposed draft language for Threshold Question B (TQ.B) here<https://docs.google.com/document/d/1pm5WCZK7RULtsflJROc-LUZvRwMSfFShTyHPxDI…> by the end of day Friday, 4 July. Please comment only on any aspect of the TQ that you cannot live with. Please select/highlight only the portion of text your comment directly relates to, in order to avoid overlapping and confusing comment tags, and please provide text that you could support in your comment(s). Next IRT Session The IRT’s next session will be held on Thursday, 26 June 15:30 UTC. This session will focus on reviewing the draft language for TQ.B<https://docs.google.com/document/d/1pm5WCZK7RULtsflJROc-LUZvRwMSfFShTyHPxDI…>. We will also review the timeline for the IRT’s final review of all TQ materials. We look forward to seeing everyone on the 26th! Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Re: PPSAI IRT: Accreditation Model Comments - Replies Posted & Document Revisions
by Jessica Puccio June 6, 2025

June 6, 2025

all – my apologies for any inconvenience; my earlier email was only half of the message we intended to share. please see the amended communication below. Hello IRT, Please find some updates below, including comment responses as well as a session reminder for ICANN83 in Prague. Responses Posted Thank you for submitting your comments to the Accreditation Models Paper [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/14FEv67ER-Qnz…> as requested. We are pleased to note that we have now posted responses to the comments that were submitted up to and including Friday, 30 May. In reviewing your comments, we identified some areas in the document where language could be updated for clarity and precision. These updates have been highlighted in yellow for the IRT’s awareness. Please do take the time to review our revisions as well as our responses to your comments in advance of next Wednesday’s IRT session, where the comment responses will be discussed. ICANN83 Session The IRT’s next session will be held on Wednesday, 11 June 07:00 UTC (09:00 CEST) at ICANN83<https://icann83.sched.com/event/246XK/gds-ppsai-irt-working-session>. This session will focus on the input received on the accreditation models and next steps for the IRT’s work. Please let us know if you have not received invitations for the June session. We look forward to connecting in Prague. Best, Jason Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>)

1 0

PPSAI IRT: Accreditation Model Comments - Replies Posted & Document Revisions
by Jessica Puccio June 6, 2025

June 6, 2025

Hello IRT, Please find some updates below, including comment responses as well as a session reminder for ICANN83 in Prague. Responses Posted Thank you for submitting your comments to the Accreditation Models Paper<https://docs.google.com/document/d/14FEv67ER-Qnz2iKiYCCGY8bK4Gky9Thi/edit#h…> as requested. We are pleased to note that we have now posted responses to the comments that were submitted up to and including Friday, 30 May. Kind Regards -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>)

1 0

PPSAI IRT: Accreditation Model Comments Due Friday 30 May
by Jessica Puccio June 6, 2025

June 6, 2025

Hello IRT, Please find a few reminders related to the current IRT task and next IRT session below. Current IRT Task Please provide your input on the accreditation models document<https://docs.google.com/document/d/14FEv67ER-Qnz2iKiYCCGY8bK4Gky9Thi/edit#h…> by Friday, 30 May. Thanks to all who have contributed already. You can find responses to the comments received thus far in the IRT comment tracker<https://docs.google.com/spreadsheets/d/1fMhQNnxEM9l4RsFc3cmw62RwhADHSICFId4…>. In reviewing your comments, we identified areas where language should be updated for consistency. These updates have been highlighted in yellow for the IRT’s reference. Next IRT Session The IRT’s next session will be held on Wednesday, 11 June 07:00 UTC at ICANN83<https://icann83.sched.com/event/246XK/gds-ppsai-irt-working-session>. This session will focus on the input received on the accreditation models and next steps for the IRT’s work. Please let us know if you have not received invitations for the June session. We look forward to connecting in Prague. Best, Jason Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>)

6 6

PPSAI IRT Session #20: Thursday 15 May 2025 Followup
by Dana Kuebler May 20, 2025

May 20, 2025

Hello IRT, Thanks to all who participated in last Thursday’s IRT session (#20). The recordings and transcripts are available here<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/200572987/15+Ma…>. Reminders: * Current task: IRT input on the accreditation models paper is due by Friday, 30 May. * Next IRT session: The next IRT session will be held on Wednesday, 11 June at ICANN83. The 29 May IRT session (#21) is cancelled to give members more time to work on the models paper. Please find more information on the IRT’s current task and project schedule below. Best, Jason IRT Task: Task# Description Due Date 20250512 Review and comment on Ext: IRT Doc - Accreditation Models (12MAY2025)<https://docs.google.com/document/d/14FEv67ER-Qnz2iKiYCCGY8bK4Gky9Thi/edit#h…> 30 May 2025 IRT input is needed on the models to identify whether any of these options cannot be implemented in accordance with the policy recommendations and why, and where further GNSO guidance is needed. To support your comments, please cite: · the PPSAI Final Report, · discussions in the original PDP Working Group, and/or · discussions in the former IRT where appropriate Avoid IRT comments that: · Identify a personal accreditation model preference, or one based on SO/AC/group affiliation, rather than making an assessment based on the scope given to us by the Final Report. · Identify known implementation challenges which have already been noted and listed for further implementation planning discussions. Reminder: only highlight the specific area of related text when making comments. Schedule: * ICANN83 Prep Week Tuesday & Wednesday 27 - 28 May (Schedule<https://icann83.sched.com/>) * ICANN83 PPSAI IRT Session #22 Wednesday 11 June - 07:00 UTC (Session Link<https://icann83.sched.com/event/246XK/gds-ppsai-irt-working-session>) * Target Milestone - 26 June 2025, finalize IRT input on threshold Question B<https://docs.google.com/spreadsheets/d/1rqfRaG1yL8HU48u0_3rIHkREoWN0Psr0rT_…>

1 0

IRT Session Thur 15 May @15:30UTC **Please attend for Introduction of Accreditation Models and IRT Task Review**
by Jason Kean May 13, 2025

May 13, 2025

Dear IRT, The next IRT meeting is scheduled for Thursday 15 May @15:30 UTC. During this session, we will introduce three accreditation models ICANN org believes align with the PPSAI Final Report policy recommendations’ intent and review the IRT’s task (below) in greater detail. Please make every effort to attend this important session. The IRT’s input will inform Threshold Question B<https://docs.google.com/spreadsheets/d/1rqfRaG1yL8HU48u0_3rIHkREoWN0Psr0rT_…>: Can an accreditation model without a formal Accreditation Program remain consistent with the policy recommendations? This is based on the IRT comment asking if the community had ever concluded that a formal Accreditation Program was needed/wanted, having found no evidence in previous discussions. IRT Task: Review and comment on accreditation models<https://docs.google.com/document/d/14FEv67ER-Qnz2iKiYCCGY8bK4Gky9Thi/edit?u…>. Due Friday, 30 May 2025 IRT input is needed on the models to identify whether any of these options cannot be implemented in accordance with the policy recommendations and why, and where further GNSO guidance is needed. To support your comments, please cite: * the PPSAI Final Report, * discussions in the original PDP Working Group, and/or * discussions in the former IRT where appropriate Avoid IRT comments that: * Identify a personal accreditation model preference, or one based on SO/AC/group affiliation, rather than making an assessment based on the scope given to us by the Final Report. * Identify known implementation challenges which have already been noted and listed for further implementation planning discussions. Reminder: only highlight the specific area of related text when making comments. We look forward to seeing you this Thursday. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> Upcoming Schedule: * 15 May @15:30 UTC: IRT meeting introducing the accreditations models and detailing IRT task instructions. * 27-28 May: ICANN 83 Prep Week. The Prep Week schedule<https://icann83.sched.com/> will be published on 5 May 2025 * 30 May: Deadline for IRT to submit its comments on the accreditation models. * 11 June: ICANN83 session in Prague from 9:00am - 10:15am local time. The IRT will discuss the input provided on the accreditations models. * To register for ICANN83, visit: https://events.icann.org/icann83/registration

3 3

Re: [Ext] Re: IRT Session Thur 15 May @15:30UTC **Please attend for Introduction of Accreditation Models and IRT Task Review**
by Jason Kean May 13, 2025

May 13, 2025

Hello Volker, Thank you for your response. We look forward to discussion on your points within the Accreditation Models document and during the upcoming IRT session. Regarding your questions as to whether this exercise is premature, whether the current policy is fit for purpose, and whether changes are necessary, these are the very questions we will be posing to the GNSO Council via the Threshold Questions as part of this initial phase of implementation planning. The GNSO Council will then provide guidance as appropriate based on its discussion on the Threshold Questions posed and the information provided. We hope to see you at this Thursday’s meeting. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> From: Volker Greimann <volker.greimann(a)centralnic.com> Date: Monday, May 12, 2025 at 4:51 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Cc: Karen Lentz <karen.lentz(a)icann.org>, Leon Grundmann <leon.grundmann(a)icann.org>, Jessica Puccio <jessica.puccio(a)icann.org>, Jason Kean <jason.kean(a)icann.org> Subject: [Ext] Re: [Gdd-gnso-ppsai-impl] IRT Session Thur 15 May @15:30UTC **Please attend for Introduction of Accreditation Models and IRT Task Review** Hi, are we not putting the cart before the horse with this? Should we not first determine whether the current policy is ft for purpose and whether changes are necessary, and if so, which ones? The last time we danced this dance with ICANN (back in the Cyrus days) ICANN came up with a model similar to Model 1 and then opined that the fees it would need to charge would be ridiculously high to an extent that it would disincentivise any potential accreditee from seeking that accreditation, essentially solving the whois privacy "issue" by ensuring there were no more privacy services. Secondly, there is not a single reason why registrars that offer these services would or should be forced to sign another agreement as the RAA is already sufficient in regulating the issues of affiliated providers. This would just add additional costs with negligible benefits and therefore any such model should be rejected. Model 2: I do not understand Model 2 as presented: No new accreditation agreement, but we must obtain an accreditation anyway? In general the basic principle of a light-weight, self-policing model that relies on consensus policy and the RAA is to be supported however. Less is more. Sincerely, Volker Greimann General Counsel & Head of Policy and Compliance - Online Division volker.greimann(a)centralnic.com Office: +49-172-6367025 Web: www.teaminternet.com Team Internet Group PLC (AIM:TIG). Registered Office: 4th Floor, Saddlers House, 44 Gutter Lane, London, United Kingdom, EC2V 6BR. Team Internet is a company registered in England and Wales with the company number 8576358. ________________________________ From: Jason Kean via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Sent: 12 May 2025 7:28 PM To: gdd-gnso-ppsai-impl(a)icann.org <gdd-gnso-ppsai-impl(a)icann.org> Cc: Karen Lentz <karen.lentz(a)icann.org>; Leon Grundmann <leon.grundmann(a)icann.org>; Jessica Puccio <jessica.puccio(a)icann.org>; Jason Kean <jason.kean(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] IRT Session Thur 15 May @15:30UTC **Please attend for Introduction of Accreditation Models and IRT Task Review** Dear IRT, The next IRT meeting is scheduled for Thursday 15 May @15:30 UTC. During this session, we will introduce three accreditation models ICANN org believes align with the PPSAI Final Report policy recommendations’ intent and review the IRT’s task (below) in greater detail. Please make every effort to attend this important session. The IRT’s input will inform Threshold Question B [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1rqfRaG1y…>: Can an accreditation model without a formal Accreditation Program remain consistent with the policy recommendations? This is based on the IRT comment asking if the community had ever concluded that a formal Accreditation Program was needed/wanted, having found no evidence in previous discussions. IRT Task: Review and comment on accreditation models [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/14FEv67ER-Qnz…>. Due Friday, 30 May 2025 IRT input is needed on the models to identify whether any of these options cannot be implemented in accordance with the policy recommendations and why, and where further GNSO guidance is needed. To support your comments, please cite: * the PPSAI Final Report, * discussions in the original PDP Working Group, and/or * discussions in the former IRT where appropriate Avoid IRT comments that: * Identify a personal accreditation model preference, or one based on SO/AC/group affiliation, rather than making an assessment based on the scope given to us by the Final Report. * Identify known implementation challenges which have already been noted and listed for further implementation planning discussions. Reminder: only highlight the specific area of related text when making comments. We look forward to seeing you this Thursday. Best, Jason Jason Kean Sr. Manager, Reviews and Stakeholder Support Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org> Upcoming Schedule: * 15 May @15:30 UTC: IRT meeting introducing the accreditations models and detailing IRT task instructions. * 27-28 May: ICANN 83 Prep Week. The Prep Week schedule [icann83.sched.com]<https://urldefense.com/v3/__https:/icann83.sched.com/__;!!PtGJab4!4Q00G60AD…> will be published on 5 May 2025 * 30 May: Deadline for IRT to submit its comments on the accreditation models. * 11 June: ICANN83 session in Prague from 9:00am - 10:15am local time. The IRT will discuss the input provided on the accreditations models. * To register for ICANN83, visit: https://events.icann.org/icann83/registration [events.icann.org]<https://urldefense.com/v3/__https:/events.icann.org/icann83/registration__;…>

1 0

PPSAI IRT Task: 20250424 Review Revised Language for Threshold Questions: A, C, K Due Monday 05 May 2025
by Dana Kuebler April 24, 2025

April 24, 2025

Hello IRT, We hope this finds you well. As a reminder that our Thursday 24 April IRT session has been cancelled. Invitations have been sent for our next IRT session on Thursday 15 May 2024 15:30 UTC. To continue our productive collaboration on list the next IRT task is here. 20250423 Review and Provide Feedback on Revised Language for Threshold Questions: A, C, K 05Dec2024 - EXT IRT Draft Proposed Candidate Questions for GNSO Council v1<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…> 05 May 2025 Please follow requested feedback guidance found within the document tab: Section 2. IRT Review Instructions<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…>, and identify any text that you CANNOT LIVE WITH (provide text that you could support in your comment; and please select only the specific part of text that you cannot live with); · Please hold back on comments on smaller issues - we are looking for any changes in direction for these TQs to prepare them for submission to the GNSO Council. To reduce confusion, tabs with “Archive” and in red text can be ignored. Quick Links to revised language: * TQ A: Definitions<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…> * TQ C: Illustrative Disclosure Framework - policy or example<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…> * TQ.K: Similarities between "High Priority" (PPSAI Disclosure Framework) and "Urgent" (Registration Data Policy issue) requests<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…> We invite further task related discussion & collaboration on the listserv until we meet again Thursday 15 May 2025. Thanks again for all you do to help our PPSAI efforts.

2 1

Schedule Update: Next IRT Session Changed to 15 May 2025
by Dana Kuebler April 17, 2025

April 17, 2025

Hello again Owen and IRT! Thanks again for flagging the schedule conflict with both the Contracted Parties Summit on May 6 and 7 in Hanoi and the APAC DNS Forum on May 8 and 9. We took another look and agree we should shift the timing of our Thursday 08 May IRT session. We will be sending out invitation updates for Thursday 15 May 15:30 UTC and will keep the next scheduled session for Thursday 22nd May. Safe travels and we look forward to reconnecting in May From: Dana Kuebler Date: Tuesday, April 15, 2025 at 5:47 PM To: Owen Smigelski Cc: Dana Kuebler <dana.kuebler(a)icann.org> Subject: Re: Meeting: PPSAI IRT | Thursday, 8 May 2025 | 1530 UTC | 90 minutes | Hi Owen, Thanks for the heads up on the schedule conflicts. Wishing safe travels for all to attending the CPS and APAC DNS Forum. Currently, the intention is to hold our scheduled session for 08 May and plan a quick meeting to introduce Implementation Models and assign the IRT a task to review. We anticipate a short/manageable session recording for those who are not able to attend and will keep our efforts moving things forward. We will continue to evaluate IRT scheduling conflicts as they arise and accommodate when feasible. Dana From: Owen Smigelski Date: Monday, April 14, 2025 at 3:31 PM To: GDS Shared Services Cc: GDS Shared Services <gds-shared-services(a)icann.org>, Owen Smigelski <owen.smigelski(a)namecheap.com> Subject: Re: Meeting: PPSAI IRT | Thursday, 8 May 2025 | 1530 UTC | 90 minutes | Hi ICANN, Due to the Contracted Parties Summit on May 6 and 7 in Hanoi (and the APAC DNS Forum on May 8 and 9), most contracted party participants will be unable to attend. Can we please reschedule this meeting? Thanks! Regards, Owen

1 0

PPSAI IRT Session #18: Thursday 10 April 2025 Follow up
by Dana Kuebler April 11, 2025

April 11, 2025

Hello IRT, Happy Friday! The session #18 recordings are available here,<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/106367969/10+Ap…> transcripts will be posted shortly. Schedule: * We have Cancelled IRT Session#19: Thursday, 24 April 2025 @15:30 UTC * Invitations for May IRT Sessions #20 & #21: Thursday 08th and 22nd May 2025 @15:30 UTC & will be sent next week. Tasks: * IRT can anticipate a request on-list to review revised language for Candidate Threshold Questions for GNSO Guidance. Have a great weekend.

1 0

PPSAI IRT Upcoming Session #18: Thursday 10 April 1530 UTC
by Dana Kuebler April 7, 2025

April 7, 2025

Dear IRT, Thank you for comments on the Ext: IRT Doc - Alignment of Disclosure Frameworks to Existing Work/Procedures (07Mar25)<https://docs.google.com/document/d/1Gx_OsTUYmF3bab1j__is2S4edYZ3r5DtEHpsTMc…>. IPT has responded to comments and looks forward to continued discussion on Disclosure Framework Threshold Category 3, Part B. Can these frameworks be aligned with existing work on RDRS, Registration Data Policy, and other existing procedures and remain consistent with the policy recommendations? Please review the recent ICANN82 session<https://icann82.sched.com/event/1vpbs/gds-ppsai-irt-working-session> if you were unable to attend. Reach out to us if you have not received an invitation for the upcoming session #18 Thursday, 10 April at 15:30 UTC. The agenda can be found here<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/106367969/10+Ap…>.

1 0

PPSAI IRT Upcoming Session #18: Thursday 10 April 1530 UTC
by Dana Kuebler April 1, 2025

April 1, 2025

Hello IRT, Thank you again for your engagement during the ICANN82 IRT Session<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/106366110/12+Ma…>. We appreciate your input on the workplan, timeline, and Disclosure Framework comments. In response to requests for more time, we extended the IRT comment deadlines on the Alignment of Disclosure Frameworks to Existing Work/Procedures<https://docs.google.com/document/d/1Gx_OsTUYmF3bab1j__is2S4edYZ3r5DtEHpsTMc…> and the Draft Disclosure Framework Assessment<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…> to Thursday, 27 March 2025. IPT responses to comments will be posted ahead of our next session on Thursday, 10 April at 15:30 UTC. Please let us know if you have any questions or need the upcoming meeting invite resent. Best regards

1 0

IRT Session #17: Meeting Cancellation for Thursday 27 March 2025
by Dana Kuebler March 24, 2025

March 24, 2025

Hello IRT, Hoping all found their way home safely from ICANN82 and have fully recovered from all the traveling. We are cancelling IRT Session #17, this Thursday 27 March 2025 to allow IRT members to utilize session time to complete assigned tasks. Reminder: Tasks are due Thursday 27 March, EOD Task # IRT Task (homework) Due Date 20250307a Review Alignment of Disclosure Frameworks to Existing Work/Procedures<https://docs.google.com/document/d/1Gx_OsTUYmF3bab1j__is2S4edYZ3r5DtEHpsTMc…> and comment on questions and assumptions 19 March 2025 27 March 2025 20250307b Provide priority comments for Threshold Question 3: Part B, within the Draft Disclosure Framework Assessment<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…> document 19 March 2025 27 March 2025 Please review the IRT Comment Guidelines section<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…> of the assessment for guidance & examples on how to best make comments. For the Alignment Document, please review the instructions in that document<https://docs.google.com/document/d/1Gx_OsTUYmF3bab1j__is2S4edYZ3r5DtEHpsTMc…> for how to best give your input. REMINDER: please select a small, specific portion of text when making comments on either document. We look forward to further discussion Session #18, Thursday 10 April 2025 @15:30 UTC. Invites will be sent out this week. Please reach out to us if you do not receive an invite.

1 0

Recordings for IRT Meeting #16 - 12 March 2025
by Dana Kuebler March 13, 2025

March 13, 2025

Hello IRT, Thank you for your thoughtful comments and informative discussions during our ICANN82 session. The session #16 recordings are available here,<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/106366110/12+Ma…> transcripts will be posted shortly. We look forward to further discussion Thursday, 27 March 2025 @15:30 UTC. Invitations for this session have been sent. Please reach out to us if you did not get an invite. Based on requests from IRT members, we are adjusting the due dates from 19 March to 27th of March for the following tasks. Please reply on-list if you have any concerns with the proposed adjusted due date. Task # IRT Task (homework) Due Date 20250307a Review Alignment of Disclosure Frameworks to Existing Work/Procedures<https://docs.google.com/document/d/1Gx_OsTUYmF3bab1j__is2S4edYZ3r5DtEHpsTMc…> and comment on questions and assumptions 19 March 2025 27 March 2025 20250307b Provide priority comments for Threshold Question 3: Part B, within the Draft Disclosure Framework Assessment<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…> document 19 March 2025 27 March 2025 Please review the IRT Comment Guidelines section<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…> of the assessment for guidance & examples on how to best make comments. For the Alignment Document, please review the instructions in that document<https://docs.google.com/document/d/1Gx_OsTUYmF3bab1j__is2S4edYZ3r5DtEHpsTMc…> for how to best give your input. REMINDER: please select a small, specific portion of text when making comments on either document. Safe travel to all those heading home from ICANN82

1 0

Reminder: IRT Preparation for ICANN82 Discussion
by Dana Kuebler March 11, 2025

March 11, 2025

Hello IRT, We look forward to connecting Wednesday, 12 March 2025 16:00 UTC for our scheduled<https://urldefense.com/v3/__https:/icann82.sched.com/event/1vpbs/gds-ppsai-…> ICANN82 IRT Session. Please add priority comments or feedback to existing responses directly within the Draft Disclosure Frameworks Assessment<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…>, in preparation for further discussion. Reminder, please select a small, specific portion of text when making comments. If you missed the last session, here is the link<https://icann-community.atlassian.net/wiki/spaces/IRT/pages/106366007/27+Fe…> to catch up.

2 2

IRT Tasks: Review and Provide Comments - Alignment of Disclosure Frameworks to Existing Work/Procedures document. Due Wednesday 19 March 2025
by Leon Grundmann March 7, 2025

March 7, 2025

Dear IRT, Thank you for your thoughtful comments and informative discussions last week. We ask you to continue your focused review and addition of priority comments on Threshold Category 3: Disclosure Framework Assessment<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…> with a focus on Part B: Can these frameworks be aligned with existing work on RDRS, Registration Data Policy, and other existing procedures and remain consistent with the policy recommendations? To support this effort we have prepared an Alignment Document<https://docs.google.com/document/d/1Gx_OsTUYmF3bab1j__is2S4edYZ3r5DtEHpsTMc…> based on the previously published Wave.1.5 report<https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-phas…>. Task # IRT Task (homework) Due Date 20250304 Review Progress of Candidate Threshold Questions discussed during IRT Session 27 Feb 2025 (See IRT email<https://lists.icann.org/hyperkitty/list/gdd-gnso-ppsai-impl@icann.org/threa…> on 04 Mar 2025 for TQs: H, L, O, M, N) 10 Mar 2025 20250307a Review Alignment of Disclosure Frameworks to Existing Work/Procedures<https://docs.google.com/document/d/1Gx_OsTUYmF3bab1j__is2S4edYZ3r5DtEHpsTMc…> and comment on questions and assumptions 19 March 2025 20250307b Provide priority comments for Threshold Question 3: Part B, within the Draft Disclosure Framework Assessment<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…> document 19 March 2025 Please review the IRT Comment Guidelines section<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…> of the assessment for guidance & examples on how to best make comments. For the Alignment Document, please review the instructions in that document<https://docs.google.com/document/d/1Gx_OsTUYmF3bab1j__is2S4edYZ3r5DtEHpsTMc…> for how to best give your input. REMINDER: please select a small, specific portion of text when making comments on either document. We kindly request your review and feedback to the Draft Disclosure Frameworks Assessment<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…> comments in preparation for further discussion in our next IRT meeting Session #16 at ICANN82, on Wednesday 12 March 2025. Best regards, The IPT

1 0

IRT Task #20250305: Review Progress of Candidate Threshold Questions. Due: Monday 10 March 2025
by Dana Kuebler March 5, 2025

March 5, 2025

Dear IRT, Thank you all for your time and feedback on draft responses to threshold questions. We would like to address several candidate threshold questions that are shown in the IRT Threshold Question tracker<https://docs.google.com/spreadsheets/d/1rqfRaG1yL8HU48u0_3rIHkREoWN0Psr0rT_…>. During the recent IRT sessions on 13 and 27 February 2025, each of the below questions were discussed and an approach was proposed to address each of them as part of existing threshold questions. Please see below the assessment and handling discussed for the relevant candidate threshold questions. For any IRT members who were not present at the last session, and who have any objections to the handling of these questions, please reply on-list by Monday, 10 March 2025. Consolidation of several of candidate threshold questions related to or with a dependency on TQ.B. Accreditation Program - was it ever officially requested?: * TQ.H: Contracted Party Addition(s): Questions related to possible GNSO structural changes including potential creation of a new contracted party, or even ICANN Bylaws amendments, are dependent on the implementation model selected and could be included as part of TQ.B. * TQ.L: Point of contact requirement for P/P providers, which requestors can contact - can be combined with TQ.B, as it relates to the implementation model which will be selected. * TQ.O: Customer surrendering domain name in lieu of disclosure - requirements for P/P provider - can be combined with TQ.B, as it also relates to the implementation model, as it is a question about how the P/P provider is covered in a case where provider is not also the registrar. Additionally, we propose including both TQs M and N to be addressed as part of TQ.C: Illustrative Disclosure Framework - policy or not?, given the dependency on Council's response to whether the illustrative disclosure framework must inform our policy, or if it the IPT and IRT have leeway in drafting such disclosure frameworks during implementation, or perhaps even to reject some or all of what is proposed in Annex B. * TQ.M: Providing evidence of wrongdoing (copyright infringement case) and * TQ.N: "General Policy Stated Herein" question The IPT is also currently working on several possible implementation models to present and discuss with the IRT, which we intend to share within the next several weeks, to support TQ.B. Accreditation Program - was it ever officially requested? Thank you again for your support and efforts, The IPT

1 0

IRT Task 20250304: Review Progress of Candidate Threshold Questions
by Leon Grundmann March 4, 2025

March 4, 2025

Dear IRT, Thank you all for your time and feedback on draft responses to threshold questions. We would like to address several candidate threshold questions that are shown in the IRT Threshold Question tracker<https://docs.google.com/spreadsheets/d/1rqfRaG1yL8HU48u0_3rIHkREoWN0Psr0rT_…>. During the recent IRT sessions on 13 and 27 February 2025, each of the below questions were discussed and an approach was proposed to address each of them as part of existing threshold questions. Please see below the assessment and handling discussed for the relevant candidate threshold questions. For any IRT members who were not present at the last session, and who have any objections to the handling of these questions, please reply on-list by Monday, 10 March 2025. Consolidation of several of candidate threshold questions related to or with a dependency on TQ.B. Accreditation Program - was it ever officially requested?: * TQ.H: Contracted Party Addition(s): Questions related to possible GNSO structural changes including potential creation of a new contracted party, or even ICANN Bylaws amendments, are dependent on the implementation model selected and could be included as part of TQ.B. * TQ.L: Point of contact requirement for P/P providers, which requestors can contact - can be combined with TQ.B, as it relates to the implementation model which will be selected. * TQ.O: Customer surrendering domain name in lieu of disclosure - requirements for P/P provider - can be combined with TQ.B, as it also relates to the implementation model, as it is a question about how the P/P provider is covered in a case where provider is not also the registrar. Additionally, we propose including both TQs M and N to be addressed as part of TQ.C: Illustrative Disclosure Framework - policy or not?, given the dependency on Council's response to whether the illustrative disclosure framework must inform our policy, or if it the IPT and IRT have leeway in drafting such disclosure frameworks during implementation, or perhaps even to reject some or all of what is proposed in Annex B. * TQ.M: Providing evidence of wrongdoing (copyright infringement case) and * TQ.N: "General Policy Stated Herein" question The IPT is also currently working on several possible implementation models to present and discuss with the IRT, which we intend to share within the next several weeks, to support TQ.B. Accreditation Program - was it ever officially requested? Thank you again for your support and efforts, The IPT

1 0

Recordings available for IRT Meeting #15 - 27 February 2025
by Dana Kuebler Feb. 28, 2025

Feb. 28, 2025

Hello IRT, Just a quick update that IRT session #15 recordings are available here,<https://community.icann.org/pages/viewpage.action?pageId=423165961> transcripts will be posted shortly. Reminder to complete your registration for ICANN82<https://meetings.icann.org/en/meetings/icann82/>. We look forward to further discussion at ICANN82 Session <https://icann82.sched.com/event/1vpbs/gds-ppsai-irt-working-session> Wednesday, 12 March 2025 @06:00 UTC. All the best, Dana

1 0

IRT Task 20250206b: Final review and comments on Draft Disclosure Frameworks Assessment - Due 20 Feb 2025
by Leon Grundmann Feb. 14, 2025

Feb. 14, 2025

Dear IRT, Thank you for the warm welcome to Jason Kean, who will be onboarding as the project lead for PPSAI and a big thank you to Dennis for all he has done to move the work forward and thank you for the continued support on the IPT. We ask that the IRT continue to review and finalize comments on the Ext: IRT Doc - Disclosure Frameworks Assessment (06Feb25)<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…>. Please review IPT Priority 1 (for immediate IRT consideration and potential GNSO Council escalation) and Priority 2 (flagged for IRT discussion in implementation) assessment comments and identify: 1. Impacts from new laws or policies: There are additional areas under new law or policy that have not been noted in the document, and which should also be revisited by the IRT. 2. Clarify additional inconsistencies: Identify any additional aspects of the frameworks that do not align (or could or should be better aligned) with existing work or procedures (e.g. on RDRS, RDP or other existing policies or procedures). 3. Provide further rationale: to support or object to an existing priority assessment comment. Please review the IRT Comment Guidelines section<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…> of the assessment for guidance & examples on how to best make comments. REMINDER: please select a small, specific portion of text when making comments. Task # IRT Task (homework) Due Date 20250206b Final review and comments Ext: IRT Doc - Draft Disclosure Frameworks Assessment (06Feb25) 20 Feb 2025 We kindly request your review and feedback to the assessment comments in preparation for further discussion in our next IRT meeting Session #15, Thursday 27 February 2025. Best regards, The IPT

1 0

Recordings available for IRT Meeting #14: 13 February 2025
by Dana Kuebler Feb. 13, 2025

Feb. 13, 2025

Hello IRT, Just a quick update that IRT session #14 recordings are available here,<https://community.icann.org/pages/viewpage.action?pageId=423165958> transcripts will be posted shortly. We look forward to further discussion next Thursday, 27 February 2025 @15:30 UTC. All the best, Dana

1 0

IRT Task 20250206: Review Ext: IRT Doc - Draft Disclosure Frameworks Assessment (06Feb25). Due: 13 Feb 2025
by Leon Grundmann Feb. 6, 2025

Feb. 6, 2025

Dear IRT, Thank you all for your input on threshold questions as we progress through our workplan. As promised, to further our discussion on recommendations that may be impacted by changes in law, inconsistencies, gaps in ICANN consensus policy in today's current environment, we are assigning the review of Ext: IRT Doc - Disclosure Frameworks Assessment (06Feb25)<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…>. Please note that this is an annotated excerpt of the Draft Privacy and Proxy Service Provider Accreditation Agreement (PPAA) from 13 Sept 2018, and intentionally omits portions of the full draft PPAA to simplify the IRT review process. Task # IRT Task (homework) Due Date 20250206a Initial review and comments Ext: IRT Doc - Draft Disclosure Frameworks Assessment (06Feb25) 13 Feb 2025 20250206b Final review and comments Ext: IRT Doc - Draft Disclosure Frameworks Assessment (06Feb25) 20 Feb 2025 Please see the IRT Comment Guidelines section<https://docs.google.com/document/d/1prbyViSAFL866FjYD9VSwSH4aGjkJZgNYn6m3NX…> of the assessment for guidance on making comments. We request your review and feedback to the assessment comments in preparation for further discussion in our next IRT meeting Session #14, Thursday 13 February 2025. Please reach out on list with any questions and check the document for IRT comments one more time on the 14th prior to the meeting. Best regards, The IPT

1 0

Re: IRT Task 20250123: Review Progress of Candidate Threshold Questions. Due: 3 Feb 2025
by Dana Kuebler Feb. 6, 2025

Feb. 6, 2025

Dear IRT, Thank you for completing IRT Task 20250123. For ease of tracking, I’ll address both of your comments here. * Roger, you are correct. We do not yet have alignment on whether the Illustrative Disclosure Framework is just an “illustrative“ example. This is addressed in TQ.C<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…>. The focus of TQ.D, on the other hand, related to unclear objectives for IP requests. Clarifying objectives can be found in Annex B<https://urldefense.com/v3/__https:/docs.google.com/document/d/1nS5WTk0p79XR…> of the final report and do not appear to need GNSO guidance. * Volker, your point on TQ.I is already covered within TQ.A and we have further noted your concerns within the IRT input section for additional context for GNSO consideration. Please let us know if you have further comments to close out this task. Thank you for your continued support. Kind Regards, The IPT From: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Tuesday, January 28, 2025 at 3:54 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Cc: Dennis Chang <dennis.chang(a)icann.org>, Volker Greimann <volker.greimann(a)centralnic.com> Subject: [Gdd-gnso-ppsai-impl] Re: IRT Task 20250123: Review Progress of Candidate Threshold Questions. Due: 3 Feb 2025 Dear Dennis, thank you for the summary. I would propose we expand a bit on the third bullet TQ:I as it is not just GDPR that has changed the landscape but also changes to the contracts and new ICANN policies that had an effect on the applicability of the original recommendations. Unless, of course, this is already included in TQ:A in which case I withdraw my proposal. Sincerely, Volker Greimann General Counsel & Head of Policy and Compliance - Online Division volker.greimann(a)centralnic.com Office: +49-172-6367025 Web: www.teaminternet.com Team Internet Group PLC (AIM:TIG). Registered Office: 4th Floor, Saddlers House, 44 Gutter Lane, London, United Kingdom, EC2V 6BR. Team Internet is a company registered in England and Wales with the company number 8576358. ________________________________ From: Dennis Chang via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Sent: 24 January 2025 12:26 AM To: gdd-gnso-ppsai-impl(a)icann.org <gdd-gnso-ppsai-impl(a)icann.org> Cc: Dennis Chang <dennis.chang(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] IRT Task 20250123: Review Progress of Candidate Threshold Questions. Due: 3 Feb 2025 Dear IRT, Thank you all for your time and feedback on draft responses to threshold questions. With three sessions remaining in our work plan on the 3 threshold questions [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1jvVfgLtnqzcS…> we would like to address the remaining candidate questions that are shown in the IRT Threshold Question tracker.. Please review our proposed assessment and handling of the following candidate threshold questions, as found in the IRT Threshold Question Tracker [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1rqfRaG1y…>. Please reply to this message on the list if you have any objections by Monday, 3 Feb 2025. * TQ.D: (Unclear objectives around Illustrative Disclosure Framework for IP requests). GNSO Guidance may not be needed as clarification of the objectives for framework are in Annex B [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1nS5WTk0p79XR…> of final report. * TQ.G: (Conflict with Transfer Policy Recommendations). This does not appear to be a threshold question, but is a coordination concern and would be useful to consider for further discussion during implementation. This has been a noted topic in implementation tracker for reference. * TQ.I: (GDPR Changing the landscape) This focus of this candidate threshold question appears to be duplicative of content already included in the drafting of TQ.A: Definitions & Industry use. * TQ.J: (Higher risk of inadvertent publication of a customer’s details in the course of de-accreditation for unaffiliated providers?) Threshold Question appears to fall into clarifying questions and has been discussed in the industry practices session during ICANN81. We are making steady progress and intend to focus our discussions in the upcoming session on Threshold Question 3 relating to disclosure frameworks. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Cancelled - PPSAI IRT Session #13, Thursday 30 January 2025
by Dennis Chang Jan. 30, 2025

Jan. 30, 2025

Dear IRT, Thank you for your feedback on revised language for threshold questions A & C. There are no further objections to the language in preparation for GNSO consideration! Well Done! We will begin coordinating the next steps with the GNSO liaison. Additionally, we are working on threshold question #3 assessment materials concerning the Intellectual Property and Law Enforcement Disclosure Frameworks that ICANN org had developed with the previous IRT. We are cancelling IRT Session 13, scheduled for this Thursday 30 January, to allow us to complete and circulate the materials and to allow the IRT time to review before the next call. We will be sending cancellations out shortly. Please continue to evaluate review of our proposed assessment and handling of candidate threshold questions D, G, I, and J which was sent out to the List on 23 January<https://lists.icann.org/hyperkitty/list/gdd-gnso-ppsai-impl@icann.org/threa…> 2025 and can also be found in the IRT Threshold Question Tracker: <https://docs.google.com/spreadsheets/d/1rqfRaG1yL8HU48u0_3rIHkREoWN0Psr0rT_I...> . Please reply on the list if you have any objections by Monday, 3 Feb 2025. Happy Lunar New Year! Wishing you the most charming holidays on this year of the Snake. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

3 3

IRT Task 20250123: Review Progress of Candidate Threshold Questions. Due: 3 Feb 2025
by Dennis Chang Jan. 28, 2025

Jan. 28, 2025

Dear IRT, Thank you all for your time and feedback on draft responses to threshold questions. With three sessions remaining in our work plan on the 3 threshold questions<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…> we would like to address the remaining candidate questions that are shown in the IRT Threshold Question tracker.. Please review our proposed assessment and handling of the following candidate threshold questions, as found in the IRT Threshold Question Tracker<https://docs.google.com/spreadsheets/d/1rqfRaG1yL8HU48u0_3rIHkREoWN0Psr0rT_…>. Please reply to this message on the list if you have any objections by Monday, 3 Feb 2025. * TQ.D: (Unclear objectives around Illustrative Disclosure Framework for IP requests). GNSO Guidance may not be needed as clarification of the objectives for framework are in Annex B<https://docs.google.com/document/d/1nS5WTk0p79XRT0CcCzByAyH_xn6KMDgElc5F6QS…> of final report. * TQ.G: (Conflict with Transfer Policy Recommendations). This does not appear to be a threshold question, but is a coordination concern and would be useful to consider for further discussion during implementation. This has been a noted topic in implementation tracker for reference. * TQ.I: (GDPR Changing the landscape) This focus of this candidate threshold question appears to be duplicative of content already included in the drafting of TQ.A: Definitions & Industry use. * TQ.J: (Higher risk of inadvertent publication of a customer’s details in the course of de-accreditation for unaffiliated providers?) Threshold Question appears to fall into clarifying questions and has been discussed in the industry practices session during ICANN81. We are making steady progress and intend to focus our discussions in the upcoming session on Threshold Question 3 relating to disclosure frameworks. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

3 2

Recordings available for IRT Meeting #12: 16 January 2025
by Dana Kuebler Jan. 23, 2025

Jan. 23, 2025

Hello IRT, Just a quick update that IRT session #12 recordings are available here<https://community.icann.org/pages/viewpage.action?pageId=422182964>, transcripts will be posted shortly. We look forward to further discussion next Thursday, 30 January 2025 @15:30 UTC. All the best, Dana

1 0

IRT Task 20250115c: TQ E: Review Draft Threshold Questions for GNSO. Due. 28 Jan 2025
by Dennis Chang Jan. 15, 2025

Jan. 15, 2025

Dear IRT, Please review and provide your comment on Threshold Question E. This question is about Indemnification Provision. Is it in scope of our implementation work? Should it be a question for GNSO? We’d like to discuss this at the IRT meeting tomorrow too if time permits. 20250115c TQ E: Review the Draft for IRT Threshold Questions<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…> for GNSO Council Guidance. Section 4.TQ.E 28 Jan 2025 As an AOB item and if we have time, we may take a quick preliminary look at other TQs too to optimize our meeting time. Thank you all for your support. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

IRT Task 20250115b: TQ A.Revision: Review on the Revised Draft Language for IRT Threshold Questions for GNSO Council Guidance. Section 4.TQ.A. Due: 27 Jan 2025
by Dennis Chang Jan. 15, 2025

Jan. 15, 2025

Dear IRT, Thank you for your comments and discussion on the Threshold Question A. Considering the IRT feedback, we’ve drafted a revised version of the question. Please follow the instruction provided in Section 2 of the document to make your comments. (IRT Task 20250115a) 20250115b TQ A.revision: Review on the Revised Draft Language for IRT Threshold Questions<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…> for GNSO Council Guidance. Section 4.TQ.A 27 Jan 2025 We’ll review the revision and begin the discussion tomorrow at the IRT meeting and you’ll have ample time to make your comments after the meeting. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

IRT Task 20250115a: Review updated Instructions for TQs in the IRT TQ Doc in Section 2.. Due: 21 Jan 2025
by Dennis Chang Jan. 15, 2025

Jan. 15, 2025

Dear IRT, Happy 2025! We have updated the instruction for reviewing and commenting on the Threshold Questions that are being presented to you for review. Leon will go over this with the IRT at tomorrow’s meeting, but I am assigning this task to ensure all IRT members are aware of proper ways to make the comments. There will be specific task assignments following this task but please complete this task before working on other tasks. 20250115a Review updated Instructions for TQs in the IRT TQ Doc<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…> in Section 2.. 21 Jan 2025 Looking forward to our first meeting of the year tomorrow. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Re: IRT Task 20241218: New due date: 13 Jan 2025. TQ.C. - Illustrative Disclosure Framework - policy or example?
by Dennis Chang Dec. 20, 2024

Dec. 20, 2024

Dear IRT, Per your request at the IRT meeting yesterday, we revised the due date to 13 Jan 2025 for this task. 20241218 TQ.C. Provide feedback on draft Threshold Question<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…> for GNSO about Illustrative Disclosure Framework - policy or example 6 Jan 2025 13 Jan 2025 Thanks again for the engaging discussion yesterday. I’ll be communicating more on TQ.A in the TQ.A email trail and the TQ doc. Cheers, Dennis Chang From: Dennis Chang via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Reply-To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org> Date: Wednesday, December 18, 2024 at 3:33 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Cc: Dennis Chang <dennis.chang(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] IRT Task 20241218: TQ.C. Provide feedback on draft Threshold Question for GNSO - Illustrative Disclosure Framework - policy or example . Due: 6 Jan 2025 Dear IRT, Thank you for the engaging comments to the TQ.A so far. I look forward to discussing it at our meeting tomorrow. Today, I am issuing another Task for another Threshold Question. The due date is not till next year but please take a look at the draft as it may inform our discussion for TQ.A. 20241218 TQ.C. Provide feedback on draft Threshold Question [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1jvVfgLtnqzcS…> for GNSO about Illustrative Disclosure Framework - policy or example 6 Jan 2025 If we have time, I wouldn’t mind initiating the discussion on this one tomorrow, but we will have it on our agenda for the first IRT meeting next year. You may be asking, “why not TQ.B next?” We’ve looked at TQ.B and decided that we should hold-off on this one till we are further along in the accreditation discussion. So, it will come but later. Thank you for the email discussion and please continue. We are reading every word and taking careful notes. We find all of your comments helpful, especially the new perspectives and diverse points of views. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Recordings available for IRT Meeting #11: 19 Dec 2024
by Dana Kuebler Dec. 19, 2024

Dec. 19, 2024

Hello IRT, Just a quick update that IRT session #11 recordings are available here<https://community.icann.org/pages/viewpage.action?pageId=393314335>, transcripts will be posted shortly. We look forward to further discussion in the new year. Thursday, 16 January 2025 @15:30 UTC. Happy Holidays All the best, Dana

2 1

Dec. 19, 2024

I hope the call goes well. Let me know if you think anything is heading off the rails. Best, Paul

1 0

Re: [Ext] RE: Re: IRT Task 20241205: TQ.A: Provide feedback to on Draft Language for IRT Threshold Questions for GNSO Council Guidance. Due: 13 Dec 2024
by Dennis Chang Dec. 19, 2024

Dec. 19, 2024

13 Dec 2024: IRT Task due Date. 19 Dec 2024: IRT Meeting Date Thanks Brian, Reg, and those making comments on the doc for TQ A. The topic is “Changes to Definition Language.” I’d like the IRT to consider beyond the Principled position of NO CHANGE at ALL. At the lowest level of change are the typos and grammar. Then word changes to reflect currency and clarity etc. We will need to create our own draft of the definition for our implementation. Could this be done without making any changes? For example, we can look at the work done by the 2016 IRT here. Final Report Definition P/P AA Definition "Privacy Service" means a service by which a Registered Name is registered to its beneficial user as the Registered Name Holder, but for which alternative, reliable contact information is provided by the privacy or proxy service provider for display of the Registered Name Holder's contact information in the Registration Data Service (WHOIS) or equivalent services. 1.24 “Privacy Service” means a service by which a Registered Name is registered to a Customer as the Registered Name Holder, but for which alternative, reliable contact information is provided by Provider for display in the Registration Data Directory Service rather than the Customer’s contact information in the Registration Data Directory Service. Please complete this task this week. Task# IRT Tasks (Homework) Due Date 20241205 TQ A. Provide feedback to on Draft Language for IRT Threshold Questions<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…> for GNSO Council Guidance. 13 Dec 2024 Thanks you! Dennis Chang From: BECKHAM Brian <brian.beckham(a)wipo.int> Date: Thursday, December 5, 2024 at 11:14 PM To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org> Cc: Dennis Chang <dennis.chang(a)icann.org>, Reg Levy <rlevy(a)tucows.com> Subject: [Ext] RE: [Gdd-gnso-ppsai-impl] Re: IRT Task 20241205: TQ.A: Provide feedback to on Draft Language for IRT Threshold Questions for GNSO Council Guidance. Due: 13 Dec 2024 Hi Reg, Denis, all, I have added a comment in the document (I may be misunderstanding the relation here, but question 2 seems to be linked to question 1, and question 3 flows from that connection). Please can we also attribute the “concerns and inputs” to individuals to give them context. More fundamentally however, we seem to be missing the core question of whether subsequent events (e.g., GDPR and NIS2) somehow “overtake” the PPSAI recommendations such that they need to be reconsidered in whole or in part. Perhaps that is the gist of question 3, but it is not immediately clear to me if that is the case. I also think questions such as “would this require a new contract” or things to that effect are beyond the scope of this IRT and need not be asked here. Brian PS, it may only be me, but there still seems to be an issue with the mtg ICS invites. From: Reg Levy via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Sent: Thursday, December 5, 2024 10:56 PM To: PPSAI IRT members, including observers <gdd-gnso-ppsai-impl(a)icann.org> Cc: Dennis S. Chang <dennis.chang(a)icann.org>; Reg Levy <rlevy(a)tucows.com> Subject: [Gdd-gnso-ppsai-impl] Re: IRT Task 20241205: TQ.A: Provide feedback to on Draft Language for IRT Threshold Questions for GNSO Council Guidance. Due: 13 Dec 2024 Dennis— Thank you! I’ve made some comments/edits to the document. There is no confusion about who the party responsible for the domain is—it is the registrant, in all cases. Where a service is affiliated with a registrar, the registrar has that information (and no other). Where a service is not affiliated with a registrar, that service is the registrant, whether or not it is apparent that a service exists. I’m pretty sure only the first question needs to be asked. The second two questions assume that the IRT can subvert the PDP by creating policy, which is the job of the working group, not of the IRT. Or of Council. Servus, Reg -- Reg Levy | Associate General Counsel – Domains +1 (323) 880-0831 Tucows #MakingTheInternetBetter UTC -8 On Dec 5, 2024, at 13:26, Dennis Chang via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>> wrote: Dear IRT, Thanks to those communicating to us about the missing calendar invitation for today’s meeting. Per your suggestion, we cancelled today’s meeting, Our team here is double checking the tool and process on our side and will refresh the invitations going forward. I addition, we will take up on the offer by a some of you to help us test early to confirm the receipt of the calendar invitations on your side. Below is a task, I had intended to assign at the meeting today with explanation. We did not meet but it’s important that we don’t lose momentum, so we’ll go ahead and start this work via this email. 20241205 TQ A. Provide feedback to on Draft Language for IRT Threshold Questions [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1jvVfgLtnqzcS…> for GNSO Council Guidance. 13 Dec 2024 When you open the document, you will see the “About” and “Instructions” which I hope will sufficiently explain your task. Please don’t hesitate to ask if you’d like further info. One note about the expand/collapse heading feature. You may see only the headers when you open the document. Please note “>” or “v” appeal when you place your curser over the Section header. You’ll see a message “Expand Heading” or “Collapse Heading” that you can click on to reveal or hide the content of the section. I find this new feature very helpful in orienting and organizing our work and I’d like us to use it. At this time of this email, you’ll see TQ A populated with the Draft Language for Questions to GNSO with the “Status: Initial draft review by IRT (5 Dec 2024)” TQ B below is also there being set up with the status “ICANN org drafting.” We plan to issue separate tasks for each TQ work to keep us together as we move forward. Thank you all for your continued support and contribution. Our staff here felt very badly about what happened with the calendar meeting invites but also remarked how cooperative, flexible, and understanding the IRT is working with us a team and even encouraging us. We indeed have the most excellent IRT. Thank you! Gratefully Yours, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org/> One World – One Internet _______________________________________________ Gdd-gnso-ppsai-impl mailing list -- gdd-gnso-ppsai-impl(a)icann.org<mailto:gdd-gnso-ppsai-impl@icann.org> To unsubscribe send an email to gdd-gnso-ppsai-impl-leave(a)icann.org<mailto:gdd-gnso-ppsai-impl-leave@icann.org> _______________________________________________ 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. World Intellectual Property Organization Disclaimer: This electronic message may contain privileged, confidential and copyright protected information. If you have received this e-mail by mistake, please immediately notify the sender and delete this e-mail and all its attachments. Please ensure all e-mail attachments are scanned for viruses prior to opening or using.

9 12

IRT Task 20241218: TQ.C. Provide feedback on draft Threshold Question for GNSO - Illustrative Disclosure Framework - policy or example . Due: 6 Jan 2025
by Dennis Chang Dec. 18, 2024

Dec. 18, 2024

Dear IRT, Thank you for the engaging comments to the TQ.A so far. I look forward to discussing it at our meeting tomorrow. Today, I am issuing another Task for another Threshold Question. The due date is not till next year but please take a look at the draft as it may inform our discussion for TQ.A. 20241218 TQ.C. Provide feedback on draft Threshold Question<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…> for GNSO about Illustrative Disclosure Framework - policy or example 6 Jan 2025 If we have time, I wouldn’t mind initiating the discussion on this one tomorrow, but we will have it on our agenda for the first IRT meeting next year. You may be asking, “why not TQ.B next?” We’ve looked at TQ.B and decided that we should hold-off on this one till we are further along in the accreditation discussion. So, it will come but later. Thank you for the email discussion and please continue. We are reading every word and taking careful notes. We find all of your comments helpful, especially the new perspectives and diverse points of views. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

IRT Task 20241205: TQ.A: Provide feedback to on Draft Language for IRT Threshold Questions for GNSO Council Guidance. Due: 13 Dec 2024
by Dennis Chang Dec. 6, 2024

Dec. 6, 2024

Dear IRT, Thanks to those communicating to us about the missing calendar invitation for today’s meeting. Per your suggestion, we cancelled today’s meeting, Our team here is double checking the tool and process on our side and will refresh the invitations going forward. I addition, we will take up on the offer by a some of you to help us test early to confirm the receipt of the calendar invitations on your side. Below is a task, I had intended to assign at the meeting today with explanation. We did not meet but it’s important that we don’t lose momentum, so we’ll go ahead and start this work via this email. 20241205 TQ A. Provide feedback to on Draft Language for IRT Threshold Questions<https://docs.google.com/document/d/1jvVfgLtnqzcSarbL2UfeHQV_CykUbpv-DB_m5ZA…> for GNSO Council Guidance. 13 Dec 2024 When you open the document, you will see the “About” and “Instructions” which I hope will sufficiently explain your task. Please don’t hesitate to ask if you’d like further info. One note about the expand/collapse heading feature. You may see only the headers when you open the document. Please note “>” or “v” appeal when you place your curser over the Section header. You’ll see a message “Expand Heading” or “Collapse Heading” that you can click on to reveal or hide the content of the section. I find this new feature very helpful in orienting and organizing our work and I’d like us to use it. At this time of this email, you’ll see TQ A populated with the Draft Language for Questions to GNSO with the “Status: Initial draft review by IRT (5 Dec 2024)” TQ B below is also there being set up with the status “ICANN org drafting.” We plan to issue separate tasks for each TQ work to keep us together as we move forward. Thank you all for your continued support and contribution. Our staff here felt very badly about what happened with the calendar meeting invites but also remarked how cooperative, flexible, and understanding the IRT is working with us a team and even encouraging us. We indeed have the most excellent IRT. Thank you! Gratefully Yours, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

3 2

PPSAI IRT Meeting Reminder: This Thursday 17:30-19:00 UTC, 9:30-11:00 am PDT | ref:_00D1aY7OU._500QkCF0Gw:ref
by GDS Shared Services Dec. 5, 2024

Dec. 5, 2024

Dear PPSAI IRT, This is a reminder for our upcoming IRT Meeting #10, scheduled for 90 minutes, this Thursday, 5 December 2024 @ 17:30-19:00 UTC, 9:30-11:00 am PDT. REMINDER: Please sign into the zoom session with your full name. Admittance to the session may be delayed or denied if your full name is not provided. Additionally, Artificial Intelligence (AI) bots will not be allowed into the meeting as discussed during IRT Session #2, 24 July 2024 Please let us know if you are an IRT member and have not received invitation details including zoom access. Meeting Agenda details will be posted here<https://community.icann.org/display/IRT/IRT+Meetings> shortly. Thank you for your support, we look forward to seeing you. Kind Regards, Yvette Guigneaux Strategic Initiatives Coordinator Global Domains & Strategy (GDS) GDS Shared Services Cell: 310-460-8432 Skype: yvette.guigneaux Email: yvette.guigneaux(a)icann.org<mailto:yvette.guigneaux@icann.org> Internet Corporation for Assigned Names and Numbers [signature_3435320353]

14 16

Privacy/Proxy Service actual offering
by Luc SEUFER Nov. 20, 2024

Nov. 20, 2024

Hi Team, I hope you all made it safely back home. It’s a shameless plug, but I trust it can help the group. I wrote it as an update to Owen's presentation of the post-2013 RRA landscape. I can give you examples if needed. https://www.eurodns.com/blog/icann-81-istanbul-insights#privacy-and-proxy-s… All the best, Luc SEUFER CLO | Namespace Group [A picture containing tableware, plate, drawing, food Description automatically generated] mobile: +352 691 600 417<tel:+352691600417> office: +352 27 220 166<tel:+35227220166> lseufer(a)namespace.com<mailto:lseufer@namespace.com> www.namespace.com<http://www.namespace.com/>

2 2

IRT Task 20241118: Comment on Analysis document. Due 30 Nov 2024
by Dennis Chang Nov. 18, 2024

Nov. 18, 2024

Dear IRT, Thank you for a great ICANN81 IRT session. I’ve received positive feedbacks including the “best IRT session to date!” Thanks again to the presenters: Margie, Owen, and Reg. We are indeed fortunate to have them with extensive knowledge and experiences on P/P going all the way back to origin of the policy. With the information we’ve been provided for the current marketplace, we continue our work to analyze the Recommendations for implementation. We will do this using a shared commentable document in the same way we’ve done on the Final Report. Here is your next task. 20241118 PPSAI Recommendation Analysis Review and Comment: Call out Threshold Question #1 related analysis. IRT Commentable Version of ICANN org's PPSAI Implementation Analysis (02 Mar 2024)<https://docs.google.com/document/d/1YasrAlcLMJT9VP5JOl8KQkPbuzQ4Nnnc0a5oIRn…> 30 Nov 2024 Please keep in mind that this is the same document we’ve provided in June 2024 for you to read. ICANN org did this analysis in 2023 and things may have changed so we are opened to receiving new thoughts and ideas. We will review the comments as a team at our next IRT meeting but please feel free to comment, reply,, question, and converse via email too. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

ICANN81 PPSAI IRT Session Thursday, 14 November, 09:00-10:00 local time at ICANN81 in Istanbul, Turkey
by Noor Zannat Nov. 13, 2024

Nov. 13, 2024

Dear PPSAI IRT, This is a reminder for our upcoming IRT Meeting scheduled for 60 minutes on Thursday, 14 November, 09:00-10:00 local time at ICANN81 in Istanbul, Turkey!. https://icann81.sched.com/event/1p2G1 Agenda details can be found here<https://community.icann.org/display/IRT/IRT+Meetings> REMINDER: Please sign into the zoom session with your full name. Admittance to the session may be delayed or denied if your full name is not provided. Additionally, Artificial Intelligence (AI) bots will not be allowed into the meeting as discussed during IRT Session #2, 24 July 2024 • Zoom Meeting Link: https://icann.zoom.us/j/99825232006?pwd=tXKucBIJMYGAA6acBkyPUPGapRwREu.1 • Zoom Meeting ID: 998 2523 2006 • Zoom Meeting Passcode: eVq@?!346* • Zoom International Dial-In Numbers: https://icann.zoom.us/u/a9eCkEwft • Zoom Phone Passcode: 119 039 8562 Regards, Noor

1 0

ICANN81 PPSAI IRT Session
by Noor Zannat Nov. 12, 2024

Nov. 12, 2024

Dear PPSAI IRT, This is a reminder for our upcoming IRT Meeting scheduled for 60 minutes on Thursday, 14 November, 09:00-10:00 local time at ICANN81 in Istanbul, Turkey!. https://icann81.sched.com/event/1p2G1 Please note Zoom link will be available 24 hours before scheduled meeting time. Agenda details can be found here<https://community.icann.org/display/IRT/IRT+Meetings> REMINDER: Please sign into the zoom session with your full name. Admittance to the session may be delayed or denied if your full name is not provided. Additionally, Artificial Intelligence (AI) bots will not be allowed into the meeting as discussed during IRT Session #2, 24 July 2024 Regards, Noor

1 0

Recordings now available for IRT Meeting #8: 31 October 2024
by Dana Kuebler Nov. 1, 2024

Nov. 1, 2024

Hello IRT, Just a quick update that IRT session #8 recordings are available here<https://community.icann.org/pages/viewpage.action?pageId=385745139>, transcripts will be posted shortly. If you missed this session, please take time to review the available recordings in advance of our next meeting. IRT members discussed concerns related to the IRT Final report recommendations 1-14. We look forward to further discussions at ICANN81 Thursday, 14 November 09:00-10:00 Local Time, 06:00 UTC, 10pm PST, 1am EST, (Register here<https://meetings.icann.org/en/meetings/icann81/>) Session schedule Link<https://icann81.sched.com/event/1p2G1> All the best, Dana

3 2

PPSAI IRT Meeting Reminder: This Thursday 15:30-17:00 UTC, 8:30-10:00 am PDT
by Noor Zannat Oct. 28, 2024

Oct. 28, 2024

Dear PPSAI IRT, This is a reminder for our upcoming IRT Meeting scheduled for 90 minutes this Thursday. REMINDER: Please sign into the zoom session with your full name. Admittance to the session may be delayed or denied if your full name is not provided. Additionally, Artificial Intelligence (AI) bots will not be allowed into the meeting as discussed during IRT Session #2, 24 July 2024 Please let us know if you are an IRT member and have not received invitation details including zoom access. Meeting Agenda details will be posted here<https://community.icann.org/display/IRT/IRT+Meetings> shortly. Thank you for your support, we look forward to seeing you. Regards, Noor Zannat

1 0

A copy of NYT article cited by Michael etc.
by John McCabe Oct. 24, 2024

Oct. 24, 2024

IRT Members, In this post of 10/18/2024, Michael Palage wrote and provided a link to a newspaper article in my hometown newspaper saying: “While Owen referred to the New York Times article as a hack, I actually would encourage all IRT members to read it, see https://www.nytimes.com/2024/10/09/business/iceland-online-disinformation-i… ” The New York Times is regarded as a first-rate newspaper, one that breaks news, tracks down leads, and does original reporting and news stories. The NYT employs journalists around the world, but does not hire “hacks.” This stands in sharp contrast to most online and print “news” outlets that are a pastiche of “news” gleaned from and citing to other “news” sources of varying and uncertain repute, including “fake news,” etc. Because access is subscription based, on the morning of 10/9/2024, when it appeared on my desktop as “front page news,” I took the initiative to copy the text into a Word doc and save it as a pdf *with internal links intact* to share for information with the RySG that day. I added a note at the bottom adding the subscriber data: NYT currenthas circulation is 10.5 million, of which 10.2 are digital only. (Their goal is at least 15 million by the end of 2027.) (See attached) I now share it with the PPSAI IRT in my individual capacity, and not in any representational one. (Photos were redacted, but included original NYT-credited pictures of the building at Kalkofnsvegur 2, Reykjavik; the manager of the basement museum outside that building; an overhead shot of the city center; and one of the leader of Iceland’s Media Commission.) On another of Michael's points, I attach a screen capture which today shows the domain record for palage.com, clearly identifying Michael D. Palage as registrant, which information had been masked without his prior knowledge or instructions as he reported. (See attached) On a personal note, I believe this highlights the need for domain records to unequivocally distinguish as to whether a registration is either under the “Proxy” or the “Privacy” paradigm. Furthermore, the choice between either disclosure of registrant name or privacy or proxy should be left to registrants based on clear definitions and free choice. Best regards, John McCabe .whoswho

1 0

Please register. ICANN81 PPSAI IRT session.
by Dennis Chang Oct. 22, 2024

Oct. 22, 2024

Dear IRT, Our PPSAI IRT session has been published on the ICANN81 Istanbul schedule. https://icann81.sched.com/event/1p2G1 Please register for the session to attend remotely or in-person. As we discussed, we’ll be devoting the hour-long session to sharing and learning the current PP practice. Answering the call for volunteers to share are: * Owen Smigelski (Namecheap) * Margie Milam (Meta) * Reg Levy (Tucows) I’ve reached out this team to begin coordinating and planning for the session. We’ll have about 15 minutes per person and provide time for others attending (non-IRT members) that are in the business of PP Services. It will be a good public session getting to know what is really happening out there today. For us to produce an implementation model that is aligned with recommendations that works in today’s PP environment is highly challenging as we are seeing. We thank the presenters for sharing their insights. Please invite your practitioner colleagues to the session. I hope for a largr participation to confirm or correct our assumptions and contribute to the discussion for our implementation. At our IRT meeting next week, we’ll provide our prep status. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Skype: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Re: [Invt-gdd-gnso-ppsai-impl] Re: PPSAI IRT Meeting Reminder: This Thursday 15:30-17:00 UTC, 8:30-10:00 am PDT
by John McElwaine Oct. 19, 2024

Oct. 19, 2024

Dennis, I had a comment marked as a “Concern” in the Google document that appears to have been removed, or at least I cannot find it. The substance of the Concern was that there should be a standard or set of best practices that should be followed in making a decision concerning disclosure. Thanks, John [http://www.nelsonmullins.com/img/ecard-logo.png] JOHN C. MCELWAINE PARTNER john.mcelwaine(a)nelsonmullins.com<mailto:john.mcelwaine@nelsonmullins.com> LIBERTY CENTER | SUITE 600 151 MEETING STREET | CHARLESTON, SC 29401 T 843.534.4302 F 843.722.8700 101 CONSTITUTION AVENUE, NW | SUITE 900 WASHINGTON, D.C., 20001 T 202.689.2939 F 202.689.2860 NELSONMULLINS.COM<http://www.nelsonmullins.com> VCARD<http://www.nelsonmullins.com/people/john-mcelwaine/vcard> VIEW BIO<http://www.nelsonmullins.com/people/john-mcelwaine> From: pimo via Invt-gdd-gnso-ppsai-impl <invt-gdd-gnso-ppsai-impl(a)icann.org> Sent: Thursday, October 17, 2024 10:31 AM To: Noor Zannat via Invt-gdd-gnso-ppsai-impl <invt-gdd-gnso-ppsai-impl(a)icann.org> Cc: pimo <pimonit(a)gmail.com> Subject: [Invt-gdd-gnso-ppsai-impl] Re: PPSAI IRT Meeting Reminder: This Thursday 15:30-17:00 UTC, 8:30-10:00 am PDT Hi Noor, I hope you are well. I was wondering if I could join the call half an hour later today—if you feel it's not too disruptive—as I have another call until 5. Otherwise, I’ll watch the recording and feed in any thoughts in due course. Hi Noor, I hope you are well. I was wondering if I could join the call half an hour later today—if you feel it's not too disruptive—as I have another call until 5. Otherwise, I’ll watch the recording and feed in any thoughts in due course. Thanks, Paola On Wed, 16 Oct 2024 at 19:03, Noor Zannat via Invt-gdd-gnso-ppsai-impl <invt-gdd-gnso-ppsai-impl(a)icann.org<mailto:invt-gdd-gnso-ppsai-impl@icann.org>> wrote: Dear PPSAI IRT, This is a reminder for our upcoming IRT Meeting scheduled for 90 minutes tomorrow. Agenda details can be found here<https://urldefense.com/v3/__https:/community.icann.org/display/IRT/IRT*Meet…> REMINDER: Please sign into the zoom session with your full name. Admittance to the session may be delayed or denied if your full name is not provided. Additionally, Artificial Intelligence (AI) bots will not be allowed into the meeting as discussed during IRT Session #2, 24 July 2024 Join the Zoom room directly (recommended): https://icann.zoom.us/j/92061188255?pwd=7RXCoyaLUvzOYsfjdDI9qBz8klNkHo.1<https://urldefense.com/v3/__https:/icann.zoom.us/j/92061188255?pwd=7RXCoyaL…> (no password required) Before joining the call: Please be sure you have read the Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> If joining Zoom via the Zoom App, the following will be required: Meeting ID: 920 6118 8255 Password: %3a?$S5ZjZ If you are joining via audio only: One tap mobile +13462487799,,92061188255#,,,,*9486090507# US (Houston) +16699006833,,92061188255#,,,,*9486090507# US (San Jose) Dial in directly with your chosen number<https://urldefense.com/v3/__https:/zoom.us/zoomconference?u=Xk-KXAYeXAJnzZv…> and provide: Meeting ID: 920 6118 8255 Password: 9486090507 If this is your first time with Zoom, please take a look here: Welcome to Zoom<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Thank you for your support, we look forward to seeing you. Regards, Noor Zannat _______________________________________________ Invt-gdd-gnso-ppsai-impl mailing list -- invt-gdd-gnso-ppsai-impl(a)icann.org<mailto:invt-gdd-gnso-ppsai-impl@icann.org> To unsubscribe send an email to invt-gdd-gnso-ppsai-impl-leave(a)icann.org<mailto:invt-gdd-gnso-ppsai-impl-leave@icann.org> Confidentiality Notice This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (800-237-2000) or reply to this e-mail and delete all copies of this message.

7 10

Recordings now available for IRT Meeting #7: 17 October 2024.
by Dana Kuebler Oct. 17, 2024

Oct. 17, 2024

Hello IRT, Just a quick update that IRT session #6 recordings are available here<https://community.icann.org/pages/viewpage.action?pageId=382042142>, transcripts will be posted shortly. If you missed this session, please take time to review the available recordings in advance of our next meeting. IRT members discussed concerns related to the IRT Final report recommendations 1-14. We look forward to further discussions on topics of concerns on the IRT final report recommendations Thursday, 31 October 2024. All the best, Dana

1 0

PPSAI IRT Meeting Reminder: This Thursday 15:30-17:00 UTC, 8:30-10:00 am PDT
by Noor Zannat Oct. 14, 2024

Oct. 14, 2024

Dear PPSAI IRT, This is a reminder for our upcoming IRT Meeting schedule for 90 minutes this Thursday. REMINDER: Please sign into the zoom session with your full name. Admittance to the session may be delayed or denied if your full name is not provided. Additionally, Artificial Intelligence (AI) bots will not be allowed into the meeting as discussed during IRT Session #2, 24 July 2024 Please let us know if you are an IRT member and have not received invitation details including zoom access. Meeting Agenda details will be posted here<https://community.icann.org/display/IRT/IRT+Meetings> shortly. Thank you for your support, we look forward to seeing you. Regards, Noor

1 0

IRT Task 20241003b: ICANN81 session volunteers: PP practice today. Due. 10 Oct 2024
by Dennis Chang Oct. 9, 2024

Oct. 9, 2024

Dear IRT, At today’s IRT meeting, we called for volunteers to present at the ICANN81. 20241003b Call for Volunteers for ICANN81 sharing of current practice. Reply to IRT email. 10 Oct 2024 The ICANN81 IRT session will be open and it’s an opportunity to share with the IRT and the community how Privacy Proxy Services work today. We agreed early in this project that it’s important for us to understand how this service works today before designing an implementation model. We’ve heard from many that much has changed since 2016 when the last IRT worked on implementation. We’d like to hear from Registrars, Privacy Proxy Service providers, and others business entities serving this are of business. Please reply to this email with your interest. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

3 2

Re: IRT Task 20241003a: Review Guidelines: Formulating Responses to Threshold Questions. Due. 10 Oct 2024
by Dennis Chang Oct. 8, 2024

Oct. 8, 2024

Dear IRT, Consider this email as a friendly reminder to complete by Thursday this week. I see that comments of concerns have slowed to stop, and you may all completed this task already but if you haven’t, please do. I plan to issue another task right after the due date of this task to review all comments prior to our meeting next week. All of us having reviewed the comment prior to the meeting will help us to be more efficient with the meeting. Thanks you for your continued support. Best, Dennis Chang From: Dennis Chang via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Reply-To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org> Date: Thursday, October 3, 2024 at 8:17 PM To: Dana Kuebler via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Cc: Dennis Chang <dennis.chang(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] IRT Task 20241003a: Review Guidelines: Formulating Responses to Threshold Questions. Due. 10 Oct 2024 Dear IRT, Thanks to those that attended the meeting today. We began discussing the Comments of Concern today and introduced a new tool to track our discussion. We call this the IRT Threshold Question Tracker and you can find it in the IRT workbook [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1rqfRaG1y…> with a sheet labeled IRT TQ Tracker. In this T-Tracker, we’ll capture what we consider as “Candidates for Threshold Questions.” This IRT Task is for all IRT members to review the Guidelines that explains what this is and how to use it. 20241003a Review Proposed Guidelines: Formulating Responses to Threshold Questions [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1G3iLFAwrFYwh…> 10 Oct 2024 This is a new tool for all of us, so I ask for your patients as we make progress and refine our process. We spend some time at the beginning of the meeting today explaining the tool and answering questions so please do listen to the recording. After you review the recording and if you still have questions, you may comment on the document. Thank you for supporting the Comments of Concern discussions as we identify potential Threshold Questions. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

IRT Task 20241003a: Review Guidelines: Formulating Responses to Threshold Questions. Due. 10 Oct 2024
by Dennis Chang Oct. 4, 2024

Oct. 4, 2024

Dear IRT, Thanks to those that attended the meeting today. We began discussing the Comments of Concern today and introduced a new tool to track our discussion. We call this the IRT Threshold Question Tracker and you can find it in the IRT workbook<https://docs.google.com/spreadsheets/d/1rqfRaG1yL8HU48u0_3rIHkREoWN0Psr0rT_…> with a sheet labeled IRT TQ Tracker. In this T-Tracker, we’ll capture what we consider as “Candidates for Threshold Questions.” This IRT Task is for all IRT members to review the Guidelines that explains what this is and how to use it. 20241003a Review Proposed Guidelines: Formulating Responses to Threshold Questions<https://docs.google.com/document/d/1G3iLFAwrFYwhoIdffiyIhPJtsYAZYYmaQdR-pxd…> 10 Oct 2024 This is a new tool for all of us, so I ask for your patients as we make progress and refine our process. We spend some time at the beginning of the meeting today explaining the tool and answering questions so please do listen to the recording. After you review the recording and if you still have questions, you may comment on the document. Thank you for supporting the Comments of Concern discussions as we identify potential Threshold Questions. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Recordings now available for IRT Meeting #6: 03 October 2024.
by Dana Kuebler Oct. 3, 2024

Oct. 3, 2024

Hello IRT, Just a quick update that IRT session #6 recordings are available here<https://community.icann.org/pages/viewpage.action?pageId=378470555>, transcripts will be posted shortly. If you missed this session, please take time to review the available recordings in advance of our next meeting. IRT members discussed concerns related to the IRT Final report recommendations 1-7. We look forward to further discussions on topics of concerns on the IRT final report recommendations Thursday, 3 October 2024. All the best, Dana

1 0

PPSAI IRT Meeting Reminder: This Thursday 15:30-17:00 UTC, 8:30-10:00 am PDT
by Noor Zannat Sept. 30, 2024

Sept. 30, 2024

Dear PPSAI IRT, This is a reminder for our upcoming IRT Meeting scheduled for 90 minutes this Thursday. Please let us know if you are an IRT member and have not received invitation details including zoom access. Meeting Agenda details will be posted here<https://community.icann.org/display/IRT/IRT+Meetings> shortly. Thank you for your support, we look forward to seeing you. Regards, Noor Zannat

1 0

Transcript is now available for IRT Meeting #5: 19 Sept 2024.
by Dana Kuebler Sept. 25, 2024

Sept. 25, 2024

Hello IRT, Just a quick update that IRT session #5 transcript is available here<https://community.icann.org/pages/viewpage.action?pageId=367362107>. We look forward to beginning discussion on comments of concerns on the IRT final report recommendations 1-7 Thursday, 3 October 2024. All the best, Dana From: Dana Kuebler <dana.kuebler(a)icann.org> Date: Thursday, September 19, 2024 at 1:44 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] Recordings now available for IRT Meeting #5: 19 Sept 2024. Hello IRT, Just a quick update that IRT session #5 recordings are available here<https://community.icann.org/pages/viewpage.action?pageId=367362107>, transcripts will be posted shortly. If you missed this session, please take time to review the available recordings in advance of our next meeting. IRT members shared useful insights and experiences in response to many clarifying questions on IRT final report recommendations 8-21. We look forward to beginning discussion on topics of concerns on the IRT final report recommendations 1-7 Thursday, 3 October 2024. All the best, Dana

1 0

IRT Task 20240923: Provide Comments of Concerns for Rec 15 - 21. Due: 7 Oct 2024
by Dennis Chang Sept. 23, 2024

Sept. 23, 2024

Dear IRT, Thanks for continuing your comments and replies. This is the last task to complete all 21 recommendations. Please check the documents to see the replies; especially before we meet. 20240923 Provide comments of concerns for 15-21 in IRT Commentable Version of the PPSAI PDP Final Report (2015)<https://docs.google.com/document/d/1nS5WTk0p79XRT0CcCzByAyH_xn6KMDgElc5F6QS…> Concerns should be focused on implementability of the recommendation. Is the recommendation implementable as written? 7 Oct 2024 IRT is welcomed to complete this task earlier than the due date. Reminder: It is challenging but we MUST stay within our remit of “implementation,” It’s easy for us to get into “policy making” discussion which is not the purpose of the IRT. Let’s keep vigilant to stay within our limited scope of the implementing the recommendations in the PPSAI Final Report that the Board approved for us to implement. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Recordings now available for IRT Meeting #5: 19 Sept 2024.
by Dana Kuebler Sept. 19, 2024

Sept. 19, 2024

Hello IRT, Just a quick update that IRT session #5 recordings are available here<https://community.icann.org/pages/viewpage.action?pageId=367362107>, transcripts will be posted shortly. If you missed this session, please take time to review the available recordings in advance of our next meeting. IRT members shared useful insights and experiences in response to many clarifying questions on IRT final report recommendations 8-21. We look forward to beginning discussion on topics of concerns on the IRT final report recommendations 1-7 Thursday, 3 October 2024. All the best, Dana

1 0

IRT Task 20240919a: Provide Comments of Concerns for Rec 8 - 14. Due: 23 Sep 2024
by Dennis Chang Sept. 19, 2024

Sept. 19, 2024

Dear IRT, Thank you for a great discussion today. We are so fortunate to have the wealth of experiences in our IRT to support us. IRT Task: 20240919a: Due: 23 Sep 2024 As mentioned at the meeting, the next IRT Task is to complete your comments of concerns on the Recommendations 8 - 14 in the IRT Commentable Version of the PPSAI PDP Final Report (2015)<https://docs.google.com/document/d/1nS5WTk0p79XRT0CcCzByAyH_xn6KMDgElc5F6QS…> Concerns should be focused on the implementability of the recommendation. Is the recommendation implementable as written? Please continue to follow the comment guidelines<https://docs.google.com/document/d/1o3RxFY1jApyiKvwbtuon2MnKUk38ZBkBIv0IceK…> and prepare for a discussion with the IRT. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

ICANN81 PPSAI IRT Session
by Noor Zannat Sept. 18, 2024

Sept. 18, 2024

Dear IRT members, We are excited to announce that we will be having an IRT meeting on Thursday, 14 November, 09:00-10:00 local time at ICANN81 in Istanbul, Turkey! The link to register is below: https://meetings.icann.org/en/meetings/icann81/ Zoom link: TBD Room: TBD We look forward to seeing you there! Regards, Noor Zannat

1 0

PPSAI IRT Meeting Reminder: This Thursday 15:30-17:00 UTC, 8:30-10:00 am PDT
by Noor Zannat Sept. 16, 2024

Sept. 16, 2024

Dear PPSAI IRT, This is a reminder for our upcoming IRT Meeting scheduled for 90 minutes this Thursday. Please let us know if you are an IRT member and have not received invitation details including zoom access. Meeting Agenda details will be posted here<https://community.icann.org/display/IRT/IRT+Meetings> shortly. Thank you for your support, we look forward to seeing you. Regards, Noor Zannat

1 0

IRT Task 20240725c: Comments of Concern for Recommendations 1 to 7. Due: 16 Sep 2024
by Dennis Chang Sept. 12, 2024

Sept. 12, 2024

Dear IRT, Thank you for posting the clarifying questions on the Commentable Final Reports. I see that questions have stopped, and all are replied to. At the next IRT meeting on 19 September 2024, we will review all Clarifying Questions we’ve not reviewed at prior the meetings. With that, we’d like to shift your focus to the Comments of Concerns. This task was originally for all Recommendations, but we’ve decided to make them 3 tasks to focus on sections at a time. First will be Recommendations 1 to 7. 2nd 8 to 14 and 3rd 15 to 21. This task is the first of the three due by 16 Sep 2024. 20240725c Provide comments of concerns for Recommendations 1 to 7 in IRT Commentable Version of the PPSAI PDP Final Report (2015)<https://docs.google.com/document/d/1nS5WTk0p79XRT0CcCzByAyH_xn6KMDgElc5F6QS…> Concerns should be focused on implementability of the recommendation. Is the recommendation implementable as written? 16Aug2024 16 Sep 2024 I’ll be issuing two more tasks following this one as we make progress. You are welcomed to work in advance to make your Comments of Concern for all recommendations of course but please complete your comments for the recommendations 1 to 7 first. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

2 1

IRT session on 5 Sep 2024 cancelled.
by Dennis Chang Aug. 30, 2024

Aug. 30, 2024

Dear IRT, I am cancelling the IRT session next week on Thursday. I am finding that we require much more preparation work on our side to make the IRT meeting productive thanks to the wealth of inputs and information the IRT has provided already. I also noted that with many being on holidays, more time to catch up with the group. We’ll continue our progress via shared documents and emails till the next meeting on 19 September 2024. Thanks to Steve and Jothan for your email discussion on the interaction of the PPSAI and other consensus policies. This is a large complex implementation task that we will have to do. Thanks for putting your thoughts down now for us. I’ll be working on our work plan and will share it when ready and then send out task assignments with due dates soon after. In the meanwhile, for those that missed the first 4 sessions, please review the recordings and transcripts posted on the IRT wiki. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

2 1

Recordings & Transcript now available for IRT Meeting #4: 22 August 2024.
by Dana Kuebler Aug. 27, 2024

Aug. 27, 2024

Hello IRT, Just a quick update that IRT session #4 recordings and transcript are available here<https://community.icann.org/pages/viewpage.action?pageId=367362107> To keep us all aligned if you missed this session, please take time to review the available recordings in advance of our next meeting. We covered important on our collaborative work, revised our project workplan and discussed clarifying questions related to IRT final report recommendations 1- 8. We look forward to continued review of clarifying questions on the IRT final report in our upcoming session 5 Sept 2024. All the best, Dana

1 0

Worksheet re interaction between P/P policy and other ICANN policies
by Steve Crocker Aug. 23, 2024

Aug. 23, 2024

Folks, I have been asking about the relationship between P/P services and ICANN's existing (and emerging) policies regarding disclosure. Accrediting P/P services without specifying what policies apply to them seems incomplete to me. Attached is a worksheet attempting to lay out the various combinations of a Registrant -- Alex Brown, 123 Crown St, Dove, FL 32000 -- registering a domain in fourteen(1) different scenarios. The worksheet then has space for specifying what the response would be for each of three different classes of Requestors (Law Enforcement, Intellectual Property attorneys, Security Practitioners). Questions: 1. Is this exercise clear? 2. Are these the right distinctions? 3. If the answers to the above are yes, can we fill in the blanks? Thanks, Steve sender

2 3

IRT session #4 recording available.. 22 August 2024 session.
by Dennis Chang Aug. 23, 2024

Aug. 23, 2024

Dear IRT, The video and audio recordings from yesterdays’ IRT session are now available on the IRT wiki: https://community.icann.org/x/O4DlFQ We were going to inform you of these recording next week when Transcript is available too, but I received a request. From those PPSAI enthusiasts for the recordings today for their weekend enjoyment. I think you find the session engaging and informative. This session is packed with interesting and useful knowledge sharing. I am grateful to the IRT for setting a culture of openness and collaboration as we ask our questions and learn together. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

PPSAI IRT Meeting Reminder: This Thursday 15:30-17:00 UTC, 8:30-10:00 am PDT
by Noor Zannat Aug. 20, 2024

Aug. 20, 2024

Dear PPSAI IRT, This is a reminder for our upcoming IRT Meeting scheduled for 90 minutes this Thursday. Please let us know if you are an IRT member and have not received invitation details including zoom access. Meeting Agenda details will be posted here<https://community.icann.org/display/IRT/IRT+Meetings> shortly. Thank you for your support, we look forward to seeing you. Regards, Noor Zannat

3 2

Recordings & Transcript is available for IRT Meeting #3: 08 August 2024.
by Dana Kuebler Aug. 13, 2024

Aug. 13, 2024

Hello IRT, Just a quick update that IRT session #3 recordings and transcript are available here<https://community.icann.org/pages/viewpage.action?pageId=363921460> To keep us all aligned if you missed this session, please take time to review the available recordings in advance of our next meeting. We covered important information about the process and approach to our collaborative work, revised our project workplan and discussed clarifying questions related to IRT final report recommendations 1-6. We look forward to continued review of clarifying questions on the IRT final report in our upcoming session 22 August 2024. All the best, Dana

1 0

ICANN81 Registration Open; PPSAI IRT session plan.
by Dennis Chang Aug. 12, 2024

Aug. 12, 2024

Dear IRT, Registration is now open for the ICANN81 Annual General Meeting, which will be held both virtually and in-person in Istanbul, Türkiye from 9-14 November 2024. https://www.icann.org/ You may have noted in the IRT Workplan that we added this information. 10 14-Nov-2024 ICANN81 IRT session (tentatively ) scheduled for Thursday, 14 November 06:00 UTC, We have received inquiries from the IRT about the ICANN81 IRT Session and your need to plan early. Thing may change and we’ll keep you updated as we learn more. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Note of Gratitude; Task #20240725c due date extend; Request to PDP WG members.
by Dennis Chang Aug. 10, 2024

Aug. 10, 2024

Dear IRT, Thanks to those that supported the IRT Call this week. I thought it was productive and informative. Thanks again to those that provided timely input on the process for me to refine the session process. As I mentioned at the meeting , we will continue our work to review the Clarifying Questions at the next meeting. This week we had planned for Rec 1 to Rec 7 but we were out of time after Rec 6. It was the first Q&A meeting, and we did spend some quality time on come together on how we work too. I expect the next session to go faster but we do have new questions that came in so we may have to go back or at least reserve some time in the future to catch those up. We’ll review them to see how we could do this efficiently. As for the IRT Task 20240725c to provide comments for Concerns on the policy recommendations, I will be extending that due date. I’ll consult my team to select a new date for that task as we are also preparing a new IRT Tasks that will need to be completed before that task. More on this later. In the meanwhile, I remind those members from the PPSAI PDP WG and Transfer PDP WG to reply to the questions that were put to you. This will help us to move efficiently. -- Gratefully Yours, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Re: IRT Task 20240725b: Provide clarifying questions in IRT Commentable Version of the PPSAI PDP Final Report (2015) Due 02 Aug 2024
by Dennis Chang Aug. 8, 2024

Aug. 8, 2024

Dear IRT, Thank you for completing the assignment to provide comments of Clarifying Questions. As you’ll see, there were many. https://docs.google.com/document/d/1nS5WTk0p79XRT0CcCzByAyH_xn6KMDgElc5F6QS… We are now going through and providing answers to your questions. As I’ve asked, if you see questions, you know the answers to, please don’t hesitate to add your reply. Let’s work as a team to address every question using our collective knowledge and experience. You’ll note that some questions are directed to PPSAI PDP WG; some to the on-going Transfer Policy WG, and there is one to RrSG member. In these cases, we will defer to the members of those groups. We’ll make note of them as we go to get your attention too. Some questions were coded as Question & Concern. In this case, we’ll try to answer the question part and leave the concern discussion for later. The questions should be about the policy recommendation language in the Final Report. Other questions should be addressed at later time. The goal of this task is to gain common understanding of the policy recommendations provided in the Final Report; as written. Thank you all for your contirbution. Dennis Chang From: Dennis Chang via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Reply-To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org> Date: Thursday, July 25, 2024 at 2:22 PM To: Dennis Chang via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Cc: Dennis Chang <dennis.chang(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] IRT Task 20240725b: Provide clarifying questions in IRT Commentable Version of the PPSAI PDP Final Report (2015) Due 02 Aug 2024 Dear IRT, This is the 2nd task we discussed at the IRT meeting today. Per the instruction given at the meeting and the guideline on working with the Cementable document, ask your Clarifying questions to better understand a recommendation” focused on Section 1.3.1 where you’ll find Recommendations 1 to 21. Please make your comments to start with “1. Question …” to separate from the notable concerns you’ll be asked to make with another task with a later due date. 20240725b Provide clarifying questions in IRT Cementable Version of the PPSAI PDP Final Report (2015) [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1nS5WTk0p79XR…> 02Aug2024 You’ll note are already comments made at the meeting by the IRT members. When you find questions that you have answers to, please feel free to add as a reply. You may also add follow-up questions as a reply as you have them. We expect that this document will get busy soon, and we plan to collect, sort, and track all comments in the IRT workbook. We’ll let you know how that gets done later. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

7 12

Reminder: The next PPSAI IRT meeting has been scheduled for Thursday, 8th August 2024
by Dana Kuebler Aug. 6, 2024

Aug. 6, 2024

Dear IRT, This is a friendly reminder for our scheduled meeting PPSAI IRT session is Thursday, 08 Aug – 15:30 UTC, 8:30am PDT, 11:30am EDT Please let us know if you are a participating IRT member and have not received invitation details. All the best, Dana Kuebler-Webler Dana.kuebler(a)icann.org

1 0

Reminder. IRT Task 20240725a Due on 01 Aug 2024. Review IRT Final Report Comment Guidelines prior to making comments
by Dennis Chang July 29, 2024

July 29, 2024

Dear IRT, This is a reminder to complete this task. I typically do not send reminders for tasks completion but thought I’ll do it here and give you an opportunity to reply with questions. If you’ve missed our meetings, please listen to both IRT session 1 and 2 recordings to get the context for this simple task. https://community.icann.org/display/IRT/IRT+Meetings After that, if you still have questions about this task or the context, you can always reach out. There are 48 IRT members. This is a large team and I’d appreciate your support in keeping all of us together as one team on the same page. Please feel free to reach out to me privately or reply to all. Thanks, Dennis Chang From: Dennis Chang via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Reply-To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org> Date: Thursday, July 25, 2024 at 1:25 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Cc: Dennis Chang <dennis.chang(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] IRT Task 20240725a: Review IRT Final Report Comment Guidelines prior to making comments Dear IRT, Thank you for supporting our call today. As we discussed, I’ll be sending out 3 IRT Tasks today. Please complete this task first and look for other emails to follow. 20240725a Review IRT Final Report Comment Guidelines [drive.google.com]<https://urldefense.com/v3/__https:/drive.google.com/file/d/1OxQmITYCFGxKrGG…> prior to making comments 01Aug2024 For those that missed the meeting, there will be an email notification sent to you when the recording is available on the IRT Wiki for you to catch up with us. This is a complex and involved policy implementation and I appreciate everyone support and patience as we are building the stable ground for all of us to operation from. There will be many more communications following. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Re: [Ext] Administrative Comment/Question
by Dennis Chang July 26, 2024

July 26, 2024

Hello Michael, 1. Thanks for catching the URL error in the workbook. * I just fixed it and it should work now. 2. On your request for Google Doc assistance, I’ll ask those on my team to reach out to you directly. * If others on the IRT would like assistance, we could conduct a special training session too. 3. ICANN org will log all comments and track them to resolution using a sheet in the IRT workbook. * I mentioned this briefly yesterday and more instructions on this will come to IRT when we have it set up. Good to see you using the IRT tools well already and thanks for support! Thanks, Dennis Chang From: "michael palage.com" <michael(a)palage.com> Date: Friday, July 26, 2024 at 8:39 AM To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org> Cc: Dennis Chang <dennis.chang(a)icann.org> Subject: [Ext] Administrative Comment/Question Hello Dennis, I have a question and a comment. First, my comment. The link to the IRT membership URL in the Google Doc tab “IRT Members” Cell B3 needs to be updated to the new URL on the Confluence site, https://community.icann.org/pages/viewpage.action?pageId=62395753 Second, my question. I would appreciate any Google Doc assistance on how to view comments that have been resolved? There was a comment that Steve had made, which was listed as “resolved” earlier this morning. However, when I checked back later in the morning I was unable to view it or find it. Can ICANN Org please explain how comments will be “resolved” and what ability there is to capture these comments should they accidentally be resolved/deleted by another group member? I think this is an important question to answer before we invest a lot of time marking up the document. Thanks in advance. Best regards, Michael

1 0

IRT Task 20240725c: Provide comments of concerns of the PPSAI PDP Final Report (2015) Due: 16Aug2024
by Dennis Chang July 26, 2024

July 26, 2024

Dear IRT, This is the 3rd Task we discuss at our meeting today. 20240725c Provide comments of concerns in in IRT Cemmentable Version of the PPSAI PDP Final Report (2015)<https://docs.google.com/document/d/1nS5WTk0p79XRT0CcCzByAyH_xn6KMDgElc5F6QS…> 16Aug2024 Please note the due that that comes after the two tasks I sent out earlier. This is by design to ensure that the IRT work on Clarifying Questions get done before we begin discussing concerns. Please focus your comment on the 21 recommendations presented in section 1.3.1 if you could. Precede each comment with “2. Concern …” to note that your comment is to be addressed after we answer the questions about the recommendation. Again, I invite the IRT members to reply to the comments to facilitate our discussion later. Per our work plan in the IRT workbook, session #4 on 22 August 2024 is when we plan to discuss these concerns as a team. Reminder: The IRT Work Plan and IRT Task List are always available to the IRT members (IRT members only) to reference and track. IRT Workbook: https://docs.google.com/spreadsheets/d/1rqfRaG1yL8HU48u0_3rIHkREoWN0Psr0rT_… As we make progress, we’ll assign more tasks that has more to do with the implementation design but for now, let’s come together to build a common understanding of the policy recommendations language. Thank you for your support and collaboration. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

2 1

Zoom Recording Available: IRT Session #2: 25 July 2024
by Dana Kuebler July 26, 2024

July 26, 2024

Dear IRT, Today’s zoom recorded session is now available on the wiki IRT Meetings Page<https://community.icann.org/pages/viewpage.action?pageId=362315806>. Please look for another email once the session transcript becomes available. All the best, Dana Kuebler-Weber

1 0

IRT Task 20240725a: Review IRT Final Report Comment Guidelines prior to making comments
by Dennis Chang July 25, 2024

July 25, 2024

Dear IRT, Thank you for supporting our call today. As we discussed, I’ll be sending out 3 IRT Tasks today. Please complete this task first and look for other emails to follow. 20240725a Review IRT Final Report Comment Guidelines<https://drive.google.com/file/d/1OxQmITYCFGxKrGGpLFS0VwmDnSQ6xDoS/view?usp=…> prior to making comments 01Aug2024 For those that missed the meeting, there will be an email notification sent to you when the recording is available on the IRT Wiki for you to catch up with us. This is a complex and involved policy implementation and I appreciate everyone support and patience as we are building the stable ground for all of us to operation from. There will be many more communications following. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

2 1

IRT Task 20240725b: Provide clarifying questions in IRT Commentable Version of the PPSAI PDP Final Report (2015) Due 02 Aug 2024
by Dennis Chang July 25, 2024

July 25, 2024

Dear IRT, This is the 2nd task we discussed at the IRT meeting today. Per the instruction given at the meeting and the guideline on working with the Cementable document, ask your Clarifying questions to better understand a recommendation” focused on Section 1.3.1 where you’ll find Recommendations 1 to 21. Please make your comments to start with “1. Question …” to separate from the notable concerns you’ll be asked to make with another task with a later due date. 20240725b Provide clarifying questions in IRT Cementable Version of the PPSAI PDP Final Report (2015)<https://docs.google.com/document/d/1nS5WTk0p79XRT0CcCzByAyH_xn6KMDgElc5F6QS…> 02Aug2024 You’ll note are already comments made at the meeting by the IRT members. When you find questions that you have answers to, please feel free to add as a reply. You may also add follow-up questions as a reply as you have them. We expect that this document will get busy soon, and we plan to collect, sort, and track all comments in the IRT workbook. We’ll let you know how that gets done later. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Background Information - Follow Up
by michael palage.com July 25, 2024

July 25, 2024

Hello Dennis, I am writing regarding my request on today's call to have equal time should the RrSG be permitted time to present on current Privacy Proxy services in the marketplace. First, I want to address your concern about limiting our work to ICANN's narrow mandate. There have been several ICANN community events in which the issue of registrant verification has been discussed. See for example ICANN79 ccNSO Tech Day, eID panel discussion, https://icann79.sched.com/event/1a1DU/tech-day-3-of-4; ICANN79 ALAC Plenary - Building Trust on the Internet through Registrant Verification, https://icann79.sched.com/event/1a1DH/at-large-plenary-session-2-building-t… registrant-verification; and the recent ICANN Contracting Party Summit session entitled NIS 2.0 and Registrant Verification, https://cpsummit2024.sched.com/event/1c1fQ/nis2registrant-verification Also, excluding these factual data points on what is currently feasible within the domain name marketplace appears to be inconsistent with ICANN Org's public statements. In connection with ICANN Org's response to the US CIRCIA Notice of Proposed Rule Making, ICANN Org made the following statement: The multistakeholder system also allows for the development and implementation of global policies. Global policies enable the Internet to remain a single, unified and interoperable platform. By contrast, regulation by local, national or regional governmental bodies risks fragmenting the Internet and creating conflicting obligations for Internet stakeholders. Regulation by one jurisdiction incentivizes other jurisdictions to intervene with their own policy objectives. See https://www.regulations.gov/comment/CISA-2022-0010-0437 If this IRT group wants to explicitly exclude market-based solutions currently available within the broader domain name marketplace, we should properly document this decision so that national governments in those markets will be free to act based on ICANN's inaction. I am copying Elena Plexida and Veni Markovski on this email as I believe this goes to the heart of some of the current WSIS+20 and GDC discussions taking place regarding the ongoing evolution and vibrancy of the ICANN multistakeholder model. I would also like to reshare the link I posted in the Zoom chat regarding the NIS 2.0 implementation guidance comment that I submitted to the Commission today regarding the broader DNS supply chain ecosystem, see https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/1… Privacy and Proxy providers are key players in the broader DNS ecosystem that ICANN currently has no contractual oversight. NIS 2.0 Article 6 (22) defines privacy and proxy providers as entities "providing domain name registration services" for purposes of Article 28. Therefore "[t]he relative complexity of the DNS registration supply chain described above (registry, registrar, reseller, registrant, hosts and other DNS providers) provides many opportunities for malicious actors" as described in the OECD whitepaper on DNS security is even more complex when you add privacy and proxy providers. Hopefully, this email helps clear up why I believe having ALL the available facts before the IRT is critical to our success. Best regards, Michael

1 0

P/P services vs Accuracy and Disclosure rules for registrars
by Steve Crocker July 24, 2024

July 24, 2024

Dennis, Thanks for your note. This working group is the restart of the IRT process for the Privacy and Proxy Services Accreditation policy. Quite a bit of time has passed since that policy was passed. There were some serious issues with the policy when it was adopted, and the situation has become worse. Accordingly, I am raising some questions about where we're going. This is a first draft of what I expect will become a more complete memo intended for wider distribution. It feels appropriate to share these thoughts first within this working group. Privacy and proxy services are intended to protect the identity of and restrict access to registrants. The fact that they have become widely used is a strong indication that registrants feel the need for such protection. (And, I think it needs to be said, their widespread use is also due in part to active sales efforts. People are spending a noticeable amount of money on these services, so this is an important source of revenue.) *Privacy Services* Let me address Privacy services first. When a registrant uses a Privacy service, the name of the registrant is provided to the registrar, but the registrant's address, email and phone number are not. Instead, the address, email and phone number of the Privacy service is provided to the registrar. If the registrant makes those data elements available to a requestor, the requestor will be able to contact Privacy service. The requestor will also know the name of the registrant and may be able to find other ways to contact the registrant. The troubling aspect of a Privacy service is the requestor has no explicit way of knowing whether the address, email and phone number are associated with the registrant or with a Privacy service. The intent of the Privacy and Proxy Service Accreditation policy is to make it clear to requestors that the data they are receiving is for a Privacy service. From my point of view, overloading the registrant's address, email and phone number fields with the Privacy service's data elements is unnecessarily confusing. *A simpler and more straightforward approach is to add a correspondence address, email and/or phone number to the registration data.* Of course, in order for this to accomplish the intended purpose, the registrant's address, email and phone number would NOT be easily available. And that involves the rules for disclosure of non-public data. More on this below. *Proxy service vs NIS2 and GDPR* A Proxy service differs from a Privacy service by hiding all data about the registrant. The registrant has no data about the actual registrant. Or, to be more precise, the registrant sees the Proxy service as the actual registrant, and the term that's often used to refer to the Proxy service's client is the "beneficial registrant." Today, Proxy service providers operate outside the ICANN contractual structure. With the exception of formal judicial processes, e.g. a government agent serving a warrant or subpoena, there is no way to compel a Proxy service to disclose the identity and other data about the beneficial registrant. The intent of the Privacy and Proxy Accreditation policy is to require Privacy and Proxy services to: - register with ICANN, - agree to an accreditation process, - conform with whatever rules are adopted later regarding collecting accurate data, and - conform to whatever rules are adopted later regarding disclosing that data. Meanwhile, ICANN is very, very, very slowly developing rules regarding the accuracy of the registration data and the disclosure of that data to appropriate requestors. ICANN has spent an inordinate amount of time wrestling with the GDPR. The sequence from SSAD to RDRS has been wasteful and ineffective. NIS2 is going to require accurate data, and we have not yet begun to take that requirement into account. The question that seems obvious to me is how these two sets of rules will interact. For example : - If registrants achieve greater protection using a Proxy service than without, does that mean the protection provided by registrars is insufficient? - The other side of that same question relates to disclosure. If a requestor has a legitimate need for registration data, but the data in its database is only the name of the Proxy service, doesn't that undermine the concept of providing registration to appropriate requestors for legitimate purposes? There are other questions related to the creation of a new bureaucracy that deserve attention, but I think those questions should come after we have a sensible understanding of how the overall system is supposed to work. *Whither the PPSAI working group?* The PPSAI working is focused on implementing an accreditation process for Privacy and Proxy services. What's missing in my view is clarity as to the purpose of this accreditation and clarity as to whether accrediting P/P Services will accomplish the purpose. In brief, we don't have a policy that is fit for purpose. ============================================= As I said at the top, this is a first draft. I invite responses, and I am particularly interested in others who wish to join the effort to make sense of this effort. Thanks, Steve sender

5 5

IRT Session #2: Agenda and preparation for 25 July Session
by Dennis Chang July 23, 2024

July 23, 2024

Dear PPSAI IRT, I look forward to our meeting on Thursday 25 July at 15:30 UTC for 90 minutes. Recurring calendar invitations with the zoom meeting details have been emailed to all current IRT members. Please reach out in advance of the meeting to Dana Kuebler<mailto:dana.kuebler@icann.org> dana.kuebler(a)icann.org<mailto:dana.kuebler@icann.org> or Noor Zannat<mailto:noor.zannat@icann.org> noor.zannat(a)icann.org<mailto:noor.zannat@icann.org> if you are an IRT member and did not receive session invitation details or are unable to access the IRT Team Google Drive<https://drive.google.com/drive/folders/0AOaxo18QlKY6Uk9PVA>. note: If your statement of interest (SOI) is incomplete or you wish to be an observer, you will not receive meeting invitations or access to the IRT working documents. We hope you have had some time to review the Board approved PPSAI Final Report<https://gnso.icann.org/sites/default/files/filefield_48305/ppsai-final-07de…> and identify any questions for further discussion with the IRT. This was an IRT Task issued on 13 June 2024. 20240613b Read PPSAI Final Report<https://gnso.icann.org/sites/default/files/filefield_48305/ppsai-final-07de…> and identify any questions for the IRT 20240710 I realized that many of you joined the IRT as recently as last week and are still working on this task. Please complete before our meeting this Thursday since we will be discussing the Final Report at our meeting. We maintain the IRT Meeting Information on the IRT Wiki: Meeting Agenda and Recording. Please check this link to confirm your access to the meeting agenda > Agenda<https://community.icann.org/pages/viewpage.action?pageId=362315806> Agenda Welcome & verify team access Orientation to IRT materials (IRT Team Drive) Collaborative review of final report section 1.3.1 Summary of the WG’s Final consensus recommendations <https://docs.google.com/document/d/1nS5WTk0p79XRT0CcCzByAyH_xn6KMDgElc5F6QS…> (pages 5-18) and Overview of IRT comment instructions AOB Next steps/tasks Session Target Objectives: 1. Verify member access to shared collaboration space and communications 2. Establish methods and tools to capture IRT questions and concerns on the 21 recommendations 3. Working session for IRT members to make comments and conduct discussion. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Re: PPSAI IRT meeting scheduling plan
by Dennis Chang July 22, 2024

July 22, 2024

Hi Luc, I just saw the meeting invitation hit my inbox. Could you confirm you received it too? Thanks, Dennis Chang From: Luc SEUFER via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Reply-To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl(a)icann.org> Date: Monday, July 22, 2024 at 8:10 AM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Cc: Luc SEUFER <lseufer(a)namespace.com> Subject: [Gdd-gnso-ppsai-impl] Re: PPSAI IRT meeting scheduling plan Hi Dennis et alia, Was the meeting invite sent already, and I missed it? Thanks, Luc From: Dennis Chang via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Date: Thursday, 18 July 2024 at 01:19 To: gdd-gnso-ppsai-impl(a)icann.org <gdd-gnso-ppsai-impl(a)icann.org> Cc: Dennis Chang <dennis.chang(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] PPSAI IRT meeting scheduling plan Dear PPSAI IRT, Thank you for responding to the recent request for availability. Our meetings will be scheduled for 90 minutes beginning on Thursday 25 July 15:30-17:00 UTC. Look for meeting call information details in a separate email. You will soon be receiving meeting invites for recurring meetings every other Thursday until ICANN81. We are reserving the time space in case we need to meet; however, meetings may be shortened or canceled if there is nothing to discuss at that time. At this time, we plan to hold an in-person meeting at ICANN81, but we are still coordinating the details internally. We will notify you as soon as we have a tentative time. Note: Meeting invitations are for IRT Members and should not be forwarded to observers or non-IRT members. Please also note that IRT membership is open, and anyone can join at any time. Please look for another email to remind you of your tasks to be prepared for the meeting. We are grateful for your participation and look forward to our next meeting. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org/> One World – One Internet

5 4

PPSAI IRT meeting scheduling plan
by Dennis Chang July 22, 2024

July 22, 2024

Dear PPSAI IRT, Thank you for responding to the recent request for availability. Our meetings will be scheduled for 90 minutes beginning on Thursday 25 July 15:30-17:00 UTC. Look for meeting call information details in a separate email. You will soon be receiving meeting invites for recurring meetings every other Thursday until ICANN81. We are reserving the time space in case we need to meet; however, meetings may be shortened or canceled if there is nothing to discuss at that time. At this time, we plan to hold an in-person meeting at ICANN81, but we are still coordinating the details internally. We will notify you as soon as we have a tentative time. Note: Meeting invitations are for IRT Members and should not be forwarded to observers or non-IRT members. Please also note that IRT membership is open, and anyone can join at any time. Please look for another email to remind you of your tasks to be prepared for the meeting. We are grateful for your participation and look forward to our next meeting. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

2 1

Scheduling Poll for IRT Meeting #2
by Noor Zannat July 12, 2024

July 12, 2024

Hello IRT members, Please complete the scheduling poll below for our next meeting by EOD Monday, July 15th. https://doodle.com/meeting/participate/id/dwRQZwmb Thanks, Noor

2 1

**No IRT meeting on 11 July**
by Leon Grundmann July 9, 2024

July 9, 2024

Dear PPSAI IRT Members, Several of you have reached out to ICANN staff inquiring about IRT meeting scheduling. As Dennis noted in his 28 June message, we had intended to hold our next meeting on 11 July 2024 but with many new members joining and unavailability of key team members, we decided to postpone to the following week tentatively. Please note that there is no meeting planned for the 11 July. We will be sending out a scheduling poll this week to this list, and you will receive emails and reminders for those meetings. Please also feel free to reach out offline with any additional questions. Best regards, Leon Grundmann

4 3

Re: IRT Task 20240613c: Read ICANN org Implementation Analysis of PDP Recommendations and identify questions for the IRT
by Noor Zannat July 8, 2024

July 8, 2024

Hello IRT Members, Both "Draft 2018 Policy Language on PPSAI" and the "Draft 2018 Privacy and Proxy Service Provider Accreditation Program Applicant Guide" are now available in the IRT drive in the folder titled Previous IRT Materials (link below) https://drive.google.com/drive/folders/1nqytlS8mdMS8HfpHqbJMdYC0EwESGOmD Regards, Noor From: rcarney--- via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Monday, July 1, 2024 at 3:52 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Cc: "rcarney(a)godaddy.com" <rcarney(a)godaddy.com> Subject: [Gdd-gnso-ppsai-impl] Re: IRT Task 20240613c: Read ICANN org Implementation Analysis of PDP Recommendations and identify questions for the IRT Good Afternoon, Could I get access to the "Draft 2018 Policy Language on PPSAI" and the "Draft 2018 Privacy and Proxy Service Provider Accreditation Program Applicant Guide" documents that are referenced in the analysis, I am receiving an access error? Thanks Roger ________________________________ From: Dennis Chang via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl(a)icann.org> Sent: Friday, June 28, 2024 4:31 PM To: gdd-gnso-ppsai-impl(a)icann.org <gdd-gnso-ppsai-impl(a)icann.org> Cc: Dennis Chang <dennis.chang(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] IRT Task 20240613c: Read ICANN org Implementation Analysis of PDP Recommendations and identify questions for the IRT Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Dear IRT, Please review the ICANN org Implementation Analysis of PDP Recommendation report and identify questions for the IRT. This is the report that was presented to the GNSO Council in ICANN79 San Juan in preparation for resuming the implementation work. ICANN org has done the preliminary work to review all recommendations and provide our findings here for IRT review. 20240613c Read ICANN org Implementation Analysis of PDP Recommendations [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> and identify questions for the IRT 20240724 -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org/> One World – One Internet

2 1

IRT Task 20240613c: Read ICANN org Implementation Analysis of PDP Recommendations and identify questions for the IRT
by Dennis Chang July 5, 2024

July 5, 2024

Dear IRT, Please review the ICANN org Implementation Analysis of PDP Recommendation report and identify questions for the IRT. This is the report that was presented to the GNSO Council in ICANN79 San Juan in preparation for resuming the implementation work. ICANN org has done the preliminary work to review all recommendations and provide our findings here for IRT review. 20240613c Read ICANN org Implementation Analysis of PDP Recommendations<https://gnso.icann.org/sites/default/files/policy/2024/presentation/ppsai-r…> and identify questions for the IRT 20240724 -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

5 4

Welcome to PPSAI IRT
by Dennis Chang June 28, 2024

June 28, 2024

Dear PPSAI IRT, Welcome to the PPSAI IRT and thank you for volunteering to support our policy implementation project. For those that missed the kick-off meeting at ICANN81 in Kigali, please begin by viewing the recording of the orientation session<https://icann.zoom.us/rec/play/iuLwo7ppNqnG8t35sBzoP6p3DoIIMkeoj3yKn_EjP9jn…>. As you’ll note, we are fortunate to have members from the original IRT (2016 IRT) as well as the members from the PDP WG that authored the report. We are also joined by members knowledgeable about the current offering and services for the privacy proxy to advise our work. The IRT member list is maintained in the IRT wiki<https://community.icann.org/display/IRT> If you are receiving this email via the IRT email, you should already have access to the IRT workspaces by now. If you need logistical support, please contact Dana Kuebler<mailto:dana.kuebler@icann.org>(Project Manager, dana.kuebler(a)icann.org<mailto:dana.kuebler@icann.org>) or Noor Zannat<mailto:noor.zannat@icann.org>(Project Coordinator, noor.zannat(a)icann.org<mailto:noor.zannat@icann.org>) After you get oriented, there are IRT tasks assignments to be completed. All assignments will be issued by emails task by task and also maintained as a list in the IRT Workbook<https://docs.google.com/spreadsheets/d/16YamTTAvkixhh0xOhfy9RQVZ05IIkuBT1o2…>. Look for separate emails following this one for task assignment. Now that the IRT email is available to use, you may choose to ask questions and conduct discussion. As much as possible, I’d like to get our work done via emails asynchronously and reserve our meeting time for topics best suited for live discussions. Our next meeting time and date will be set and announced after we conduct a brief survey to find the optimum timeslot. Please reply promptly to the survey so that we can lock on the date and time. We had intended to hold our meeting on 11 July 2024 but with many new members joining and unavailability of key team members, we decided to postpone to the following week tentatively. . The next IRT meeting will be the sharing of observations of the PPSAI Final Report that has been assigned to you (Task 20240613b) We’ve allocated the full 90-minute for this one agenda. This being our first discussion with many new to PPSAI, an open discussion of the policy recommendations in the final report will serve us well to ensure that we all have a good understanding of the recommendations language. For the subsequent IRT meetings, you’ll find a draft work plan in the IRT workbook<https://docs.google.com/spreadsheets/d/16YamTTAvkixhh0xOhfy9RQVZ05IIkuBT1o2…> subject to change based on how we see the IRT work pace. Thank you for your support and we look forward to working together for a successful project. -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

8 8

IRT Task 20240613b: Read PPSAI Final Report. Due: 20240710
by Dennis Chang June 28, 2024

June 28, 2024

Dear IRT, Please read the PPSAI Final Report and prepare for a discussion with the IRT. Are there points of confusion or varying interpretation of the recommendation language? Let’s begin with an open discussion and resolve differences in understanding of the PDP Recommendations for our implementation. We’d like to get the IRT work started as soon as IRT is ready. Hence, please initiate the IRT discussion on the IRT email list whenever you are ready and not wait till the next IRT meeting.. Please be specific about the language you are referring to by quoting the exact language with the section and page numbers for us to see the context surrounding the recommendation. IRT Task 20240613b: Read PPSAI Final Report<https://gnso.icann.org/sites/default/files/filefield_48305/ppsai-final-07de…> and identify any questions for the IRT Due: 20240710 -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Meeting schedule & question
by Sarah Wyld June 28, 2024

June 28, 2024

Hello Dennis and team, I wanted to check in about the upcoming PPSAI IRT meeting, has it been scheduled? I recall that we were talking about July 11, but I didn't see an invite?/ / The RrSG PPSAI IRT members have been reviewing the Final Report and considering our input for the various recs. Where do you want our feedback, is it that we should be prepared to discuss at the meeting? Thanks, -- *Sarah Wyld, CIPP/E* Policy & Privacy Manager Pronouns: she/they swyld(a)tucows.com

2 1

Informal Gathering at ICANN78 for Privacy/Proxy Policy Implementation
by Dennis Chang Oct. 6, 2023

Oct. 6, 2023

Dear Privacy Proxy IRT members, I am writing to you to see if we could get together at ICANN78 for an informal conversation regarding Privacy Proxy Policy Implementation. As you may recall, the implementation work in progress on the PPSAI recommendations<https://www.icann.org/en/board-activities-and-meetings/materials/approved-r…> was paused in September 2019 due to overlapping issues being considered in expedited policy work. ICANN org has been looking at when and how this work can be resumed and has identified some key questions and options for proceeding. We thought it would be helpful to get some feedback on current thinking, to help with our planning, taking advantage of ICANN78. To be clear, this is not a reconvening of the IRT nor a commitment to volunteer for future work. Rather, this is an informal discussion on what has changed, and how to weigh the options that are available to us now. I am thinking of a 45-minute session where we can discuss what was done, why, and what has changed since then. We could also potentially open discussion for new implementation approach options that may be available to us now. Since this is an informal gathering and not a closed meeting for IRT, please let me know of others who would be interested and helpful in this conversation. Please reply to me off list and we will set up a time and space. -- Kind Regards, Dennis S. Chang - dennis.chang(a)icann.org GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

PPSAI IRT Member Bandwith Assessment Request
by Cyrus Jamnejad June 3, 2021

June 3, 2021

Dear PPSAI IRT Members, I hope this message finds you well. As you know, the implementation of the PPSAI IRT has been on hold since 2019 as we have awaited clarity on a variety of EPDP-related activities. With the completion of certain portions of EPDP work, the GNSO Council has asked ICANN org to gauge our ability, and the IRT members’ capacity, to undertake additional work on this effort. The GNSO Council as well as ICANN org will need to assess bandwidth and priorities to determine what can be supported. We are writing at the Council’s request to gauge your interest and ability to re-engage in work related to this IRT should this be determined to proceed. We ask that if you would wish to continue participation in future work, please respond (off list to me at cyrus.jamnejad(a)icann.org<mailto:cyrus.jamnejad@icann.org>) affirmatively to indicate your interest by Wednesday, 09 June. We will provide this numerical data to the GNSO Council to inform its deliberations. Please contact me with any questions, and thank you for your time and attention to this matter. Best, Cyrus Jamnejad GDD Accounts Manager Internet Corporation for Assigned Names and Numbers (ICANN) Skype: cyrus.jamnejad.icann Telephone: +1 310 578 8635 www.icann.org<http://www.icann.org/>

1 0

PPSAI IRT Status Update
by Cyrus Jamnejad Sept. 23, 2019

Sept. 23, 2019

Dear Members of the PPSAI IRT, I hope this message finds you well. As some of you may know, Amy Bivins has moved to a different department within ICANN org and will no longer be directly supporting the PPSAI IRT. As such, and knowing that it has been a while since our last communication, I’d like to provide a brief status update to this list. For those of you who do not know me, I am a Services Manager on the newly-branded gTLD Accounts and Services team within the GDD. I was previously a Registrar Services & Engagement manager for the North American and Latin American/Caribbean ICANN regions, and I have been supporting the PP Implementation work from the staff side for the past 2+ years. When we last spoke in November of last year, ICANN org indicated that due to the ongoing work of the EPDP on the Temporary Specification for gTLD registration data and the need for uniformity of approach toward issues raised by the European Union General Data Protection Regulation (GDPR), the PPSAI IRT would slow its work. This approach was for the purpose of monitoring the recommendations of the EPDP for potential impacts to ICANN org’s implementation of the Privacy & Proxy service provider accreditation program, and was intended to focus and conserve limited ICANN org and community resources for the work of the EPDP. The general sentiment from the IRT members in response to this status update was that proceeding with any work outside of these issues was not a prudent use of resources at the time. In March of this year, ICANN org notified the GNSO Council<https://www.icann.org/en/system/files/correspondence/namazi-to-drazek-et-al…> of the intention to formally pause the implementation work for PPSAI. In late April, the Council considered this approach and determined that deference to ICANN org and the IRT<https://www.icann.org/en/system/files/correspondence/drazek-et-al-to-namazi…> was prudent. On 5 September, ICANN org confirmed in response<https://www.icann.org/en/system/files/correspondence/namazi-to-drazek-et-al…> that the PPSAI Implementation would be put on hold pending the implementation of the forthcoming EPDP Phase 2 recommendations. We understand that reactions within the community and the IRT to this plan remain mixed, but believe this is the best path forward when considering all relevant factors. We appreciate all of the time and effort spent by the IRT to date. ICANN org remains committed to implementing the policy once the EPDP Phase 2 work is complete and any impacts to the Privacy & Proxy service provider accreditation program can be appropriately assessed and accounted for in our implementation plan. Best Regards, Cyrus Jamnejad gTLD Accounts & Services Manager Internet Corporation for Assigned Names and Numbers (ICANN) Skype: cyrus.jamnejad.icann Telephone: +1 310 578 8635 www.icann.org<http://www.icann.org/>

2 1

Re: [Gdd-gnso-ppsai-impl] PP IRT: Next Steps
by Michele Neylon - Blacknight Nov. 2, 2018

Nov. 2, 2018

Amy While I’m sure many of us appreciate the update I’m not sure that scheduling meetings for updates is of much value. The email updates should be enough unless there is something very substantive to be discussed. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Friday 2 November 2018 at 14:16 To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] PP IRT: Next Steps Dear Colleagues, Following up on our discussions at ICANN63, I want to provide some additional context around next steps for the Privacy/Proxy IRT. As noted during several discussions in Barcelona, ICANN org believes that there is currently a significant amount of uncertainty around interpreting the data processing requirements of GDPR related to this type of proposed accreditation agreement. Until we gain enough certainty to address this, we don’t believe it’s prudent to move forward at our prior pace. Areas of uncertainty include, but are not limited to: * The purposes of gTLD registration data, including contact data that is protected by a privacy or proxy service; * The lawful bases for processing of gTLD registration data, including: * Collection; * Retention; * Transfer of data to third parties, including data escrow agents and third-party requestors; * Allocation of controller/processor obligations w/r/t gTLD registration data; and * The expected solution for third-party access to non-public registration data (and whether this might be applied to PP customer data, which would impact implementation of the PP accreditation program). Many of these issues will be considered in the Expedited PDP on the Temporary Specification for gTLD Registration Data and continued ICANN org discussions with the European Data Protection Board. As a result, we believe we should continue to monitor this work as we proceed to finalize other, unrelated aspects of the proposed program requirements. IRT Action Items During meetings in Barcelona, many IRT members had questions about the IRT’s status. If you have additional questions or comments about next steps, please send them to the list. In addition, if you have suggestions for items that you believe should be discussed now, please also send those to the list. I’ll continue to update you via the list on work being done on this project by ICANN org. We plan to schedule meetings periodically (every 4-6 weeks) to ensure that you have the opportunity to raise questions or issues you would like to discuss with the group. During these meetings, we can also discuss progress made in other parallel efforts, and potential impacts that these efforts may have on proposed PP accreditation requirements. Regards, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

4 3

Re: [Gdd-gnso-ppsai-impl] PP IRT: Next Steps
by Chris Pelling Nov. 2, 2018

Nov. 2, 2018

Totally agree with Michele Sent by Chris on the move. -------- Original message --------From: Michele Neylon - Blacknight <michele(a)blacknight.com> Date: 02/11/2018 14:25 (GMT+00:00) To: gdd-gnso-ppsai-impl(a)icann.org Subject: Re: [Gdd-gnso-ppsai-impl] PP IRT: Next Steps Amy While I’m sure many of us appreciate the update I’m not sure that scheduling meetings for updates is of much value. The email updates should be enough unless there is something very substantive to be discussed. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Friday 2 November 2018 at 14:16 To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] PP IRT: Next Steps Dear Colleagues, Following up on our discussions at ICANN63, I want to provide some additional context around next steps for the Privacy/Proxy IRT. As noted during several discussions in Barcelona, ICANN org believes that there is currently a significant amount of uncertainty around interpreting the data processing requirements of GDPR related to this type of proposed accreditation agreement. Until we gain enough certainty to address this, we don’t believe it’s prudent to move forward at our prior pace. Areas of uncertainty include, but are not limited to: The purposes of gTLD registration data, including contact data that is protected by a privacy or proxy service; The lawful bases for processing of gTLD registration data, including: Collection; Retention; Transfer of data to third parties, including data escrow agents and third-party requestors; Allocation of controller/processor obligations w/r/t gTLD registration data; and The expected solution for third-party access to non-public registration data (and whether this might be applied to PP customer data, which would impact implementation of the PP accreditation program). Many of these issues will be considered in the Expedited PDP on the Temporary Specification for gTLD Registration Data and continued ICANN org discussions with the European Data Protection Board. As a result, we believe we should continue to monitor this work as we proceed to finalize other, unrelated aspects of the proposed program requirements. IRT Action Items During meetings in Barcelona, many IRT members had questions about the IRT’s status. If you have additional questions or comments about next steps, please send them to the list. In addition, if you have suggestions for items that you believe should be discussed now, please also send those to the list. I’ll continue to update you via the list on work being done on this project by ICANN org. We plan to schedule meetings periodically (every 4-6 weeks) to ensure that you have the opportunity to raise questions or issues you would like to discuss with the group. During these meetings, we can also discuss progress made in other parallel efforts, and potential impacts that these efforts may have on proposed PP accreditation requirements. Regards, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org www.icann.org

1 0

PP IRT: Next Steps
by Amy Bivins Nov. 2, 2018

Nov. 2, 2018

Dear Colleagues, Following up on our discussions at ICANN63, I want to provide some additional context around next steps for the Privacy/Proxy IRT. As noted during several discussions in Barcelona, ICANN org believes that there is currently a significant amount of uncertainty around interpreting the data processing requirements of GDPR related to this type of proposed accreditation agreement. Until we gain enough certainty to address this, we don't believe it's prudent to move forward at our prior pace. Areas of uncertainty include, but are not limited to: * The purposes of gTLD registration data, including contact data that is protected by a privacy or proxy service; * The lawful bases for processing of gTLD registration data, including: * Collection; * Retention; * Transfer of data to third parties, including data escrow agents and third-party requestors; * Allocation of controller/processor obligations w/r/t gTLD registration data; and * The expected solution for third-party access to non-public registration data (and whether this might be applied to PP customer data, which would impact implementation of the PP accreditation program). Many of these issues will be considered in the Expedited PDP on the Temporary Specification for gTLD Registration Data and continued ICANN org discussions with the European Data Protection Board. As a result, we believe we should continue to monitor this work as we proceed to finalize other, unrelated aspects of the proposed program requirements. IRT Action Items During meetings in Barcelona, many IRT members had questions about the IRT's status. If you have additional questions or comments about next steps, please send them to the list. In addition, if you have suggestions for items that you believe should be discussed now, please also send those to the list. I'll continue to update you via the list on work being done on this project by ICANN org. We plan to schedule meetings periodically (every 4-6 weeks) to ensure that you have the opportunity to raise questions or issues you would like to discuss with the group. During these meetings, we can also discuss progress made in other parallel efforts, and potential impacts that these efforts may have on proposed PP accreditation requirements. Regards, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

PP IRT Working Meeting at ICANN 63--Updated With Phone Bridge Info
by Amy Bivins Oct. 19, 2018

Oct. 19, 2018

[Web Meeting] [Sponsor] Dear Colleagues, This is a calendar reminder for the Privacy and Proxy Service Provider Accreditation Program IRT meeting at ICANN 63. During this session, we will discuss the current project status and any feedback or questions you may have about next steps. For those attending in person, the session will be held in Room 133. Remote participation information is available at: https://63.schedule.icann.org/meetings/901773 Safe travels to all of you who will be attending ICANN63 in Barcelona. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org> __________________________________________________________________ You're Invited. You've been invited to a GlobalMeet® phone only meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me <https://go.conferencinghub.com/2z1fx> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://1-605-475-5618,*,,1350875547#<tel://1-605-475-5618,*,,1350875547> Phone Only Controls: https://go.conferencinghub.com/2z1fx Primary Access Number: 1-605-475-5618 Guest Passcode: 135 087 5547 Additional Access: USA 1-605-475-5618 USA 1-719-325-2630 Canada, Calgary +1 403 407 5780 Canada, Montreal +1 514 669 5909 Canada, Toronto +1 416 915 3615 Canada, Vancouver +1 604 205 5118 Argentina, Buenos Aires +54 (0) 11 5172 6019 Argentina (toll free) 0800 800 1250 Australia, Sydney +61 (0) 2 8017 6391 Australia, Melbourne +61 (0) 3 8687 0614 Australia, Brisbane +61 (0) 7 3015 0608 Australia (toll free) 1 800 720 493 Austria, Vienna +43 (0)1 928 2722 Austria (toll free) 0800 070 841 Bahrain, Manama +973 1650 0402 Bahrain (toll free) 8008 1214 Belarus (toll free) 8 820 0011 0353 Belgium, Brussels +32 (0) 2 400 1980 Belgium (toll free) 0800 39 268 Bosnia and Herzegovina +387 7031 1461 Brazil, Sao Paulo +55 11 4935 7122 Brazil, Rio de Janeiro +55 21 4560 0023 Brazil (toll free) 0800 887 0283 Bulgaria, Sofia +359 (0) 2 491 7244 Bulgaria (toll free) 00800 111 4944 Cambodia, Phnom Penh +855 23 962 579 Canada (toll free) 1 855 950 3706 Chile, Santiago +56 (0) 2 2666 0711 Chile (toll free) 800 914 858 China (national) +400 681 8104 China, Beijing +86 10 5667 0005 China, Shanghai +86 21 2039 7079 Colombia, Bogota +57 1 508 8112 Colombia (toll free) 1 800 518 9147 Costa Rica (toll free) 800 542 5331 Croatia (toll free) 0800 223 004 Cyprus (toll free) 800 97400 Czech Republic, Prague +420 225 986 505 Czech Republic (toll free) 800 701 236 Denmark, Copenhagen +45 32 71 16 70 Denmark (toll free) 80 70 35 78 Egypt (toll free) 0800 000 0401 Estonia, Tallinn +372 622 6519 Estonia (toll free) 800 011 1569 Fiji (toll free) 00800 3317 Finland, Helsinki +358 (0) 9 2310 1611 Finland (toll free) 0800 772 230 France, Paris +33 (0) 1 76 77 22 50 France (toll free) 0800 946 112 France (national) 0811 655 134 France (national) 0821 231 687 Georgia, Tbilisi +995 32 2 053 082 Germany, Frankfurt +49 (0) 69 5060 9515 Germany, Munich +49 (0) 89 24443 2900 Germany (national) 01801 001 378 Germany (toll free) 0800 588 9225 Greece, Athens +30 211 181 3815 Greece (toll free) 00800 128 811 Hong Kong +852 3018 9103 Hong Kong (toll free) 800 968 082 Hungary, Budapest +36 1 808 8134 Hungary (toll free) 068 001 9662 Iceland (toll free) 800 9841 India, Delhi +91 11 6310 0272 India, Mumbai +91 22 6310 0274 India, Chennai +91 44 6310 0227 India, Bangalore +91 80 6760 8747 India (toll free) 1800 3010 1564 Indonesia, Jakarta +62 21 2188 9079 Indonesia (toll free) 007 803 321 8120 Ireland, Dublin +353 (0) 1 246 5614 Ireland (national) 0818 270 287 Ireland (toll free) 1800 937 695 Ireland (national) 1890 907 722 Israel, Tel Aviv +972 (0)3 763 0384 Israel (toll free) 180 921 2890 Italy, Milan +39 02 3046 4837 Italy, Rome +39 06 4523 6635 Italy (toll free) 800 148 288 Japan, Tokyo +81 3 4560 1274 Japan, Osaka +81 6 4560 0303 Japan (mobile) 0120 270 611 Japan (toll free) 0120 286 011 Japan (national) 0570 005 744 Jordan (toll free) 0800 22156 Kazakhstan (toll free) 8800 333 7552 Kenya, Nairobi +254 (0)207 643 596 South Korea, Seoul +82 (0) 2 6007 0072 South Korea (toll free) 007 986 136 2233 Kuwait (national) +965 2206 3083 Latvia, Riga +371 6778 2598 Latvia (toll free) 8000 4374 Lithuania, Vilnius +370 5205 5239 Lithuania (toll free) 8800 31445 Luxembourg +352 2730 2276 Luxembourg (toll free) 800 28428 Macau (national) +853 6262 1674 Malaysia, Kuala Lumpur +60 (0) 3 7723 7140 Malaysia (toll free) 1 800 815 805 Mexico, Guadalajara +52 33 2101 0284 Mexico, Mexico City +52 55 7100 2163 Mexico, Monterrey +52 81 2188 0267 Mexico (toll free) 1 800 099 1104 Morocco, Casablanca +212 (0)520 480 128 Morocco (toll free) 0800 092 258 Netherlands, Amsterdam +31 (0) 20 716 8266 Netherlands (toll free) 0800 020 0593 New Zealand, Christchurch +64 (0) 3 974 2597 New Zealand, Wellington +64 (0) 4 909 4676 New Zealand, Auckland +64 (0) 9 929 1769 New Zealand (toll free) 0800 459 127 Nigeria, Lagos +234 1 277 5140 Norway, Oslo +47 2162 4054 Norway (toll free) 800 58459 Oman (toll free) 800 77269 Pakistan, Islamabad +92 5181 08874 Panama, Panama City +507 8 339 782 Panama (toll free) 00800 223 1430 Peru, Lima +51 (0) 1 700 9587 Peru (toll free) 0800 78125 Philippines, Manila +63 (0)2 395 3365 Philippines (toll free) 1800 111 017 51 Poland, Warsaw +48 22 295 3504 Poland (toll free) 00800 121 4340 Portugal, Lisbon +351 21 316 4041 Portugal (toll free) 800 784 434 Qatar (freephone) 00 800 100 499 Romania, Bucharest +40 (0) 21 529 3969 Romania (toll free) 0800 801 030 Russia, Moscow +7 495 213 0988 Russia (toll free) 8 800 500 9319 Saudi Arabia (toll free) 800 844 4963 Saudi Arabia (toll free) 800 850 0227 Serbia (toll free) 0800 190 698 Singapore +65 6654 9111 Singapore (toll free) 800 616 3175 Slovakia, Bratislava +421 (0)2 3321 5333 Slovakia (toll free) 0800 001 661 Slovenia, Ljubljana +386 1 600 1622 Slovenia (toll free) 0800 80994 South Africa, Johannesburg +27 (0)11 019 7087 South Africa (toll free) 0800 988 886 Spain, Madrid +34 91 114 6640 Spain, Barcelona +34 93 800 1935 Spain (toll free) 900 803 689 Sri Lanka, Sri Lanka +94 720 910 348 Sweden, Stockholm +46 (0) 8 5065 3944 Sweden (toll free) 0200 125 456 Switzerland, Geneva +41 (0) 22 595 4857 Switzerland, Zurich +41 (0) 44 580 7246 Switzerland (toll free) 0800 841 702 Taiwan, Taipei +886 (0) 2 2656 7213 Taiwan (toll free) 00 801 615 184 Thailand, Bangkok +66 (0) 2104 0767 Thailand (toll free) 1 800 012 172 Tunisia, Tunis +216 31 378 109 Turkey, Istanbul +90 212 375 50 13 Turkey (toll free) 00 800 448 828 358 Ukraine (toll free) 0800 500 732 UAE (toll free) 8000 3570 2638 UK (03) +44 (0)330 336 6010 UK (toll free) 0800 368 0950 UK (national) 0844 473 5003 UK (national) 0845 545 0040 USA /Canada (toll free) 1-855-747-8824 Uruguay (toll free) 0004 019 0561 Venezuela, Caracas +58 212 720 2342 Venezuela (toll free) 0800 102 9660 Vietnam, Hanoi +84 24 4458 3323 Vietnam, Ho Chi Minh +84 28 4458 1333 Vietnam (toll free) 1800 400 415 Questions? Go to GlobalMeet Support<http://community.globalmeet.com> © Premiere Global Services, Inc. and/or its affiliates | PGi

1 0

PP IRT Working Meeting at ICANN 63
by Amy Bivins Oct. 19, 2018

Oct. 19, 2018

Dear Colleagues, This is a calendar reminder for the Privacy and Proxy Service Provider Accreditation Program IRT meeting at ICANN 63. During this session, we will discuss the current project status and any feedback or questions you may have about next steps. Remote participation information is available at: https://63.schedule.icann.org/meetings/901773 If you will be attending the meeting remotely and would like to use a phone bridge, please let me know as soon as possible. Safe travels to all of you who will be attending ICANN63 in Barcelona. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 2

Update on PP IRT Status
by Amy Bivins Oct. 17, 2018

Oct. 17, 2018

Dear Colleagues, I hope you are well. I want to share a status update on the Privacy and Proxy Service Provider Accreditation Program implementation project. After much consideration, ICANN org believes that work toward implementation of the Privacy and Proxy Service Provider Accreditation Program should be slowed, pending the completion of work on the EPDP and related efforts, which are expected to provide greater clarity about third-party access to non-public registration data. ICANN org believes that we should slow our work toward final implementation of PP Accreditation Program requirements until the results of the EPDP are known. Proceeding to implementation of privacy/proxy at this stage may result in establishing requirements for third-party access to nonpublic registration data held by privacy and proxy service providers that would be inconsistent with the policies developed for registry operators and registrars in the EPDP. In the interim, ICANN org will continue work on unfinished items that are not directly related to data privacy issues in consultation with the IRT (e.g. final reviews of the accreditation program materials, consideration of data escrow-related arrangements for registrar affiliates, etc). I want to reiterate how much we appreciate your hard work on this IRT. I'll update you as I know more about how ICANN org plans to proceed on this project. If you would like to discuss further, I encourage you to attend our scheduled PP IRT working meeting at ICANN 63, on Wednesday, 24 October, at 1330 UTC, and/or reply to the list. At our session at ICANN63, we will discuss any questions or feedback you may have about the project's status. Remote participation for the session will be available here: https://63.schedule.icann.org/meetings/901773. I'll send you a separate calendar invite, as well. I look forward to seeing those of you who will be in Barcelona (and safe travels). Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

Canceled: PP IRT Standing Call Time
by Amy Bivins Oct. 5, 2018

Oct. 5, 2018

[Web Meeting] [Sponsor] Dear Colleagues, Please note that the standing call time for the Privacy and Proxy Service Provider Accreditation Program Implementation Review Team is now Thursdays at 1600 UTC. Individual occurrences will be canceled on weeks where a meeting will not be held. Adobe Connect: https://participate.icann.org/ppirt/ __________________________________________________________________ You're Invited. You've been invited to a GlobalMeet® phone only meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me <https://go.conferencinghub.com/2y4ql> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://1-605-475-5618,*,,1350875547#<tel://1-605-475-5618,*,,1350875547> Phone Only Controls: https://go.conferencinghub.com/2y4ql Primary Access Number: 1-605-475-5618 Guest Passcode: 135 087 5547 Additional Access: USA 1-605-475-5618 USA 1-719-325-2630 Canada, Calgary +1 403 407 5780 Canada, Montreal +1 514 669 5909 Canada, Toronto +1 416 915 3615 Canada, Vancouver +1 604 205 5118 Argentina, Buenos Aires +54 (0) 11 5172 6019 Argentina (toll free) 0800 800 1250 Australia, Sydney +61 (0) 2 8017 6391 Australia, Melbourne +61 (0) 3 8687 0614 Australia, Brisbane +61 (0) 7 3015 0608 Australia (toll free) 1 800 720 493 Austria, Vienna +43 (0)1 928 2722 Austria (toll free) 0800 070 841 Bahrain, Manama +973 1650 0402 Bahrain (toll free) 8008 1214 Belarus (toll free) 8 820 0011 0353 Belgium, Brussels +32 (0) 2 400 1980 Belgium (toll free) 0800 39 268 Bosnia and Herzegovina +387 7031 1461 Brazil, Sao Paulo +55 11 4935 7122 Brazil, Rio de Janeiro +55 21 4560 0023 Brazil (toll free) 0800 887 0283 Bulgaria, Sofia +359 (0) 2 491 7244 Bulgaria (toll free) 00800 111 4944 Cambodia, Phnom Penh +855 23 962 579 Canada (toll free) 1 855 950 3706 Chile, Santiago +56 (0) 2 2666 0711 Chile (toll free) 171 800 835 943 China (national) +400 681 8104 China, Beijing +86 10 5667 0005 China, Shanghai +86 21 2039 7079 Colombia, Bogota +57 1 508 8112 Colombia (toll free) 01 800 755 0043 Costa Rica (toll free) 800 542 5331 Croatia (toll free) 0800 223 004 Cyprus (toll free) 800 97400 Czech Republic, Prague +420 225 986 505 Czech Republic (toll free) 800 701 236 Denmark, Copenhagen +45 32 71 16 70 Denmark (toll free) 80 70 35 78 Egypt (toll free) 0800 000 0401 Estonia, Tallinn +372 622 6519 Estonia (toll free) 800 011 1569 Fiji (toll free) 00800 3317 Finland, Helsinki +358 (0) 9 2310 1611 Finland (toll free) 0800 772 230 France, Paris +33 (0) 1 76 77 22 50 France (toll free) 0800 946 112 France (national) 0811 655 134 France (national) 0821 231 687 Georgia, Tbilisi +995 32 2 053 082 Germany, Frankfurt +49 (0) 69 5060 9515 Germany, Munich +49 (0) 89 24443 2900 Germany (national) 01801 001 378 Germany (toll free) 0800 588 9225 Greece, Athens +30 211 181 3815 Greece (toll free) 00800 128 811 Hong Kong +852 3018 9103 Hong Kong (toll free) 800 968 082 Hungary, Budapest +36 1 808 8134 Hungary (toll free) 068 001 9662 Iceland (toll free) 800 9841 India, Delhi +91 11 6310 0272 India, Mumbai +91 22 6310 0274 India, Chennai +91 44 6310 0227 India, Bangalore +91 80 6760 8747 India (toll free) 1800 3010 1564 Indonesia, Jakarta +62 21 2188 9079 Indonesia (toll free) 007 803 321 8120 Ireland, Dublin +353 (0) 1 246 5614 Ireland (national) 0818 270 287 Ireland (toll free) 1800 937 695 Ireland (national) 1890 907 722 Israel, Tel Aviv +972 (0)3 763 0384 Israel (toll free) 180 921 2890 Italy, Milan +39 02 3046 4837 Italy, Rome +39 06 4523 6635 Italy (toll free) 800 148 288 Japan, Tokyo +81 3 4560 1274 Japan, Osaka +81 6 4560 0303 Japan (mobile) 0120 270 611 Japan (toll free) 0120 286 011 Japan (national) 0570 005 744 Jordan (toll free) 0800 22156 Kazakhstan (toll free) 8800 333 7552 Kenya, Nairobi +254 (0)207 643 596 South Korea, Seoul +82 (0) 2 6007 0072 South Korea (toll free) 007 986 136 2233 Kuwait (national) +965 2206 3083 Latvia, Riga +371 6778 2598 Latvia (toll free) 8000 4374 Lithuania, Vilnius +370 5205 5239 Lithuania (toll free) 8800 31445 Luxembourg +352 2730 2276 Luxembourg (toll free) 800 28428 Macau (national) +853 6262 1674 Malaysia, Kuala Lumpur +60 (0) 3 7723 7140 Malaysia (toll free) 1 800 815 805 Mexico, Guadalajara +52 33 4162 5891 Mexico, Mexico City +52 55 8421 0857 Mexico, Monterrey +52 81 4770 2472 Mexico (toll free) 01 800 283 3129 Morocco, Casablanca +212 (0)520 480 128 Morocco (toll free) 0800 092 258 Netherlands, Amsterdam +31 (0) 20 716 8266 Netherlands (toll free) 0800 020 0593 New Zealand, Christchurch +64 (0) 3 974 2597 New Zealand, Wellington +64 (0) 4 909 4676 New Zealand, Auckland +64 (0) 9 929 1769 New Zealand (toll free) 0800 459 127 Nigeria, Lagos +234 1 277 5140 Norway, Oslo +47 2162 4054 Norway (toll free) 800 58459 Oman (toll free) 800 77269 Pakistan, Islamabad +92 5181 08874 Panama, Panama City +507 8 339 782 Panama (toll free) 00800 223 1430 Peru, Lima +51 (0) 1 700 9587 Peru (toll free) 0800 78125 Philippines, Manila +63 (0)2 395 3365 Philippines (toll free) 1800 111 017 51 Poland, Warsaw +48 22 295 3504 Poland (toll free) 00800 121 4340 Portugal, Lisbon +351 21 316 4041 Portugal (toll free) 800 784 434 Qatar (freephone) 00 800 100 499 Romania, Bucharest +40 (0) 21 529 3969 Romania (toll free) 0800 801 030 Russia, Moscow +7 495 213 0988 Russia (toll free) 8 800 500 9319 Saudi Arabia (toll free) 800 844 4963 Saudi Arabia (toll free) 800 850 0227 Serbia (toll free) 0800 190 698 Singapore +65 6654 9111 Singapore (toll free) 800 616 3175 Slovakia, Bratislava +421 (0)2 3321 5333 Slovakia (toll free) 0800 001 661 Slovenia, Ljubljana +386 1 600 1622 Slovenia (toll free) 0800 80994 South Africa, Johannesburg +27 (0)11 019 7087 South Africa (toll free) 0800 988 886 Spain, Madrid +34 91 114 6640 Spain, Barcelona +34 93 800 1935 Spain (toll free) 900 803 689 Sri Lanka, Sri Lanka +94 720 910 348 Sweden, Stockholm +46 (0) 8 5065 3944 Sweden (toll free) 0200 125 456 Switzerland, Geneva +41 (0) 22 595 4857 Switzerland, Zurich +41 (0) 44 580 7246 Switzerland (toll free) 0800 841 702 Taiwan, Taipei +886 (0) 2 2656 7213 Taiwan (toll free) 00 801 615 184 Thailand, Bangkok +66 (0) 2104 0767 Thailand (toll free) 1 800 012 172 Tunisia, Tunis +216 31 378 109 Turkey, Istanbul +90 212 375 50 13 Turkey (toll free) 00 800 448 828 358 Ukraine (toll free) 0800 500 732 UAE (toll free) 8000 3570 2638 UK (03) +44 (0)330 336 6010 UK (toll free) 0800 368 0950 UK (national) 0844 473 5003 UK (national) 0845 545 0040 USA /Canada (toll free) 1-855-747-8824 Uruguay (toll free) 0004 019 0561 Venezuela, Caracas +58 212 720 2342 Venezuela (toll free) 0800 102 9660 Vietnam, Hanoi +84 24 4458 3323 Vietnam, Ho Chi Minh +84 28 4458 1333 Vietnam (toll free) 1800 9228 Questions? Go to GlobalMeet Support<http://community.globalmeet.com> © Premiere Global Services, Inc. and/or its affiliates | PGi

1 0

PP IRT Status Update, Plans for ICANN63
by Amy Bivins Oct. 5, 2018

Oct. 5, 2018

Dear Colleagues, I hope you are well! I have an update on the PP IRT's status. ICANN org is reviewing of all of the materials that ICANN and the IRT have been working on in preparation for public comment. As a reminder, we are planning to post the following items for public comment, once these are final (and following your final review of these documents): (a) the draft PPAA; (b) the draft PP Accreditation Policy document; (c) the draft PP De-Accreditation and Transition Procedure; (d) the PP Accreditation Program fees proposal; (e) the PP Service Provider Accreditation Applicant Guide; and (f) a list of any unresolved items and questions for community discussion. Our next meeting will be at ICANN63 (Weds, 24 Oct, 13:30 local time). We plan to distribute these materials to you prior to ICANN63 so that we can discuss any further feedback, comments, or questions you may have during our working meeting in Barcelona. I'll send you an invite for the ICANN63 session separately. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

Canceled: PP IRT Standing Call Time
by Amy Bivins Oct. 1, 2018

Oct. 1, 2018

[Web Meeting] [Sponsor] Dear Colleagues, Please note that the standing call time for the Privacy and Proxy Service Provider Accreditation Program Implementation Review Team is now Thursdays at 1600 UTC. Individual occurrences will be canceled on weeks where a meeting will not be held. Adobe Connect: https://participate.icann.org/ppirt/ __________________________________________________________________ You're Invited. You've been invited to a GlobalMeet® phone only meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me <https://go.conferencinghub.com/2y4ql> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://1-605-475-5618,*,,1350875547#<tel://1-605-475-5618,*,,1350875547> Phone Only Controls: https://go.conferencinghub.com/2y4ql Primary Access Number: 1-605-475-5618 Guest Passcode: 135 087 5547 Additional Access: USA 1-605-475-5618 USA 1-719-325-2630 Canada, Calgary +1 403 407 5780 Canada, Montreal +1 514 669 5909 Canada, Toronto +1 416 915 3615 Canada, Vancouver +1 604 205 5118 Argentina, Buenos Aires +54 (0) 11 5172 6019 Argentina (toll free) 0800 800 1250 Australia, Sydney +61 (0) 2 8017 6391 Australia, Melbourne +61 (0) 3 8687 0614 Australia, Brisbane +61 (0) 7 3015 0608 Australia (toll free) 1 800 720 493 Austria, Vienna +43 (0)1 928 2722 Austria (toll free) 0800 070 841 Bahrain, Manama +973 1650 0402 Bahrain (toll free) 8008 1214 Belarus (toll free) 8 820 0011 0353 Belgium, Brussels +32 (0) 2 400 1980 Belgium (toll free) 0800 39 268 Bosnia and Herzegovina +387 7031 1461 Brazil, Sao Paulo +55 11 4935 7122 Brazil, Rio de Janeiro +55 21 4560 0023 Brazil (toll free) 0800 887 0283 Bulgaria, Sofia +359 (0) 2 491 7244 Bulgaria (toll free) 00800 111 4944 Cambodia, Phnom Penh +855 23 962 579 Canada (toll free) 1 855 950 3706 Chile, Santiago +56 (0) 2 2666 0711 Chile (toll free) 171 800 835 943 China (national) +400 681 8104 China, Beijing +86 10 5667 0005 China, Shanghai +86 21 2039 7079 Colombia, Bogota +57 1 508 8112 Colombia (toll free) 01 800 755 0043 Costa Rica (toll free) 800 542 5331 Croatia (toll free) 0800 223 004 Cyprus (toll free) 800 97400 Czech Republic, Prague +420 225 986 505 Czech Republic (toll free) 800 701 236 Denmark, Copenhagen +45 32 71 16 70 Denmark (toll free) 80 70 35 78 Egypt (toll free) 0800 000 0401 Estonia, Tallinn +372 622 6519 Estonia (toll free) 800 011 1569 Fiji (toll free) 00800 3317 Finland, Helsinki +358 (0) 9 2310 1611 Finland (toll free) 0800 772 230 France, Paris +33 (0) 1 76 77 22 50 France (toll free) 0800 946 112 France (national) 0811 655 134 France (national) 0821 231 687 Georgia, Tbilisi +995 32 2 053 082 Germany, Frankfurt +49 (0) 69 5060 9515 Germany, Munich +49 (0) 89 24443 2900 Germany (national) 01801 001 378 Germany (toll free) 0800 588 9225 Greece, Athens +30 211 181 3815 Greece (toll free) 00800 128 811 Hong Kong +852 3018 9103 Hong Kong (toll free) 800 968 082 Hungary, Budapest +36 1 808 8134 Hungary (toll free) 068 001 9662 Iceland (toll free) 800 9841 India, Delhi +91 11 6310 0272 India, Mumbai +91 22 6310 0274 India, Chennai +91 44 6310 0227 India, Bangalore +91 80 6760 8747 India (toll free) 1800 3010 1564 Indonesia, Jakarta +62 21 2188 9079 Indonesia (toll free) 007 803 321 8120 Ireland, Dublin +353 (0) 1 246 5614 Ireland (national) 0818 270 287 Ireland (toll free) 1800 937 695 Ireland (national) 1890 907 722 Israel, Tel Aviv +972 (0)3 763 0384 Israel (toll free) 180 921 2890 Italy, Milan +39 02 3046 4837 Italy, Rome +39 06 4523 6635 Italy (toll free) 800 148 288 Japan, Tokyo +81 3 4560 1274 Japan, Osaka +81 6 4560 0303 Japan (mobile) 0120 270 611 Japan (toll free) 0120 286 011 Japan (national) 0570 005 744 Jordan (toll free) 0800 22156 Kazakhstan (toll free) 8800 333 7552 Kenya, Nairobi +254 (0)207 643 596 South Korea, Seoul +82 (0) 2 6007 0072 South Korea (toll free) 007 986 136 2233 Kuwait (national) +965 2206 3083 Latvia, Riga +371 6778 2598 Latvia (toll free) 8000 4374 Lithuania, Vilnius +370 5205 5239 Lithuania (toll free) 8800 31445 Luxembourg +352 2730 2276 Luxembourg (toll free) 800 28428 Macau (national) +853 6262 1674 Malaysia, Kuala Lumpur +60 (0) 3 7723 7140 Malaysia (toll free) 1 800 815 805 Mexico, Guadalajara +52 33 4162 5891 Mexico, Mexico City +52 55 8421 0857 Mexico, Monterrey +52 81 4770 2472 Mexico (toll free) 01 800 283 3129 Morocco, Casablanca +212 (0)520 480 128 Morocco (toll free) 0800 092 258 Netherlands, Amsterdam +31 (0) 20 716 8266 Netherlands (toll free) 0800 020 0593 New Zealand, Christchurch +64 (0) 3 974 2597 New Zealand, Wellington +64 (0) 4 909 4676 New Zealand, Auckland +64 (0) 9 929 1769 New Zealand (toll free) 0800 459 127 Nigeria, Lagos +234 1 277 5140 Norway, Oslo +47 2162 4054 Norway (toll free) 800 58459 Oman (toll free) 800 77269 Pakistan, Islamabad +92 5181 08874 Panama, Panama City +507 8 339 782 Panama (toll free) 00800 223 1430 Peru, Lima +51 (0) 1 700 9587 Peru (toll free) 0800 78125 Philippines, Manila +63 (0)2 395 3365 Philippines (toll free) 1800 111 017 51 Poland, Warsaw +48 22 295 3504 Poland (toll free) 00800 121 4340 Portugal, Lisbon +351 21 316 4041 Portugal (toll free) 800 784 434 Qatar (freephone) 00 800 100 499 Romania, Bucharest +40 (0) 21 529 3969 Romania (toll free) 0800 801 030 Russia, Moscow +7 495 213 0988 Russia (toll free) 8 800 500 9319 Saudi Arabia (toll free) 800 844 4963 Saudi Arabia (toll free) 800 850 0227 Serbia (toll free) 0800 190 698 Singapore +65 6654 9111 Singapore (toll free) 800 616 3175 Slovakia, Bratislava +421 (0)2 3321 5333 Slovakia (toll free) 0800 001 661 Slovenia, Ljubljana +386 1 600 1622 Slovenia (toll free) 0800 80994 South Africa, Johannesburg +27 (0)11 019 7087 South Africa (toll free) 0800 988 886 Spain, Madrid +34 91 114 6640 Spain, Barcelona +34 93 800 1935 Spain (toll free) 900 803 689 Sri Lanka, Sri Lanka +94 720 910 348 Sweden, Stockholm +46 (0) 8 5065 3944 Sweden (toll free) 0200 125 456 Switzerland, Geneva +41 (0) 22 595 4857 Switzerland, Zurich +41 (0) 44 580 7246 Switzerland (toll free) 0800 841 702 Taiwan, Taipei +886 (0) 2 2656 7213 Taiwan (toll free) 00 801 615 184 Thailand, Bangkok +66 (0) 2104 0767 Thailand (toll free) 1 800 012 172 Tunisia, Tunis +216 31 378 109 Turkey, Istanbul +90 212 375 50 13 Turkey (toll free) 00 800 448 828 358 Ukraine (toll free) 0800 500 732 UAE (toll free) 8000 3570 2638 UK (03) +44 (0)330 336 6010 UK (toll free) 0800 368 0950 UK (national) 0844 473 5003 UK (national) 0845 545 0040 USA /Canada (toll free) 1-855-747-8824 Uruguay (toll free) 0004 019 0561 Venezuela, Caracas +58 212 720 2342 Venezuela (toll free) 0800 102 9660 Vietnam, Hanoi +84 24 4458 3323 Vietnam, Ho Chi Minh +84 28 4458 1333 Vietnam (toll free) 1800 9228 Questions? Go to GlobalMeet Support<http://community.globalmeet.com> © Premiere Global Services, Inc. and/or its affiliates | PGi

1 0

No PP IRT Meeting This Week
by Amy Bivins Oct. 1, 2018

Oct. 1, 2018

Dear Colleagues, We will not have a PP IRT meeting this week. I'll distribute an update on the project status, timeline, and remaining deliverables as soon as possible. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

No PP IRT meeting this week
by Amy Bivins Sept. 25, 2018

Sept. 25, 2018

Dear Colleagues: Please note that there is no PP IRT meeting this week. ICANN org is actively evaluating your recent feedback on the data processing-related proposals. I'll update you on next steps as soon as possible. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 1

Re: [Gdd-gnso-ppsai-impl] No PP IRT meeting this week
by Sara Bockey Sept. 25, 2018

Sept. 25, 2018

Hi Amy, Thank you for the update. I note that the RrSG has a planning call next week, October 4, that conflicts with the PPSAI timeslot. If possible, it would be appreciated if we could push the next PPSAI IRT call out til the week of Oct 8. Thanks! Sara Sara Bockey GoDaddy | Senior Policy Manager +1 480-366-3616 sbockey(a)godaddy.com<mailto:sbockey@godaddy.com> This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments. From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Tuesday, September 25, 2018 at 10:05 AM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] No PP IRT meeting this week Dear Colleagues: Please note that there is no PP IRT meeting this week. ICANN org is actively evaluating your recent feedback on the data processing-related proposals. I’ll update you on next steps as soon as possible. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

Canceled: PP IRT Standing Call Time
by Amy Bivins Sept. 25, 2018

Sept. 25, 2018

[Web Meeting] [Sponsor] Dear Colleagues, Please note that the standing call time for the Privacy and Proxy Service Provider Accreditation Program Implementation Review Team is now Thursdays at 1600 UTC. Individual occurrences will be canceled on weeks where a meeting will not be held. Adobe Connect: https://participate.icann.org/ppirt/ __________________________________________________________________ You're Invited. You've been invited to a GlobalMeet® phone only meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me <https://go.conferencinghub.com/2y4ql> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://1-605-475-5618,*,,1350875547#<tel://1-605-475-5618,*,,1350875547> Phone Only Controls: https://go.conferencinghub.com/2y4ql Primary Access Number: 1-605-475-5618 Guest Passcode: 135 087 5547 Additional Access: USA 1-605-475-5618 USA 1-719-325-2630 Canada, Calgary +1 403 407 5780 Canada, Montreal +1 514 669 5909 Canada, Toronto +1 416 915 3615 Canada, Vancouver +1 604 205 5118 Argentina, Buenos Aires +54 (0) 11 5172 6019 Argentina (toll free) 0800 800 1250 Australia, Sydney +61 (0) 2 8017 6391 Australia, Melbourne +61 (0) 3 8687 0614 Australia, Brisbane +61 (0) 7 3015 0608 Australia (toll free) 1 800 720 493 Austria, Vienna +43 (0)1 928 2722 Austria (toll free) 0800 070 841 Bahrain, Manama +973 1650 0402 Bahrain (toll free) 8008 1214 Belarus (toll free) 8 820 0011 0353 Belgium, Brussels +32 (0) 2 400 1980 Belgium (toll free) 0800 39 268 Bosnia and Herzegovina +387 7031 1461 Brazil, Sao Paulo +55 11 4935 7122 Brazil, Rio de Janeiro +55 21 4560 0023 Brazil (toll free) 0800 887 0283 Bulgaria, Sofia +359 (0) 2 491 7244 Bulgaria (toll free) 00800 111 4944 Cambodia, Phnom Penh +855 23 962 579 Canada (toll free) 1 855 950 3706 Chile, Santiago +56 (0) 2 2666 0711 Chile (toll free) 171 800 835 943 China (national) +400 681 8104 China, Beijing +86 10 5667 0005 China, Shanghai +86 21 2039 7079 Colombia, Bogota +57 1 508 8112 Colombia (toll free) 01 800 755 0043 Costa Rica (toll free) 800 542 5331 Croatia (toll free) 0800 223 004 Cyprus (toll free) 800 97400 Czech Republic, Prague +420 225 986 505 Czech Republic (toll free) 800 701 236 Denmark, Copenhagen +45 32 71 16 70 Denmark (toll free) 80 70 35 78 Egypt (toll free) 0800 000 0401 Estonia, Tallinn +372 622 6519 Estonia (toll free) 800 011 1569 Fiji (toll free) 00800 3317 Finland, Helsinki +358 (0) 9 2310 1611 Finland (toll free) 0800 772 230 France, Paris +33 (0) 1 76 77 22 50 France (toll free) 0800 946 112 France (national) 0811 655 134 France (national) 0821 231 687 Georgia, Tbilisi +995 32 2 053 082 Germany, Frankfurt +49 (0) 69 5060 9515 Germany, Munich +49 (0) 89 24443 2900 Germany (national) 01801 001 378 Germany (toll free) 0800 588 9225 Greece, Athens +30 211 181 3815 Greece (toll free) 00800 128 811 Hong Kong +852 3018 9103 Hong Kong (toll free) 800 968 082 Hungary, Budapest +36 1 808 8134 Hungary (toll free) 068 001 9662 Iceland (toll free) 800 9841 India, Delhi +91 11 6310 0272 India, Mumbai +91 22 6310 0274 India, Chennai +91 44 6310 0227 India, Bangalore +91 80 6760 8747 India (toll free) 1800 3010 1564 Indonesia, Jakarta +62 21 2188 9079 Indonesia (toll free) 007 803 321 8120 Ireland, Dublin +353 (0) 1 246 5614 Ireland (national) 0818 270 287 Ireland (toll free) 1800 937 695 Ireland (national) 1890 907 722 Israel, Tel Aviv +972 (0)3 763 0384 Israel (toll free) 180 921 2890 Italy, Milan +39 02 3046 4837 Italy, Rome +39 06 4523 6635 Italy (toll free) 800 148 288 Japan, Tokyo +81 3 4560 1274 Japan, Osaka +81 6 4560 0303 Japan (mobile) 0120 270 611 Japan (toll free) 0120 286 011 Japan (national) 0570 005 744 Jordan (toll free) 0800 22156 Kazakhstan (toll free) 8800 333 7552 Kenya, Nairobi +254 (0)207 643 596 South Korea, Seoul +82 (0) 2 6007 0072 South Korea (toll free) 007 986 136 2233 Kuwait (national) +965 2206 3083 Latvia, Riga +371 6778 2598 Latvia (toll free) 8000 4374 Lithuania, Vilnius +370 5205 5239 Lithuania (toll free) 8800 31445 Luxembourg +352 2730 2276 Luxembourg (toll free) 800 28428 Macau (national) +853 6262 1674 Malaysia, Kuala Lumpur +60 (0) 3 7723 7140 Malaysia (toll free) 1 800 815 805 Mexico, Guadalajara +52 33 4162 5891 Mexico, Mexico City +52 55 8421 0857 Mexico, Monterrey +52 81 4770 2472 Mexico (toll free) 01 800 283 3129 Morocco, Casablanca +212 (0)520 480 128 Morocco (toll free) 0800 092 258 Netherlands, Amsterdam +31 (0) 20 716 8266 Netherlands (toll free) 0800 020 0593 New Zealand, Christchurch +64 (0) 3 974 2597 New Zealand, Wellington +64 (0) 4 909 4676 New Zealand, Auckland +64 (0) 9 929 1769 New Zealand (toll free) 0800 459 127 Nigeria, Lagos +234 1 277 5140 Norway, Oslo +47 2162 4054 Norway (toll free) 800 58459 Oman (toll free) 800 77269 Pakistan, Islamabad +92 5181 08874 Panama, Panama City +507 8 339 782 Panama (toll free) 00800 223 1430 Peru, Lima +51 (0) 1 700 9587 Peru (toll free) 0800 78125 Philippines, Manila +63 (0)2 395 3365 Philippines (toll free) 1800 111 017 51 Poland, Warsaw +48 22 295 3504 Poland (toll free) 00800 121 4340 Portugal, Lisbon +351 21 316 4041 Portugal (toll free) 800 784 434 Qatar (freephone) 00 800 100 499 Romania, Bucharest +40 (0) 21 529 3969 Romania (toll free) 0800 801 030 Russia, Moscow +7 495 213 0988 Russia (toll free) 8 800 500 9319 Saudi Arabia (toll free) 800 844 4963 Saudi Arabia (toll free) 800 850 0227 Serbia (toll free) 0800 190 698 Singapore +65 6654 9111 Singapore (toll free) 800 616 3175 Slovakia, Bratislava +421 (0)2 3321 5333 Slovakia (toll free) 0800 001 661 Slovenia, Ljubljana +386 1 600 1622 Slovenia (toll free) 0800 80994 South Africa, Johannesburg +27 (0)11 019 7087 South Africa (toll free) 0800 988 886 Spain, Madrid +34 91 114 6640 Spain, Barcelona +34 93 800 1935 Spain (toll free) 900 803 689 Sri Lanka, Sri Lanka +94 720 910 348 Sweden, Stockholm +46 (0) 8 5065 3944 Sweden (toll free) 0200 125 456 Switzerland, Geneva +41 (0) 22 595 4857 Switzerland, Zurich +41 (0) 44 580 7246 Switzerland (toll free) 0800 841 702 Taiwan, Taipei +886 (0) 2 2656 7213 Taiwan (toll free) 00 801 615 184 Thailand, Bangkok +66 (0) 2104 0767 Thailand (toll free) 1 800 012 172 Tunisia, Tunis +216 31 378 109 Turkey, Istanbul +90 212 375 50 13 Turkey (toll free) 00 800 448 828 358 Ukraine (toll free) 0800 500 732 UAE (toll free) 8000 3570 2638 UK (03) +44 (0)330 336 6010 UK (toll free) 0800 368 0950 UK (national) 0844 473 5003 UK (national) 0845 545 0040 USA /Canada (toll free) 1-855-747-8824 Uruguay (toll free) 0004 019 0561 Venezuela, Caracas +58 212 720 2342 Venezuela (toll free) 0800 102 9660 Vietnam, Hanoi +84 24 4458 3323 Vietnam, Ho Chi Minh +84 28 4458 1333 Vietnam (toll free) 1800 9228 Questions? Go to GlobalMeet Support<http://community.globalmeet.com> © Premiere Global Services, Inc. and/or its affiliates | PGi

1 0

No PP IRT Meeting This Week
by Amy Bivins Sept. 18, 2018

Sept. 18, 2018

Dear Colleagues, We will not have a PP IRT meeting this week, as it seems the issues that are currently being discuss can be addressed on the list. If you have any further feedback on these items, please sent it to the list no later than the end of this week. I should be able to update you on next steps related to your feedback on the data processing-related provisions in the PPAA within the next week. Once we have an approved course of action for these provisions, we will be able to update the contract relatively quickly and move ahead to finalize all of the materials for public comment. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 1

Canceled: PP IRT Standing Call Time
by Amy Bivins Sept. 18, 2018

Sept. 18, 2018

[Web Meeting] [Sponsor] Dear Colleagues, Please note that the standing call time for the Privacy and Proxy Service Provider Accreditation Program Implementation Review Team is now Thursdays at 1600 UTC. Individual occurrences will be canceled on weeks where a meeting will not be held. Adobe Connect: https://participate.icann.org/ppirt/ __________________________________________________________________ You're Invited. You've been invited to a GlobalMeet® phone only meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me <https://go.conferencinghub.com/2y4ql> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://1-605-475-5618,*,,1350875547#<tel://1-605-475-5618,*,,1350875547> Phone Only Controls: https://go.conferencinghub.com/2y4ql Primary Access Number: 1-605-475-5618 Guest Passcode: 135 087 5547 Additional Access: USA 1-605-475-5618 USA 1-719-325-2630 Canada, Calgary +1 403 407 5780 Canada, Montreal +1 514 669 5909 Canada, Toronto +1 416 915 3615 Canada, Vancouver +1 604 205 5118 Argentina, Buenos Aires +54 (0) 11 5172 6019 Argentina (toll free) 0800 800 1250 Australia, Sydney +61 (0) 2 8017 6391 Australia, Melbourne +61 (0) 3 8687 0614 Australia, Brisbane +61 (0) 7 3015 0608 Australia (toll free) 1 800 720 493 Austria, Vienna +43 (0)1 928 2722 Austria (toll free) 0800 070 841 Bahrain, Manama +973 1650 0402 Bahrain (toll free) 8008 1214 Belarus (toll free) 8 820 0011 0353 Belgium, Brussels +32 (0) 2 400 1980 Belgium (toll free) 0800 39 268 Bosnia and Herzegovina +387 7031 1461 Brazil, Sao Paulo +55 11 4935 7122 Brazil, Rio de Janeiro +55 21 4560 0023 Brazil (toll free) 0800 887 0283 Bulgaria, Sofia +359 (0) 2 491 7244 Bulgaria (toll free) 00800 111 4944 Cambodia, Phnom Penh +855 23 962 579 Canada (toll free) 1 855 950 3706 Chile, Santiago +56 (0) 2 2666 0711 Chile (toll free) 171 800 835 943 China (national) +400 681 8104 China, Beijing +86 10 5667 0005 China, Shanghai +86 21 2039 7079 Colombia, Bogota +57 1 508 8112 Colombia (toll free) 01 800 755 0043 Costa Rica (toll free) 800 542 5331 Croatia (toll free) 0800 223 004 Cyprus (toll free) 800 97400 Czech Republic, Prague +420 225 986 505 Czech Republic (toll free) 800 701 236 Denmark, Copenhagen +45 32 71 16 70 Denmark (toll free) 80 70 35 78 Egypt (toll free) 0800 000 0401 Estonia, Tallinn +372 622 6519 Estonia (toll free) 800 011 1569 Fiji (toll free) 00800 3317 Finland, Helsinki +358 (0) 9 2310 1611 Finland (toll free) 0800 772 230 France, Paris +33 (0) 1 76 77 22 50 France (toll free) 0800 946 112 France (national) 0811 655 134 France (national) 0821 231 687 Georgia, Tbilisi +995 32 2 053 082 Germany, Frankfurt +49 (0) 69 5060 9515 Germany, Munich +49 (0) 89 24443 2900 Germany (national) 01801 001 378 Germany (toll free) 0800 588 9225 Greece, Athens +30 211 181 3815 Greece (toll free) 00800 128 811 Hong Kong +852 3018 9103 Hong Kong (toll free) 800 968 082 Hungary, Budapest +36 1 808 8134 Hungary (toll free) 068 001 9662 Iceland (toll free) 800 9841 India, Delhi +91 11 6310 0272 India, Mumbai +91 22 6310 0274 India, Chennai +91 44 6310 0227 India, Bangalore +91 80 6760 8747 India (toll free) 1800 3010 1564 Indonesia, Jakarta +62 21 2188 9079 Indonesia (toll free) 007 803 321 8120 Ireland, Dublin +353 (0) 1 246 5614 Ireland (national) 0818 270 287 Ireland (toll free) 1800 937 695 Ireland (national) 1890 907 722 Israel, Tel Aviv +972 (0)3 763 0384 Israel (toll free) 180 921 2890 Italy, Milan +39 02 3046 4837 Italy, Rome +39 06 4523 6635 Italy (toll free) 800 148 288 Japan, Tokyo +81 3 4560 1274 Japan, Osaka +81 6 4560 0303 Japan (mobile) 0120 270 611 Japan (toll free) 0120 286 011 Japan (national) 0570 005 744 Jordan (toll free) 0800 22156 Kazakhstan (toll free) 8800 333 7552 Kenya, Nairobi +254 (0)207 643 596 South Korea, Seoul +82 (0) 2 6007 0072 South Korea (toll free) 007 986 136 2233 Kuwait (national) +965 2206 3083 Latvia, Riga +371 6778 2598 Latvia (toll free) 8000 4374 Lithuania, Vilnius +370 5205 5239 Lithuania (toll free) 8800 31445 Luxembourg +352 2730 2276 Luxembourg (toll free) 800 28428 Macau (national) +853 6262 1674 Malaysia, Kuala Lumpur +60 (0) 3 7723 7140 Malaysia (toll free) 1 800 815 805 Mexico, Guadalajara +52 33 4162 5891 Mexico, Mexico City +52 55 8421 0857 Mexico, Monterrey +52 81 4770 2472 Mexico (toll free) 01 800 283 3129 Morocco, Casablanca +212 (0)520 480 128 Morocco (toll free) 0800 092 258 Netherlands, Amsterdam +31 (0) 20 716 8266 Netherlands (toll free) 0800 020 0593 New Zealand, Christchurch +64 (0) 3 974 2597 New Zealand, Wellington +64 (0) 4 909 4676 New Zealand, Auckland +64 (0) 9 929 1769 New Zealand (toll free) 0800 459 127 Nigeria, Lagos +234 1 277 5140 Norway, Oslo +47 2162 4054 Norway (toll free) 800 58459 Oman (toll free) 800 77269 Pakistan, Islamabad +92 5181 08874 Panama, Panama City +507 8 339 782 Panama (toll free) 00800 223 1430 Peru, Lima +51 (0) 1 700 9587 Peru (toll free) 0800 78125 Philippines, Manila +63 (0)2 395 3365 Philippines (toll free) 1800 111 017 51 Poland, Warsaw +48 22 295 3504 Poland (toll free) 00800 121 4340 Portugal, Lisbon +351 21 316 4041 Portugal (toll free) 800 784 434 Qatar (freephone) 00 800 100 499 Romania, Bucharest +40 (0) 21 529 3969 Romania (toll free) 0800 801 030 Russia, Moscow +7 495 213 0988 Russia (toll free) 8 800 500 9319 Saudi Arabia (toll free) 800 844 4963 Saudi Arabia (toll free) 800 850 0227 Serbia (toll free) 0800 190 698 Singapore +65 6654 9111 Singapore (toll free) 800 616 3175 Slovakia, Bratislava +421 (0)2 3321 5333 Slovakia (toll free) 0800 001 661 Slovenia, Ljubljana +386 1 600 1622 Slovenia (toll free) 0800 80994 South Africa, Johannesburg +27 (0)11 019 7087 South Africa (toll free) 0800 988 886 Spain, Madrid +34 91 114 6640 Spain, Barcelona +34 93 800 1935 Spain (toll free) 900 803 689 Sri Lanka, Sri Lanka +94 720 910 348 Sweden, Stockholm +46 (0) 8 5065 3944 Sweden (toll free) 0200 125 456 Switzerland, Geneva +41 (0) 22 595 4857 Switzerland, Zurich +41 (0) 44 580 7246 Switzerland (toll free) 0800 841 702 Taiwan, Taipei +886 (0) 2 2656 7213 Taiwan (toll free) 00 801 615 184 Thailand, Bangkok +66 (0) 2104 0767 Thailand (toll free) 1 800 012 172 Tunisia, Tunis +216 31 378 109 Turkey, Istanbul +90 212 375 50 13 Turkey (toll free) 00 800 448 828 358 Ukraine (toll free) 0800 500 732 UAE (toll free) 8000 3570 2638 UK (03) +44 (0)330 336 6010 UK (toll free) 0800 368 0950 UK (national) 0844 473 5003 UK (national) 0845 545 0040 USA /Canada (toll free) 1-855-747-8824 Uruguay (toll free) 0004 019 0561 Venezuela, Caracas +58 212 720 2342 Venezuela (toll free) 0800 102 9660 Vietnam, Hanoi +84 24 4458 3323 Vietnam, Ho Chi Minh +84 28 4458 1333 Vietnam (toll free) 1800 9228 Questions? Go to GlobalMeet Support<http://community.globalmeet.com> © Premiere Global Services, Inc. and/or its affiliates | PGi

1 0

Re: [Gdd-gnso-ppsai-impl] PP IRT Action Items This Week --- specification 4
by Metalitz, Steven Sept. 18, 2018

Sept. 18, 2018

PPIRTers, Two points regarding specification 4, the Intellectual Property Disclosure Framework specification. First, as previously discussed on our calls, attached please find a proposed revision to section 3.1.2.1 of this specification, which spells out what the provider should do if it decides to disclose to the requester. This provision as originally drafted refers to disclosing the information "that would ordinarily appear in the publicly accessible Registration Data Directory Service." Since, post-Temp Spec, there is no longer a uniform set of data that "ordinarily appears" in the RDDS for various registrars and registries, this language needs to be updated. The full set of data that the PDP Working Group proposed, and that the GNSO council and ICANN board approved, should be disclosed in response to a successful IPR request corresponds to the data elements listed in section 3.3 of the PPAA (for ready reference I paste these in the attachment as well). At the time that the PDP WG, Council and Board acted, that list was synonymous with what would "ordinarily appear" in RDDS (Whois) for particular non-P/P registrations. Since that is no longer the case, it is important to spell out what the requester can expect to receive as part of a disclosure under this specification, in order to maintain the substance of the approved consensus policy. Second, regarding Amy's question (3) below about the dispute resolution provisions of this specification, while I agree that the title of section 4 of specification 4 can go away, it may be possible to drop the section altogether, or at least to condense it substantially. The background here is a bit complicated. During the negotiation in 2015 of the Illustrative Disclosure Framework (the basis for specification 4 of the PPAA now before us), a lot of effort was spent on developing a dispute resolution mechanism. I believe we ultimately could not reach agreement on such a mechanism, and instead decided to leave this to "other available remedies at law" (as section 4 of specification 4 now begins). We also agreed that for a defined category of disputes (those arising from wrongful disclosure or misuse of disclosed information), requesters would submit to the jurisdiction of specified courts. The second prong of this conclusion is now reflected in the specification as one of the representations requesters must make in order to have their request for disclosure considered (see, sections 2.1.6.3, 2.2.7.4, 2.3.6.3 of the specification). It may be that the only thing we need to say here is in the first sentence of section 4, that nothing precludes the pursuit of available remedies at law when disputes arise. That would certainly include the pursuit of data subject rights under the GDPR to the extent those are applicable. I'd like to study this issue a little further and aim to provide a more definitive proposal by the Friday deadline Amy has set, but wanted to share my preliminary thinking on it. Steve Metalitz From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> On Behalf Of Amy Bivins Sent: Monday, September 17, 2018 9:40 AM To: gdd-gnso-ppsai-impl(a)icann.org Subject: [Gdd-gnso-ppsai-impl] PP IRT Action Items This Week Dear Colleagues, ICANN org is continuing to review your feedback on the PPAA draft, and I hope to have an update this week as to your specific feedback on the data processing provisions. In the interim, please provide any feedback you have on the following no later than your end of day on Friday, 21 Sept: (1) In Specification 3, do you have any issue with incorporating a definition of action/actioned? We have attempted to clarify the term in Section 3.2.3 (p. 52) to state "action, in accordance with Sections 4.1 and 4.2..." but we believe this could be made more clear by explicitly defining this term. For example, we could add a definition that states that action means "to disclose the Requested Information, to refuse in writing to disclose the Requested Information, and/or to inform the LEA Requester that more time is required to respond to the request." (2) Should we add a new explicit basis for a Provider to reasonably refuse to disclose Requested Information in Specification 3, Section 4.1, where the Provider has a basis for reasonably believing that such Disclosure would violate relevant data protection law? (3) In Specification 4 (p. 62)-should this section title be updated since it doesn't specifically address how to resolve disputes? In addition, does the IRT wish to review the meaning and intent of this section in light of data subject rights in the GDPR, and its relevance to resolving disputes concerning data protection matters? Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 1

PP IRT Action Items This Week
by Amy Bivins Sept. 17, 2018

Sept. 17, 2018

Dear Colleagues, ICANN org is continuing to review your feedback on the PPAA draft, and I hope to have an update this week as to your specific feedback on the data processing provisions. In the interim, please provide any feedback you have on the following no later than your end of day on Friday, 21 Sept: 1. In Specification 3, do you have any issue with incorporating a definition of action/actioned? We have attempted to clarify the term in Section 3.2.3 (p. 52) to state "action, in accordance with Sections 4.1 and 4.2..." but we believe this could be made more clear by explicitly defining this term. For example, we could add a definition that states that action means "to disclose the Requested Information, to refuse in writing to disclose the Requested Information, and/or to inform the LEA Requester that more time is required to respond to the request." 2. Should we add a new explicit basis for a Provider to reasonably refuse to disclose Requested Information in Specification 3, Section 4.1, where the Provider has a basis for reasonably believing that such Disclosure would violate relevant data protection law? 3. In Specification 4 (p. 62)-should this section title be updated since it doesn't specifically address how to resolve disputes? In addition, does the IRT wish to review the meaning and intent of this section in light of data subject rights in the GDPR, and its relevance to resolving disputes concerning data protection matters? Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

Canceled: PP IRT Standing Call Time
by Amy Bivins Sept. 13, 2018

Sept. 13, 2018

[Web Meeting] [Sponsor] Dear Colleagues, Please note that the standing call time for the Privacy and Proxy Service Provider Accreditation Program Implementation Review Team is now Thursdays at 1600 UTC. Individual occurrences will be canceled on weeks where a meeting will not be held. Adobe Connect: https://participate.icann.org/ppirt/ __________________________________________________________________ You're Invited. You've been invited to a GlobalMeet® phone only meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me <https://go.conferencinghub.com/2y4ql> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://1-605-475-5618,*,,1350875547#<tel://1-605-475-5618,*,,1350875547> Phone Only Controls: https://go.conferencinghub.com/2y4ql Primary Access Number: 1-605-475-5618 Guest Passcode: 135 087 5547 Additional Access: USA 1-605-475-5618 USA 1-719-325-2630 Canada, Calgary +1 403 407 5780 Canada, Montreal +1 514 669 5909 Canada, Toronto +1 416 915 3615 Canada, Vancouver +1 604 205 5118 Argentina, Buenos Aires +54 (0) 11 5172 6019 Argentina (toll free) 0800 800 1250 Australia, Sydney +61 (0) 2 8017 6391 Australia, Melbourne +61 (0) 3 8687 0614 Australia, Brisbane +61 (0) 7 3015 0608 Australia (toll free) 1 800 720 493 Austria, Vienna +43 (0)1 928 2722 Austria (toll free) 0800 070 841 Bahrain, Manama +973 1650 0402 Bahrain (toll free) 8008 1214 Belarus (toll free) 8 820 0011 0353 Belgium, Brussels +32 (0) 2 400 1980 Belgium (toll free) 0800 39 268 Bosnia and Herzegovina +387 7031 1461 Brazil, Sao Paulo +55 11 4935 7122 Brazil, Rio de Janeiro +55 21 4560 0023 Brazil (toll free) 0800 887 0283 Bulgaria, Sofia +359 (0) 2 491 7244 Bulgaria (toll free) 00800 111 4944 Cambodia, Phnom Penh +855 23 962 579 Canada (toll free) 1 855 950 3706 Chile, Santiago +56 (0) 2 2666 0711 Chile (toll free) 171 800 835 943 China (national) +400 681 8104 China, Beijing +86 10 5667 0005 China, Shanghai +86 21 2039 7079 Colombia, Bogota +57 1 508 8112 Colombia (toll free) 01 800 755 0043 Costa Rica (toll free) 800 542 5331 Croatia (toll free) 0800 223 004 Cyprus (toll free) 800 97400 Czech Republic, Prague +420 225 986 505 Czech Republic (toll free) 800 701 236 Denmark, Copenhagen +45 32 71 16 70 Denmark (toll free) 80 70 35 78 Egypt (toll free) 0800 000 0401 Estonia, Tallinn +372 622 6519 Estonia (toll free) 800 011 1569 Fiji (toll free) 00800 3317 Finland, Helsinki +358 (0) 9 2310 1611 Finland (toll free) 0800 772 230 France, Paris +33 (0) 1 76 77 22 50 France (toll free) 0800 946 112 France (national) 0811 655 134 France (national) 0821 231 687 Georgia, Tbilisi +995 32 2 053 082 Germany, Frankfurt +49 (0) 69 5060 9515 Germany, Munich +49 (0) 89 24443 2900 Germany (national) 01801 001 378 Germany (toll free) 0800 588 9225 Greece, Athens +30 211 181 3815 Greece (toll free) 00800 128 811 Hong Kong +852 3018 9103 Hong Kong (toll free) 800 968 082 Hungary, Budapest +36 1 808 8134 Hungary (toll free) 068 001 9662 Iceland (toll free) 800 9841 India, Delhi +91 11 6310 0272 India, Mumbai +91 22 6310 0274 India, Chennai +91 44 6310 0227 India, Bangalore +91 80 6760 8747 India (toll free) 1800 3010 1564 Indonesia, Jakarta +62 21 2188 9079 Indonesia (toll free) 007 803 321 8120 Ireland, Dublin +353 (0) 1 246 5614 Ireland (national) 0818 270 287 Ireland (toll free) 1800 937 695 Ireland (national) 1890 907 722 Israel, Tel Aviv +972 (0)3 763 0384 Israel (toll free) 180 921 2890 Italy, Milan +39 02 3046 4837 Italy, Rome +39 06 4523 6635 Italy (toll free) 800 148 288 Japan, Tokyo +81 3 4560 1274 Japan, Osaka +81 6 4560 0303 Japan (mobile) 0120 270 611 Japan (toll free) 0120 286 011 Japan (national) 0570 005 744 Jordan (toll free) 0800 22156 Kazakhstan (toll free) 8800 333 7552 Kenya, Nairobi +254 (0)207 643 596 South Korea, Seoul +82 (0) 2 6007 0072 South Korea (toll free) 007 986 136 2233 Kuwait (national) +965 2206 3083 Latvia, Riga +371 6778 2598 Latvia (toll free) 8000 4374 Lithuania, Vilnius +370 5205 5239 Lithuania (toll free) 8800 31445 Luxembourg +352 2730 2276 Luxembourg (toll free) 800 28428 Macau (national) +853 6262 1674 Malaysia, Kuala Lumpur +60 (0) 3 7723 7140 Malaysia (toll free) 1 800 815 805 Mexico, Guadalajara +52 33 4162 5891 Mexico, Mexico City +52 55 8421 0857 Mexico, Monterrey +52 81 4770 2472 Mexico (toll free) 01 800 283 3129 Morocco, Casablanca +212 (0)520 480 128 Morocco (toll free) 0800 092 258 Netherlands, Amsterdam +31 (0) 20 716 8266 Netherlands (toll free) 0800 020 0593 New Zealand, Christchurch +64 (0) 3 974 2597 New Zealand, Wellington +64 (0) 4 909 4676 New Zealand, Auckland +64 (0) 9 929 1769 New Zealand (toll free) 0800 459 127 Nigeria, Lagos +234 1 277 5140 Norway, Oslo +47 2162 4054 Norway (toll free) 800 58459 Oman (toll free) 800 77269 Pakistan, Islamabad +92 5181 08874 Panama, Panama City +507 8 339 782 Panama (toll free) 00800 223 1430 Peru, Lima +51 (0) 1 700 9587 Peru (toll free) 0800 78125 Philippines, Manila +63 (0)2 395 3365 Philippines (toll free) 1800 111 017 51 Poland, Warsaw +48 22 295 3504 Poland (toll free) 00800 121 4340 Portugal, Lisbon +351 21 316 4041 Portugal (toll free) 800 784 434 Qatar (freephone) 00 800 100 499 Romania, Bucharest +40 (0) 21 529 3969 Romania (toll free) 0800 801 030 Russia, Moscow +7 495 213 0988 Russia (toll free) 8 800 500 9319 Saudi Arabia (toll free) 800 844 4963 Saudi Arabia (toll free) 800 850 0227 Serbia (toll free) 0800 190 698 Singapore +65 6654 9111 Singapore (toll free) 800 616 3175 Slovakia, Bratislava +421 (0)2 3321 5333 Slovakia (toll free) 0800 001 661 Slovenia, Ljubljana +386 1 600 1622 Slovenia (toll free) 0800 80994 South Africa, Johannesburg +27 (0)11 019 7087 South Africa (toll free) 0800 988 886 Spain, Madrid +34 91 114 6640 Spain, Barcelona +34 93 800 1935 Spain (toll free) 900 803 689 Sri Lanka, Sri Lanka +94 720 910 348 Sweden, Stockholm +46 (0) 8 5065 3944 Sweden (toll free) 0200 125 456 Switzerland, Geneva +41 (0) 22 595 4857 Switzerland, Zurich +41 (0) 44 580 7246 Switzerland (toll free) 0800 841 702 Taiwan, Taipei +886 (0) 2 2656 7213 Taiwan (toll free) 00 801 615 184 Thailand, Bangkok +66 (0) 2104 0767 Thailand (toll free) 1 800 012 172 Tunisia, Tunis +216 31 378 109 Turkey, Istanbul +90 212 375 50 13 Turkey (toll free) 00 800 448 828 358 Ukraine (toll free) 0800 500 732 UAE (toll free) 8000 3570 2638 UK (03) +44 (0)330 336 6010 UK (toll free) 0800 368 0950 UK (national) 0844 473 5003 UK (national) 0845 545 0040 USA /Canada (toll free) 1-855-747-8824 Uruguay (toll free) 0004 019 0561 Venezuela, Caracas +58 212 720 2342 Venezuela (toll free) 0800 102 9660 Vietnam, Hanoi +84 24 4458 3323 Vietnam, Ho Chi Minh +84 28 4458 1333 Vietnam (toll free) 1800 9228 Questions? Go to GlobalMeet Support<http://community.globalmeet.com> © Premiere Global Services, Inc. and/or its affiliates | PGi

1 0

Materials From Today's PP IRT Meeting
by Amy Bivins Sept. 13, 2018

Sept. 13, 2018

Dear Colleagues, Thank you for your active participation on today's PP IRT call. The call recording and related materials are now available on the wiki, https://community.icann.org/display/IRT/13+September+2018 For those who could not attend, I encourage you to review the recording. We were able to complete our discussion of IRT feedback that has been received on the PPAA markup. If anyone has additional feedback on the topics discussed today, please send it to the list this week, if possible. I'm referring your feedback to the internal team as we receive it, and will have an update on timeline on completing this round of review of the issues raised as soon as possible. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

PPAA draft markup for today's meeting
by Amy Bivins Sept. 13, 2018

Sept. 13, 2018

Dear Colleagues, I've attached an updated PPAA draft that incorporates all of the new feedback received since our last meeting. We're planning to pick up at Section 3.5.3.3 today and get as far as we can on the feedback we've received. As a reminder, our call is at 1600 UTC today. The Adobe Connect room is https://participate.icann.org/ppirt/ . Thanks in advance for your active participation, and I look forward to speaking with you later today. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

Materials, discussion topics for this week's PP IRT meeting
by Amy Bivins Sept. 12, 2018

Sept. 12, 2018

Dear Colleagues, Thank you for your feedback on the list since our last meeting. We will continue to discuss your feedback on the PPAA draft during our next PPIRT meeting on Thursday, 13 September, 1600 UTC. The most recent PPAA draft, including comments received on the list since our last meeting, is attached. Action Item: The purpose of our call this week is to continue reviewing your feedback on the PPAA draft. We will pick up at Section 3.5, where we adjourned last week. If you have any additional items that you would like to note in this week's discussion version of the draft (for display in the AC room), please send them to the list no later than your end of day Wednesday. Action Item: We'd also like to hear any feedback you have on the possibility of adding a PPAA provision(s) to require provider logging of third-party requests for non-public RDDS data. Please consider this possibility and share any feedback you have on the list this week or during Thursday's call. I'm attaching a screenshot of the results of the PP IRT poll. Of the 15 IRT members who responded to the poll: * Nine IRT members answered "yes" to the question, "Do you believe that the Privacy and Proxy Service Provider Accreditation Program Implementation Review Team should consult with the GNSO Council prior to proceeding to public comment due to one or more Policy questions surrounding the implementation of the Final Recommendations?" (8-registrar; 1-no affiliation provided) * Six IRT members answered "No." (2-PSWG, 1-registrar, 2-IPC, 1-BC) Your feedback on the PPAA draft and all other issues is being shared with the broader internal team for review. I won't have official feedback to share this week, but am hoping that there will be more to share next week. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

4 4

Materials From Today's PP IRT Call, Action Items
by Amy Bivins Sept. 9, 2018

Sept. 9, 2018

Dear Colleagues, Thanks for your active participation on today's PP IRT call. If you didn't attend, I encourage you to review the materials and recording, which are available on the wiki, https://community.icann.org/display/IRT/6+Sept+2018+Meeting. Notes and Action Items 1. The first item on today's agenda was a discussion of the feedback and comments from some members of the IRT that the current RDDS environment might signal a need to consult with the GNSO Council about the status of the PP IRT's work. IRT members were asked whether they believe questions exist that should be taken to the Council and, if so, what the questions are. IRT members are encouraged to review the recording to hear their all positions raised on this item. * Action Item 1: If any IRT member believes that one or more Policy issues have arisen that should be referred to the GNSO Council, the member is requested to clearly identify that question on the list no later than the end of the day on Friday. * Action Item 2: IRT members are requested to provide feedback on any issues raised via the list. * Action Item 3: IRT members are also invited to, either instead of writing to the list or as a supplement, indicate their position on whether or not they believe a Policy issue has arisen that should be escalated to the Council, by participating in this poll: https://www.surveymonkey.com/r/8MW2JMM Please complete the poll by the end of this week. I will circulate the results of the poll on Monday. The poll results will be considered along with feedback received on the list and the call. * If the results of the poll and continued discussion on the list this week indicate that there is a likely consensus to escalate one or more issues to the Council, this potential course of action will be continued to be explored next week. If not, we will continue to work to finalize the PPAA in preparation for public comment. 2. PPAA Markup * We began reviewing the PPAA markup, and will continue reviewing next week. * Action Item: IRT members are invited to continue reviewing the markup and provide any additional feedback on the document no later than end of day Monday for discussion on Thursday's call. * Action Item: I will consult with Legal about points raised on the call, for discussion next week. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 1

PP services for gated access data
by Roman, Peter (CRM) Sept. 7, 2018

Sept. 7, 2018

All – Just to continue the smaller discussion from today’s call: Putting aside the existential question of whether the business case for privacy/proxy makes sense following the implementation of the GDPR, and assuming that: 1) privacy/proxy providers will continue to do business and 2) the EPDP is going to reach a solution that will give IP rights holders, cybersecurity researchers, law enforcement, and other vetted people access to the registrant data that is not publicly available; I propose that the IRT consider that, since the second tier of WHOIS data would only be available to vetted, accredited law enforcement, cybersecurity, IP rights holders, etc. that have represented that they have a legitimate purpose for accessing the data, and since that data is merely subscriber data (which under the Council of Europe’s CyberCrime Convention, and numerous other legal regimes as well, is deserving of the lowest level of privacy protection), and therefore no legitimate purpose is served by further hindering access to such data, the IRT should add the following language to the draft PPAA: 3.5.7 Provider shall not provide Services for Customers whose data is non-public. Or 3.5.7 Provider shall not provide Services for Customers whose data is only accessible through gated access in the RDDS system and is not publicly available through WHOIS. Thanks, Peter Roman Senior Counsel Computer Crime & Intellectual Property Section Criminal Division Department of Justice 1301 New York Ave., NW Washington, DC 20530 (202) 305-1323 peter.roman(a)usdoj.gov<mailto:peter.roman@usdoj.gov> From: Gdd-gnso-ppsai-impl [mailto:gdd-gnso-ppsai-impl-bounces@icann.org] On Behalf Of Theo Geurts Sent: Thursday, August 30, 2018 3:08 AM To: gdd-gnso-ppsai-impl(a)icann.org; Michele Neylon - Blacknight <michele(a)blacknight.com> Subject: Re: [Gdd-gnso-ppsai-impl] Materials for tomorrow's PP IRT meeting are attached Agreed on the moving target part. Not too mention another moving target that will render most of our work right down into the trash if it happens. http://domainincite.com/23371-could-a-new-us-law-make-gdpr-irrelevant This draft seems to be in direct conflict with some of the WG's recommendations; https://via.hypothes.is/https://www.internetgovernance.org/wp-content/uploa…<https://via.hypothes.is/https:/www.internetgovernance.org/wp-content/upload…> Thanks, Theo On 30-8-2018 7:55, Michele Neylon - Blacknight wrote: I won’t be able to attend as I’m at an event. I also agree with the concerns raised by others about pegging *anything* to a moving target, which the Temp Spec is TLDR – it’s not policy – it’s a stopgap. Baking it into anything else is a really bad idea Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org><mailto:gdd-gnso-ppsai-impl-bounces@icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org><mailto:amy.bivins@icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org"<mailto:gdd-gnso-ppsai-impl@icann.org> <gdd-gnso-ppsai-impl(a)icann.org><mailto:gdd-gnso-ppsai-impl@icann.org> Date: Wednesday 29 August 2018 at 16:22 To: "gdd-gnso-ppsai-impl(a)icann.org"<mailto:gdd-gnso-ppsai-impl@icann.org> <gdd-gnso-ppsai-impl(a)icann.org><mailto:gdd-gnso-ppsai-impl@icann.org> Subject: [Gdd-gnso-ppsai-impl] Materials for tomorrow's PP IRT meeting are attached Dear Colleagues, This is a reminder that the PP IRT will meet tomorrow, Thursday, 30 August, at 1600 UTC. A draft markup of the PPAA is attached. This markup is for discussion purposes only—it is not a final proposal and remains subject to revision. The draft is being circulated, without further delay, to continue the conversation. It has not been approved by senior management and is for discussion only. We would like to begin discussing the following topics tomorrow (but please feel free to comment before then on the list): (1) Some suggested edits track what’s in the Temporary Specification for gTLD Registration Data. For example, section 3.5.3.3. How should we approach drafting provisions modeled on the Temp Spec, given that its language is subject to change in the near future? (2) The disclosure frameworks seem to be written from the position that there’s no discretion for the Provider to not provide the underlying customer data if the conditions in the framework are met. Is this the intent? This could potentially cause issues under the GDPR, because this doesn’t seem to leave room to balance the interests of the data subjects with the legitimate interest of the parties requesting personal data. (3) The disclosure frameworks raise additional GDPR-related questions that are similar to questions raised in the Draft Framework Elements of a Potential Unified Access Model<https://www.icann.org/en/system/files/files/framework-elements-unified-acce…> paper published by ICANN org. For example, what would the requirements be for logging requests for disclosure made under the frameworks (or even requests not governed by the frameworks)? (4) Do you see any other issues that you believe must be addressed related to GDPR that were not addressed in this markup? (5) Following the completion of the IRT’s review of this draft accreditation agreement and related matters, we believe are ready to proceed to public comment. Do you believe there is any reason why the IRT should not proceed to public comment? (6) We have heard questions from various members of the community about how the proposed accreditation program requirements will operate within the current Temp Spec RDDS environment. These proposed program requirements do not address how PP registrations interact with a gated access model or how they might be impacted, if at all, by the results of the EPDP. Is this an issue that the IRT believes should be explored at this stage? If any member of the IRT wishes to raise any comments or points about this topic, you are encouraged to do so during the IRT call or via the list. One area that may need further attention in the agreement is specifically defining what data is to be collected and for what purpose. In addition, the new Specification 8 contains some data processing requirements, but additional discussion is needed on the appropriate controller arrangements that are needed between ICANN, the registrar and the Provider. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org> _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl(a)icann.org<mailto:Gdd-gnso-ppsai-impl@icann.org> https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl

7 8

Updated PPAA draft including all new comments from list
by Amy Bivins Sept. 6, 2018

Sept. 6, 2018

Dear Colleagues, Attached is an updated PPAA draft that incorporates all of the proposed edits (and comments about those proposed edits) received on the list this week. I look forward to speaking with you later today. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

Agenda, materials, poll for tomorrow's PP IRT meeting
by Amy Bivins Sept. 6, 2018

Sept. 6, 2018

Dear Colleagues, This is a reminder that the PP IRT will meet tomorrow, 6 Sept, at 1600 UTC. Adobe Connect: https://participate.icann.org/ppirt/ I'm attaching the current markup of the PPAA, showing all IRT feedback received thus far on the GDPR-related markup. Please note that all edits proposed by Volker have also been supported by Theo, Sara, Chris, and Eric. Agenda: 1. Discussion Topic 1: Do you believe that the Privacy and Proxy Service Provider Accreditation Program Implementation Review Team should consult with the GNSO Council prior to proceeding to public comment due to one or more Policy questions surrounding the implementation of the Final Recommendations? * Background: Please note that ICANN Legal has advised that data processing provisions are necessary in PPAA (as proposed in Section 3.5.3.3 and Specification 8), though the current text may be edited based on IRT feedback. * Draft WHOIS2 Report: Also, please note that the impact of GDPR on PP was raised in the WHOIS2 draft report that was published yesterday for public comment, https://www.icann.org/en/system/files/files/draft-rds-whois2-review-31aug18… (see p. 67-9). The report said that GDPR and other privacy regimes might reduce the apparent need for PP services, but that this impact would have to be assessed in concert with any future review of the effectiveness of the policy. The report also raised points related to fees and the time that was required for the recent Legal review. The report had recommendations for additional steps to be taken if this accreditation program is not implemented by 31 December 2019. * Action item: Please complete poll to determine level of IRT consensus on this topic no later than this Friday, 7 Sept: https://www.surveymonkey.com/r/8MW2JMM 2. Discussion Topic 2: IRT feedback on PPAA draft (attached). We will begin with the IRT feedback on Specification 8 and then return to the beginning of the agreement and proceed as far as we can on feedback received thus far during the call. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

4 4

Follow-Up on Yesterday's PP IRT Discussion
by Amy Bivins Sept. 6, 2018

Sept. 6, 2018

Dear Colleagues, Following up on our discussion yesterday, I checked with the Legal team about a couple of items that were discussed. 1. With respect to the proposed edits to the PPAA that are related to data processing (see, e.g. Section 3.5.3 of the contract and the new draft Specification 8), provisions on these topics must be included in this contract, though these can be edited based on your feedback. If you have suggested edits to these new provisions, please send them to the list and we can discuss them on the call next week. If, as discussed yesterday, you believe the inclusion of these provisions raises more fundamental questions about status, in light of the pending ePDP on similar topics, we can also discuss that. As a reminder, the way the PPAA is drafted, any new ICANN Policy that is in conflict with current provisions (GDPR-related or otherwise) would supersede any conflicting provisions in this contract. 1. On the overall timeline, and additional deliverables, any additional GDPR-related changes will be based on IRT feedback. We have a couple of additional discussion topics that we didn't reach last week, which could require additional PPAA changes. We'll discuss these next week: * Are the disclosure frameworks intended to give Providers limited or no discretion on disclosure if other requirements in the framework are met? * What should requirements be for a Provider's logging of disclosure requests from third parties? We are continuing to review the contract for any copy-editing related issues, and I expect we will finish with those in the next week or so. I hope this is helpful. Please continue to consider these issues and share any feedback you have on-list. We can pick up on these issues next week. Thanks, and have a great weekend! Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

8 10

PP IRT Standing Call Time
by Amy Bivins Sept. 5, 2018

Sept. 5, 2018

[Web Meeting] [Sponsor] Dear Colleagues, Please note that the standing call time for the Privacy and Proxy Service Provider Accreditation Program Implementation Review Team is now Thursdays at 1600 UTC. Individual occurrences will be canceled on weeks where a meeting will not be held. Adobe Connect: https://participate.icann.org/ppirt/ __________________________________________________________________ You're Invited. You've been invited to a GlobalMeet® phone only meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me <https://go.conferencinghub.com/2y4ql> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://1-605-475-5618,*,,1350875547#<tel://1-605-475-5618,*,,1350875547> Phone Only Controls: https://go.conferencinghub.com/2y4ql Primary Access Number: 1-605-475-5618 Guest Passcode: 135 087 5547 Additional Access: USA 1-605-475-5618 USA 1-719-325-2630 Canada, Calgary +1 403 407 5780 Canada, Montreal +1 514 669 5909 Canada, Toronto +1 416 915 3615 Canada, Vancouver +1 604 205 5118 Argentina, Buenos Aires +54 (0) 11 5172 6019 Argentina (toll free) 0800 800 1250 Australia, Sydney +61 (0) 2 8017 6391 Australia, Melbourne +61 (0) 3 8687 0614 Australia, Brisbane +61 (0) 7 3015 0608 Australia (toll free) 1 800 720 493 Austria, Vienna +43 (0)1 928 2722 Austria (toll free) 0800 070 841 Bahrain, Manama +973 1650 0402 Bahrain (toll free) 8008 1214 Belarus (toll free) 8 820 0011 0353 Belgium, Brussels +32 (0) 2 400 1980 Belgium (toll free) 0800 39 268 Bosnia and Herzegovina +387 7031 1461 Brazil, Sao Paulo +55 11 4935 7122 Brazil, Rio de Janeiro +55 21 4560 0023 Brazil (toll free) 0800 887 0283 Bulgaria, Sofia +359 (0) 2 491 7244 Bulgaria (toll free) 00800 111 4944 Cambodia, Phnom Penh +855 23 962 579 Canada (toll free) 1 855 950 3706 Chile, Santiago +56 (0) 2 2666 0711 Chile (toll free) 171 800 835 943 China (national) +400 681 8104 China, Beijing +86 10 5667 0005 China, Shanghai +86 21 2039 7079 Colombia, Bogota +57 1 508 8112 Colombia (toll free) 01 800 755 0043 Costa Rica (toll free) 800 542 5331 Croatia (toll free) 0800 223 004 Cyprus (toll free) 800 97400 Czech Republic, Prague +420 225 986 505 Czech Republic (toll free) 800 701 236 Denmark, Copenhagen +45 32 71 16 70 Denmark (toll free) 80 70 35 78 Egypt (toll free) 0800 000 0401 Estonia, Tallinn +372 622 6519 Estonia (toll free) 800 011 1569 Fiji (toll free) 00800 3317 Finland, Helsinki +358 (0) 9 2310 1611 Finland (toll free) 0800 772 230 France, Paris +33 (0) 1 76 77 22 50 France (toll free) 0800 946 112 France (national) 0811 655 134 France (national) 0821 231 687 Georgia, Tbilisi +995 32 2 053 082 Germany, Frankfurt +49 (0) 69 5060 9515 Germany, Munich +49 (0) 89 24443 2900 Germany (national) 01801 001 378 Germany (toll free) 0800 588 9225 Greece, Athens +30 211 181 3815 Greece (toll free) 00800 128 811 Hong Kong +852 3018 9103 Hong Kong (toll free) 800 968 082 Hungary, Budapest +36 1 808 8134 Hungary (toll free) 068 001 9662 Iceland (toll free) 800 9841 India, Delhi +91 11 6310 0272 India, Mumbai +91 22 6310 0274 India, Chennai +91 44 6310 0227 India, Bangalore +91 80 6760 8747 India (toll free) 1800 3010 1564 Indonesia, Jakarta +62 21 2188 9079 Indonesia (toll free) 007 803 321 8120 Ireland, Dublin +353 (0) 1 246 5614 Ireland (national) 0818 270 287 Ireland (toll free) 1800 937 695 Ireland (national) 1890 907 722 Israel, Tel Aviv +972 (0)3 763 0384 Israel (toll free) 180 921 2890 Italy, Milan +39 02 3046 4837 Italy, Rome +39 06 4523 6635 Italy (toll free) 800 148 288 Japan, Tokyo +81 3 4560 1274 Japan, Osaka +81 6 4560 0303 Japan (mobile) 0120 270 611 Japan (toll free) 0120 286 011 Japan (national) 0570 005 744 Jordan (toll free) 0800 22156 Kazakhstan (toll free) 8800 333 7552 Kenya, Nairobi +254 (0)207 643 596 South Korea, Seoul +82 (0) 2 6007 0072 South Korea (toll free) 007 986 136 2233 Kuwait (national) +965 2206 3083 Latvia, Riga +371 6778 2598 Latvia (toll free) 8000 4374 Lithuania, Vilnius +370 5205 5239 Lithuania (toll free) 8800 31445 Luxembourg +352 2730 2276 Luxembourg (toll free) 800 28428 Macau (national) +853 6262 1674 Malaysia, Kuala Lumpur +60 (0) 3 7723 7140 Malaysia (toll free) 1 800 815 805 Mexico, Guadalajara +52 33 4162 5891 Mexico, Mexico City +52 55 8421 0857 Mexico, Monterrey +52 81 4770 2472 Mexico (toll free) 01 800 283 3129 Morocco, Casablanca +212 (0)520 480 128 Morocco (toll free) 0800 092 258 Netherlands, Amsterdam +31 (0) 20 716 8266 Netherlands (toll free) 0800 020 0593 New Zealand, Christchurch +64 (0) 3 974 2597 New Zealand, Wellington +64 (0) 4 909 4676 New Zealand, Auckland +64 (0) 9 929 1769 New Zealand (toll free) 0800 459 127 Nigeria, Lagos +234 1 277 5140 Norway, Oslo +47 2162 4054 Norway (toll free) 800 58459 Oman (toll free) 800 77269 Pakistan, Islamabad +92 5181 08874 Panama, Panama City +507 8 339 782 Panama (toll free) 00800 223 1430 Peru, Lima +51 (0) 1 700 9587 Peru (toll free) 0800 78125 Philippines, Manila +63 (0)2 395 3365 Philippines (toll free) 1800 111 017 51 Poland, Warsaw +48 22 295 3504 Poland (toll free) 00800 121 4340 Portugal, Lisbon +351 21 316 4041 Portugal (toll free) 800 784 434 Qatar (freephone) 00 800 100 499 Romania, Bucharest +40 (0) 21 529 3969 Romania (toll free) 0800 801 030 Russia, Moscow +7 495 213 0988 Russia (toll free) 8 800 500 9319 Saudi Arabia (toll free) 800 844 4963 Saudi Arabia (toll free) 800 850 0227 Serbia (toll free) 0800 190 698 Singapore +65 6654 9111 Singapore (toll free) 800 616 3175 Slovakia, Bratislava +421 (0)2 3321 5333 Slovakia (toll free) 0800 001 661 Slovenia, Ljubljana +386 1 600 1622 Slovenia (toll free) 0800 80994 South Africa, Johannesburg +27 (0)11 019 7087 South Africa (toll free) 0800 988 886 Spain, Madrid +34 91 114 6640 Spain, Barcelona +34 93 800 1935 Spain (toll free) 900 803 689 Sri Lanka, Sri Lanka +94 720 910 348 Sweden, Stockholm +46 (0) 8 5065 3944 Sweden (toll free) 0200 125 456 Switzerland, Geneva +41 (0) 22 595 4857 Switzerland, Zurich +41 (0) 44 580 7246 Switzerland (toll free) 0800 841 702 Taiwan, Taipei +886 (0) 2 2656 7213 Taiwan (toll free) 00 801 615 184 Thailand, Bangkok +66 (0) 2104 0767 Thailand (toll free) 1 800 012 172 Tunisia, Tunis +216 31 378 109 Turkey, Istanbul +90 212 375 50 13 Turkey (toll free) 00 800 448 828 358 Ukraine (toll free) 0800 500 732 UAE (toll free) 8000 3570 2638 UK (03) +44 (0)330 336 6010 UK (toll free) 0800 368 0950 UK (national) 0844 473 5003 UK (national) 0845 545 0040 USA /Canada (toll free) 1-855-747-8824 Uruguay (toll free) 0004 019 0561 Venezuela, Caracas +58 212 720 2342 Venezuela (toll free) 0800 102 9660 Vietnam, Hanoi +84 24 4458 3323 Vietnam, Ho Chi Minh +84 28 4458 1333 Vietnam (toll free) 1800 9228 Questions? Go to GlobalMeet Support<http://community.globalmeet.com> © Premiere Global Services, Inc. and/or its affiliates | PGi

1 0

PP IRT Standing Call Time
by Amy Bivins Sept. 5, 2018

Sept. 5, 2018

[Web Meeting] [Sponsor] Dear Colleagues, Please note that the standing call time for the Privacy and Proxy Service Provider Accreditation Program Implementation Review Team is now Thursdays at 1600 UTC. Individual occurrences will be canceled on weeks where a meeting will not be held. Adobe Connect: https://participate.icann.org/ppirt/ __________________________________________________________________ You're Invited. You've been invited to a GlobalMeet® phone only meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me <https://go.conferencinghub.com/2y4ql> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://1-605-475-5618,*,,1350875547#<tel://1-605-475-5618,*,,1350875547> Phone Only Controls: https://go.conferencinghub.com/2y4ql Primary Access Number: 1-605-475-5618 Guest Passcode: 135 087 5547 Additional Access: USA 1-605-475-5618 USA 1-719-325-2630 Canada, Calgary +1 403 407 5780 Canada, Montreal +1 514 669 5909 Canada, Toronto +1 416 915 3615 Canada, Vancouver +1 604 205 5118 Argentina, Buenos Aires +54 (0) 11 5172 6019 Argentina (toll free) 0800 800 1250 Australia, Sydney +61 (0) 2 8017 6391 Australia, Melbourne +61 (0) 3 8687 0614 Australia, Brisbane +61 (0) 7 3015 0608 Australia (toll free) 1 800 720 493 Austria, Vienna +43 (0)1 928 2722 Austria (toll free) 0800 070 841 Bahrain, Manama +973 1650 0402 Bahrain (toll free) 8008 1214 Belarus (toll free) 8 820 0011 0353 Belgium, Brussels +32 (0) 2 400 1980 Belgium (toll free) 0800 39 268 Bosnia and Herzegovina +387 7031 1461 Brazil, Sao Paulo +55 11 4935 7122 Brazil, Rio de Janeiro +55 21 4560 0023 Brazil (toll free) 0800 887 0283 Bulgaria, Sofia +359 (0) 2 491 7244 Bulgaria (toll free) 00800 111 4944 Cambodia, Phnom Penh +855 23 962 579 Canada (toll free) 1 855 950 3706 Chile, Santiago +56 (0) 2 2666 0711 Chile (toll free) 171 800 835 943 China (national) +400 681 8104 China, Beijing +86 10 5667 0005 China, Shanghai +86 21 2039 7079 Colombia, Bogota +57 1 508 8112 Colombia (toll free) 01 800 755 0043 Costa Rica (toll free) 800 542 5331 Croatia (toll free) 0800 223 004 Cyprus (toll free) 800 97400 Czech Republic, Prague +420 225 986 505 Czech Republic (toll free) 800 701 236 Denmark, Copenhagen +45 32 71 16 70 Denmark (toll free) 80 70 35 78 Egypt (toll free) 0800 000 0401 Estonia, Tallinn +372 622 6519 Estonia (toll free) 800 011 1569 Fiji (toll free) 00800 3317 Finland, Helsinki +358 (0) 9 2310 1611 Finland (toll free) 0800 772 230 France, Paris +33 (0) 1 76 77 22 50 France (toll free) 0800 946 112 France (national) 0811 655 134 France (national) 0821 231 687 Georgia, Tbilisi +995 32 2 053 082 Germany, Frankfurt +49 (0) 69 5060 9515 Germany, Munich +49 (0) 89 24443 2900 Germany (national) 01801 001 378 Germany (toll free) 0800 588 9225 Greece, Athens +30 211 181 3815 Greece (toll free) 00800 128 811 Hong Kong +852 3018 9103 Hong Kong (toll free) 800 968 082 Hungary, Budapest +36 1 808 8134 Hungary (toll free) 068 001 9662 Iceland (toll free) 800 9841 India, Delhi +91 11 6310 0272 India, Mumbai +91 22 6310 0274 India, Chennai +91 44 6310 0227 India, Bangalore +91 80 6760 8747 India (toll free) 1800 3010 1564 Indonesia, Jakarta +62 21 2188 9079 Indonesia (toll free) 007 803 321 8120 Ireland, Dublin +353 (0) 1 246 5614 Ireland (national) 0818 270 287 Ireland (toll free) 1800 937 695 Ireland (national) 1890 907 722 Israel, Tel Aviv +972 (0)3 763 0384 Israel (toll free) 180 921 2890 Italy, Milan +39 02 3046 4837 Italy, Rome +39 06 4523 6635 Italy (toll free) 800 148 288 Japan, Tokyo +81 3 4560 1274 Japan, Osaka +81 6 4560 0303 Japan (mobile) 0120 270 611 Japan (toll free) 0120 286 011 Japan (national) 0570 005 744 Jordan (toll free) 0800 22156 Kazakhstan (toll free) 8800 333 7552 Kenya, Nairobi +254 (0)207 643 596 South Korea, Seoul +82 (0) 2 6007 0072 South Korea (toll free) 007 986 136 2233 Kuwait (national) +965 2206 3083 Latvia, Riga +371 6778 2598 Latvia (toll free) 8000 4374 Lithuania, Vilnius +370 5205 5239 Lithuania (toll free) 8800 31445 Luxembourg +352 2730 2276 Luxembourg (toll free) 800 28428 Macau (national) +853 6262 1674 Malaysia, Kuala Lumpur +60 (0) 3 7723 7140 Malaysia (toll free) 1 800 815 805 Mexico, Guadalajara +52 33 4162 5891 Mexico, Mexico City +52 55 8421 0857 Mexico, Monterrey +52 81 4770 2472 Mexico (toll free) 01 800 283 3129 Morocco, Casablanca +212 (0)520 480 128 Morocco (toll free) 0800 092 258 Netherlands, Amsterdam +31 (0) 20 716 8266 Netherlands (toll free) 0800 020 0593 New Zealand, Christchurch +64 (0) 3 974 2597 New Zealand, Wellington +64 (0) 4 909 4676 New Zealand, Auckland +64 (0) 9 929 1769 New Zealand (toll free) 0800 459 127 Nigeria, Lagos +234 1 277 5140 Norway, Oslo +47 2162 4054 Norway (toll free) 800 58459 Oman (toll free) 800 77269 Pakistan, Islamabad +92 5181 08874 Panama, Panama City +507 8 339 782 Panama (toll free) 00800 223 1430 Peru, Lima +51 (0) 1 700 9587 Peru (toll free) 0800 78125 Philippines, Manila +63 (0)2 395 3365 Philippines (toll free) 1800 111 017 51 Poland, Warsaw +48 22 295 3504 Poland (toll free) 00800 121 4340 Portugal, Lisbon +351 21 316 4041 Portugal (toll free) 800 784 434 Qatar (freephone) 00 800 100 499 Romania, Bucharest +40 (0) 21 529 3969 Romania (toll free) 0800 801 030 Russia, Moscow +7 495 213 0988 Russia (toll free) 8 800 500 9319 Saudi Arabia (toll free) 800 844 4963 Saudi Arabia (toll free) 800 850 0227 Serbia (toll free) 0800 190 698 Singapore +65 6654 9111 Singapore (toll free) 800 616 3175 Slovakia, Bratislava +421 (0)2 3321 5333 Slovakia (toll free) 0800 001 661 Slovenia, Ljubljana +386 1 600 1622 Slovenia (toll free) 0800 80994 South Africa, Johannesburg +27 (0)11 019 7087 South Africa (toll free) 0800 988 886 Spain, Madrid +34 91 114 6640 Spain, Barcelona +34 93 800 1935 Spain (toll free) 900 803 689 Sri Lanka, Sri Lanka +94 720 910 348 Sweden, Stockholm +46 (0) 8 5065 3944 Sweden (toll free) 0200 125 456 Switzerland, Geneva +41 (0) 22 595 4857 Switzerland, Zurich +41 (0) 44 580 7246 Switzerland (toll free) 0800 841 702 Taiwan, Taipei +886 (0) 2 2656 7213 Taiwan (toll free) 00 801 615 184 Thailand, Bangkok +66 (0) 2104 0767 Thailand (toll free) 1 800 012 172 Tunisia, Tunis +216 31 378 109 Turkey, Istanbul +90 212 375 50 13 Turkey (toll free) 00 800 448 828 358 Ukraine (toll free) 0800 500 732 UAE (toll free) 8000 3570 2638 UK (03) +44 (0)330 336 6010 UK (toll free) 0800 368 0950 UK (national) 0844 473 5003 UK (national) 0845 545 0040 USA /Canada (toll free) 1-855-747-8824 Uruguay (toll free) 0004 019 0561 Venezuela, Caracas +58 212 720 2342 Venezuela (toll free) 0800 102 9660 Vietnam, Hanoi +84 24 4458 3323 Vietnam, Ho Chi Minh +84 28 4458 1333 Vietnam (toll free) 1800 9228 Questions? Go to GlobalMeet Support<http://community.globalmeet.com> © Premiere Global Services, Inc. and/or its affiliates | PGi

1 0

Materials, Action Items From 30 Aug PP IRT Meeting
by Amy Bivins Aug. 31, 2018

Aug. 31, 2018

Dear Colleagues, Thanks so much for your active participation on today's PP IRT call. The recording and associated materials are now available on the wiki: https://community.icann.org/display/IRT/30+August+2018 For those of you who could not attend, I encourage you to listen to the recording. We did not make it all the way through our list of discussion questions today, but hope to keep the discussion moving on the list between now and next week's call. Our main topics of discussion today were: 1. An overview of the draft changes to the PPAA, which everyone is asked to review this week. * Action Item: I will consult with Legal regarding scope of remaining changes/work that are expected in re: the GDPR-related review (and timeline). * Action Item: IRT is asked to share any feedback with the list and bring any issues ready to discuss to the call next week. 1. How to manage PPAA provisions that are similar to or related to the Temporary Specification for gTLD Registration Data and/or the ePDP. * Action Item: I will consult with Legal regarding whether the proposed Specification 8 (or some version of it) must, in ICANN org's view, appear in this agreement, or whether some other solution to this issue could be developed. * Action Item: IRT members who have ideas for other approaches are asked to share these with the list. 1. A discussion of whether we are ready to proceed to public comment after discussion on the PPAA is complete. Ideally, we could finalize these discussions before ICANN63, but if issues need more time, we will take it. * IRT appeared to generally favor this course of action, but some IRT members raised questions about how the proposed requirements would operate under a gated access model. * IRT members would like to review how material in call for comments is presented. ICANN org agreed to provide that opportunity, provided that this will not unduly extend timeline. * Action Item: Answer on whether ICANN org views the inclusion of processing spec as a requirement may impact this decision (see Action Item (a) under 2 above). * Action Item: Any additional IRT feedback is requested on-list. * Action Item: Peter Roman, PSWG, will share proposal on-list re: treatment of data under gated access model, with goal of discussing whether this could be addressed in this IRT or some other forum. If anyone else who was on the call would like to flag other issues for those who were not in attendance, please do. I'll return my action items as quickly as possible, and look forward to continued discussion this week. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 1

Materials for tomorrow's PP IRT meeting are attached
by Amy Bivins Aug. 30, 2018

Aug. 30, 2018

Dear Colleagues, This is a reminder that the PP IRT will meet tomorrow, Thursday, 30 August, at 1600 UTC. A draft markup of the PPAA is attached. This markup is for discussion purposes only-it is not a final proposal and remains subject to revision. The draft is being circulated, without further delay, to continue the conversation. It has not been approved by senior management and is for discussion only. We would like to begin discussing the following topics tomorrow (but please feel free to comment before then on the list): 1. Some suggested edits track what's in the Temporary Specification for gTLD Registration Data. For example, section 3.5.3.3. How should we approach drafting provisions modeled on the Temp Spec, given that its language is subject to change in the near future? 2. The disclosure frameworks seem to be written from the position that there's no discretion for the Provider to not provide the underlying customer data if the conditions in the framework are met. Is this the intent? This could potentially cause issues under the GDPR, because this doesn't seem to leave room to balance the interests of the data subjects with the legitimate interest of the parties requesting personal data. 3. The disclosure frameworks raise additional GDPR-related questions that are similar to questions raised in the Draft Framework Elements of a Potential Unified Access Model<https://www.icann.org/en/system/files/files/framework-elements-unified-acce…> paper published by ICANN org. For example, what would the requirements be for logging requests for disclosure made under the frameworks (or even requests not governed by the frameworks)? 4. Do you see any other issues that you believe must be addressed related to GDPR that were not addressed in this markup? 5. Following the completion of the IRT's review of this draft accreditation agreement and related matters, we believe are ready to proceed to public comment. Do you believe there is any reason why the IRT should not proceed to public comment? 6. We have heard questions from various members of the community about how the proposed accreditation program requirements will operate within the current Temp Spec RDDS environment. These proposed program requirements do not address how PP registrations interact with a gated access model or how they might be impacted, if at all, by the results of the EPDP. Is this an issue that the IRT believes should be explored at this stage? If any member of the IRT wishes to raise any comments or points about this topic, you are encouraged to do so during the IRT call or via the list. One area that may need further attention in the agreement is specifically defining what data is to be collected and for what purpose. In addition, the new Specification 8 contains some data processing requirements, but additional discussion is needed on the appropriate controller arrangements that are needed between ICANN, the registrar and the Provider. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

7 7

Re: [Gdd-gnso-ppsai-impl] Materials for tomorrow's PP IRT meeting are attached
by Chris Pelling Aug. 29, 2018

Aug. 29, 2018

My apologies I won't be able to make tomorrow. Sent by Chris on the move. -------- Original message --------From: Amy Bivins <amy.bivins(a)icann.org> Date: 29/08/2018 14:22 (GMT+00:00) To: gdd-gnso-ppsai-impl(a)icann.org Subject: [Gdd-gnso-ppsai-impl] Materials for tomorrow's PP IRT meeting are attached Dear Colleagues, This is a reminder that the PP IRT will meet tomorrow, Thursday, 30 August, at 1600 UTC. A draft markup of the PPAA is attached. This markup is for discussion purposes only—it is not a final proposal and remains subject to revision. The draft is being circulated, without further delay, to continue the conversation. It has not been approved by senior management and is for discussion only. We would like to begin discussing the following topics tomorrow (but please feel free to comment before then on the list): Some suggested edits track what’s in the Temporary Specification for gTLD Registration Data. For example, section 3.5.3.3. How should we approach drafting provisions modeled on the Temp Spec, given that its language is subject to change in the near future?The disclosure frameworks seem to be written from the position that there’s no discretion for the Provider to not provide the underlying customer data if the conditions in the framework are met. Is this the intent? This could potentially cause issues under the GDPR, because this doesn’t seem to leave room to balance the interests of the data subjects with the legitimate interest of the parties requesting personal data.The disclosure frameworks raise additional GDPR-related questions that are similar to questions raised in the Draft Framework Elements of a Potential Unified Access Model paper published by ICANN org. For example, what would the requirements be for logging requests for disclosure made under the frameworks (or even requests not governed by the frameworks)?Do you see any other issues that you believe must be addressed related to GDPR that were not addressed in this markup?Following the completion of the IRT’s review of this draft accreditation agreement and related matters, we believe are ready to proceed to public comment. Do you believe there is any reason why the IRT should not proceed to public comment?We have heard questions from various members of the community about how the proposed accreditation program requirements will operate within the current Temp Spec RDDS environment. These proposed program requirements do not address how PP registrations interact with a gated access model or how they might be impacted, if at all, by the results of the EPDP. Is this an issue that the IRT believes should be explored at this stage? If any member of the IRT wishes to raise any comments or points about this topic, you are encouraged to do so during the IRT call or via the list. One area that may need further attention in the agreement is specifically defining what data is to be collected and for what purpose. In addition, the new Specification 8 contains some data processing requirements, but additional discussion is needed on the appropriate controller arrangements that are needed between ICANN, the registrar and the Provider. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org www.icann.org

1 0

PP IRT Standing Call Time
by Amy Bivins Aug. 22, 2018

Aug. 22, 2018

[Web Meeting] [Sponsor] Dear Colleagues, Please note that the standing call time for the Privacy and Proxy Service Provider Accreditation Program Implementation Review Team is now Thursdays at 1600 UTC. Individual occurrences will be canceled on weeks where a meeting will not be held. Adobe Connect: https://participate.icann.org/ppirt/ __________________________________________________________________ You're Invited. You've been invited to a GlobalMeet® phone only meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me <https://go.conferencinghub.com/2y4ql> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://1-605-475-5618,*,,1350875547#<tel://1-605-475-5618,*,,1350875547> Phone Only Controls: https://go.conferencinghub.com/2y4ql Primary Access Number: 1-605-475-5618 Guest Passcode: 135 087 5547 Additional Access: USA 1-605-475-5618 USA 1-719-325-2630 Canada, Calgary +1 403 407 5780 Canada, Montreal +1 514 669 5909 Canada, Toronto +1 416 915 3615 Canada, Vancouver +1 604 205 5118 Argentina, Buenos Aires +54 (0) 11 5172 6019 Argentina (toll free) 0800 800 1250 Australia, Sydney +61 (0) 2 8017 6391 Australia, Melbourne +61 (0) 3 8687 0614 Australia, Brisbane +61 (0) 7 3015 0608 Australia (toll free) 1 800 720 493 Austria, Vienna +43 (0)1 928 2722 Austria (toll free) 0800 070 841 Bahrain, Manama +973 1650 0402 Bahrain (toll free) 8008 1214 Belarus (toll free) 8 820 0011 0353 Belgium, Brussels +32 (0) 2 400 1980 Belgium (toll free) 0800 39 268 Bosnia and Herzegovina +387 7031 1461 Brazil, Sao Paulo +55 11 4935 7122 Brazil, Rio de Janeiro +55 21 4560 0023 Brazil (toll free) 0800 887 0283 Bulgaria, Sofia +359 (0) 2 491 7244 Bulgaria (toll free) 00800 111 4944 Cambodia, Phnom Penh +855 23 962 579 Canada (toll free) 1 855 950 3706 Chile, Santiago +56 (0) 2 2666 0711 Chile (toll free) 171 800 835 943 China (national) +400 681 8104 China, Beijing +86 10 5667 0005 China, Shanghai +86 21 2039 7079 Colombia, Bogota +57 1 508 8112 Colombia (toll free) 01 800 755 0043 Costa Rica (toll free) 800 542 5331 Croatia (toll free) 0800 223 004 Cyprus (toll free) 800 97400 Czech Republic, Prague +420 225 986 505 Czech Republic (toll free) 800 701 236 Denmark, Copenhagen +45 32 71 16 70 Denmark (toll free) 80 70 35 78 Egypt (toll free) 0800 000 0401 Estonia, Tallinn +372 622 6519 Estonia (toll free) 800 011 1569 Fiji (toll free) 00800 3317 Finland, Helsinki +358 (0) 9 2310 1611 Finland (toll free) 0800 772 230 France, Paris +33 (0) 1 76 77 22 50 France (toll free) 0800 946 112 France (national) 0811 655 134 France (national) 0821 231 687 Georgia, Tbilisi +995 32 2 053 082 Germany, Frankfurt +49 (0) 69 5060 9515 Germany, Munich +49 (0) 89 24443 2900 Germany (national) 01801 001 378 Germany (toll free) 0800 588 9225 Greece, Athens +30 211 181 3815 Greece (toll free) 00800 128 811 Hong Kong +852 3018 9103 Hong Kong (toll free) 800 968 082 Hungary, Budapest +36 1 808 8134 Hungary (toll free) 068 001 9662 Iceland (toll free) 800 9841 India, Delhi +91 11 6310 0272 India, Mumbai +91 22 6310 0274 India, Chennai +91 44 6310 0227 India, Bangalore +91 80 6760 8747 India (toll free) 1800 3010 1564 Indonesia, Jakarta +62 21 2188 9079 Indonesia (toll free) 007 803 321 8120 Ireland, Dublin +353 (0) 1 246 5614 Ireland (national) 0818 270 287 Ireland (toll free) 1800 937 695 Ireland (national) 1890 907 722 Israel, Tel Aviv +972 (0)3 763 0384 Israel (toll free) 180 921 2890 Italy, Milan +39 02 3046 4837 Italy, Rome +39 06 4523 6635 Italy (toll free) 800 148 288 Japan, Tokyo +81 3 4560 1274 Japan, Osaka +81 6 4560 0303 Japan (mobile) 0120 270 611 Japan (toll free) 0120 286 011 Japan (national) 0570 005 744 Jordan (toll free) 0800 22156 Kazakhstan (toll free) 8800 333 7552 Kenya, Nairobi +254 (0)207 643 596 South Korea, Seoul +82 (0) 2 6007 0072 South Korea (toll free) 007 986 136 2233 Kuwait (national) +965 2206 3083 Latvia, Riga +371 6778 2598 Latvia (toll free) 8000 4374 Lithuania, Vilnius +370 5205 5239 Lithuania (toll free) 8800 31445 Luxembourg +352 2730 2276 Luxembourg (toll free) 800 28428 Macau (national) +853 6262 1674 Malaysia, Kuala Lumpur +60 (0) 3 7723 7140 Malaysia (toll free) 1 800 815 805 Mexico, Guadalajara +52 33 4162 5891 Mexico, Mexico City +52 55 8421 0857 Mexico, Monterrey +52 81 4770 2472 Mexico (toll free) 01 800 283 3129 Morocco, Casablanca +212 (0)520 480 128 Morocco (toll free) 0800 092 258 Netherlands, Amsterdam +31 (0) 20 716 8266 Netherlands (toll free) 0800 020 0593 New Zealand, Christchurch +64 (0) 3 974 2597 New Zealand, Wellington +64 (0) 4 909 4676 New Zealand, Auckland +64 (0) 9 929 1769 New Zealand (toll free) 0800 459 127 Nigeria, Lagos +234 1 277 5140 Norway, Oslo +47 2162 4054 Norway (toll free) 800 58459 Oman (toll free) 800 77269 Pakistan, Islamabad +92 5181 08874 Panama, Panama City +507 8 339 782 Panama (toll free) 00800 223 1430 Peru, Lima +51 (0) 1 700 9587 Peru (toll free) 0800 78125 Philippines, Manila +63 (0)2 395 3365 Philippines (toll free) 1800 111 017 51 Poland, Warsaw +48 22 295 3504 Poland (toll free) 00800 121 4340 Portugal, Lisbon +351 21 316 4041 Portugal (toll free) 800 784 434 Qatar (freephone) 00 800 100 499 Romania, Bucharest +40 (0) 21 529 3969 Romania (toll free) 0800 801 030 Russia, Moscow +7 495 213 0988 Russia (toll free) 8 800 500 9319 Saudi Arabia (toll free) 800 844 4963 Saudi Arabia (toll free) 800 850 0227 Serbia (toll free) 0800 190 698 Singapore +65 6654 9111 Singapore (toll free) 800 616 3175 Slovakia, Bratislava +421 (0)2 3321 5333 Slovakia (toll free) 0800 001 661 Slovenia, Ljubljana +386 1 600 1622 Slovenia (toll free) 0800 80994 South Africa, Johannesburg +27 (0)11 019 7087 South Africa (toll free) 0800 988 886 Spain, Madrid +34 91 114 6640 Spain, Barcelona +34 93 800 1935 Spain (toll free) 900 803 689 Sri Lanka, Sri Lanka +94 720 910 348 Sweden, Stockholm +46 (0) 8 5065 3944 Sweden (toll free) 0200 125 456 Switzerland, Geneva +41 (0) 22 595 4857 Switzerland, Zurich +41 (0) 44 580 7246 Switzerland (toll free) 0800 841 702 Taiwan, Taipei +886 (0) 2 2656 7213 Taiwan (toll free) 00 801 615 184 Thailand, Bangkok +66 (0) 2104 0767 Thailand (toll free) 1 800 012 172 Tunisia, Tunis +216 31 378 109 Turkey, Istanbul +90 212 375 50 13 Turkey (toll free) 00 800 448 828 358 Ukraine (toll free) 0800 500 732 UAE (toll free) 8000 3570 2638 UK (03) +44 (0)330 336 6010 UK (toll free) 0800 368 0950 UK (national) 0844 473 5003 UK (national) 0845 545 0040 USA /Canada (toll free) 1-855-747-8824 Uruguay (toll free) 0004 019 0561 Venezuela, Caracas +58 212 720 2342 Venezuela (toll free) 0800 102 9660 Vietnam, Hanoi +84 24 4458 3323 Vietnam, Ho Chi Minh +84 28 4458 1333 Vietnam (toll free) 1800 9228 Questions? Go to GlobalMeet Support<http://community.globalmeet.com> © Premiere Global Services, Inc. and/or its affiliates | PGi

1 0

PP IRT Standing Call Time
by Amy Bivins Aug. 22, 2018

Aug. 22, 2018

[Web Meeting] [Sponsor] Dear Colleagues, Please note that the standing call time for the Privacy and Proxy Service Provider Accreditation Program Implementation Review Team is now Thursdays at 1600 UTC. Individual occurrences will be canceled on weeks where a meeting will not be held. Adobe Connect: https://participate.icann.org/ppirt/ __________________________________________________________________ You're Invited. You've been invited to a GlobalMeet® phone only meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me <https://go.conferencinghub.com/2y4ql> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://1-605-475-5618,*,,1350875547#<tel://1-605-475-5618,*,,1350875547> Phone Only Controls: https://go.conferencinghub.com/2y4ql Primary Access Number: 1-605-475-5618 Guest Passcode: 135 087 5547 Additional Access: USA 1-605-475-5618 USA 1-719-325-2630 Canada, Calgary +1 403 407 5780 Canada, Montreal +1 514 669 5909 Canada, Toronto +1 416 915 3615 Canada, Vancouver +1 604 205 5118 Argentina, Buenos Aires +54 (0) 11 5172 6019 Argentina (toll free) 0800 800 1250 Australia, Sydney +61 (0) 2 8017 6391 Australia, Melbourne +61 (0) 3 8687 0614 Australia, Brisbane +61 (0) 7 3015 0608 Australia (toll free) 1 800 720 493 Austria, Vienna +43 (0)1 928 2722 Austria (toll free) 0800 070 841 Bahrain, Manama +973 1650 0402 Bahrain (toll free) 8008 1214 Belarus (toll free) 8 820 0011 0353 Belgium, Brussels +32 (0) 2 400 1980 Belgium (toll free) 0800 39 268 Bosnia and Herzegovina +387 7031 1461 Brazil, Sao Paulo +55 11 4935 7122 Brazil, Rio de Janeiro +55 21 4560 0023 Brazil (toll free) 0800 887 0283 Bulgaria, Sofia +359 (0) 2 491 7244 Bulgaria (toll free) 00800 111 4944 Cambodia, Phnom Penh +855 23 962 579 Canada (toll free) 1 855 950 3706 Chile, Santiago +56 (0) 2 2666 0711 Chile (toll free) 171 800 835 943 China (national) +400 681 8104 China, Beijing +86 10 5667 0005 China, Shanghai +86 21 2039 7079 Colombia, Bogota +57 1 508 8112 Colombia (toll free) 01 800 755 0043 Costa Rica (toll free) 800 542 5331 Croatia (toll free) 0800 223 004 Cyprus (toll free) 800 97400 Czech Republic, Prague +420 225 986 505 Czech Republic (toll free) 800 701 236 Denmark, Copenhagen +45 32 71 16 70 Denmark (toll free) 80 70 35 78 Egypt (toll free) 0800 000 0401 Estonia, Tallinn +372 622 6519 Estonia (toll free) 800 011 1569 Fiji (toll free) 00800 3317 Finland, Helsinki +358 (0) 9 2310 1611 Finland (toll free) 0800 772 230 France, Paris +33 (0) 1 76 77 22 50 France (toll free) 0800 946 112 France (national) 0811 655 134 France (national) 0821 231 687 Georgia, Tbilisi +995 32 2 053 082 Germany, Frankfurt +49 (0) 69 5060 9515 Germany, Munich +49 (0) 89 24443 2900 Germany (national) 01801 001 378 Germany (toll free) 0800 588 9225 Greece, Athens +30 211 181 3815 Greece (toll free) 00800 128 811 Hong Kong +852 3018 9103 Hong Kong (toll free) 800 968 082 Hungary, Budapest +36 1 808 8134 Hungary (toll free) 068 001 9662 Iceland (toll free) 800 9841 India, Delhi +91 11 6310 0272 India, Mumbai +91 22 6310 0274 India, Chennai +91 44 6310 0227 India, Bangalore +91 80 6760 8747 India (toll free) 1800 3010 1564 Indonesia, Jakarta +62 21 2188 9079 Indonesia (toll free) 007 803 321 8120 Ireland, Dublin +353 (0) 1 246 5614 Ireland (national) 0818 270 287 Ireland (toll free) 1800 937 695 Ireland (national) 1890 907 722 Israel, Tel Aviv +972 (0)3 763 0384 Israel (toll free) 180 921 2890 Italy, Milan +39 02 3046 4837 Italy, Rome +39 06 4523 6635 Italy (toll free) 800 148 288 Japan, Tokyo +81 3 4560 1274 Japan, Osaka +81 6 4560 0303 Japan (mobile) 0120 270 611 Japan (toll free) 0120 286 011 Japan (national) 0570 005 744 Jordan (toll free) 0800 22156 Kazakhstan (toll free) 8800 333 7552 Kenya, Nairobi +254 (0)207 643 596 South Korea, Seoul +82 (0) 2 6007 0072 South Korea (toll free) 007 986 136 2233 Kuwait (national) +965 2206 3083 Latvia, Riga +371 6778 2598 Latvia (toll free) 8000 4374 Lithuania, Vilnius +370 5205 5239 Lithuania (toll free) 8800 31445 Luxembourg +352 2730 2276 Luxembourg (toll free) 800 28428 Macau (national) +853 6262 1674 Malaysia, Kuala Lumpur +60 (0) 3 7723 7140 Malaysia (toll free) 1 800 815 805 Mexico, Guadalajara +52 33 4162 5891 Mexico, Mexico City +52 55 8421 0857 Mexico, Monterrey +52 81 4770 2472 Mexico (toll free) 01 800 283 3129 Morocco, Casablanca +212 (0)520 480 128 Morocco (toll free) 0800 092 258 Netherlands, Amsterdam +31 (0) 20 716 8266 Netherlands (toll free) 0800 020 0593 New Zealand, Christchurch +64 (0) 3 974 2597 New Zealand, Wellington +64 (0) 4 909 4676 New Zealand, Auckland +64 (0) 9 929 1769 New Zealand (toll free) 0800 459 127 Nigeria, Lagos +234 1 277 5140 Norway, Oslo +47 2162 4054 Norway (toll free) 800 58459 Oman (toll free) 800 77269 Pakistan, Islamabad +92 5181 08874 Panama, Panama City +507 8 339 782 Panama (toll free) 00800 223 1430 Peru, Lima +51 (0) 1 700 9587 Peru (toll free) 0800 78125 Philippines, Manila +63 (0)2 395 3365 Philippines (toll free) 1800 111 017 51 Poland, Warsaw +48 22 295 3504 Poland (toll free) 00800 121 4340 Portugal, Lisbon +351 21 316 4041 Portugal (toll free) 800 784 434 Qatar (freephone) 00 800 100 499 Romania, Bucharest +40 (0) 21 529 3969 Romania (toll free) 0800 801 030 Russia, Moscow +7 495 213 0988 Russia (toll free) 8 800 500 9319 Saudi Arabia (toll free) 800 844 4963 Saudi Arabia (toll free) 800 850 0227 Serbia (toll free) 0800 190 698 Singapore +65 6654 9111 Singapore (toll free) 800 616 3175 Slovakia, Bratislava +421 (0)2 3321 5333 Slovakia (toll free) 0800 001 661 Slovenia, Ljubljana +386 1 600 1622 Slovenia (toll free) 0800 80994 South Africa, Johannesburg +27 (0)11 019 7087 South Africa (toll free) 0800 988 886 Spain, Madrid +34 91 114 6640 Spain, Barcelona +34 93 800 1935 Spain (toll free) 900 803 689 Sri Lanka, Sri Lanka +94 720 910 348 Sweden, Stockholm +46 (0) 8 5065 3944 Sweden (toll free) 0200 125 456 Switzerland, Geneva +41 (0) 22 595 4857 Switzerland, Zurich +41 (0) 44 580 7246 Switzerland (toll free) 0800 841 702 Taiwan, Taipei +886 (0) 2 2656 7213 Taiwan (toll free) 00 801 615 184 Thailand, Bangkok +66 (0) 2104 0767 Thailand (toll free) 1 800 012 172 Tunisia, Tunis +216 31 378 109 Turkey, Istanbul +90 212 375 50 13 Turkey (toll free) 00 800 448 828 358 Ukraine (toll free) 0800 500 732 UAE (toll free) 8000 3570 2638 UK (03) +44 (0)330 336 6010 UK (toll free) 0800 368 0950 UK (national) 0844 473 5003 UK (national) 0845 545 0040 USA /Canada (toll free) 1-855-747-8824 Uruguay (toll free) 0004 019 0561 Venezuela, Caracas +58 212 720 2342 Venezuela (toll free) 0800 102 9660 Vietnam, Hanoi +84 24 4458 3323 Vietnam, Ho Chi Minh +84 28 4458 1333 Vietnam (toll free) 1800 9228 Questions? Go to GlobalMeet Support<http://community.globalmeet.com> © Premiere Global Services, Inc. and/or its affiliates | PGi

1 0

PP IRT Standing Call Time
by Amy Bivins Aug. 22, 2018

Aug. 22, 2018

[Web Meeting] [Sponsor] Dear Colleagues, Please note that the standing call time for the Privacy and Proxy Service Provider Accreditation Program Implementation Review Team is now Thursdays at 1600 UTC. Individual occurrences will be canceled on weeks where a meeting will not be held. Adobe Connect: https://participate.icann.org/ppirt/ __________________________________________________________________ You're Invited. You've been invited to a GlobalMeet® phone only meeting. Have the meeting call you. Click the Connect Me link below. No need to dial-in. Connect Me <https://go.conferencinghub.com/2y4ql> Not at your computer? You can join by dialing one of the access numbers below. Mobile: tel://1-605-475-5618,*,,1350875547#<tel://1-605-475-5618,*,,1350875547> Phone Only Controls: https://go.conferencinghub.com/2y4ql Primary Access Number: 1-605-475-5618 Guest Passcode: 135 087 5547 Additional Access: USA 1-605-475-5618 USA 1-719-325-2630 Canada, Calgary +1 403 407 5780 Canada, Montreal +1 514 669 5909 Canada, Toronto +1 416 915 3615 Canada, Vancouver +1 604 205 5118 Argentina, Buenos Aires +54 (0) 11 5172 6019 Argentina (toll free) 0800 800 1250 Australia, Sydney +61 (0) 2 8017 6391 Australia, Melbourne +61 (0) 3 8687 0614 Australia, Brisbane +61 (0) 7 3015 0608 Australia (toll free) 1 800 720 493 Austria, Vienna +43 (0)1 928 2722 Austria (toll free) 0800 070 841 Bahrain, Manama +973 1650 0402 Bahrain (toll free) 8008 1214 Belarus (toll free) 8 820 0011 0353 Belgium, Brussels +32 (0) 2 400 1980 Belgium (toll free) 0800 39 268 Bosnia and Herzegovina +387 7031 1461 Brazil, Sao Paulo +55 11 4935 7122 Brazil, Rio de Janeiro +55 21 4560 0023 Brazil (toll free) 0800 887 0283 Bulgaria, Sofia +359 (0) 2 491 7244 Bulgaria (toll free) 00800 111 4944 Cambodia, Phnom Penh +855 23 962 579 Canada (toll free) 1 855 950 3706 Chile, Santiago +56 (0) 2 2666 0711 Chile (toll free) 171 800 835 943 China (national) +400 681 8104 China, Beijing +86 10 5667 0005 China, Shanghai +86 21 2039 7079 Colombia, Bogota +57 1 508 8112 Colombia (toll free) 01 800 755 0043 Costa Rica (toll free) 800 542 5331 Croatia (toll free) 0800 223 004 Cyprus (toll free) 800 97400 Czech Republic, Prague +420 225 986 505 Czech Republic (toll free) 800 701 236 Denmark, Copenhagen +45 32 71 16 70 Denmark (toll free) 80 70 35 78 Egypt (toll free) 0800 000 0401 Estonia, Tallinn +372 622 6519 Estonia (toll free) 800 011 1569 Fiji (toll free) 00800 3317 Finland, Helsinki +358 (0) 9 2310 1611 Finland (toll free) 0800 772 230 France, Paris +33 (0) 1 76 77 22 50 France (toll free) 0800 946 112 France (national) 0811 655 134 France (national) 0821 231 687 Georgia, Tbilisi +995 32 2 053 082 Germany, Frankfurt +49 (0) 69 5060 9515 Germany, Munich +49 (0) 89 24443 2900 Germany (national) 01801 001 378 Germany (toll free) 0800 588 9225 Greece, Athens +30 211 181 3815 Greece (toll free) 00800 128 811 Hong Kong +852 3018 9103 Hong Kong (toll free) 800 968 082 Hungary, Budapest +36 1 808 8134 Hungary (toll free) 068 001 9662 Iceland (toll free) 800 9841 India, Delhi +91 11 6310 0272 India, Mumbai +91 22 6310 0274 India, Chennai +91 44 6310 0227 India, Bangalore +91 80 6760 8747 India (toll free) 1800 3010 1564 Indonesia, Jakarta +62 21 2188 9079 Indonesia (toll free) 007 803 321 8120 Ireland, Dublin +353 (0) 1 246 5614 Ireland (national) 0818 270 287 Ireland (toll free) 1800 937 695 Ireland (national) 1890 907 722 Israel, Tel Aviv +972 (0)3 763 0384 Israel (toll free) 180 921 2890 Italy, Milan +39 02 3046 4837 Italy, Rome +39 06 4523 6635 Italy (toll free) 800 148 288 Japan, Tokyo +81 3 4560 1274 Japan, Osaka +81 6 4560 0303 Japan (mobile) 0120 270 611 Japan (toll free) 0120 286 011 Japan (national) 0570 005 744 Jordan (toll free) 0800 22156 Kazakhstan (toll free) 8800 333 7552 Kenya, Nairobi +254 (0)207 643 596 South Korea, Seoul +82 (0) 2 6007 0072 South Korea (toll free) 007 986 136 2233 Kuwait (national) +965 2206 3083 Latvia, Riga +371 6778 2598 Latvia (toll free) 8000 4374 Lithuania, Vilnius +370 5205 5239 Lithuania (toll free) 8800 31445 Luxembourg +352 2730 2276 Luxembourg (toll free) 800 28428 Macau (national) +853 6262 1674 Malaysia, Kuala Lumpur +60 (0) 3 7723 7140 Malaysia (toll free) 1 800 815 805 Mexico, Guadalajara +52 33 4162 5891 Mexico, Mexico City +52 55 8421 0857 Mexico, Monterrey +52 81 4770 2472 Mexico (toll free) 01 800 283 3129 Morocco, Casablanca +212 (0)520 480 128 Morocco (toll free) 0800 092 258 Netherlands, Amsterdam +31 (0) 20 716 8266 Netherlands (toll free) 0800 020 0593 New Zealand, Christchurch +64 (0) 3 974 2597 New Zealand, Wellington +64 (0) 4 909 4676 New Zealand, Auckland +64 (0) 9 929 1769 New Zealand (toll free) 0800 459 127 Nigeria, Lagos +234 1 277 5140 Norway, Oslo +47 2162 4054 Norway (toll free) 800 58459 Oman (toll free) 800 77269 Pakistan, Islamabad +92 5181 08874 Panama, Panama City +507 8 339 782 Panama (toll free) 00800 223 1430 Peru, Lima +51 (0) 1 700 9587 Peru (toll free) 0800 78125 Philippines, Manila +63 (0)2 395 3365 Philippines (toll free) 1800 111 017 51 Poland, Warsaw +48 22 295 3504 Poland (toll free) 00800 121 4340 Portugal, Lisbon +351 21 316 4041 Portugal (toll free) 800 784 434 Qatar (freephone) 00 800 100 499 Romania, Bucharest +40 (0) 21 529 3969 Romania (toll free) 0800 801 030 Russia, Moscow +7 495 213 0988 Russia (toll free) 8 800 500 9319 Saudi Arabia (toll free) 800 844 4963 Saudi Arabia (toll free) 800 850 0227 Serbia (toll free) 0800 190 698 Singapore +65 6654 9111 Singapore (toll free) 800 616 3175 Slovakia, Bratislava +421 (0)2 3321 5333 Slovakia (toll free) 0800 001 661 Slovenia, Ljubljana +386 1 600 1622 Slovenia (toll free) 0800 80994 South Africa, Johannesburg +27 (0)11 019 7087 South Africa (toll free) 0800 988 886 Spain, Madrid +34 91 114 6640 Spain, Barcelona +34 93 800 1935 Spain (toll free) 900 803 689 Sri Lanka, Sri Lanka +94 720 910 348 Sweden, Stockholm +46 (0) 8 5065 3944 Sweden (toll free) 0200 125 456 Switzerland, Geneva +41 (0) 22 595 4857 Switzerland, Zurich +41 (0) 44 580 7246 Switzerland (toll free) 0800 841 702 Taiwan, Taipei +886 (0) 2 2656 7213 Taiwan (toll free) 00 801 615 184 Thailand, Bangkok +66 (0) 2104 0767 Thailand (toll free) 1 800 012 172 Tunisia, Tunis +216 31 378 109 Turkey, Istanbul +90 212 375 50 13 Turkey (toll free) 00 800 448 828 358 Ukraine (toll free) 0800 500 732 UAE (toll free) 8000 3570 2638 UK (03) +44 (0)330 336 6010 UK (toll free) 0800 368 0950 UK (national) 0844 473 5003 UK (national) 0845 545 0040 USA /Canada (toll free) 1-855-747-8824 Uruguay (toll free) 0004 019 0561 Venezuela, Caracas +58 212 720 2342 Venezuela (toll free) 0800 102 9660 Vietnam, Hanoi +84 24 4458 3323 Vietnam, Ho Chi Minh +84 28 4458 1333 Vietnam (toll free) 1800 9228 Questions? Go to GlobalMeet Support<http://community.globalmeet.com> © Premiere Global Services, Inc. and/or its affiliates | PGi

1 0

Status update on PP Legal Review
by Amy Bivins Aug. 22, 2018

Aug. 22, 2018

Dear Colleagues, I hope you are well. I wanted to update you that ICANN has received the external legal review back on the PP program materials. The internal team is currently reviewing and I expect that we will be ready to bring items back for discussion during our regular 1400 UTC call time on 28 August. In the interim, if you have any comments, issues, or concerns, please don't hesitate to raise them on the list or to contact me directly. Thanks, and have a great weekend. Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

5 8

Updated PP De-Accreditation Procedure Document Attached for IRT review
by Amy Bivins Aug. 7, 2018

Aug. 7, 2018

Dear Colleagues, Attached you will find a new draft of the PP De-accreditation and transition procedure, updated based on IRT feedback and our final (prior to public comment) internal review. If you have any further questions or comments on this document, please send them to the list. We're nearly finished with the final editing/review process for the applicant guide and fees document, as well (there will be copy edits but no significant substantive changes). I'll send those to the list as soon as they are complete, likely before the end of this week. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

9 21

PP IRT Action Items This Week (No Meeting)
by Amy Bivins July 30, 2018

July 30, 2018

Dear Colleagues, Following up on the draft de-accreditation process document that was sent to the list (thread attached), if anyone has further feedback, please send it to the list this week. In the interim, I've taken the feedback raised in this thread back to the internal team for discussion. The legal/GDPR-related review is proceeding, and I should be able to share more information with you soon. The drafting is taking some time to work through. I'm expecting that we should be ready to discuss that and the remaining data escrow-related materials later in August. In the interim, if you have a PP IRT meeting invite showing as a series on your calendar, can you please delete it? My phone bridge information has been updated so I will need to distribute a new series ahead of our next meeting. Thanks so much. Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

Updated PP Fees Proposal Document Attached
by Amy Bivins July 27, 2018

July 27, 2018

Dear Colleagues, Attached is a slightly updated version of the fees proposal document, updated to reflect IRT feedback (see, specifically, p. 3) to date in preparation for publishing this for public comment. If you have any further comments, please send them to the list. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 1

Canceled: Privacy and Proxy Service Provider Accreditation Program IRT (new series)
by Amy Bivins July 23, 2018

July 23, 2018

Dear Colleagues, Please find below the remote participation details for the Privacy and Proxy Services Accreditation Program IRT Meetings which will be held WEEKLY on Tuesdays, starting on 29 November 2016 at 14:00 UTC for 1 hour. Adobe Connect link: https://participate.icann.org/ppirt Participant code: 4824695647 Dial-In Phone Numbers: US: +1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina (toll free): 0800 800 1223 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Australia (toll free): 1 800 804 786 Australia, Brisbane: +61 (0) 7 3015 0535 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Sydney: +61 (0) 2 8017 6064 Austria (toll free): 0800 8866 3413 Austria, Vienna: +43 (0) 1 25302 1785 Bahrain (toll free): 800 04212 Bahrain, Manama: +973 1619 8739 Belarus (toll free): 8 820 0011 0341 Belgium (toll free): 0800 39279 Belgium, Brussels: +32 (0) 2 400 6928 Brazil (toll free): 0800 887 0233 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil, Sao Paulo: +55 11 4935 7169 Bulgaria (toll free): 00800 111 4950 Bulgaria, Sofia: +359 (0) 2 491 6045 Canada (toll free): 1 855 950 3717 Chile (toll free): 171 800 835 783 Chile, Santiago: +56 (0) 2 2666 0696 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia (toll free): 01 800 755 0102 Colombia, Bogota: +57 1 508 8137 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic (toll free): 800 701 532 Czech Republic, Prague: +420 225 986 554 Denmark (toll free): 80 70 35 86 Denmark, Copenhagen: +45 32 72 78 10 Egypt (toll free): 0800 000 0593 Estonia (toll free): 800 011 1589 Estonia, Tallinn: +372 622 6551 Fiji (toll free): 00800 3322 Finland (toll free): 0800 772 236 Finland, Helsinki: +358 (0) 9 2310 1677 France (national): 0811 655 100 France (toll free): 0800 946 531 France, Paris: +33 (0) 1 70 37 16 56 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Greece (toll free): 00800 128 913 Greece, Athens: +30 211 181 3824 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary (toll free): 068 001 9673 Hungary, Budapest: +36 1408 8953 Iceland (toll free): 800 9847 India, Bangalore: +91 (0) 80 6127 6710 India, Chennai: +91 (0)44 6688 6061 India, Delhi: +91 (0) 11 6641 1394 India, Mumbai: +91 (0)22 6187 5028 Indonesia (toll free): 007 803 321 8927 Ireland (national): 1890 907 630 Ireland (toll free): 1800 937 649 Ireland, Dublin: +353 (0) 1 526 9421 Israel (toll free): 1809 213 168 Israel, Tel Aviv: +972 (0)3 721 7943 Italy (toll free): 800 146 094 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Japan (mobile): 0120 632 611 Japan (toll free): 0120 305 211 Japan, Osaka: +81 (0) 6 4560 2410 Japan, Tokyo: +81 (0) 3 4560 1270 Kazakhstan (toll free): 8800 333 7554 Latvia (toll free): 8000 4418 Latvia, Riga: +371 6601 3627 Lithuania (toll free): 8800 31449 Lithuania, Vilnius: +370 5205 5468 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Malaysia (toll free): 1 800 816 152 Malaysia,Kuala Lumpur: +60 (0) 3 7724 8010 Mexico (toll free): 01 800 733 4102 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Morocco (toll free): 0800 091 296 Morocco, Casablanca: +212 (0) 520 48 0022 Netherlands (toll free): 0800 020 2597 Netherlands, Amsterdam: +31 (0) 20 716 8345 New Zealand (toll free): 0800 452 947 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 Nigeria, Lagos: +234 1 277 3944 Norway (toll free): 800 56081 Norway, Oslo: +47 21 00 48 15 Panama (toll free): 00800 223 1390 Panama, Panama City: +507 8 335 913 Peru, Lima: +51 (0) 1 700 9571 Philippines (toll free): 1 800 111 013 99 Philippines, Manila: +63 (0)2 395 3426 Poland (toll free): 00 800 121 4356 Poland, Warsaw: +48 22 295 3570 Portugal (toll free): 800 784 442 Portugal, Lisbon: +351 21 316 4093 Qatar (toll free): 00 800 100 491 Romania (toll free): 0800 801 035 Romania, Bucharest: +40 (0) 21 529 3992 Russia (toll free): 8 800 500 9241 Russia, Moscow: +7 495 646 9181 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Singapore: +65 6622 1957 Singapore (toll free): 800 616 3192 Slovakia (toll free): 0800 002 002 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovenia (toll free): 0800 81193 Slovenia, Ljubljana: +386 1600 8695 South Africa (toll free): 0800 999 434 South Africa, Johannesburg: +27 (0)11 589 8321 South Korea (toll free): 00798 6136 1454 South Korea, Seoul: +82 (0) 2 6007 0079 Spain (toll free): 900 828 035 Spain, Barcelona: +34 93 800 1946 Spain, Madrid: +34 91 114 6653 Sweden (toll free): 0200 125 588 Sweden, Stockholm: +46 (0) 8 5065 3956 Switzerland (toll free): 0800 740 360 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Taiwan (toll free): 0800 666 596 Taiwan, Taipei: +886 (0) 2 2650 7329 Thailand (toll free): 001 800 6136 1473 Turkey (toll free): 00800 4488 26642 Turkey, Istanbul: +90 212 375 50 49 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 Ukraine (toll free): 0800 500 896 Uruguay (toll free): 0004 019 0152 USA /Canada (toll free): 1-866-398-2885 Venezuela (toll free): 0 800 162 7451 Vietnam (toll free): 1800 9226 Costa Rica (toll free): 800 542 5328 France (national): 0821 231 671 India (toll free): 1800 200 9415 Indonesia, Jakarta: +62 21 2188 9084 Ireland (national): 0818 270 271 Japan (national): 0570 085 744 Serbia (toll free): 0800 190 712 UK (national): 0844 473 5010 UK (national): 0845 545 0015 Venezuela, Caracas: +58 212 720 2164

1 0

No PP IRT meeting tomorrow
by Amy Bivins July 23, 2018

July 23, 2018

Dear Colleagues, We will not have a Privacy/Proxy IRT meeting tomorrow. I'll provide you with a status update on the remaining outstanding items later this week. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

Re: [Gdd-gnso-ppsai-impl] PP IRT status update; no meeting Tuesday
by Sara Bockey July 18, 2018

July 18, 2018

Hi Amy, I’m a little unclear as to how we intend the Privacy/Proxy Accreditation Agreement to dictate the terms for data processing, as this is something that will need to be agreed to between the Registrar and the Privacy/Proxy Provider, unless the intent is to create a standard set of terms that are included as a model, but capable of being modified or supplemented by the Registrar? If so, then perhaps this should be handled similar to that of the recent RRA Amendment, which adds appropriate data processing terms to the RAA (via the form and process outlined here https://www.icann.org/en/system/files/files/rra-amendment-terms-temp-spec-0…) It would differ in that these terms could be directly incorporated into the P/P Accreditation Agreement, rather than via an amendment as in the case of the previously executed RAAs, and the form and substance would need to be modified for these particular purposes, but the concept of “model clauses” might be viable. In any event, we do not believe use of Section 4 of the Temp Specification is adequate or appropriate for these purposes. Sara sara bockey sr. policy manager | GoDaddy™ sbockey(a)godaddy.com<mailto:sbockey@godaddy.com> 480-366-3616 skype: sbockey This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments. From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Thursday, July 12, 2018 at 12:13 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] PP IRT status update; no meeting Tuesday Dear Colleagues, We will not have a PP IRT meeting on Tuesday, 17 July. Our next meeting is scheduled for Tuesday, 24 July. The Legal review of the current PPAA draft is not yet complete. However, I do have an update on the GDPR-related work. We believe that we will likely need to add data processing provisions in the PP materials—potentially in the policy document. We are planning to begin drafting this, for discussion with you, using Section 4 of the Temporary Specification<https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#4> as a model for adaptation. If you have other ideas or recommendations for this initial drafting exercise, please let us know. We can discuss this at our next meeting. A data processing addendum may also be needed for the PPAA. In addition, we are also considering how to address data processing in data escrow agreements. I should have more to share on that with you by our next meeting. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

3 2

PP IRT status update; no meeting Tuesday
by Amy Bivins July 13, 2018

July 13, 2018

Dear Colleagues, We will not have a PP IRT meeting on Tuesday, 17 July. Our next meeting is scheduled for Tuesday, 24 July. The Legal review of the current PPAA draft is not yet complete. However, I do have an update on the GDPR-related work. We believe that we will likely need to add data processing provisions in the PP materials-potentially in the policy document. We are planning to begin drafting this, for discussion with you, using Section 4 of the Temporary Specification<https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#4> as a model for adaptation. If you have other ideas or recommendations for this initial drafting exercise, please let us know. We can discuss this at our next meeting. A data processing addendum may also be needed for the PPAA. In addition, we are also considering how to address data processing in data escrow agreements. I should have more to share on that with you by our next meeting. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

3 3

Privacy and Proxy Service Provider Accreditation Program IRT (new series)
by Amy Bivins July 9, 2018

July 9, 2018

Dear Colleagues, Please find below the remote participation details for the Privacy and Proxy Services Accreditation Program IRT Meetings which will be held WEEKLY on Tuesdays, starting on 29 November 2016 at 14:00 UTC for 1 hour. Adobe Connect link: https://participate.icann.org/ppirt Participant code: 4824695647 Dial-In Phone Numbers: US: +1-719-457-6209 Canada, Calgary: +1 403 407 5793 Canada, Montreal: +1 514 669 5928 Canada, Toronto: +1 647 426 9172 Canada, Vancouver: +1 604 222 7836 Argentina (toll free): 0800 800 1223 Argentina, Buenos Aires: +54 (0) 11 5172 6003 Australia (toll free): 1 800 804 786 Australia, Brisbane: +61 (0) 7 3015 0535 Australia, Melbourne: +61 (0) 3 8687 0553 Australia, Sydney: +61 (0) 2 8017 6064 Austria (toll free): 0800 8866 3413 Austria, Vienna: +43 (0) 1 25302 1785 Bahrain (toll free): 800 04212 Bahrain, Manama: +973 1619 8739 Belarus (toll free): 8 820 0011 0341 Belgium (toll free): 0800 39279 Belgium, Brussels: +32 (0) 2 400 6928 Brazil (toll free): 0800 887 0233 Brazil, Rio de Janeiro: +55 21 4560 0072 Brazil, Sao Paulo: +55 11 4935 7169 Bulgaria (toll free): 00800 111 4950 Bulgaria, Sofia: +359 (0) 2 491 6045 Canada (toll free): 1 855 950 3717 Chile (toll free): 171 800 835 783 Chile, Santiago: +56 (0) 2 2666 0696 China (national): +400 613 8103 China, Beijing: +86 10 5667 0003 China, Shanghai: +86 21 2039 7081 Colombia (toll free): 01 800 755 0102 Colombia, Bogota: +57 1 508 8137 Croatia (toll free): 0800 805 940 Cyprus (toll free): 800 97424 Czech Republic (toll free): 800 701 532 Czech Republic, Prague: +420 225 986 554 Denmark (toll free): 80 70 35 86 Denmark, Copenhagen: +45 32 72 78 10 Egypt (toll free): 0800 000 0593 Estonia (toll free): 800 011 1589 Estonia, Tallinn: +372 622 6551 Fiji (toll free): 00800 3322 Finland (toll free): 0800 772 236 Finland, Helsinki: +358 (0) 9 2310 1677 France (national): 0811 655 100 France (toll free): 0800 946 531 France, Paris: +33 (0) 1 70 37 16 56 Germany (national): 01801 003 899 Germany (toll free): 0800 588 9170 Germany, Frankfurt: +49 (0) 69 2222 10612 Germany, Munich: +49 (0) 89 2030 31207 Greece (toll free): 00800 128 913 Greece, Athens: +30 211 181 3824 Hong Kong: +852 3018 9111 Hong Kong (toll free): 800 901 787 Hungary (toll free): 068 001 9673 Hungary, Budapest: +36 1408 8953 Iceland (toll free): 800 9847 India, Bangalore: +91 (0) 80 6127 6710 India, Chennai: +91 (0)44 6688 6061 India, Delhi: +91 (0) 11 6641 1394 India, Mumbai: +91 (0)22 6187 5028 Indonesia (toll free): 007 803 321 8927 Ireland (national): 1890 907 630 Ireland (toll free): 1800 937 649 Ireland, Dublin: +353 (0) 1 526 9421 Israel (toll free): 1809 213 168 Israel, Tel Aviv: +972 (0)3 721 7943 Italy (toll free): 800 146 094 Italy, Milan: +39 02 3600 8006 Italy, Rome: +39 06 8750 0676 Japan (mobile): 0120 632 611 Japan (toll free): 0120 305 211 Japan, Osaka: +81 (0) 6 4560 2410 Japan, Tokyo: +81 (0) 3 4560 1270 Kazakhstan (toll free): 8800 333 7554 Latvia (toll free): 8000 4418 Latvia, Riga: +371 6601 3627 Lithuania (toll free): 8800 31449 Lithuania, Vilnius: +370 5205 5468 Luxembourg: +352 2088 1749 Luxembourg (toll free): 800 28433 Malaysia (toll free): 1 800 816 152 Malaysia,Kuala Lumpur: +60 (0) 3 7724 8010 Mexico (toll free): 01 800 733 4102 Mexico, Guadalajara: +52 33 4162 4504 Mexico, Mexico City: +52 55 8421 0326 Mexico, Monterrey: +52 81 4162 5648 Morocco (toll free): 0800 091 296 Morocco, Casablanca: +212 (0) 520 48 0022 Netherlands (toll free): 0800 020 2597 Netherlands, Amsterdam: +31 (0) 20 716 8345 New Zealand (toll free): 0800 452 947 New Zealand, Auckland: +64 (0) 9 929 1825 New Zealand, Christchurch: +64 (0) 3 974 2596 New Zealand, Wellington: +64 (0) 4 909 4674 Nigeria, Lagos: +234 1 277 3944 Norway (toll free): 800 56081 Norway, Oslo: +47 21 00 48 15 Panama (toll free): 00800 223 1390 Panama, Panama City: +507 8 335 913 Peru, Lima: +51 (0) 1 700 9571 Philippines (toll free): 1 800 111 013 99 Philippines, Manila: +63 (0)2 395 3426 Poland (toll free): 00 800 121 4356 Poland, Warsaw: +48 22 295 3570 Portugal (toll free): 800 784 442 Portugal, Lisbon: +351 21 316 4093 Qatar (toll free): 00 800 100 491 Romania (toll free): 0800 801 035 Romania, Bucharest: +40 (0) 21 529 3992 Russia (toll free): 8 800 500 9241 Russia, Moscow: +7 495 646 9181 Saudi Arabia (toll free): 800 844 6641 Saudi Arabia (toll free): 800 850 0219 Singapore: +65 6622 1957 Singapore (toll free): 800 616 3192 Slovakia (toll free): 0800 002 002 Slovakia, Bratislava: +421 (0)2 3321 5498 Slovenia (toll free): 0800 81193 Slovenia, Ljubljana: +386 1600 8695 South Africa (toll free): 0800 999 434 South Africa, Johannesburg: +27 (0)11 589 8321 South Korea (toll free): 00798 6136 1454 South Korea, Seoul: +82 (0) 2 6007 0079 Spain (toll free): 900 828 035 Spain, Barcelona: +34 93 800 1946 Spain, Madrid: +34 91 114 6653 Sweden (toll free): 0200 125 588 Sweden, Stockholm: +46 (0) 8 5065 3956 Switzerland (toll free): 0800 740 360 Switzerland, Geneva: +41 (0) 22 595 4795 Switzerland, Zurich: +41 (0) 44 580 7207 Taiwan (toll free): 0800 666 596 Taiwan, Taipei: +886 (0) 2 2650 7329 Thailand (toll free): 001 800 6136 1473 Turkey (toll free): 00800 4488 26642 Turkey, Istanbul: +90 212 375 50 49 UAE (toll free): 8000 3570 2662 UK (03): +44 (0)330 336 6002 UK (toll free): 0800 358 6385 Ukraine (toll free): 0800 500 896 Uruguay (toll free): 0004 019 0152 USA /Canada (toll free): 1-866-398-2885 Venezuela (toll free): 0 800 162 7451 Vietnam (toll free): 1800 9226 Costa Rica (toll free): 800 542 5328 France (national): 0821 231 671 India (toll free): 1800 200 9415 Indonesia, Jakarta: +62 21 2188 9084 Ireland (national): 0818 270 271 Japan (national): 0570 085 744 Serbia (toll free): 0800 190 712 UK (national): 0844 473 5010 UK (national): 0845 545 0015 Venezuela, Caracas: +58 212 720 2164

1 0

No PP IRT meeting tomorrow
by Amy Bivins July 9, 2018

July 9, 2018

Dear Colleagues, I hope you are well! We will not have an IRT meeting tomorrow. I'll provide an update this week on timeline and status as soon as I am able to do so. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

Re: [Gdd-gnso-ppsai-impl] No PP IRT meeting next week
by Chris Pelling July 8, 2018

July 8, 2018

Steve , today is July 6, I would suspect after the damming eu letter, we can safely say ICANN review by end of June is a no. Of course unless ICANN can pull out a tardis (you and I are old enough to know what that is ;) ) (dr who for thosr that do not know y oungens) and aend us back 20 odd years ... Sent by Chris on the move. -------- Original message --------From: "Metalitz, Steven" <met(a)msk.com> Date: 06/07/2018 22:05 (GMT+00:00) To: "'gdd-gnso-ppsai-impl(a)icann.org'" <gdd-gnso-ppsai-impl(a)icann.org> Subject: Re: [Gdd-gnso-ppsai-impl] No PP IRT meeting next week Amy and colleagues, Since we have not seen any update from you this week as anticipated below, may we take it that the effort to complete the legal review of the PPSAI implementation papers “by the end of June” is no longer operative? Please advise the status. Thank you. Steve Metalitz From: Metalitz, Steven Sent: Friday, June 29, 2018 9:18 AM To: gdd-gnso-ppsai-impl(a)icann.org Subject: RE: No PP IRT meeting next week Amy, As Akram indicated in his June 6 letter that this review should be completed “by the end of June,” we expect to hear the results from you by early next week. Thanks. Steve Metalitz Steven J. Metalitz | Partner, through his professional corporation T: 202.355.7902 | met(a)msk.com Mitchell Silberberg & Knupp LLP | www.msk.com 1818 N Street NW, 7th Floor, Washington, DC 20036 THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE IS INTENDED ONLY FOR THE PERSONAL AND CONFIDENTIAL USE OF THE DESIGNATED RECIPIENTS. THIS MESSAGE MAY BE AN ATTORNEY-CLIENT COMMUNICATION, AND AS SUCH IS PRIVILEGED AND CONFIDENTIAL. IF THE READER OF THIS MESSAGE IS NOT AN INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY REVIEW, USE, DISSEMINATION, FORWARDING OR COPYING OF THIS MESSAGE IS STRICTLY PROHIBITED. PLEASE NOTIFY US IMMEDIATELY BY REPLY E-MAIL OR TELEPHONE, AND DELETE THE ORIGINAL MESSAGE AND ALL ATTACHMENTS FROM YOUR SYSTEM. THANK YOU. From: Gdd-gnso-ppsai-impl [mailto:gdd-gnso-ppsai-impl-bounces@icann.org] On Behalf Of Amy Bivins Sent: Friday, June 29, 2018 7:42 AM To: gdd-gnso-ppsai-impl(a)icann.org Subject: [Gdd-gnso-ppsai-impl] No PP IRT meeting next week Dear Colleagues, We will not be having a PP IRT meeting next week. Next week, I expect to be able to share an update with you on the Legal review of all of the proposed accreditation program requirements and materials (including a review related to GDPR). If you have questions, please don’t hesitate to contact me, and safe travels to those who traveled to ICANN62. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org www.icann.org

2 1

No PP IRT meeting next week
by Amy Bivins July 6, 2018

July 6, 2018

Dear Colleagues, We will not be having a PP IRT meeting next week. Next week, I expect to be able to share an update with you on the Legal review of all of the proposed accreditation program requirements and materials (including a review related to GDPR). If you have questions, please don't hesitate to contact me, and safe travels to those who traveled to ICANN62. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 2

No PP IRT Meeting Next Two Weeks, Data Escrow Materials Attached
by Amy Bivins June 19, 2018

June 19, 2018

Dear Colleagues, We will not have a meeting on Tuesday, as the attached will be easier to review on your own. We won't have a meeting the following week, either, as that is ICANN62. We're planning to meet again on 3 July. I have attached several documents for your review: 1. The latest version of the 4 RRI specifications required for data escrow and quarterly reporting. 2. The PP data escrow specification, updated to support the standalone data escrow model (the previous draft proposed to allow an affiliated registrar to make its data escrow deposits through the affiliated PP provider, rather than the other way around). Please note that we are still working on documentation that will be required to support the allowance for registrar-affiliated PPs to meet their data escrow requirements as part of the registrar's data escrow deposit procedures. This will likely involve an addendum either to the registrar data escrow agreement or the pp data escrow agreement-I will share a concrete proposal on that when we have it. For PPs that follow the registrar-supported data escrow model, there are three requirements that will apply (these will be included in the data escrow agreement): * Privacy and Proxy Service customer information escrowed through Affiliate Registrar(s) data escrow deposits must include for each domain name: the PPSP identifier assigned by ICANN to the Provider, the domain name ROID, notwithstanding the requirements and format defined by the Registrar Data Escrow Specifications. The Affiliate Registrar(s) will deliver to ICANN (using the API described in https://tools.ietf.org/html/draft-icann-registrar-interfaces) a statement that includes a copy of the report generated upon creation of each Registrar data escrow Deposit that states that the Deposit has been inspected by the Registrar to be complete and accurate. The preparation and submission of this statement must be performed by the Affiliate Registrar(s) or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent's Affiliates. * The Provider will deliver each day to ICANN (using the API described in https://tools.ietf.org/html/draft-icann-ppsp-interfaces) a statement from Provider that states that the Provider has verified that the Privacy and Proxy Services customer information submitted in Affiliate Registrar(s) data escrow deposits is complete, accurate and includes the contact information corresponding to each and all of the Provider's customers. The preparation and submission of this statement must be performed by the Provider or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent's Affiliates. Provider will include the Deposit's <id> in its statement. The preparation and submission of this statement must be performed by the Provider or its designee, provided that such designee may not be the Escrow Agent or any of Escrow Agent's Affiliates. Provider will generate and include a Deposit's <id> in its statement. * The Provider will include the contact information corresponding to each and all of the Provider's customers through Affiliate Registrar(s) data escrow deposits, otherwise the Provider will be obligated to comply with the Data Escrow obligations in the Privacy and Proxy Service Provider Data Escrow Specifications. If you have questions or comments, please send them to the list. Thanks, and have a great weekend! Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

3 4

PP fees proposal document attached
by Amy Bivins June 14, 2018

June 14, 2018

Dear Colleagues, Attached, you will find additional information related to the proposed fees for the privacy and proxy service provider accreditation program. Please review and send any comments/questions to the list. Thank you for your patience. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

4 5

Re: [Gdd-gnso-ppsai-impl] [Ext] Re: PP fees proposal document attached
by Jennifer Gore June 13, 2018

June 13, 2018

Thanks Chris for your feedback. As a reminder the nature of ICANN staff role during the IRT phase greatly differs from the Working Group phase. ICANN has taken the concerns of IRT members into consideration. If you are seeking additional materials, I kindly as you to be very specific in the information you are seeking. Best Regards, Jennifer Gore From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Chris Pelling <chris(a)netearth.net> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Wednesday, June 13, 2018 at 3:07 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org>, gtheo <gtheo(a)xs4all.nl> Subject: Re: [Gdd-gnso-ppsai-impl] [Ext] Re: PP fees proposal document attached Hi Amy, Its astounding that icann org have literally taken no notice of the concerns the IRT have about the representation of the fee structure. Is it no wonder half of us no longer bother to interact with giving feedback as icann simply do as they please anyway? If took months for icann to "back up" their fee structure and what was provided was simply third grade material. Sent by Chris on the move. -------- Original message -------- From: Amy Bivins <amy.bivins(a)icann.org> Date: 13/06/2018 19:12 (GMT+01:00) To: gtheo <gtheo(a)xs4all.nl>, gdd-gnso-ppsai-impl(a)icann.org Subject: Re: [Gdd-gnso-ppsai-impl] [Ext] Re: PP fees proposal document attached Dear Colleagues, Thank you for taking the time to review and provide feedback on the privacy and proxy service provider accreditation fees-related documentation, both on the list and during the meetings we have recently had on this topic. ICANN org has carefully considered the feedback of all IRT members in developing the proposed fee structure. Despite recommendations from some IRT members to reduce the proposed fees, ICANN org continues to believe that the fees proposed are reasonable and appropriate, for the reasons identified in the fees proposal documentation (attached). As noted in the fees proposal, ICANN org analyzed three relevant factors in reaching the fee structure that was proposed: relevant benchmarks; fees transparency, simplicity, stability and predictability; and anticipated program management costs. ICANN org understands that some IRT members disagree with this assessment, but did not find any of the arguments or suggestions raised by IRT members persuasive. If persuasive reasons are raised for revisiting the proposed fee structure during the public comment period, ICANN org commits to revisit the proposed fees. Please know that ICANN org sincerely appreciates the time and effort you committed to this exercise and the broader work of the IRT. Best, Amy -----Original Message----- From: gtheo [mailto:gtheo@xs4all.nl] Sent: Wednesday, May 23, 2018 10:04 AM To: gdd-gnso-ppsai-impl(a)icann.org Cc: Amy Bivins <amy.bivins(a)icann.org> Subject: [Ext] Re: [Gdd-gnso-ppsai-impl] PP fees proposal document attached Thanks Amy, Am I reading this correctly? The program startup and application processing is going to cost; 1,117,390??? That is a huge amount of money for a program startup if only a few providers signup for this and the majority decides that the temporary spec or it's successor is enough privacy for registrants. But maybe I am reading it incorrectly. When I look at the Activity Relevant Department(s) Accredited Provider Account Management Services, it seems many of these activities already exist for Registrars. Can those activities not be handled by the same folks? I mean does it matter if a Registrar changes its name or a Privacy Provider? It's the same type of processing is it not? Also, a question about the PP Data Retention Waiver activity. What is this activity? Thanks, Theo Amy Bivins schreef op 2018-05-22 10:20 PM: > Dear Colleagues, > > Attached, you will find additional information related to the proposed > fees for the privacy and proxy service provider accreditation program. > Please review and send any comments/questions to the list. > > Thank you for your patience. > > Best, > > Amy > > AMY E. BIVINS > > Registrar Services and Engagement Senior Manager > > Registrar Services and Industry Relations > > Internet Corporation for Assigned Names and Numbers (ICANN) > > Direct: +1 (202) 249-7551 > > Fax: +1 (202) 789-0104 > > Email: amy.bivins(a)icann.org > > www.icann.org [1] > > > > Links: > ------ > [1] > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=Dw > ICAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=uerz4ckt1v4Qhbv-T > plkjKTey9bgtdWrvLyZDu0mXuk&m=BJtpG8Olp_3NAmSVAsUTW_HmMsKblc3_3k59uUScn > vs&s=YBcBo-2U5vstASdpDcav-4W8w712XbFjerD180TrPRo&e= > _______________________________________________ > Gdd-gnso-ppsai-impl mailing list > Gdd-gnso-ppsai-impl(a)icann.org > https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl(a)icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl

1 0

Re: [Gdd-gnso-ppsai-impl] [Ext] Re: PP fees proposal document attached
by Chris Pelling June 13, 2018

June 13, 2018

Hi Amy, Its astounding that icann org have literally taken no notice of the concerns the IRT have about the representation of the fee structure. Is it no wonder half of us no longer bother to interact with giving feedback as icann simply do as they please anyway? If took months for icann to "back up" their fee structure and what was provided was simply third grade material. Sent by Chris on the move. -------- Original message --------From: Amy Bivins <amy.bivins(a)icann.org> Date: 13/06/2018 19:12 (GMT+01:00) To: gtheo <gtheo(a)xs4all.nl>, gdd-gnso-ppsai-impl(a)icann.org Subject: Re: [Gdd-gnso-ppsai-impl] [Ext] Re: PP fees proposal document attached Dear Colleagues, Thank you for taking the time to review and provide feedback on the privacy and proxy service provider accreditation fees-related documentation, both on the list and during the meetings we have recently had on this topic. ICANN org has carefully considered the feedback of all IRT members in developing the proposed fee structure. Despite recommendations from some IRT members to reduce the proposed fees, ICANN org continues to believe that the fees proposed are reasonable and appropriate, for the reasons identified in the fees proposal documentation (attached). As noted in the fees proposal, ICANN org analyzed three relevant factors in reaching the fee structure that was proposed: relevant benchmarks; fees transparency, simplicity, stability and predictability; and anticipated program management costs. ICANN org understands that some IRT members disagree with this assessment, but did not find any of the arguments or suggestions raised by IRT members persuasive. If persuasive reasons are raised for revisiting the proposed fee structure during the public comment period, ICANN org commits to revisit the proposed fees. Please know that ICANN org sincerely appreciates the time and effort you committed to this exercise and the broader work of the IRT. Best, Amy -----Original Message----- From: gtheo [mailto:gtheo@xs4all.nl] Sent: Wednesday, May 23, 2018 10:04 AM To: gdd-gnso-ppsai-impl(a)icann.org Cc: Amy Bivins <amy.bivins(a)icann.org> Subject: [Ext] Re: [Gdd-gnso-ppsai-impl] PP fees proposal document attached Thanks Amy, Am I reading this correctly? The program startup and application processing is going to cost; 1,117,390??? That is a huge amount of money for a program startup if only a few providers signup for this and the majority decides that the temporary spec or it's successor is enough privacy for registrants. But maybe I am reading it incorrectly. When I look at the Activity Relevant Department(s) Accredited Provider Account Management Services, it seems many of these activities already exist for Registrars. Can those activities not be handled by the same folks? I mean does it matter if a Registrar changes its name or a Privacy Provider? It's the same type of processing is it not? Also, a question about the PP Data Retention Waiver activity. What is this activity? Thanks, Theo Amy Bivins schreef op 2018-05-22 10:20 PM: > Dear Colleagues, > > Attached, you will find additional information related to the proposed > fees for the privacy and proxy service provider accreditation program. > Please review and send any comments/questions to the list. > > Thank you for your patience. > > Best, > > Amy > > AMY E. BIVINS > > Registrar Services and Engagement Senior Manager > > Registrar Services and Industry Relations > > Internet Corporation for Assigned Names and Numbers (ICANN) > > Direct: +1 (202) 249-7551 > > Fax: +1 (202) 789-0104 > > Email: amy.bivins(a)icann.org > > www.icann.org [1] > > > > Links: > ------ > [1] > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=Dw > ICAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=uerz4ckt1v4Qhbv-T > plkjKTey9bgtdWrvLyZDu0mXuk&m=BJtpG8Olp_3NAmSVAsUTW_HmMsKblc3_3k59uUScn > vs&s=YBcBo-2U5vstASdpDcav-4W8w712XbFjerD180TrPRo&e= > _______________________________________________ > Gdd-gnso-ppsai-impl mailing list > Gdd-gnso-ppsai-impl(a)icann.org > https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl(a)icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl

1 0

Re: [Gdd-gnso-ppsai-impl] No PP IRT Meeting on Tuesday
by Sara Bockey June 11, 2018

June 11, 2018

Thanks Amy. Can we get a copy of the latest PPAA for review? The last version I have is from February and I know several changes were made since that time. Thanks! Sara sara bockey sr. policy manager | GoDaddy™ sbockey(a)godaddy.com<mailto:sbockey@godaddy.com> 480-366-3616 skype: sbockey This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments. From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Friday, June 8, 2018 at 9:36 AM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] No PP IRT Meeting on Tuesday Dear Colleagues, We will not have a PP IRT meeting on Tuesday, 12 June. I expect to be able to send you an updated data escrow specification, possibly with a couple of questions, toward the end of next week. Also, please note that ICANN org has published a response to the 4 May request to pause the work of this IRT. It is available on the ICANN correspondence page, https://www.icann.org/en/system/files/correspondence/atallah-to-bunton-06ju… Thanks, and have a great weekend. Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 2

No PP IRT Meeting on Tuesday
by Amy Bivins June 8, 2018

June 8, 2018

Dear Colleagues, We will not have a PP IRT meeting on Tuesday, 12 June. I expect to be able to send you an updated data escrow specification, possibly with a couple of questions, toward the end of next week. Also, please note that ICANN org has published a response to the 4 May request to pause the work of this IRT. It is available on the ICANN correspondence page, https://www.icann.org/en/system/files/correspondence/atallah-to-bunton-06ju… Thanks, and have a great weekend. Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

Agenda for Tuesday's PP IRT meeting
by Amy Bivins June 1, 2018

June 1, 2018

Dear Colleagues, We will have our regularly-scheduled Privacy/Proxy IRT meeting on Tuesday, but we aren't expecting it to be a long one. I will provide an update on the project status and timeline and will also provide an opportunity for any additional feedback you may have on the fees document that was recently distributed. As mentioned last week, ICANN is reviewing all of the proposed accreditation program materials, including against the Temporary Specification, and will bring any items that arise back to the IRT for discussion. If you have any practical examples you would like to share with the group of how PP services are operating now, in light of the approval of the Temporary Specification, please feel free to share them with the list (before our meeting or anytime) or come prepared to share on Tuesday. Thanks, and have a great weekend. Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 1

Re: [Gdd-gnso-ppsai-impl] Agenda for Tuesday's PP IRT meeting
by Sara Bockey June 1, 2018

June 1, 2018

I will not be able to attend Tuesday’s call. Please note my apologies. Thanks, Sara sara bockey sr. policy manager | GoDaddy™ sbockey(a)godaddy.com<mailto:sbockey@godaddy.com> 480-366-3616 skype: sbockey This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments. From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Friday, June 1, 2018 at 12:44 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] Agenda for Tuesday's PP IRT meeting Dear Colleagues, We will have our regularly-scheduled Privacy/Proxy IRT meeting on Tuesday, but we aren’t expecting it to be a long one. I will provide an update on the project status and timeline and will also provide an opportunity for any additional feedback you may have on the fees document that was recently distributed. As mentioned last week, ICANN is reviewing all of the proposed accreditation program materials, including against the Temporary Specification, and will bring any items that arise back to the IRT for discussion. If you have any practical examples you would like to share with the group of how PP services are operating now, in light of the approval of the Temporary Specification, please feel free to share them with the list (before our meeting or anytime) or come prepared to share on Tuesday. Thanks, and have a great weekend. Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 1

PP IRT canceled next week, status update
by Amy Bivins May 24, 2018

May 24, 2018

Dear Colleagues, The PP IRT meeting scheduled for 29 May is canceled. We expect to have an update/answer to the communications to ICANN org, requesting a pause of this group's work, to be published next week. In the interim, I can report that ICANN is reviewing all of the proposed accreditation program materials, including against the Temporary Specification, and will bring any issues that arise back to the IRT for discussion. Following any additional feedback from you on the proposed next steps on the data escrow specification (requested deadline of tomorrow, 25 May), we will finalize the data escrow-related materials for distribution and feedback. Thanks, and have a great weekend. Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

PP IRT question, no meeting Tues, fees info to be distributed shortly
by Amy Bivins May 21, 2018

May 21, 2018

Dear Colleagues, This week's PP IRT meeting will be canceled, as the issues on our to-do list this week can be addressed without a call. We have one question for you, below. Please consider this issue and provide your comments on this no later than 28 May. I hope to be able to update you later this week on the status of the RrSG request (received by ICANN 4 May) to pause this IRT's work (and the COA's letter in opposition). I also expect to be able to send the fees-related documentation to you within the next couple of days. Background The IRT has recommended that, with respect to the data escrow specification, Privacy and Proxy service providers that are affiliated with an ICANN-accredited registrar should be able to meet their data escrow deposit obligations through the registrar (so the registrar would deposit the PP registration data and underlying customer data, similar to the process currently followed under the interim RAA specification). In order to achieve this result, ICANN would need to make slight updates to the Registrar Data Escrow specification, to add two required data elements for the deposit (the privacy/proxy service provider ID and the domain ID). Question: Is this an acceptable result (updating registrar data escrow specification for PP-affiliated registrars that wish to have combined data escrow deposits), or should ICANN revert to having a completely separate data escrow specification that all PPs must deposit under, regardless of whether the PP is affiliated with a registrar or not? Please note that, regardless of the answer to this question, there will be a separate PP data escrow specification for (a) third-party providers and (b) providers that work with more than 1 registrar. Based on discussions thus far, we believe the intent was the former (updating the registrar specification) but we wanted to confirm before finalizing that proposed update to the registrar specification and distributing it to the designated data escrow agents to alert them to the proposed update. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

4 3

New Temp Spec reference
by Volker Greimann May 18, 2018

May 18, 2018

As the new Temporary Spec now contains a direct obligation with regard to privacy services: /in the case of a domain name registration where a privacy/proxy service used (e.g. where data associated with a natural person is masked), Registrar MUST return in response to any query full WHOIS data, including the existing proxy/proxy pseudonymized email./ Correctly interpreted, this means that ICANN must offer a complete and up-to-date machine readable list of privacy services along with a reference of how to automatically recognize them as part of the accreditation program because otherwise there will be no way for registries and registrars of automatically setting their records to "display". Just another point in case why the TempSpec is deeply flawed. // -- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.

1 0

Re: [Gdd-gnso-ppsai-impl] Notes, action items from today's PP IRT meeting--feedback requested by 27 April
by Sara Bockey May 18, 2018

May 18, 2018

Regarding Section 4.2.2 “without limitations” is necessary to ensure legitimate instances not yet listed or thought of are covered. Examples of additional causes beyond the control of the Provider: war, terrorism, riots, power outage, internet outage, internet failure, server failure, foreign gov’t changes, labor disputes, etc. Regarding Section 4.2.2.5 – I see no issue with redundancy and there is no harm in including this. If anything, it protects against potential abuse (in parts of the world that are less democratic) Regarding Section 4.2.6 – Not redundant and 100% necessary. Particularly for providers in parts of the world that are less democratic. We must remember this will be applied globally. Belt and suspenders! At ICANN61 this addition gave registrars that spoke with me the most comfort. Finally, I note that Staff is using the 24-hr timeframe as the default in the document instead of one business day as agreed by the registrars. Since one business day is what the registrars have agreed to, should it not be the default until otherwise determined? sara bockey sr. policy manager | GoDaddy™ sbockey(a)godaddy.com<mailto:sbockey@godaddy.com> 480-366-3616 skype: sbockey This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments. From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Tuesday, April 17, 2018 at 10:53 AM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] Notes, action items from today's PP IRT meeting--feedback requested by 27 April Dear Colleagues, Thank you for your participation on today’s privacy/proxy IRT call. For those who could not attend, I regret that we were unable to record this meeting (an issue with a new internal recording policy), but this was a one-time issue and all future meetings will be recorded. I’ve done my best to annotate the LEA specification document with the items we discussed, and have also attached the chat transcript. IRT Action Items We are nearing the completion of discussions on the LEA Specification. Other than the item of clear disagreement among members of the IRT—the time period for high priority requests—we are largely in the refining stage. To that end, we have a few final proposed edits for the group to review and comment on—including some edits that were originally suggested by Sara Bockey a few weeks ago and supported by many registrar members of the IRT. If we don’t hear any opposition to these edits that would warrant further discussion, we will make these edits as requested in the draft we publish for comment. Today, we considered whether the LEA Framework Specification would be clearer if we reorganized it slightly, to make more clear where processes apply to high priority requests and when they don’t. I’ve included two versions of the draft—the one with “orig” at the end of the title—which includes the proposed edits without reorganizing, and the “reorganized” one. Please review both and respond to the list with your thoughts about the proposed reorganizing of this. Please provide any additional input you have on this draft no later than next Friday, 27 April. Please note, specifically, questions in the following sections: Original Numbering Reorganized Version Section 2.1.10 (addition of “except in high priority” language at beginning of edit) Same section Section 3.2.1 (addition of the words “Standard Priority” to make clear this 2 business day receipt process doesn’t apply in high priority cases) Moved to Section 3.2.2 Section 4.2.2 (inclusion of “without limitations” language, plus input about and question from Steve Metalitz—any other reasons that registrars feel would be reasonable for refusing disclosure?); Also see feedback, generally, from PSWG liaison, in meeting chat transcript (most pasted into specification document but cuts off at the end) Same section Section 4.2.2.5 (is this redundant? ) Same section Section 4.2.6 (is this redundant?) Same section I’m also attaching the most recent draft de-accreditation procedure document. As mentioned on the list last week, upon further consideration on the ICANN org side we think we should add back in the proposed transition procedure for customers impacted by the de-accreditation or termination of a third-party provider (section 4). Please review and provide any further comments on this no later than 27 April. For next week, we are hoping to have the requested fees information ready for you to discuss. I’ll update you as soon as I can. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

8 16

Response from COA to RrSG's request for PP IRT/AFAV pause received, posted to ICANN.org
by Amy Bivins May 11, 2018

May 11, 2018

Dear Colleagues, ICANN org received a letter yesterday from the Coalition for Online Accountability that responded to the RrSG's 4 May request that ICANN org pause the work of the PP IRT and the AFAV project. The letter is posted on ICANN org's correspondence page at https://www.icann.org/en/system/files/correspondence/marks-metalitz-to-atal… These communications are being evaluated. I'll provide an update re: status as soon as it is available. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

No PP IRT meeting tomorrow
by Amy Bivins May 7, 2018

May 7, 2018

Dear Colleagues, We will not have a PP IRT meeting tomorrow because there are no new materials available to discuss. As noted in Xavier's message to the group on Friday, ICANN is working to finalize the additional fees-related materials and will provide an update to the group this week. The regularly-scheduled IRT meeting will also be canceled for next week, as many IRT members and staff will be attending the GDD Summit meeting. However, please watch your inboxes-I will send you anything we have that is ready for your feedback. In case you didn't see it, ICANN received a letter from the RrSG on Friday, recommending that this IRT's work be paused, https://www.icann.org/en/system/files/correspondence/bunton-to-atallah-04ma…. This recommendation is being evaluated, and I'll provide you an update as soon as I can. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

Privacy and proxy services accreditation IRT - Fee evaluation - Follow up and update
by Xavier J. Calvez May 5, 2018

May 5, 2018

Dear IRT members, I am following up on the call held last week on the fee determination and the follow up actions we discussed. We have made good progress since last week’s call and are working towards completion. I am providing a status update on and some comments below. 1. Fee determination methodology: document the approach described verbally during the call last week – 80% complete. Need final review and editing. 2. PP accreditation application fee: provide breakdown of the cost estimate – 80% complete. Need to match the cost breakdown items to the list of activities provided, and perform final review. 3. PP annual accreditation fee: provide breakdown of the cost estimate – We had not included this topic in the original responses and we need to develop a response that provides an overall view of costing. The annual accreditation fee encompasses a much broader scope of activities than the more specific application process. As a reminder, the cost estimate is only one of the factors that contribute to the determination of a fee, and one that is used to corroborate the reasonableness of the fee levels considered, rather than a determining factor. We do understand that addressing this topic is the last open item before moving to the next step, and we are working diligently on completing the work on this matter, among several other priorities. We will provide an update on the above in course of next week. Thank you. Best, Xavier Xavier Calvez ICANN – SVP & CFO 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 Phone: 310-301-5838 Mobile: 805-312-0052 Fax: 310-957-2348

1 0

PP LEA Framework: Remaining items for IRT feedback (requested deadline 8 May)
by Amy Bivins May 1, 2018

May 1, 2018

Dear Colleagues, Upon reviewing your most recent feedback on the LEA Framework Specification, we have a couple of items left where there isn't a clear consensus among the members of the IRT. Please review this list this week and share any additional feedback you have no later than next Tuesday, 8 May. We can discuss on our scheduled call next week, if needed. I've attached the most recent markup, showing in redline only the comments on the sections where there is some disagreement among members of the IRT. For reference, those sections and issues are: Section 3.3.1 (time period for responses to high-priority requests)-it appears likely we will not obtain consensus on this item Section 4.1.2: The proposed addition of "without limitations," either here or moved to Section 4.1.4. Section 4.1.2.5.: The proposed addition of this section in its entirety. Section 4.1.6: The proposed addition of this section in its entirety, including whether this would be redundant or whether this should be incorporated elsewhere. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

4 7

Re: [Gdd-gnso-ppsai-impl] Notes, action items from today's PP IRT meeting--feedback requested by 27 April
by Chris Pelling April 30, 2018

April 30, 2018

I also agree with Sara's, Eric and Theo points. Sent by Chris on the move. -------- Original message --------From: theo geurts <gtheo(a)xs4all.nl> Date: 30/04/2018 20:28 (GMT+00:00) To: gdd-gnso-ppsai-impl(a)icann.org, Eric Rokobauer <eric.rokobauer(a)endurance.com> Subject: Re: [Gdd-gnso-ppsai-impl] Notes, action items from today's PP IRT meeting--feedback requested by 27 April Agreed with Eric and Sara, 4.2.6, we could move that one around some. 4.2.2.5, I rather keep it in, it does not hurt and I 100% agree, democracy is not a given. Theo On 30-4-2018 21:05, Eric Rokobauer wrote: Apologies for the late reply in providing some feedback. Comments following Sara's comments from 19 April: Inclusion of "without limitations" in section 4.2.2 - I agree with Sara here. Ideally again it is to cover the Provider from potential instances that we here in this IRT may not be recognizing here. 4.2.2.5 being potentially redundant - I believe this should be removed if IRT does find to be redundant. While I do appreciate Sara's comments, if we do all agree there is duplication here with the statement, best we remove to clear any potential confusion that could come later (thinking when we may not necessarily remember why we had this added in the first place). 4.2.6 - I agree that this is not redundant and should still be kept, but open to having it included elsewhere within section 4.2 if majority feels it would be better represented. As for the timeframe, agree that one business day should be our default. Thanks Eric Eric Rokobauer Sr. Registrar Compliance Manager | Endurance International Group 10 Corporate Drive, Suite 300, Burlington MA 01803 T - 781.852.3445 E - eric.rokobauer(a)endurance.com On Mon, Apr 30, 2018 at 5:12 AM, Volker Greimann <vgreimann(a)key-systems.net> wrote: If you are not willing to compromise, we may get nowhere. If the line has to be drawn between this is what is reasonably possible for us to deliver (meaning everything beyond that is either unreasonable or impossible) and this is what we (meaning the PSWG) want because it is an artificial number we want, it seems clear where the policy should end up. So you are not willing to compromise and continue to demand the impossible or unreasonable. Fine, but that is not how this works at ICANN. Our compromise line is one business day. If no one moves, we are at an impasse. But please remember: Usually, you are going to get answers quicker, it is just a minimum guaranteed response time we are talking about. And anything you get here - ANYTHING! - is better than what you have now. We are not proposing to take anything away from you. We are freely agreeing to give you something. Let's not lose focus on this very important point. Volker Am 27.04.2018 um 23:24 schrieb Roman, Peter (CRM): All, A quick additional response to the comments in the LEA specification: Note 7 says that “Registrar members of the IRT contend that the 24-hour period recommended by the PSWG is unworkable; PSWG members contend that 24 hours should be the maximum allowable time for a request to be actioned in an emergency situation.” This is a complete misrepresentation of the PSWG position. The PSWG has maintained from the beginning of the conversation on emergency requests that they needed to be “actioned” immediately. The PSWG does NOT recommend the 24-hour period, the PSWG is willing to COMPROMISE to the 24 hour period. The PSWG is NOT willing to compromise to the one business day response time. One business day, as the providers have explained it, means that an emergency request delivered to the provider on Friday afternoon does not need to be responded to until Monday afternoon. So, one business day means 72 hours or more. In an emergency, this is completely useless response time. By that time, people are dead. An imminent threat to life means that somebody is going to die any moment without this information. I hope that you never have to respond to one of these requests but I also hope that if you do, you will not ignore it until you get to it the next business day. Peter Roman Senior Counsel Computer Crime & Intellectual Property Section Criminal Division Department of Justice 1301 New York Ave., NW Washington, DC 20530 (202) 305-1323 peter.roman(a)usdoj.gov From: Gdd-gnso-ppsai-impl [mailto:gdd-gnso-ppsai-impl-bounces@icann.org] On Behalf Of Metalitz, Steven Sent: Friday, April 27, 2018 2:24 PM To: gdd-gnso-ppsai-impl(a)icann.org Subject: Re: [Gdd-gnso-ppsai-impl] Notes, action items from today's PP IRT meeting--feedback requested by 27 April Please see in-line feedback below regarding some of Sara’s points on the LEA specification. On behalf of Coalition for Online Accountability (COA) | www.onlineaccountability.net Steven J. Metalitz | Partner, through his professional corporation T: +1.202.355.7902 | met(a)msk.com Mitchell Silberberg & Knupp LLP | www.msk.com 1818 N Street NW, 8th Floor, Washington, DC 20036 THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE IS INTENDED ONLY FOR THE PERSONAL AND CONFIDENTIAL USE OF THE DESIGNATED RECIPIENTS. THIS MESSAGE MAY BE AN ATTORNEY-CLIENT COMMUNICATION, AND AS SUCH IS PRIVILEGED AND CONFIDENTIAL. IF THE READER OF THIS MESSAGE IS NOT AN INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY REVIEW, USE, DISSEMINATION, FORWARDING OR COPYING OF THIS MESSAGE IS STRICTLY PROHIBITED. PLEASE NOTIFY US IMMEDIATELY BY REPLY E-MAIL OR TELEPHONE, AND DELETE THE ORIGINAL MESSAGE AND ALL ATTACHMENTS FROM YOUR SYSTEM. THANK YOU. From: Gdd-gnso-ppsai-impl [mailto:gdd-gnso-ppsai-impl-bounces@icann.org] On Behalf Of Amy Bivins Sent: Thursday, April 19, 2018 2:36 PM To: gdd-gnso-ppsai-impl(a)icann.org Subject: Re: [Gdd-gnso-ppsai-impl] Notes, action items from today's PP IRT meeting--feedback requested by 27 April Thanks, Sara and Steve, for your comments on this draft thus far. I’ve updated the draft to address your last point, Sara, and in line with Steve’s comment about separating out standard and high priority requests. I’ve left the comments in the draft from Tuesday’s call for now. Absent any strong opposition to the inclusion of the other edits proposed by Sara, as noted in the draft, these will be accepted in the next draft. I encourage all IRT members to review the draft again when you are able and provide any further feedback no later than the end of next week. I don’t have any further information or materials for you today for next week’s meeting, but I hope to have something for you soon (I’ll send it as soon as I have it). Best, Amy From: Gdd-gnso-ppsai-impl [mailto:gdd-gnso-ppsai-impl-bounces@icann.org] On Behalf Of Sara Bockey Sent: Thursday, April 19, 2018 1:20 PM To: gdd-gnso-ppsai-impl(a)icann.org Subject: Re: [Gdd-gnso-ppsai-impl] Notes, action items from today's PP IRT meeting--feedback requested by 27 April Regarding Section 4.2.2 “without limitations” is necessary to ensure legitimate instances not yet listed or thought of are covered. Examples of additional causes beyond the control of the Provider: war, terrorism, riots, power outage, internet outage, internet failure, server failure, foreign gov’t changes, labor disputes, etc. Steve’s comment: (I think this refers to 4.1.2 of the revised document Amy sent out 4/17. ) This strikes me as a reasonable list of reasons why a provider would not be able to respond in a timely fashion to an LEA disclosure request (whether High Priority or Standard Priority), but not of reasons to deny altogether a request that otherwise meets the requirements of the specification. Should we append this list to what is now 4.1.4 (following “acts of nature”)? I would be much more comfortable including “without limitations” there rather than in 4.1.2. Regarding Section 4.2.2.5 – I see no issue with redundancy and there is no harm in including this. If anything, it protects against potential abuse (in parts of the world that are less democratic) Steve’s comment: This refers to the “well founded” phrasing in 4.1.2.5. I still have trouble understanding what would make a request that meets all the requirements of the specification not “well founded,” and believe I pointed out on the April 17 call why this situation differs from RAA 3.18.2 where “well-founded” appears (in short, that the RAA does not define what needs to go into an actionable LE request, and this specification does). Can Sara or others provide an example of when this ground for refusal of an LEA request might come into play? Regarding Section 4.2.6 – Not redundant and 100% necessary. Particularly for providers in parts of the world that are less democratic. We must remember this will be applied globally. Belt and suspenders! At ICANN61 this addition gave registrars that spoke with me the most comfort. Steve’s comment (this refers to the “due process” language now appearing in 4.1.6): I think it is redundant and for that reason do not object to it. “Foregoing due process within its applicable jurisdiction” is really a subset of 4.1.2.2, disclosure in contravention of applicable law. Regarding the legitimate concerns about “less democratic” jurisdictions: remember that this entire specification only applies to disclosure requests received from LE authorities within the provider’s own jurisdiction. If you choose to establish the provider within a “less democratic” jurisdiction, that provider still has to follow the laws of that jurisdiction, including the laws that define what process is due in a particular situation. Finally, I note that Staff is using the 24-hr timeframe as the default in the document instead of one business day as agreed by the registrars. Since one business day is what the registrars have agreed to, should it not be the default until otherwise determined? Steve’s comments: I have suggested putting the two options in square brackets, don’t care which one is listed first. sara bockey sr. policy manager | GoDaddy™ sbockey(a)godaddy.com 480-366-3616 skype: sbockey This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments. From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Tuesday, April 17, 2018 at 10:53 AM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] Notes, action items from today's PP IRT meeting--feedback requested by 27 April Dear Colleagues, Thank you for your participation on today’s privacy/proxy IRT call. For those who could not attend, I regret that we were unable to record this meeting (an issue with a new internal recording policy), but this was a one-time issue and all future meetings will be recorded. I’ve done my best to annotate the LEA specification document with the items we discussed, and have also attached the chat transcript. IRT Action Items We are nearing the completion of discussions on the LEA Specification. Other than the item of clear disagreement among members of the IRT—the time period for high priority requests—we are largely in the refining stage. To that end, we have a few final proposed edits for the group to review and comment on—including some edits that were originally suggested by Sara Bockey a few weeks ago and supported by many registrar members of the IRT. If we don’t hear any opposition to these edits that would warrant further discussion, we will make these edits as requested in the draft we publish for comment. Today, we considered whether the LEA Framework Specification would be clearer if we reorganized it slightly, to make more clear where processes apply to high priority requests and when they don’t. I’ve included two versions of the draft—the one with “orig” at the end of the title—which includes the proposed edits without reorganizing, and the “reorganized” one. Please review both and respond to the list with your thoughts about the proposed reorganizing of this. Please provide any additional input you have on this draft no later than next Friday, 27 April. Please note, specifically, questions in the following sections: Original Numbering Reorganized Version Section 2.1.10 (addition of “except in high priority” language at beginning of edit) Same section Section 3.2.1 (addition of the words “Standard Priority” to make clear this 2 business day receipt process doesn’t apply in high priority cases) Moved to Section 3.2.2 Section 4.2.2 (inclusion of “without limitations” language, plus input about and question from Steve Metalitz—any other reasons that registrars feel would be reasonable for refusing disclosure?); Also see feedback, generally, from PSWG liaison, in meeting chat transcript (most pasted into specification document but cuts off at the end) Same section Section 4.2.2.5 (is this redundant? ) Same section Section 4.2.6 (is this redundant?) Same section I’m also attaching the most recent draft de-accreditation procedure document. As mentioned on the list last week, upon further consideration on the ICANN org side we think we should add back in the proposed transition procedure for customers impacted by the de-accreditation or termination of a third-party provider (section 4). Please review and provide any further comments on this no later than 27 April. For next week, we are hoping to have the requested fees information ready for you to discuss. I’ll update you as soon as I can. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org www.icann.org _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl(a)icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl -- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone. _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl(a)icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl(a)icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl

1 0

1 May PP IRT meeting canceled
by Amy Bivins April 27, 2018

April 27, 2018

Dear Colleagues, We will not have a privacy/proxy IRT meeting this upcoming Tuesday, 1 May, as we don't have any new items to discuss next week. ICANN org intends to have the more detailed document on the fees-setting process, as referenced by Xavier Calvez on Tuesday's call, ready to share with the IRT by the end of next week. In terms of overall timeline, we are currently doing final reviews of the draft accreditation agreement and doing some outreach to the data escrow agents with respect to the draft escrow specification. We will need to discuss both with you prior to proceeding to the public comment period, so it's looking like it will be at least late May by the time we are able to reach that point. Thanks, and have a great weekend. Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

1 0

Re: [Gdd-gnso-ppsai-impl] FW: PP fees document from ICANN61 attached
by Darcy Southwell April 26, 2018

April 26, 2018

Amy, given the activity that took place during the meetings on April 17 and 24, and the follow up requests by email regarding fees, what is your new estimate timeline for publication? The last estimate was late April/early May, but the same fee-related information is still at issue. Thanks, Darcy From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org> Reply-To: <gdd-gnso-ppsai-impl(a)icann.org> Date: Tuesday, April 24, 2018 at 7:26 AM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] FW: PP fees document from ICANN61 attached From: Amy Bivins Sent: Tuesday, April 24, 2018 10:20 AM To: Chris Pelling <chris(a)netearth.net> Subject: PP fees document from ICANN61 attached Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org www.icann.org _______________________________________________ Gdd-gnso-ppsai-impl mailing list Gdd-gnso-ppsai-impl(a)icann.org https://mm.icann.org/mailman/listinfo/gdd-gnso-ppsai-impl

2 1

Re: [Gdd-gnso-ppsai-impl] FW: PP fees document from ICANN61 attached
by Michele Neylon - Blacknight April 25, 2018

April 25, 2018

Amy et al Will ICANN be providing a detailed breakdown and rationale for the proposed fees structure? We’ve been asking for this for some time and to the best of my knowledge nothing in writing beyond the very high level fees list has been forthcoming. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Tuesday 24 April 2018 at 15:26 To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] FW: PP fees document from ICANN61 attached From: Amy Bivins Sent: Tuesday, April 24, 2018 10:20 AM To: Chris Pelling <chris(a)netearth.net> Subject: PP fees document from ICANN61 attached Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

4 4

Re: [Gdd-gnso-ppsai-impl] FW: PP fees document from ICANN61 attached
by Michelle DeSmyter April 25, 2018

April 25, 2018

Hi Seth, Thank you, I will go ahead and remove you from the mailing list. Best regards, Michelle From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Seth M Reiss <seth.reiss(a)lex-ip.com> Organization: Seth M Reiss, AAL, ALLLC Reply-To: "seth.reiss(a)lex-ip.com" <seth.reiss(a)lex-ip.com>, "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Wednesday, April 25, 2018 at 12:05 PM To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: Re: [Gdd-gnso-ppsai-impl] FW: PP fees document from ICANN61 attached Please remove me from this list. Thank you. Seth Reiss From: Gdd-gnso-ppsai-impl [mailto:gdd-gnso-ppsai-impl-bounces@icann.org] On Behalf Of Amy Bivins Sent: Wednesday, April 25, 2018 2:36 AM To: gdd-gnso-ppsai-impl(a)icann.org Subject: Re: [Gdd-gnso-ppsai-impl] FW: PP fees document from ICANN61 attached Hi Michele and all, Yes. ICANN will provide an explanation in writing (building upon Xavier’s presentation yesterday) about the factors that were used to reach the proposed fees structure (estimated costs being one of the three factors that influenced the proposal). We hope to have this for the group next week. Best, Amy From: Gdd-gnso-ppsai-impl [mailto:gdd-gnso-ppsai-impl-bounces@icann.org] On Behalf Of Michele Neylon - Blacknight Sent: Wednesday, April 25, 2018 5:18 AM To: gdd-gnso-ppsai-impl(a)icann.org Subject: Re: [Gdd-gnso-ppsai-impl] FW: PP fees document from ICANN61 attached Amy et al Will ICANN be providing a detailed breakdown and rationale for the proposed fees structure? We’ve been asking for this for some time and to the best of my knowledge nothing in writing beyond the very high level fees list has been forthcoming. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org<mailto:gdd-gnso-ppsai-impl-bounces@icann.org>> on behalf of Amy Bivins <amy.bivins(a)icann.org<mailto:amy.bivins@icann.org>> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>" <gdd-gnso-ppsai-impl(a)icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>> Date: Tuesday 24 April 2018 at 15:26 To: "gdd-gnso-ppsai-impl(a)icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>" <gdd-gnso-ppsai-impl(a)icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>> Subject: [Gdd-gnso-ppsai-impl] FW: PP fees document from ICANN61 attached From: Amy Bivins Sent: Tuesday, April 24, 2018 10:20 AM To: Chris Pelling <chris(a)netearth.net<mailto:chris@netearth.net>> Subject: PP fees document from ICANN61 attached Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMGaQ&…>

1 0

FW: PP fees document from ICANN61 attached
by Amy Bivins April 24, 2018

April 24, 2018

From: Amy Bivins Sent: Tuesday, April 24, 2018 10:20 AM To: Chris Pelling <chris(a)netearth.net> Subject: PP fees document from ICANN61 attached Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 1

Agenda for today's PP IRT call
by Amy Bivins April 24, 2018

April 24, 2018

Dear Colleagues, On the PP IRT call this morning (starting in about 90 minutes at 1400 UTC) we will have Xavier Calvez joining us to provide an overview of how ICANN org developed the PP IRT fees proposal. Xavier will also be available to answer any questions. I'm aware that there is a community call on GDPR starting at 1500 UTC, so we plan to wrap up before that call begins, as I know many of you will likely be attending that meeting. I look forward to meeting with you shortly. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 3

Re: [Gdd-gnso-ppsai-impl] Agenda for today's PP IRT call
by Michele Neylon - Blacknight April 24, 2018

April 24, 2018

What “community call” on GDPR? -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845 From: Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl-bounces(a)icann.org> on behalf of Amy Bivins <amy.bivins(a)icann.org> Reply-To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Date: Tuesday 24 April 2018 at 13:34 To: "gdd-gnso-ppsai-impl(a)icann.org" <gdd-gnso-ppsai-impl(a)icann.org> Subject: [Gdd-gnso-ppsai-impl] Agenda for today's PP IRT call Dear Colleagues, On the PP IRT call this morning (starting in about 90 minutes at 1400 UTC) we will have Xavier Calvez joining us to provide an overview of how ICANN org developed the PP IRT fees proposal. Xavier will also be available to answer any questions. I’m aware that there is a community call on GDPR starting at 1500 UTC, so we plan to wrap up before that call begins, as I know many of you will likely be attending that meeting. I look forward to meeting with you shortly. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

3 3

Remove, unsubscribe
by Denise Michel April 19, 2018

April 19, 2018

Please remove me from this group and unsubscribe me from this email list. Thanks Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com<mailto:denisemichel@fb.com>

1 0

Notes, action items from today's PP IRT meeting--feedback requested by 27 April
by Amy Bivins April 17, 2018

April 17, 2018

Dear Colleagues, Thank you for your participation on today's privacy/proxy IRT call. For those who could not attend, I regret that we were unable to record this meeting (an issue with a new internal recording policy), but this was a one-time issue and all future meetings will be recorded. I've done my best to annotate the LEA specification document with the items we discussed, and have also attached the chat transcript. IRT Action Items We are nearing the completion of discussions on the LEA Specification. Other than the item of clear disagreement among members of the IRT-the time period for high priority requests-we are largely in the refining stage. To that end, we have a few final proposed edits for the group to review and comment on-including some edits that were originally suggested by Sara Bockey a few weeks ago and supported by many registrar members of the IRT. If we don't hear any opposition to these edits that would warrant further discussion, we will make these edits as requested in the draft we publish for comment. Today, we considered whether the LEA Framework Specification would be clearer if we reorganized it slightly, to make more clear where processes apply to high priority requests and when they don't. I've included two versions of the draft-the one with "orig" at the end of the title-which includes the proposed edits without reorganizing, and the "reorganized" one. Please review both and respond to the list with your thoughts about the proposed reorganizing of this. Please provide any additional input you have on this draft no later than next Friday, 27 April. Please note, specifically, questions in the following sections: Original Numbering Reorganized Version Section 2.1.10 (addition of "except in high priority" language at beginning of edit) Same section Section 3.2.1 (addition of the words "Standard Priority" to make clear this 2 business day receipt process doesn't apply in high priority cases) Moved to Section 3.2.2 Section 4.2.2 (inclusion of "without limitations" language, plus input about and question from Steve Metalitz-any other reasons that registrars feel would be reasonable for refusing disclosure?); Also see feedback, generally, from PSWG liaison, in meeting chat transcript (most pasted into specification document but cuts off at the end) Same section Section 4.2.2.5 (is this redundant? ) Same section Section 4.2.6 (is this redundant?) Same section I'm also attaching the most recent draft de-accreditation procedure document. As mentioned on the list last week, upon further consideration on the ICANN org side we think we should add back in the proposed transition procedure for customers impacted by the de-accreditation or termination of a third-party provider (section 4). Please review and provide any further comments on this no later than 27 April. For next week, we are hoping to have the requested fees information ready for you to discuss. I'll update you as soon as I can. Best, Amy Amy E. Bivins Registrar Services and Engagement Senior Manager Registrar Services and Industry Relations Internet Corporation for Assigned Names and Numbers (ICANN) Direct: +1 (202) 249-7551 Fax: +1 (202) 789-0104 Email: amy.bivins(a)icann.org<mailto:amy.bivins@icann.org> www.icann.org<http://www.icann.org>

2 1