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

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