<div dir="ltr"><div>I agree with Alan here. Let's not turn third party obligations into registrar obligations. If something is an obligation of a p/p service provider, it does not need to also be a registrar obligation.</div><div>Best,<br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span lang="EN-US">-- <br>Volker A. Greimann<br>General Counsel and Policy Manager<br><b>KEY-SYSTEMS GMBH</b><br><br>T: +49 6894 9396901<br>M: +49 6894 9396851<br>F: +49 6894 9396851<br>W: </span><a href="http://www.key-systems.net/" style="color:rgb(17,85,204)" target="_blank"><span lang="EN-US">www.key-systems.net</span></a><span lang="EN-US"><br><br>Key-Systems GmbH is a company registered at the local court of Saarbruecken, Germany with the registration no. HR B 18835<br>CEO: Oliver Fries and Robert Birkner<br><br>Part of the CentralNic Group PLC (LON: CNIC) a company registered in England and Wales with company number 8576358.</span><br></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 28, 2020 at 4:35 PM Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">My understanding is that under the new P/P policy, an accredited P/P service has an agreement with ICANN and it is THEIR contractual obligation, not the registrar. The meaningfulness of an affiliated P/P service disappears once the new accreditation process is operational.<br><br>Alan<br><br><div class="gmail_quote">On July 28, 2020 10:20:38 AM EDT, "James M. Bladel" <<a href="mailto:jbladel@godaddy.com" target="_blank">jbladel@godaddy.com</a>> wrote:<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="gmail-m_8954613518351071825WordSection1">
<p class="MsoNormal">If they aren’t “affiliated” then we can’t accept any contractual obligations on their behalf. And if they aren’t “accredited” then they shouldn’t be offering privacy services. So leaving the sentence with “and” ensures that we are both
authorized (accredited) and capable (accredited) of meeting the requirement.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Note: I can’t help feeling like we are polishing the chrome on the Titanic here. Privacy services are becoming less relevant (and less attractive to customers) as the year progresses.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">J.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border-color:rgb(181,196,223) currentcolor currentcolor;border-style:solid none none;border-width:1pt medium medium;padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" target="_blank">gnso-epdp-team-bounces@icann.org</a>> on behalf of "Kapin, Laureen via Gnso-epdp-team" <<a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a>><br>
<b>Reply-To: </b>"Kapin, Laureen" <<a href="mailto:LKAPIN@ftc.gov" target="_blank">LKAPIN@ftc.gov</a>><br>
<b>Date: </b>Tuesday, July 28, 2020 at 5:53 AM<br>
<b>To: </b>"<a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a>" <<a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a>><br>
<b>Subject: </b>Re: [Gnso-epdp-team] Rec. 19 (time sensitive)<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div style="border-color:currentcolor currentcolor currentcolor rgb(166,166,166);border-style:none none none solid;border-width:medium medium medium 4.5pt;padding:0in 0in 0in 14pt">
<p class="MsoNormal" style="background:rgb(235,235,235) none repeat scroll 0% 0%"><span style="font-size:9pt;font-family:"Tahoma",sans-serif;color:black">Notice:</span><span style="color:black">
</span><span style="font-size:9pt;font-family:"Tahoma",sans-serif;color:black">This email is from an external sender.
</span><u></u><u></u></p>
</div>
<p> <u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)">I welcome input from my Registrar colleagues on this issue re: the first sentence of Rec. 19.1 (</span><span style="font-size:14pt;font-family:"Arial",sans-serif">“In
the case of a domain name registration where an <i><span style="background:yellow none repeat scroll 0% 0%">affiliated and</span>
</i>accredited privacy/proxy service is used. . .”)</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:14pt;font-family:"Arial",sans-serif;color:black">GAC Note: Should this be
<i>“or”</i> or <i>“and/or”</i>?</span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:0.5in"><b><span style="font-size:14pt;font-family:"Arial",sans-serif;color:black">“In the case of a domain name registration where an affiliated
<span style="background:yellow none repeat scroll 0% 0%">‘or’</span> accredited privacy proxy service is used?”</span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:14pt;font-family:"Arial",sans-serif;color:black">My understanding is that no P/P providers will actually be “accredited” until the implementation of the PPSAI Policy Recommendations. Having suggested this revision,
I want to make sure we’ve gotten it right. </span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)"> </span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">Kind regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">Laureen Kapin</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">Counsel for International Consumer Protection</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">Federal Trade Commission</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">(202) 326-3237
</span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)"> </span><u></u><u></u></p>
<div>
<div style="border-color:rgb(225,225,225) currentcolor currentcolor;border-style:solid none none;border-width:1pt medium medium;padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" target="_blank">gnso-epdp-team-bounces@icann.org</a>>
<b>On Behalf Of </b>Kapin, Laureen via Gnso-epdp-team<br>
<b>Sent:</b> Monday, July 27, 2020 3:47 PM<br>
<b>To:</b> <a href="mailto:gnso-epdp-team@icann.org" target="_blank">gnso-epdp-team@icann.org</a><br>
<b>Subject:</b> [Gnso-epdp-team] FW: Rec. 19 (time sensitive)<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)">Hi folks,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)"> I’m forwarding proposed changes to Rec. 19 (Privacy Proxy) that the Rgr’s, Rgy’s (deferring to Rgr’s) and GAC have agreed to. As you’ll see below, we think these
edits will improve the clarity of the Recommendation 19. For convenience, more context is provided in this email chain and I’m also including the revised text (changes highlighted) here below. I’m happy to answer any questions.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)"> </span><b><span style="font-size:14pt;font-family:"Arial",sans-serif">Proposed Revised text of Rec. 19:</span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">Recommendation #19 Display of information of affiliated
<i><span style="background:yellow none repeat scroll 0% 0%">and accredited</span></i> privacy/proxy providers</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">19.1 In the case of a domain name registration where an
<i><span style="background:yellow none repeat scroll 0% 0%">affiliated and</span> </i>
accredited privacy/proxy service is used, e.g., where data associated with a natural person is masked,<span style="color:rgb(0,32,96)">
</span>Registrar (and Registry, where applicable) MUST include the full RDDS data of the
<s>accredited</s> <i><span style="background:yellow none repeat scroll 0% 0%">applicable</span>
</i>privacy/proxy service in response to an RDDS query. The full privacy/proxy RDDS data may also include a pseudonymized email.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">Implementation notes:
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">19.2 Once ICANN org has implemented a privacy/proxy service accreditation program, this
<i><span style="background:yellow none repeat scroll 0% 0%">R</span></i>ecommendation
<i><span style="background:yellow none repeat scroll 0% 0%">19</span> </i>once in effect
<i><span style="background:yellow none repeat scroll 0% 0%">will</span> </i>replace<s><span style="background:yellow none repeat scroll 0% 0%">s</span></s> or otherwise supersede<s><span style="background:yellow none repeat scroll 0% 0%">s</span></s> EPDP phase 1 recommendation
#14.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">19.3 The intent of this recommendation is to provide clear instruction to registrars (and registries where applicable) that where a domain registration is done via
<i><span style="background:yellow none repeat scroll 0% 0%">an affiliated or</span> </i>
accredited privacy/proxy provider, that data MUST NOT also be redacted. The working group is intending that domain registration data should MUST NOT be both redacted and privacy/proxied.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)"> </span><u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">Kind regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">Laureen Kapin</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">Counsel for International Consumer Protection</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">Federal Trade Commission</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">(202) 326-3237
</span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:rgb(0,32,96)"> </span><u></u><u></u></p>
<div>
<div style="border-color:rgb(225,225,225) currentcolor currentcolor;border-style:solid none none;border-width:1pt medium medium;padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> Kapin, Laureen <br>
<b>Sent:</b> Monday, July 27, 2020 10:12 AM<br>
<b>To:</b> James M. Bladel <<a href="mailto:jbladel@godaddy.com" target="_blank">jbladel@godaddy.com</a>>; <a href="mailto:swyld@tucows.com" target="_blank">swyld@tucows.com</a>; '<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>' <<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>>; King, Brian (<a href="mailto:Brian.King@markmonitor.com" target="_blank">Brian.King@markmonitor.com</a>) <<a href="mailto:Brian.King@markmonitor.com" target="_blank">Brian.King@markmonitor.com</a>>; <a href="mailto:Christopher.Lewis-Evans@nca.gov.uk" target="_blank">Christopher.Lewis-Evans@nca.gov.uk</a>; Anderson, Marc (<a href="mailto:mcanderson@verisign.com" target="_blank">mcanderson@verisign.com</a>)
<<a href="mailto:mcanderson@verisign.com" target="_blank">mcanderson@verisign.com</a>><br>
<b>Cc:</b> Marika Konings <<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</a>>; Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>><br>
<b>Subject:</b> Rec. 19 (time sensitive)<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">Hi folks,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> Rec. 19 seems like something we may be able to clarify and agree upon prior to submitting our consensus designations. I think the current wording of Rec. 19 is not clear in
these ways:</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<ol style="margin-top:0in" type="1" start="1">
<li class="gmail-m_8954613518351071825MsoListParagraph" style="margin-left:0in"><span style="font-size:14pt;font-family:"Arial",sans-serif">The inconsistency between the title of the Rec. and the content (title references “affiliated” and content references
“accredited”)</span><u></u><u></u></li><li class="gmail-m_8954613518351071825MsoListParagraph" style="margin-left:0in"><span style="font-size:14pt;font-family:"Arial",sans-serif">The open question of its applicability to both affiliated and accredited Privacy Proxy Service Providers</span><u></u><u></u></li><li class="gmail-m_8954613518351071825MsoListParagraph" style="margin-left:0in"><span style="font-size:14pt;font-family:"Arial",sans-serif">The indefinite “this” reference</span><u></u><u></u></li></ol>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">This seems like something we should sort out before going to final publication. To that end, I’m proposing some clarifying revisions below. For context, I also include
</span><u></u><u></u></p>
<ol style="margin-top:0in" type="1" start="1">
<li class="gmail-m_8954613518351071825MsoListParagraph" style="margin-left:0in"><span style="font-size:14pt;font-family:"Arial",sans-serif">the Category 2 comment by the GAC, joined by ALAC and BC and objected to by the Registrars and Registries;</span><u></u><u></u></li><li class="gmail-m_8954613518351071825MsoListParagraph" style="margin-left:0in"><span style="font-size:14pt;font-family:"Arial",sans-serif">the original Rec. 19 text</span><u></u><u></u></li></ol>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">I welcome your input and hope we can resolve and improve this recommendation. Doing so will affect the GAC’s Consensus designations, so please let us know whether this is something
we can resolve sooner rather than later. Thanks!</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Times New Roman",serif"> </span><u></u><u></u></p>
<div style="border-color:currentcolor currentcolor windowtext;border-style:none none solid;border-width:medium medium 1.5pt;padding:0in 0in 1pt">
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Times New Roman",serif"> </span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Times New Roman",serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:14pt;font-family:"Arial",sans-serif">Category 2 proposed changes:</span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Times New Roman",serif"> </span><u></u><u></u></p>
<table style="border-collapse:collapse" cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td style="border:1pt solid black;padding:0in 5.4pt" valign="top">
<p class="gmail-m_8954613518351071825MsoListParagraph" style="margin-left:21pt;vertical-align:baseline">
<span>131.<span style="font:7pt "Times New Roman"">
</span></span><span style="font-size:12pt;color:black">GAC / BC /ALAC</span><u></u><u></u></p>
</td>
<td style="border-color:black black black currentcolor;border-style:solid solid solid none;border-width:1pt 1pt 1pt medium;padding:0in 5.4pt" valign="top">
<p class="MsoNormal"><span style="font-size:12pt;color:black">Rec. 19 Privacy/Proxy</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Times New Roman",serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12pt;color:black">2041-42</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Times New Roman",serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12pt;color:black">Display of information of affiliated privacy / proxy providers</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12pt;color:black"> </span><u></u><u></u></p>
</td>
<td style="border-color:black black black currentcolor;border-style:solid solid solid none;border-width:1pt 1pt 1pt medium;padding:0in 5.4pt" valign="top">
<p class="MsoNormal"><span style="font-size:12pt;color:black">Clarify ambiguity -- the phrase “once in effect” seems unclear and unnecessary. Also, does this language mean that Rec. 19 only goes into effect once the PPSAI implementation is complete? </span><u></u><u></u></p>
</td>
<td style="border-color:black black black currentcolor;border-style:solid solid solid none;border-width:1pt 1pt 1pt medium;padding:0in 5.4pt" valign="top">
<p class="MsoNormal"><span style="font-size:12pt;color:black">Delete “once in effect” from the following: “Once ICANN org has implemented a privacy/proxy service accreditation program, this recommendation ‘once in effect’ replaces or otherwise supersedes
EPDP phase 1 recommendation #14.” Also clarify timing of when this Rec. comes into play.</span><u></u><u></u></p>
</td>
<td style="border-color:black black black currentcolor;border-style:solid solid solid none;border-width:1pt 1pt 1pt medium;padding:0in 5.4pt" valign="top">
<p class="MsoNormal"><span style="font-size:12pt;color:black">RrSG: Disagree with change. Recommendation 19 cannot possibly come into effect until after PPSAI is live, as Rec 19 relies on the existence of accredited P/P providers (which will not exist until
after PPSAI is live). </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Times New Roman",serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12pt;color:black">ALAC: Title of Rec #19 still refers to AFFILIATED P/P providers, but the text of the first paragraph refers to accredited P/P services. Surely the intent of this Rec if to cover Affiliated P/P
services now and Accredited ones once they exist.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12pt;font-family:"Times New Roman",serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:12pt;color:black">RySG: Do Not Support</span><u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif;color:white"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:14pt;font-family:"Arial",sans-serif">Current language Rec. 19:</span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><img style="width: 8.5937in; height: 5.25in;" id="gmail-m_8954613518351071825Picture_x0020_1" width="825" height="504"><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:14pt;font-family:"Arial",sans-serif">Proposed Revised text of Rec. 19:</span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">Recommendation #19 Display of information of affiliated
<i><span style="background:yellow none repeat scroll 0% 0%">and accredited</span></i> privacy/proxy providers</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">19.1 In the case of a domain name registration where an
<i><span style="background:yellow none repeat scroll 0% 0%">affiliated and</span> </i>
accredited privacy/proxy service is used, e.g., where data associated with a natural person is masked,Registrar (and Registry, where applicable) MUST include the full RDDS data of the
<s>accredited</s> <i><span style="background:yellow none repeat scroll 0% 0%">applicable</span>
</i>privacy/proxy service in response to an RDDS query. The full privacy/proxy RDDS data may also include a pseudonymized email.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">Implementation notes:
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">19.2 Once ICANN org has implemented a privacy/proxy service accreditation program, this
<i><span style="background:yellow none repeat scroll 0% 0%">R</span></i>ecommendation
<i><span style="background:yellow none repeat scroll 0% 0%">19</span> </i>once in effect
<i><span style="background:yellow none repeat scroll 0% 0%">will</span> </i>replace<s><span style="background:yellow none repeat scroll 0% 0%">s</span></s> or otherwise supersede<s><span style="background:yellow none repeat scroll 0% 0%">s</span></s> EPDP phase 1 recommendation
#14.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif">19.3 The intent of this recommendation is to provide clear instruction to registrars (and registries where applicable) that where a domain registration is done via
<i><span style="background:yellow none repeat scroll 0% 0%">an affiliated or</span> </i>
accredited privacy/proxy provider, that data MUST NOT also be redacted. The working group is intending that domain registration data should MUST NOT be both redacted and privacy/proxied.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:"Arial",sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">Kind regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">Laureen Kapin</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">Counsel for International Consumer Protection</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">Federal Trade Commission</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Helvetica;color:rgb(88,0,176)">(202) 326-3237
</span><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</div>_______________________________________________<br>
Gnso-epdp-team mailing list<br>
<a href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a><br>
_______________________________________________<br>
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 (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). 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.</blockquote></div>