<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:"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:sans-serif;
panose-1:0 0 0 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:"Times New Roman",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;}
span.EmailStyle17
{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"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">For those interested, please note that a public comment forum is currently open to obtain community input on the effectiveness of the updated ICANN Procedure for Handling WHOIS Conflicts
with Privacy Law (WHOIS Procedure), which was recently revised to incorporate an "Alternative Trigger," in addition to the existing trigger to invoke the procedure (see
<a href="https://www.icann.org/public-comments/whois-privacy-law-2017-05-03-en">https://www.icann.org/public-comments/whois-privacy-law-2017-05-03-en</a>). Comments may be submitted until 7 July.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Marika <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Calibri",sans-serif;color:black">From:
</span></b><span style="font-family:"Calibri",sans-serif;color:black"><gnso-rds-pdp-wg-bounces@icann.org> on behalf of Carlton Samuels <carlton.samuels@gmail.com><br>
<b>Date: </b>Tuesday, June 6, 2017 at 08:45<br>
<b>To: </b>Volker Greimann <vgreimann@key-systems.net><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] What registrars must do (was Re: The principle for thin data)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif">Um, well, there is a procedure for handling WHOIS conflicts with local law that is out there. The baseline position appears to be break the law and we will tell you how to explain it, even
evade sanctions.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif">See <a href="https://whois.icann.org/en/revised-icann-procedure-handling-whois-conflicts-privacy-law">
https://whois.icann.org/en/revised-icann-procedure-handling-whois-conflicts-privacy-law</a>.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"sans-serif",serif">Since I began to following these matters from the At-Large side in 2008, I have held this posture to be cockeyed, designed to make a priori scofflaws of registrars and a generator of work for
lawyers.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"sans-serif",serif">So you know, I hold the view that one existential attribute of ICANN is to make work for lawyers. But truth be know if I had a sign hung I would be applauding them for gutsy stewardship. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"sans-serif",serif">-Carlton</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><br>
==============================<br>
<i><span style="font-family:"sans-serif",serif">Carlton A Samuels</span></i><br>
<i><span style="font-family:"sans-serif",serif">Mobile: 876-818-1799<br>
<span style="color:#33CC00">Strategy, Planning, Governance, Assessment & Turnaround</span></span></i><br>
=============================<o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Jun 6, 2017 at 4:10 AM, Volker Greimann <<a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</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">
<p class="MsoNormal"><br>
<br>
Am 02.06.2017 um 18:17 schrieb Andrew Sullivan:<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">
<p class="MsoNormal">On Fri, Jun 02, 2017 at 07:00:23PM +0300, jonathan matkowsky 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">
<p class="MsoNormal" style="margin-bottom:12.0pt">"3.7.2 Registrar shall abide by applicable laws and governmental<br>
regulations." Applicable laws vary from jurisdiction to jurisdiction.<br>
We should keep this in mind.<o:p></o:p></p>
</blockquote>
<p class="MsoNormal">Yes. Also, I don't know why we have to have an opinion on what<br>
registrars or registries must do overall. What we need to do, as far<br>
as I can tell, is understand what the data is and what it is collected<br>
for, and then propose a policy that makes it _possible_ for registrars<br>
and registries to conform with their local laws. No?<o:p></o:p></p>
</blockquote>
<p class="MsoNormal">The main issue is that ICANN has no working process in place for a contracted party to show it has an issue with local laws that can be reasonably invoked before getting called on it by local authorities, e.g. being sued or fined. So we
need the excemptions baked into the policy to be safe down the road.<br>
<br>
"Just deal with that on your own later!" is not an acceptable result.<br>
<br>
As a non-European leader recently put it: "No deal is better than a bad deal!"<br>
<br>
Best,<br>
Volker <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
_______________________________________________<br>
gnso-rds-pdp-wg mailing list<br>
<a href="mailto:gnso-rds-pdp-wg@icann.org" target="_blank">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>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>