<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:Wingdings}
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
@font-face
{font-family:Consolas}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
pre
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black}
span.HTMLPreformattedChar
{font-family:Consolas;
color:black}
span.EmailStyle19
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style><style type="text/css" id="owaParaStyle"></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple" fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Times New Roman;color: #000000;font-size: 12pt;">
<div><font size="3">Thank you, Volker, for the initial proposal, and Todd for clarifying it.</font></div>
<div><font size="3"><br>
</font></div>
<div><font size="3">Another narrower approach would be to</font><font size="3"> ensure that </font><font size="3"><u>all</u></font><font size="3"> communications that contain </font><font size="3">legal complaints are relayed without exception. </font><font size="3">To
be clear, under this approach, there would be no content evaluation, other than to determine that any given communication is or contains a legal complaint. </font></div>
<div>
<div><font size="3"><br>
</font></div>
<div><font size="3">Just an initial thought; reserving comment on the remainder of points raised both by Volker and Todd for Tuesday's call. Look forward to hearing everyone's ideas on the proposal.</font></div>
</div>
<div><font size="3"><br>
</font></div>
<div><span style="font-size: medium;">Val, Jim and David</span></div>
<div><br>
</div>
<div><br>
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<p class="MsoNormal" style="margin-bottom:0.0001pt"><font face="Times New Roman" size="3"><span dir="ltr">Valeriya Sherman<br>
Silverberg, Goldman & Bikoff, L.L.P.<br>
1101 30th Street, N.W.<br>
Suite 120<br>
Washington, D.C. 20007<br>
Tel 202.944.3300<br>
Cell 303.589.7477<br>
</span><a target="_blank" href="mailto:vsherman@law.gwu.edu" tabindex="0" style="color:rgb(17,85,204)">vsherman@sgbdc.com</a></font></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF947588" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> gnso-ppsai-pdp-wg-bounces@icann.org [gnso-ppsai-pdp-wg-bounces@icann.org] on behalf of Williams, Todd [Todd.Williams@turner.com]<br>
<b>Sent:</b> Friday, August 15, 2014 2:39 PM<br>
<b>To:</b> Volker Greimann; gnso-ppsai-pdp-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] Proposal contactability<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Thank you for this proposal Volker – very useful for moving the discussion ahead, as you noted. There’s quite a bit to unpack here, so let me take one specific
part of it while reserving comment/judgment on the rest; specifically, this sentence:</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">“Service Provider may refuse to forward spam, duplicate messages, purchase or business inquiries, harrassing communications, anonymous communications and/or
unwanted communications.”</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Of course, saying that a Service Provider
<b><i>may</i></b> refuse to forward certain enumerated categories of communications implies that the Service Provider
<b><i>may not</i></b> refuse to forward a communication that does not fall into one of those enumerated categories. So as I read it (and correct me if this is wrong), that seems consistent with Option #1 from the attached. In fact, it simply seems to be a
further elucidation of the term “abusive communications” from Option 1; if it was a redline, it would read:</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">“A provider must relay all electronic requests received (including emails and via web forms), but may
<s>implement commercially reasonable safeguards (including CAPTCHA) to</s> filter out spam,
<s>and other forms of abusive communications.</s> </span><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:red">duplicate messages, purchase or business inquiries, harassing communications, anonymous communications and/or unwanted communications.”</span><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Assuming that reading is correct, then I think what we’d be left to debate as a working group would be: what enumerated exceptions (to the general default
rule of relay) do we think are appropriate? My main thought is only that notices that include a legal claim should not be included among those enumerated exceptions. But beyond that, here are some initial thoughts on each of the exceptions that you’ve proposed
(again, all subject to further discussion):</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt; font-family:Symbol; color:#1F497D"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Spam: I think we all agree on that.</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt; font-family:Symbol; color:#1F497D"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Duplicate messages: my only question on this is how is it defined? A certain number of messages from the same sender within a defined timeframe (e.g., 24
hours)?</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt; font-family:Symbol; color:#1F497D"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Purchase or business inquiries: I confess that I don’t quite understand this one. What is the rationale for this exception? Wouldn’t the Beneficial Owner
want to receive these?</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt; font-family:Symbol; color:#1F497D"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Harassing communications: again, my question would be how is “harassing” defined?
</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt; font-family:Symbol; color:#1F497D"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Anonymous communications: I don’t necessarily have a problem with this.</span></p>
<p class="MsoListParagraph" style="text-indent:-.25in"><span style="font-size:11.0pt; font-family:Symbol; color:#1F497D"><span style="">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Unwanted communications: I think this one is the most problematic exception proposed, and is a non-starter, for several reasons, at least one of which is
that it would seem to include notices that include a legal claim (because who really “wants” to receive those?).</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Those are my initial thoughts at least; I look forward to hearing what everybody else thinks.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Todd.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:windowtext">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:windowtext"> gnso-ppsai-pdp-wg-bounces@icann.org [mailto:gnso-ppsai-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>Volker Greimann<br>
<b>Sent:</b> Wednesday, August 13, 2014 5:28 AM<br>
<b>To:</b> gnso-ppsai-pdp-wg@icann.org<br>
<b>Subject:</b> [Gnso-ppsai-pdp-wg] Proposal contactability</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">As Susan and Steve have repeatedly asked what my proposal would be to ensure contactability of the beneficial owner/registrant.<br>
<br>
As a basis, a spec derivative of the WAP spec to the RAA would have to be developed. I took the liberty of modifying the WAP for this purpose as a basis for discussion.<br>
This would bring the obligation of the privacy service provider to validate and verify the contact details to the same level of that of the registrar, thus ensuring the Service Provider has either accurate details or a duty to verify and validate.<br>
<br>
Now, I would agree that some level of a contactibility guarantee is warranted. This could be something to this tune, as a basis for discussion:<br>
<br>
<i>"Service Provider are required provide a means for third parties to directly or indirectly communicate with the Beneficial Owner. Such means may include any of the following:<br>
a) providing a postal mail forwarding address<br>
b) providing a collective email point of contact for all domain names under the Service (such as
<a href="mailto:abuse@service.provider" target="_blank">abuse@service.provider</a>)<br>
c) providing an individual email point of contact for each domain name under the Service (such as
<a href="mailto:string@domain.name" target="_blank">string@domain.name</a> or <a href="mailto:domain.name@service.provider" target="_blank">
domain.name@service.provider</a>)<br>
...<br>
...<br>
<br>
Service Provider must inform potential complainants about the accepted means of communication on its website. Service provider may refuse to forward, process or even accept communications sent by a non-accepted means of communication. In case forwarding of
postal communications is offered, Service Provider may charge complainant reasonable handling fees and costs for the forwarding service and defer the forwarding of communications until payment is received.
<br>
<br>
Service Provider may refuse to forward spam, duplicate messages, purchase or business inquiries, harrassing communications, anonymous communications and/or unwanted communications. Service Provider is authorized to update or modify the means of communication
from time to time. Service Provider is authorized to blacklist complainants with a history of abusing the provided means of communication."</i><br>
<br>
All subject to further discussion, ofc. <br>
<br>
I realize this draft goes into detail more than we should in this WG, but having been asked for a proposal, I felt it necessary in order to move the discussion ahead.<br>
Terms:<br>
Service Provider - Privacy/Proxy Service Provider<br>
Beneficial Owner - Replaces "Registrant"<br>
filter - not deliver to Beneficial owner<br>
Service - the privacy/proxy services<br>
<br>
</p>
<pre>-- </pre>
<pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.</pre>
<pre> </pre>
<pre>Mit freundlichen Grüßen,</pre>
<pre> </pre>
<pre>Volker A. Greimann</pre>
<pre>- Rechtsabteilung -</pre>
<pre> </pre>
<pre>Key-Systems GmbH</pre>
<pre>Im Oberen Werk 1</pre>
<pre>66386 St. Ingbert</pre>
<pre>Tel.: +49 (0) 6894 - 9396 901</pre>
<pre>Fax.: +49 (0) 6894 - 9396 851</pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a></pre>
<pre> </pre>
<pre>Web: <a href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a></pre>
<pre><a href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a></pre>
<pre> </pre>
<pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:</pre>
<pre><a href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a></pre>
<pre><a href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a></pre>
<pre> </pre>
<pre>Geschäftsführer: Alexander Siffrin</pre>
<pre>Handelsregister Nr.: HR B 18835 - Saarbruecken </pre>
<pre>Umsatzsteuer ID.: DE211006534</pre>
<pre> </pre>
<pre>Member of the KEYDRIVE GROUP</pre>
<pre><a href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a> </pre>
<pre> </pre>
<pre>Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.</pre>
<pre> </pre>
<pre>--------------------------------------------</pre>
<pre> </pre>
<pre>Should you have any further questions, please do not hesitate to contact us.</pre>
<pre> </pre>
<pre>Best regards,</pre>
<pre> </pre>
<pre>Volker A. Greimann</pre>
<pre>- legal department -</pre>
<pre> </pre>
<pre>Key-Systems GmbH</pre>
<pre>Im Oberen Werk 1</pre>
<pre>66386 St. Ingbert</pre>
<pre>Tel.: +49 (0) 6894 - 9396 901</pre>
<pre>Fax.: +49 (0) 6894 - 9396 851</pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a></pre>
<pre> </pre>
<pre>Web: <a href="http://www.key-systems.net" target="_blank">www.key-systems.net</a> / <a href="http://www.RRPproxy.net" target="_blank">www.RRPproxy.net</a></pre>
<pre><a href="http://www.domaindiscount24.com" target="_blank">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com" target="_blank">www.BrandShelter.com</a></pre>
<pre> </pre>
<pre>Follow us on Twitter or join our fan community on Facebook and stay updated:</pre>
<pre><a href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a></pre>
<pre><a href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a></pre>
<pre> </pre>
<pre>CEO: Alexander Siffrin</pre>
<pre>Registration No.: HR B 18835 - Saarbruecken </pre>
<pre>V.A.T. ID.: DE211006534</pre>
<pre> </pre>
<pre>Member of the KEYDRIVE GROUP</pre>
<pre><a href="http://www.keydrive.lu" target="_blank">www.keydrive.lu</a> </pre>
<pre> </pre>
<pre>This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.</pre>
<pre> </pre>
<pre> </pre>
<pre> </pre>
</div>
</div>
</div>
</div>
</body>
</html>