<html 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=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Arial;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Lucida Grande";
panose-1:2 11 6 0 4 5 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier",serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">I did a google search and found the following: <a href="https://harvardlawreview.org/wp-content/uploads/pdfs/vol126_schwartz.pdf">
https://harvardlawreview.org/wp-content/uploads/pdfs/vol126_schwartz.pdf</a>. Stephanie, can you confirm this is the article you were referring to?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Marika<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black"><gnso-rds-pdp-wg-bounces@icann.org> on behalf of jonathan matkowsky <jonathan.matkowsky@riskiq.net><br>
<b>Date: </b>Wednesday, September 27, 2017 at 11:57<br>
<b>To: </b>Stephanie Perrin <stephanie.perrin@mail.utoronto.ca><br>
<b>Cc: </b>"gnso-rds-pdp-wg@icann.org" <gnso-rds-pdp-wg@icann.org><br>
<b>Subject: </b>Re: [gnso-rds-pdp-wg] FW: WSGR Final Memorandum<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Hi, Stephanie. I am getting caught up as I was traveling last week, and then the Jewish holidays...I was hoping you can send me a copy of that law review article you referenced or a citation so I can pull it if not publicly available?
Thanks, in advance, Jonathan <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Sep 27, 2017 at 7:28 AM, Stephanie Perrin <<a href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank">stephanie.perrin@mail.utoronto.ca</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p><span style="font-size:13.5pt;font-family:"Lucida Grande",sans-serif">Binding corporate rules, with a set of derogations that would be specified in certain contracts, (as the kind of contractual clauses that clarify what can be done in certain jurisdictions)
is not that hard to build. International companies have been working on these mechanisms since the 90s, the Article 29 group have clarified how to do it in a series of their Opinions, .....and the corporations and working parties in the International Conference
of Privacy and Data Commissioners made sure these things would work internationally. yes it is work but global operations require quite a bit of work. Time to get going on it.</span><o:p></o:p></p>
<p><span style="font-size:13.5pt;font-family:"Lucida Grande",sans-serif">The lawyer we hired for this opinion (Chris Kuner) is an expert in this, he has worked with tons of companies striving for compliance with the Directive 95/46. ICANN is awfully late to
the party, but this is certainly not the most complex application in the world to figure out....</span><o:p></o:p></p>
<p><span style="font-size:13.5pt;font-family:"Lucida Grande",sans-serif">Paul Schwarz (another data protection lawyer who is expert in these matters) wrote an excellent article on the coming confrontation between the US and EU over the GDPR (Harvard Law REview
2012). He notes the excellent work that companies and dpas did to make sure that such mechanisms as contractual clauses actually worked, when dealing with the Directive. Historically, the first companies to really start pushing contractual clauses way back
in the early 90s as I recall were the direct marketing companies. Anyway....the bottom line is where there is a will there is a way. I hope we can muster a common will to actually work on solutions, instead of denying the reality of rights and data protection
law, a position that puts various parties at risk in a variety of ways. </span>
<o:p></o:p></p>
<p><span style="font-size:13.5pt;font-family:"Lucida Grande",sans-serif">Stephanie</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 2017-09-27 10:04, Chuck wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>It's hard to disagree with Sam's point that "ICANN needs a resilient and<o:p></o:p></pre>
<pre>sustainable policy strategy here. A strategy that sits above the weeds of<o:p></o:p></pre>
<pre>conflicting GDPRs". Put in other words that we have all heard many times, a<o:p></o:p></pre>
<pre>one size fits all approach will not work for all users, for all<o:p></o:p></pre>
<pre>jurisdictions, for all registrants, for all registrars, for all registries,<o:p></o:p></pre>
<pre>etc. <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Chuck<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-----Original Message-----<o:p></o:p></pre>
<pre>From: <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">gnso-rds-pdp-wg-bounces@icann.org</a><o:p></o:p></pre>
<pre>[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank">mailto:gnso-rds-pdp-wg-bounces@icann.org</a>] On Behalf Of Sam Lanfranco<o:p></o:p></pre>
<pre>Sent: Wednesday, September 27, 2017 5:53 AM<o:p></o:p></pre>
<pre>To: <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre>Subject: Re: [gnso-rds-pdp-wg] FW: WSGR Final Memorandum<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I remind us that we are looking at some principles to drive a process here,<o:p></o:p></pre>
<pre>the selection of the MPDS. We should not get lost in the weeds of<o:p></o:p></pre>
<pre>conflicting GDPRs.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Nations will have differences, to be negotiated, and ICANN itself (as<o:p></o:p></pre>
<pre>ICANN) should retain some procedural latitude to both navigate those<o:p></o:p></pre>
<pre>conflicts, and at the same time accept that it has an organizational<o:p></o:p></pre>
<pre>stakeholder interest in the resolution of those conflicts.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>This is the world we live in. It will never be neat and tidy, so ICANN needs<o:p></o:p></pre>
<pre>a resilient and sustainable policy strategy here.<o:p></o:p></pre>
<pre>A strategy that sits above the weeds of conflicting GDPRs.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Sam Lanfranco<o:p></o:p></pre>
<pre>(ncsg/npoc)<o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>gnso-rds-pdp-wg mailing list<o:p></o:p></pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>gnso-rds-pdp-wg mailing list<o:p></o:p></pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">gnso-rds-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><br>
<span style="font-size:9.5pt;font-family:"Arial",sans-serif;color:#222222;background:white">*******************************************************************<br>
This message was sent from RiskIQ, and is intended only for the designated recipient(s). It may contain confidential or proprietary information and may be subject to confidentiality protections. If you are not a designated recipient, you may not review, copy
or distribute this message. If you receive this in error, please notify the sender by reply e-mail and delete this message. Thank you.</span>
<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"Arial",sans-serif;color:#222222;background:white">*******************************************************************</span>
<o:p></o:p></p>
</div>
</body>
</html>