PPSAI IRT: Accreditation Model Comments Due Friday 30 May
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#he...> 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/1fMhQNnxEM9l4RsFc3cmw62RwhADHSICFId4E...>. 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/>)
I need help finding how to add my comments into the document. Here's what I want to add. Privacy and Proxy providers provide different services, so my comments on them are distinct. Proxy providers submit their own name as the Registrant. (The Registrant is also known as the Registered Name Holder (RNH).) The Proxy provider does not provide to the Registrar the name of the beneficial user of the domain name, thereby undermining the requirement that accurate information must be provided. This practice of using proxy providers arose prior to the GDPR because Registrars did not restrict access to registration data. Registrars are now required to protect the privacy of Registrants, so there is no longer a legitimate purpose for Proxy providers. Registrars should refuse registrations from known Proxy providers. If a registration is made from an unknown Proxy provider, the Registrar should treat the Proxy as the legal Registrant. No accreditation of Proxy providers is required. Registrars do need to operate Proxy Providers. They can restrict access to the registration data in accordance with applicable laws and policies while maintaining accurate records. Privacy providers provide a distinctly different service. They submit the accurate name of the Registrant but alternative contact information -- email address, phone and/or physical address. The purpose is to have communications from parties seeking to communicate with the Registrant directed to an intermediary instead of directly to the Registrant. This function can and should be provided in a more direct and visible fashion. Instead of putting alternative contact data into the data fields associated with the Registrant, there should be a new role defined for accepting correspondence, *Correspondence.* The Registrant's contact data should still be collected, but it need not be supplied to most Requestors. If the Correspondence role is populated with contact data, it should be returned to the Requestor and explicitly labeled as Correspondence contact data. Thanks, Steve Crocker On Wed, May 28, 2025 at 2:55 PM Jessica Puccio via Gdd-gnso-ppsai-impl < gdd-gnso-ppsai-impl@icann.org> wrote:
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#he...> 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/1fMhQNnxEM9l4RsFc3cmw62RwhADHSICFId4E...> .
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
--
Jessica Puccio
Sr Coordinator, Review Support and Accountability Projects
Internet Corporation for Assigned Names and Numbers (ICANN <http://www.icann.org/>)
_______________________________________________ Gdd-gnso-ppsai-impl mailing list -- gdd-gnso-ppsai-impl@icann.org To unsubscribe send an email to 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.
-- Sent by a Verified sender
I agree with Steve that the definitions are woefully out of date but have reviewed the document and look forward to our conversation. Servus, Reg -- Reg Levy | Associate General Counsel – Domains +1 (323) 880-0831 Tucows #MakingTheInternetBetter UTC -8
On May 28, 2025, at 15:09, Steve Crocker via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org> wrote:
I need help finding how to add my comments into the document. Here's what I want to add.
Privacy and Proxy providers provide different services, so my comments on them are distinct.
Proxy providers submit their own name as the Registrant. (The Registrant is also known as the Registered Name Holder (RNH).) The Proxy provider does not provide to the Registrar the name of the beneficial user of the domain name, thereby undermining the requirement that accurate information must be provided. This practice of using proxy providers arose prior to the GDPR because Registrars did not restrict access to registration data. Registrars are now required to protect the privacy of Registrants, so there is no longer a legitimate purpose for Proxy providers.
Registrars should refuse registrations from known Proxy providers. If a registration is made from an unknown Proxy provider, the Registrar should treat the Proxy as the legal Registrant.
No accreditation of Proxy providers is required. Registrars do need to operate Proxy Providers. They can restrict access to the registration data in accordance with applicable laws and policies while maintaining accurate records.
Privacy providers provide a distinctly different service. They submit the accurate name of the Registrant but alternative contact information -- email address, phone and/or physical address. The purpose is to have communications from parties seeking to communicate with the Registrant directed to an intermediary instead of directly to the Registrant. This function can and should be provided in a more direct and visible fashion. Instead of putting alternative contact data into the data fields associated with the Registrant, there should be a new role defined for accepting correspondence, Correspondence. The Registrant's contact data should still be collected, but it need not be supplied to most Requestors. If the Correspondence role is populated with contact data, it should be returned to the Requestor and explicitly labeled as Correspondence contact data.
Thanks,
Steve Crocker
On Wed, May 28, 2025 at 2:55 PM Jessica Puccio via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org <mailto:gdd-gnso-ppsai-impl@icann.org>> wrote:
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#he...> 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/1fMhQNnxEM9l4RsFc3cmw62RwhADHSICFId4E...>.
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/>)
_______________________________________________ Gdd-gnso-ppsai-impl mailing list -- gdd-gnso-ppsai-impl@icann.org <mailto:gdd-gnso-ppsai-impl@icann.org> To unsubscribe send an email to gdd-gnso-ppsai-impl-leave@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.
--
_______________________________________________ Gdd-gnso-ppsai-impl mailing list -- gdd-gnso-ppsai-impl@icann.org To unsubscribe send an email to 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.
Thank you for your comments, Reg and Steve. We look forward to the IRT’s discussion on this as well. Steve, Jessica Puccio will reach out to you separately about posting your comments in the document. Best, Jason From: Reg Levy via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org> Reply-To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl@icann.org> Date: Wednesday, May 28, 2025 at 7:32 PM To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl@icann.org> Cc: Jessica Puccio <jessica.puccio@icann.org>, "steve@shinkuro.com" <steve@shinkuro.com>, Reg Levy <rlevy@tucows.com> Subject: [Gdd-gnso-ppsai-impl] Re: PPSAI IRT: Accreditation Model Comments Due Friday 30 May I agree with Steve that the definitions are woefully out of date but have reviewed the document and look forward to our conversation. Servus, Reg -- Reg Levy | Associate General Counsel – Domains +1 (323) 880-0831 Tucows #MakingTheInternetBetter UTC -8 On May 28, 2025, at 15:09, Steve Crocker via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org> wrote: I need help finding how to add my comments into the document. Here's what I want to add. Privacy and Proxy providers provide different services, so my comments on them are distinct. Proxy providers submit their own name as the Registrant. (The Registrant is also known as the Registered Name Holder (RNH).) The Proxy provider does not provide to the Registrar the name of the beneficial user of the domain name, thereby undermining the requirement that accurate information must be provided. This practice of using proxy providers arose prior to the GDPR because Registrars did not restrict access to registration data. Registrars are now required to protect the privacy of Registrants, so there is no longer a legitimate purpose for Proxy providers. Registrars should refuse registrations from known Proxy providers. If a registration is made from an unknown Proxy provider, the Registrar should treat the Proxy as the legal Registrant. No accreditation of Proxy providers is required. Registrars do need to operate Proxy Providers. They can restrict access to the registration data in accordance with applicable laws and policies while maintaining accurate records. Privacy providers provide a distinctly different service. They submit the accurate name of the Registrant but alternative contact information -- email address, phone and/or physical address. The purpose is to have communications from parties seeking to communicate with the Registrant directed to an intermediary instead of directly to the Registrant. This function can and should be provided in a more direct and visible fashion. Instead of putting alternative contact data into the data fields associated with the Registrant, there should be a new role defined for accepting correspondence, Correspondence. The Registrant's contact data should still be collected, but it need not be supplied to most Requestors. If the Correspondence role is populated with contact data, it should be returned to the Requestor and explicitly labeled as Correspondence contact data. Thanks, Steve Crocker On Wed, May 28, 2025 at 2:55 PM Jessica Puccio via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>> wrote: 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 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/14FEv67ER-Qnz2...> 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 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1fMhQNnxEM...>. 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 [icann83.sched.com]<https://urldefense.com/v3/__https:/icann83.sched.com/event/246XK/gds-ppsai-i...>. 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/>) _______________________________________________ Gdd-gnso-ppsai-impl mailing list -- gdd-gnso-ppsai-impl@icann.org<mailto:gdd-gnso-ppsai-impl@icann.org> To unsubscribe send an email to gdd-gnso-ppsai-impl-leave@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. -- Sent by a Verified sender _______________________________________________ Gdd-gnso-ppsai-impl mailing list -- gdd-gnso-ppsai-impl@icann.org To unsubscribe send an email to 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.
I agree 100%; the definitions are outdated and nonsensical. There are proxy service providers whose details replace those of the underlying RNH. But registrars cannot screen out those. As a retail-focused registrar, we do not have resellers but many web agencies as direct customers who, for one reason or another, will appoint themselves as registrants instead of their clients. One can determine they are acting as a proxy only by browsing the website the domain name points to. This is also true for law firms, holding companies etc. For those registrations, registrars don’t know the identity of the underlying registrant. And there are privacy service providers most often affiliated with registrars. Those will also publish the names of their entities used for the privacy service, but will most often publish an anonymised details that allow to contact the RNH without disclosing their identity. For those registrations, registrars know the identity of the underlying registrant. And some standardisation of the disclosure process could be beneficial/possible. Some examples: https://www.domainsbyproxy.com/domainsbyproxy/difference https://support.opensrs.com/support/solutions/articles/201000063415-contact-... https://www.eurodns.com/domain-privacy https://withheldforprivacy.com<https://withheldforprivacy.com/> https://www.name.com/whois-privacy https://kb.centralnicreseller.com/services/whois-privacy However, I have yet to encounter the definition of privacy providers where the registrant’s name is still published. See you all in Prague! Luc From: Jason Kean via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org> Date: Thursday, 29 May 2025 at 17:44 To: PPSAI IRT members, including observers <gdd-gnso-ppsai-impl@icann.org> Cc: Jessica Puccio <jessica.puccio@icann.org>, steve@shinkuro.com <steve@shinkuro.com>, Reg Levy <rlevy@tucows.com>, Jason Kean <jason.kean@icann.org> Subject: [Gdd-gnso-ppsai-impl] Re: PPSAI IRT: Accreditation Model Comments Due Friday 30 May Thank you for your comments, Reg and Steve. We look forward to the IRT’s discussion on this as well. Steve, Jessica Puccio will reach out to you separately about posting your comments in the document. Best, Jason From: Reg Levy via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org> Reply-To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl@icann.org> Date: Wednesday, May 28, 2025 at 7:32 PM To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl@icann.org> Cc: Jessica Puccio <jessica.puccio@icann.org>, "steve@shinkuro.com" <steve@shinkuro.com>, Reg Levy <rlevy@tucows.com> Subject: [Gdd-gnso-ppsai-impl] Re: PPSAI IRT: Accreditation Model Comments Due Friday 30 May I agree with Steve that the definitions are woefully out of date but have reviewed the document and look forward to our conversation. Servus, Reg -- Reg Levy | Associate General Counsel – Domains +1 (323) 880-0831 Tucows #MakingTheInternetBetter UTC -8 On May 28, 2025, at 15:09, Steve Crocker via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org> wrote: I need help finding how to add my comments into the document. Here's what I want to add. Privacy and Proxy providers provide different services, so my comments on them are distinct. Proxy providers submit their own name as the Registrant. (The Registrant is also known as the Registered Name Holder (RNH).) The Proxy provider does not provide to the Registrar the name of the beneficial user of the domain name, thereby undermining the requirement that accurate information must be provided. This practice of using proxy providers arose prior to the GDPR because Registrars did not restrict access to registration data. Registrars are now required to protect the privacy of Registrants, so there is no longer a legitimate purpose for Proxy providers. Registrars should refuse registrations from known Proxy providers. If a registration is made from an unknown Proxy provider, the Registrar should treat the Proxy as the legal Registrant. No accreditation of Proxy providers is required. Registrars do need to operate Proxy Providers. They can restrict access to the registration data in accordance with applicable laws and policies while maintaining accurate records. Privacy providers provide a distinctly different service. They submit the accurate name of the Registrant but alternative contact information -- email address, phone and/or physical address. The purpose is to have communications from parties seeking to communicate with the Registrant directed to an intermediary instead of directly to the Registrant. This function can and should be provided in a more direct and visible fashion. Instead of putting alternative contact data into the data fields associated with the Registrant, there should be a new role defined for accepting correspondence, Correspondence. The Registrant's contact data should still be collected, but it need not be supplied to most Requestors. If the Correspondence role is populated with contact data, it should be returned to the Requestor and explicitly labeled as Correspondence contact data. Thanks, Steve Crocker On Wed, May 28, 2025 at 2:55 PM Jessica Puccio via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>> wrote: 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 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/14FEv67ER-Qnz2...> 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 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1fMhQNnxEM...>. 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 [icann83.sched.com]<https://urldefense.com/v3/__https:/icann83.sched.com/event/246XK/gds-ppsai-i...>. 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/>) _______________________________________________ Gdd-gnso-ppsai-impl mailing list -- gdd-gnso-ppsai-impl@icann.org<mailto:gdd-gnso-ppsai-impl@icann.org> To unsubscribe send an email to gdd-gnso-ppsai-impl-leave@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. -- Sent by a Verified sender _______________________________________________ Gdd-gnso-ppsai-impl mailing list -- gdd-gnso-ppsai-impl@icann.org To unsubscribe send an email to 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.
Hi Luc, Namecheap’s affiliated privacy service would in theory put the registrant’s name in the RDDS, but we redact that per the GDPR/Temp Spec. The output thus looks like: Registrant Name: Redacted for Privacy Registrant Organization: Privacy service provided by Withheld for Privacy ehf Registrant Street: Kalkofnsvegur 2 Registrant City: Reykjavik Registrant State/Province: Capital Region Registrant Postal Code: 101 Registrant Country: IS Registrant Phone: +354.4212434 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: [letters/numbers redacted by OS].protect@withheldforprivacy.com The service is thus only used to mask the personal data of all contacts, and yes, we know the underlying data. Regards, Owen
On Jun 5, 2025, at 19:01, Luc SEUFER via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org> wrote:
CAUTION: This email originated from outside the organization. Do not click links unless you can confirm the sender and know the content is safe. I agree 100%; the definitions are outdated and nonsensical.
There are proxy service providers whose details replace those of the underlying RNH. But registrars cannot screen out those. As a retail-focused registrar, we do not have resellers but many web agencies as direct customers who, for one reason or another, will appoint themselves as registrants instead of their clients. One can determine they are acting as a proxy only by browsing the website the domain name points to. This is also true for law firms, holding companies etc. For those registrations, registrars don’t know the identity of the underlying registrant.
And there are privacy service providers most often affiliated with registrars. Those will also publish the names of their entities used for the privacy service, but will most often publish an anonymised details that allow to contact the RNH without disclosing their identity. For those registrations, registrars know the identity of the underlying registrant. And some standardisation of the disclosure process could be beneficial/possible. Some examples: https://www.domainsbyproxy.com/domainsbyproxy/difference https://support.opensrs.com/support/solutions/articles/201000063415-contact-... https://www.eurodns.com/domain-privacy https://withheldforprivacy.com <https://withheldforprivacy.com/> https://www.name.com/whois-privacy https://kb.centralnicreseller.com/services/whois-privacy
However, I have yet to encounter the definition of privacy providers where the registrant’s name is still published.
See you all in Prague!
Luc
From: Jason Kean via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org <mailto:gdd-gnso-ppsai-impl@icann.org>> Date: Thursday, 29 May 2025 at 17:44 To: PPSAI IRT members, including observers <gdd-gnso-ppsai-impl@icann.org <mailto:gdd-gnso-ppsai-impl@icann.org>> Cc: Jessica Puccio <jessica.puccio@icann.org <mailto:jessica.puccio@icann.org>>, steve@shinkuro.com <mailto:steve@shinkuro.com> <steve@shinkuro.com <mailto:steve@shinkuro.com>>, Reg Levy <rlevy@tucows.com <mailto:rlevy@tucows.com>>, Jason Kean <jason.kean@icann.org <mailto:jason.kean@icann.org>> Subject: [Gdd-gnso-ppsai-impl] Re: PPSAI IRT: Accreditation Model Comments Due Friday 30 May
Thank you for your comments, Reg and Steve. We look forward to the IRT’s discussion on this as well.
Steve, Jessica Puccio will reach out to you separately about posting your comments in the document.
Best, Jason
From: Reg Levy via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org> Reply-To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl@icann.org> Date: Wednesday, May 28, 2025 at 7:32 PM To: "PPSAI IRT members, including observers" <gdd-gnso-ppsai-impl@icann.org> Cc: Jessica Puccio <jessica.puccio@icann.org>, "steve@shinkuro.com" <steve@shinkuro.com>, Reg Levy <rlevy@tucows.com> Subject: [Gdd-gnso-ppsai-impl] Re: PPSAI IRT: Accreditation Model Comments Due Friday 30 May
I agree with Steve that the definitions are woefully out of date but have reviewed the document and look forward to our conversation.
Servus, Reg
-- Reg Levy | Associate General Counsel – Domains +1 (323) 880-0831 Tucows #MakingTheInternetBetter
UTC -8
On May 28, 2025, at 15:09, Steve Crocker via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org> wrote:
I need help finding how to add my comments into the document. Here's what I want to add.
Privacy and Proxy providers provide different services, so my comments on them are distinct.
Proxy providers submit their own name as the Registrant. (The Registrant is also known as the Registered Name Holder (RNH).) The Proxy provider does not provide to the Registrar the name of the beneficial user of the domain name, thereby undermining the requirement that accurate information must be provided. This practice of using proxy providers arose prior to the GDPR because Registrars did not restrict access to registration data. Registrars are now required to protect the privacy of Registrants, so there is no longer a legitimate purpose for Proxy providers.
Registrars should refuse registrations from known Proxy providers. If a registration is made from an unknown Proxy provider, the Registrar should treat the Proxy as the legal Registrant.
No accreditation of Proxy providers is required. Registrars do need to operate Proxy Providers. They can restrict access to the registration data in accordance with applicable laws and policies while maintaining accurate records.
Privacy providers provide a distinctly different service. They submit the accurate name of the Registrant but alternative contact information -- email address, phone and/or physical address. The purpose is to have communications from parties seeking to communicate with the Registrant directed to an intermediary instead of directly to the Registrant. This function can and should be provided in a more direct and visible fashion. Instead of putting alternative contact data into the data fields associated with the Registrant, there should be a new role defined for accepting correspondence, Correspondence. The Registrant's contact data should still be collected, but it need not be supplied to most Requestors. If the Correspondence role is populated with contact data, it should be returned to the Requestor and explicitly labeled as Correspondence contact data.
Thanks,
Steve Crocker
On Wed, May 28, 2025 at 2:55 PM Jessica Puccio via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org <mailto:gdd-gnso-ppsai-impl@icann.org>> wrote: 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 [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/document/d/14FEv67ER-Qnz2...> 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 [docs.google.com] <https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1fMhQNnxEM...>.
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 [icann83.sched.com] <https://urldefense.com/v3/__https:/icann83.sched.com/event/246XK/gds-ppsai-i...>. 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/>)
_______________________________________________ Gdd-gnso-ppsai-impl mailing list -- gdd-gnso-ppsai-impl@icann.org <mailto:gdd-gnso-ppsai-impl@icann.org> To unsubscribe send an email to gdd-gnso-ppsai-impl-leave@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.
-- Sent by a Verified
sender _______________________________________________ Gdd-gnso-ppsai-impl mailing list -- gdd-gnso-ppsai-impl@icann.org To unsubscribe send an email to 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.
******************** CAUTION: This email originated from outside the organization. Do not click links unless you can confirm the sender and know the content is safe. ********************
_______________________________________________ Gdd-gnso-ppsai-impl mailing list -- gdd-gnso-ppsai-impl@icann.org To unsubscribe send an email to 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.
Hello Steve – I will be glad to reach out directly and assist with getting your comments applied to the appropriate sections of the document. Many Thanks -- Jessica Puccio Sr Coordinator, Review Support and Accountability Projects Internet Corporation for Assigned Names and Numbers (ICANN<http://www.icann.org/>) On 5/28/25, 18:09, "Steve Crocker" <steve@shinkuro.com<mailto:steve@shinkuro.com>> wrote: I need help finding how to add my comments into the document. Here's what I want to add. Privacy and Proxy providers provide different services, so my comments on them are distinct. Proxy providers submit their own name as the Registrant. (The Registrant is also known as the Registered Name Holder (RNH).) The Proxy provider does not provide to the Registrar the name of the beneficial user of the domain name, thereby undermining the requirement that accurate information must be provided. This practice of using proxy providers arose prior to the GDPR because Registrars did not restrict access to registration data. Registrars are now required to protect the privacy of Registrants, so there is no longer a legitimate purpose for Proxy providers. Registrars should refuse registrations from known Proxy providers. If a registration is made from an unknown Proxy provider, the Registrar should treat the Proxy as the legal Registrant. No accreditation of Proxy providers is required. Registrars do need to operate Proxy Providers. They can restrict access to the registration data in accordance with applicable laws and policies while maintaining accurate records. Privacy providers provide a distinctly different service. They submit the accurate name of the Registrant but alternative contact information -- email address, phone and/or physical address. The purpose is to have communications from parties seeking to communicate with the Registrant directed to an intermediary instead of directly to the Registrant. This function can and should be provided in a more direct and visible fashion. Instead of putting alternative contact data into the data fields associated with the Registrant, there should be a new role defined for accepting correspondence, Correspondence. The Registrant's contact data should still be collected, but it need not be supplied to most Requestors. If the Correspondence role is populated with contact data, it should be returned to the Requestor and explicitly labeled as Correspondence contact data. Thanks, Steve Crocker On Wed, May 28, 2025 at 2:55 PM Jessica Puccio via Gdd-gnso-ppsai-impl <gdd-gnso-ppsai-impl@icann.org<mailto:gdd-gnso-ppsai-impl@icann.org>> wrote: 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 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/14FEv67ER-Qnz2...> 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 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1fMhQNnxEM...>. 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 [icann83.sched.com]<https://urldefense.com/v3/__https:/icann83.sched.com/event/246XK/gds-ppsai-i...>. 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/>) _______________________________________________ Gdd-gnso-ppsai-impl mailing list -- gdd-gnso-ppsai-impl@icann.org<mailto:gdd-gnso-ppsai-impl@icann.org> To unsubscribe send an email to gdd-gnso-ppsai-impl-leave@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. -- Sent by a Verified sender
participants (6)
-
Jason Kean -
Jessica Puccio -
Luc SEUFER -
Owen Smigelski -
Reg Levy -
Steve Crocker