<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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks James. Quick question: if, as you note, most of your P/P customers engage the service to avoid being spammed – why is that objective/purpose not sufficiently
protected by a standard that says “A provider must relay all electronic requests received (including emails and via web forms), but may implement commercially reasonable safeguards (including CAPTCHA) to filter out spam.”?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">By asking the question I don’t necessarily mean to make a judgment on your “access whitelist” idea. I’m just not sure I understand its utility on this specific
question (relay), where a means to address the problem that it is trying to solve (i.e., spam) appears to have already been baked in.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
TW. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></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"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> gnso-ppsai-pdp-wg-bounces@icann.org [mailto:gnso-ppsai-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>James M. Bladel<br>
<b>Sent:</b> Sunday, August 17, 2014 6:23 PM<br>
<b>To:</b> Volker Greimann; gnso-ppsai-pdp-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] Proposal contactability<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Thanks to Volker for getting this conversation started. I also share the belief that we should define a system that assures reporters their claims will be relayed
by P/P services. However, I disagree on some key points raised by Volker and others.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">First, I do not believe there should be any attempt to filter submitted reports based on content. That approach does not scale, and simply results in an arms
race where would-be spammers attempt to circumvent the filters. Also, I do not believe P/P services should relay —all—reports. This treats the P/P email point of contact as an email “alias” for the beneficial user’s real address, and completely defeats the
purpose of the service (most of our P/P customers engage the service to avoid being spammed). <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">I favor an approach that is modeled after ICANN’s Invalid WHOIS Reporting System, and one that many Registrars have implemented to guard against WHOIS harvesting
– an access whitelist. Speaking generally, such a system would require reporters to identify themselves when submitting a claim for relay. Is reporter should also have to designate the email address from which relay claims will originate, and the service
provider agrees to honor relay request from that Address without discriminating on its content. The P/P service provider can then monitor the use of the relay system by each reporter, and suspend or terminate access for any reporter that is found to be abusing
the system. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">If this sounds familiar, it is blatantly copied from the EWG's proposed RDS concept. I think this idea has merit, and regardless of what happens to the rest of
the EWG's recommendations, we should consider opportunities to implement this proposal in existing contexts.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Look forward to continuing our discussions on this point on Tuesday.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Thanks—<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">J.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></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:11.0pt;font-family:"Calibri","sans-serif";color:black">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black">Volker Greimann <<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>><br>
<b>Date: </b>Wednesday, August 13, 2014 at 4:27 <br>
<b>To: </b>"<a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>" <<a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a>><br>
<b>Subject: </b>[Gnso-ppsai-pdp-wg] Proposal contactability<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">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">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">string@domain.name</a> or <a href="mailto:domain.name@service.provider">
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>
<o:p></o:p></span></p>
<pre><span style="color:black">-- <o:p></o:p></span></pre>
<pre><span style="color:black">Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Mit freundlichen Grüßen,<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Volker A. Greimann<o:p></o:p></span></pre>
<pre><span style="color:black">- Rechtsabteilung -<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Key-Systems GmbH<o:p></o:p></span></pre>
<pre><span style="color:black">Im Oberen Werk 1<o:p></o:p></span></pre>
<pre><span style="color:black">66386 St. Ingbert<o:p></o:p></span></pre>
<pre><span style="color:black">Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></span></pre>
<pre><span style="color:black">Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></span></pre>
<pre><span style="color:black">Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Web: <a href="http://www.key-systems.net">www.key-systems.net</a> / <a href="http://www.RRPproxy.net">www.RRPproxy.net</a><a href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com">www.BrandShelter.com</a><o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<o:p></o:p></span></pre>
<pre><span style="color:black"><a href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><a href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a><o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Geschäftsführer: Alexander Siffrin<o:p></o:p></span></pre>
<pre><span style="color:black">Handelsregister Nr.: HR B 18835 - Saarbruecken <o:p></o:p></span></pre>
<pre><span style="color:black">Umsatzsteuer ID.: DE211006534<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Member of the KEYDRIVE GROUP<o:p></o:p></span></pre>
<pre><span style="color:black"><a href="http://www.keydrive.lu">www.keydrive.lu</a> <o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">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.<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">--------------------------------------------<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Should you have any further questions, please do not hesitate to contact us.<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Best regards,<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Volker A. Greimann<o:p></o:p></span></pre>
<pre><span style="color:black">- legal department -<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Key-Systems GmbH<o:p></o:p></span></pre>
<pre><span style="color:black">Im Oberen Werk 1<o:p></o:p></span></pre>
<pre><span style="color:black">66386 St. Ingbert<o:p></o:p></span></pre>
<pre><span style="color:black">Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></span></pre>
<pre><span style="color:black">Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></span></pre>
<pre><span style="color:black">Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Web: <a href="http://www.key-systems.net">www.key-systems.net</a> / <a href="http://www.RRPproxy.net">www.RRPproxy.net</a><a href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a href="http://www.BrandShelter.com">www.BrandShelter.com</a><o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Follow us on Twitter or join our fan community on Facebook and stay updated:<o:p></o:p></span></pre>
<pre><span style="color:black"><a href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><a href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a><o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">CEO: Alexander Siffrin<o:p></o:p></span></pre>
<pre><span style="color:black">Registration No.: HR B 18835 - Saarbruecken <o:p></o:p></span></pre>
<pre><span style="color:black">V.A.T. ID.: DE211006534<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">Member of the KEYDRIVE GROUP<o:p></o:p></span></pre>
<pre><span style="color:black"><a href="http://www.keydrive.lu">www.keydrive.lu</a> <o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black">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.<o:p></o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
<pre><span style="color:black"><o:p> </o:p></span></pre>
</div>
</div>
</div>
</body>
</html>