<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:HelveticaNeue;}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.ms-outlook-ios-reference-expand, li.ms-outlook-ios-reference-expand, div.ms-outlook-ios-reference-expand
{mso-style-name:ms-outlook-ios-reference-expand;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#999999;}
p.ms-outlook-ios-availability-container, li.ms-outlook-ios-availability-container, div.ms-outlook-ios-availability-container
{mso-style-name:ms-outlook-ios-availability-container;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.ms-outlook-ios-mention, li.ms-outlook-ios-mention, div.ms-outlook-ios-mention
{mso-style-name:ms-outlook-ios-mention;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
background:#F1F1F1;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#333333;}
p.ms-outlook-ios-mention-external, li.ms-outlook-ios-mention-external, div.ms-outlook-ios-mention-external
{mso-style-name:ms-outlook-ios-mention-external;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
background:#FDF7E7;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#BA8F0D;}
p.ms-outlook-ios-mention-external-clear-design, li.ms-outlook-ios-mention-external-clear-design, div.ms-outlook-ios-mention-external-clear-design
{mso-style-name:ms-outlook-ios-mention-external-clear-design;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
background:#F1F1F1;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:#BA8F0D;}
span.emailstyle17
{mso-style-name:emailstyle17;
font-family:"Calibri",sans-serif;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;}
span.EmailStyle29
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:JA">Forwarding to list<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:JA"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Mark Svancarek (CELA)
<br>
<b>Sent:</b> Wednesday, December 19, 2018 12:37 PM<br>
<b>To:</b> Anderson, Marc <mcanderson@verisign.com>; jbladel@godaddy.com; caitlin.tubergen@icann.org<br>
<b>Subject:</b> RE: [Gnso-epdp-team] language re: affiliated privacy/proxy companies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Alternately: <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> "or offered by an accredited P/P provider"<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Although this assumes that PPSAI proceeds.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Mark Svancarek (CELA)
<br>
<b>Sent:</b> Wednesday, December 19, 2018 11:41<br>
<b>To:</b> 'Anderson, Marc' <<a href="mailto:mcanderson@verisign.com">mcanderson@verisign.com</a>>;
<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>; <a href="mailto:caitlin.tubergen@icann.org">
caitlin.tubergen@icann.org</a><br>
<b>Subject:</b> RE: [Gnso-epdp-team] language re: affiliated privacy/proxy companies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Marc, I would prefer:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt">“known Privacy or Proxy service”
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Which is a superset of <o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt">“<i><span style="color:black">offered or made available by Registrar or its Affiliates”</span></i><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">/msv<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org">gnso-epdp-team-bounces@icann.org</a>>
<b>On Behalf Of </b>Anderson, Marc via Gnso-epdp-team<br>
<b>Sent:</b> Wednesday, December 19, 2018 09:09<br>
<b>To:</b> <a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>; <a href="mailto:caitlin.tubergen@icann.org">
caitlin.tubergen@icann.org</a>; <a href="mailto:gnso-epdp-team@icann.org">gnso-epdp-team@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-epdp-team] language re: affiliated privacy/proxy companies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Hi all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">James makes a good point, I support his edit.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Caitlin’s proposed text has a typo showing “proxy/proxy” where I assume “privacy/proxy” is intended.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I have concerns with the text “…Registrar MUST return in response to any query full WHOIS data…” More specifically, I don’t think “any” actually means “any” in this context, “full” is undefined and should
more appropriately be “unredacted” and WHOIS should be replaced with RDS or RDDS. I suggest: “…<i>Registrar MUST return unredacted data in response to RDDS queries… “</i><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I understand the reason for this recommendation is so that Registrars do not redact registration data that is already protected by a known Privacy or Proxy service. If the Privacy/Proxy service is operating
as intended than personally identifiable information of the registrant has already been removed from the RDDS record and so further redacting it is redundant and creates an unnecessary hurdle for a requestor with a legitimate need to access the actual registration
data behind the service. While Caitlin’s proposed language is generally clear, sometimes an explanation of the intent can be helpful in particular when it comes time to implement the policy. I suggest adding text along these lines:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><i><span style="font-size:11.0pt">The intent of the working group in making this recommendation is that Registrars should not redact registration data that is already protected by a known Privacy/Proxy service.
Redacting the RDS data of a Privacy/Proxy service provider shouldn’t be necessary for GDPR compliance and creates an unnecessary hurdle for a requestor with a legitimate need to access the actual registration data behind the service.<o:p></o:p></span></i></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">On our Tuesday call we discussed the fact that it is not always know to the registrar that the registration is from a privacy/proxy service. I used the words “known Privacy or Proxy service” while Caitlin
uses “<i><span style="color:black">offered or made available by Registrar or its Affiliates”.</span></i><span style="color:black"> I’m not sure which is better and perhaps this is a question for registrars. I’m sensitive to registrars potentially getting
sideways with compliance over this. On last Thursday’s (meting #34) call, Marika talked to us about the “policy change impact” section of the report which could include information on how to measure compliance. While we agreed on Thursday’s call to table
that until we are a little further along in our policy recommendations, that does have me wondering if there is language we could add so that Registrars and compliance are on the same page as to how this should be implemented and enforced?</span><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">We also spoke about the currently on hold Privacy/Proxy implementation effort. I understand them to be on hold waiting our final policy recommendations as that may inform or otherwise impact their work.
I am maybe being overly cautious here, but I want to make sure nothing in our recommendations conflicts with or constrains the Privacy/Proxy group. Our group is responsible for GDPR compliance, their group for implementing a Privacy/Proxy policy. Some overlap
may be unavoidable but we should leave Privacy/Proxy policy to them. I’m thinking adding language that this recommendation is subject to that policy might be prudent. If there is no conflict then this recommendation stands, but if it conflicts with their
policy, then their policy takes precedent.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks,<br>
Marc<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org">gnso-epdp-team-bounces@icann.org</a>>
<b>On Behalf Of </b>James M. Bladel<br>
<b>Sent:</b> Wednesday, December 19, 2018 8:15 AM<br>
<b>To:</b> Caitlin Tubergen <<a href="mailto:caitlin.tubergen@icann.org">caitlin.tubergen@icann.org</a>>; GNSO EPDP <<a href="mailto:gnso-epdp-team@icann.org">gnso-epdp-team@icann.org</a>><br>
<b>Subject:</b> [EXTERNAL] Re: [Gnso-epdp-team] language re: affiliated privacy/proxy companies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333">Hi All-</span><span style="font-size:11.0pt;line-height:150%;font-family:HelveticaNeue;color:#333333"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333">This language is mostly ok (thanks Caitlin!), but the parenthetical example sideswipes the natural vs. legal debate. Recommend we change this:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333"> (e.g. where data associated with a natural person is masked)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333">To this:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333"> (e.g. where data associated with
<i>the Privacy/Proxy customer</i> is masked)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333">Thanks-<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333">J.<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333">-------------<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333">James Bladel<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-family:HelveticaNeue;color:#333333">GoDaddy<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center;line-height:150%">
<span style="font-family:HelveticaNeue;color:#333333">
<hr size="2" width="98%" align="center">
</span></div>
<div id="divRplyFwdMsg">
<p class="MsoNormal" style="line-height:150%"><b><span style="color:black">From:</span></b><span style="color:black"> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org">gnso-epdp-team-bounces@icann.org</a>> on behalf of Caitlin Tubergen <<a href="mailto:caitlin.tubergen@icann.org">caitlin.tubergen@icann.org</a>><br>
<b>Sent:</b> Tuesday, December 18, 2018 18:48<br>
<b>To:</b> GNSO EPDP<br>
<b>Subject:</b> [Gnso-epdp-team] language re: affiliated privacy/proxy companies <o:p>
</o:p></span></p>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;color:#333333">Dear All,</span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;color:#333333"> </span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;color:#333333">Following up on an action item from today’s EPDP call, please find draft language regarding</span><span style="font-size:11.0pt;line-height:150%;color:black">registrar
disclosure of privacy/proxy data to a requestor</span><span style="font-size:11.0pt;line-height:150%;color:#333333"> (section 2.6 of Appendix A of the Temp Spec).For ease of reference, the updated language is italicized.</span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;color:#333333"> </span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;color:black">The EPDP Team recommends that in the case of a domain name registration where a Privacy/Proxy service,<i>offered or made available by Registrar or its
Affiliates in connection with a registration is</i>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. (emphasis added)</span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;color:#333333"> </span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;color:#333333">Please respond to the list if you have any issues with the above draft language.</span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;color:#333333"> </span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;color:#333333">Best regards,</span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;color:#333333"> </span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;color:#333333">Marika, Berry, and Caitlin</span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;color:#333333"> </span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="font-size:11.0pt;line-height:150%;font-family:"Times New Roman",serif;color:black"> </span><span style="color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:150%"><span style="color:#333333"> <o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>