<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font size="+1"><font face="Lucida Grande">Indeed yes, that is
the one. Sorry for the delay in response. Life beckons every
now and then....</font></font></p>
<p><font size="+1"><font face="Lucida Grande">cheers SP</font></font><br>
</p>
<br>
<div class="moz-cite-prefix">On 2017-09-27 16:46, jonathan matkowsky
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALsyHBnFnyLB_Kx7k1si69vwdkPN+8=VfZnkXXdv8cEVcjFK0w@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">Marika, yes, that's the one. Jonathan
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Sep 27, 2017 at 11:01 AM,
Marika Konings <span dir="ltr"><<a
href="mailto:marika.konings@icann.org" target="_blank"
moz-do-not-send="true">marika.konings@icann.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" link="blue" vlink="purple"
lang="EN-US">
<div class="m_-5970329244481042064WordSection1">
<p class="MsoNormal">I did a google search and found
the following: <a
href="https://harvardlawreview.org/wp-content/uploads/pdfs/vol126_schwartz.pdf"
target="_blank" moz-do-not-send="true">
https://harvardlawreview.org/<wbr>wp-content/uploads/pdfs/<wbr>vol126_schwartz.pdf</a>.
Stephanie, can you confirm this is the article you
were referring to?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Best regards,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Marika</p>
<p class="MsoNormal"> </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"><<a
href="mailto:gnso-rds-pdp-wg-bounces@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg-bounces@<wbr>icann.org</a>>
on behalf of jonathan matkowsky <<a
href="mailto:jonathan.matkowsky@riskiq.net"
target="_blank" moz-do-not-send="true">jonathan.matkowsky@riskiq.net</a><wbr>><br>
<b>Date: </b>Wednesday, September 27, 2017 at
11:57<br>
<b>To: </b>Stephanie Perrin <<a
href="mailto:stephanie.perrin@mail.utoronto.ca"
target="_blank" moz-do-not-send="true">stephanie.perrin@mail.<wbr>utoronto.ca</a>><br>
<b>Cc: </b>"<a
href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>"
<<a href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a>><br>
<b>Subject: </b>Re: [gnso-rds-pdp-wg] FW: WSGR
Final Memorandum</span></p>
</div>
<div>
<p class="MsoNormal"> </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 </p>
<div>
<p class="MsoNormal"> </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" moz-do-not-send="true">stephanie.perrin@mail.<wbr>utoronto.ca</a>>
wrote:</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></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></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>
</p>
<p><span
style="font-size:13.5pt;font-family:"Lucida
Grande",sans-serif">Stephanie</span></p>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On 2017-09-27 10:04,
Chuck wrote:</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</pre>
<pre>sustainable policy strategy here. A strategy that sits above the weeds of</pre>
<pre>conflicting GDPRs". Put in other words that we have all heard many times, a</pre>
<pre>one size fits all approach will not work for all users, for all</pre>
<pre>jurisdictions, for all registrants, for all registrars, for all registries,</pre>
<pre>etc. </pre>
<pre> </pre>
<pre>Chuck</pre>
<pre> </pre>
<pre>-----Original Message-----</pre>
<pre>From: <a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg-bounces@icann.<wbr>org</a></pre>
<pre>[<a href="mailto:gnso-rds-pdp-wg-bounces@icann.org" target="_blank" moz-do-not-send="true">mailto:gnso-rds-pdp-wg-<wbr>bounces@icann.org</a>] On Behalf Of Sam Lanfranco</pre>
<pre>Sent: Wednesday, September 27, 2017 5:53 AM</pre>
<pre>To: <a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></pre>
<pre>Subject: Re: [gnso-rds-pdp-wg] FW: WSGR Final Memorandum</pre>
<pre> </pre>
<pre>I remind us that we are looking at some principles to drive a process here,</pre>
<pre>the selection of the MPDS. We should not get lost in the weeds of</pre>
<pre>conflicting GDPRs.</pre>
<pre> </pre>
<pre>Nations will have differences, to be negotiated, and ICANN itself (as</pre>
<pre>ICANN) should retain some procedural latitude to both navigate those</pre>
<pre>conflicts, and at the same time accept that it has an organizational</pre>
<pre>stakeholder interest in the resolution of those conflicts.</pre>
<pre> </pre>
<pre>This is the world we live in. It will never be neat and tidy, so ICANN needs</pre>
<pre>a resilient and sustainable policy strategy here.</pre>
<pre>A strategy that sits above the weeds of conflicting GDPRs.</pre>
<pre> </pre>
<pre>Sam Lanfranco</pre>
<pre>(ncsg/npoc)</pre>
<pre>______________________________<wbr>_________________</pre>
<pre>gnso-rds-pdp-wg mailing list</pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
<pre> </pre>
<pre>______________________________<wbr>_________________</pre>
<pre>gnso-rds-pdp-wg mailing list</pre>
<pre><a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></pre>
</blockquote>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal"><br>
______________________________<wbr>_________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org"
target="_blank" moz-do-not-send="true">gnso-rds-pdp-wg@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg"
target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/gnso-rds-pdp-wg</a></p>
</blockquote>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
<p class="MsoNormal"><br>
<span
style="font-size:9.5pt;font-family:"Arial",sans-serif;color:#222222;background:white">******************************<wbr>******************************<wbr>*******<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>
</p>
<p class="MsoNormal"><span
style="font-size:9.5pt;font-family:"Arial",sans-serif;color:#222222;background:white">******************************<wbr>******************************<wbr>*******</span>
</p>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)">******************************</span><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>******************************</span><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>*******<br>
</span><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)">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><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)">******************************</span><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>******************************</span><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><wbr>*******</span>
</blockquote>
<br>
</body>
</html>