<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";
color:black;
mso-fareast-language:JA;}
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:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
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";
color:black;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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 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";color:#1F497D">To Graeme’s last point below:<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">We can stipulate that all available processes can and will be abused. I think the extent of abuse under the DMCA is often exaggerated, but certainly it exists.
Before jumping to the DMCA analogy, let’s consider the consequences of abuse in the two situations:
<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">Consequence if a spurious legal claim is submitted via DMCA notice (and the affected party does not submit a counter-notice): material is taken down from
a website, or access to it is blocked. <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">Consequence if an e-mail containing a spurious legal claim is relayed by a p/p service provider to its customer:
<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">Nothing is taken down.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Nothing is blocked.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Customer does not need to invoke another procedure (like counter-notice) to avoid adverse consequences.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Customer receives an e-mail containing a spurious legal claim at the e-mail address it has provided to the p/p service in the its inbox; customer is not obligated
to respond to, read or even open the e-mail. <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">For this reason I don’t think the DMCA analogy is particularly illuminating for our assignment.
<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">Steve <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"><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";color:windowtext;mso-fareast-language:EN-US">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:EN-US">
gnso-ppsai-pdp-wg-bounces@icann.org [mailto:gnso-ppsai-pdp-wg-bounces@icann.org]
<b>On Behalf Of </b>Graeme Bunton<br>
<b>Sent:</b> Monday, August 18, 2014 10:20 PM<br>
<b>To:</b> 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>
<p class="MsoNormal" style="margin-bottom:12.0pt">First off, this has been an excellent discussion. Thanks again to Volker for giving us something to focus on.<br>
A couple of my own thoughts below:<br>
<br>
- In regards to the accurate and reliable below, I believe what Volker is saying is that under the 2013 RAA we know that either phone or email for a registrant is going to be verified. As such the service provider will have some record that either is reliable.
This doesn't necessarily mean (at least, until we've settled this discussion) that it's accessible to 3rd parties.
<br>
<br>
- I'm interested in James' idea of the reporters having to identify themselves when submitting a request. It gives the service provider greater insight into the system, allows for the mitigation of abuse, and could provide the submitter with information
on when their requests were submitted, possibly including successful delivery. Submitters in any relay scenario are not anonymous, as even full and automatic email relay could log sending email address, ip etc. This seems like it might increase accountability
on both sides. <br>
<br>
- Lastly, I think it's worth pointing out that legal claims have been, and continue to be used (and abused) as a method of curtailing free speech. There are numerous cases of the DMCA being used as such, which is why organizations like chillingeffects.org
exist. I know of hosting providers receiving hundreds of thousands of spurious, generated complaints. We need to be able to deal with such scenarios.
<br>
<br>
Thanks <br>
<br>
Graeme <br>
<br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal">On 8/18/2014 2:29 PM, Susan Kawaguchi wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Hi Volker, <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Please see my comments in red. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">I do appreciate the discussion. <o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri","sans-serif"">Susan Kawaguchi</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri","sans-serif"">Domain Name Manager</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri","sans-serif"">Facebook Legal Dept.</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri","sans-serif""> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Calibri","sans-serif"">Phone - 650 485-6064</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><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"">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Volker Greimann <<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>><br>
<b>Date: </b>Monday, August 18, 2014 at 10:27 AM<br>
<b>To: </b>Susan Kawaguchi <<a href="mailto:susank@fb.com">susank@fb.com</a>>, "Williams, Todd" <<a href="mailto:Todd.Williams@turner.com">Todd.Williams@turner.com</a>>, "James M. Bladel" <<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>>, "<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>Re: [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""><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Hi Susan,<br>
<br>
I do not see it as necessarily as a different treatment. The registrant is still required to provide
</span><span style="font-family:"Calibri","sans-serif";color:#262626;background:yellow;mso-highlight:yellow">accurate and reliable contact details,</span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> these details are just not published.
Just in the same way I can have a functioning email address but route undesired mails to the trashcan automatically prior to retrieving the mails, so can other automated or manual means be employed to filter undesired communications. A privacy service is just
another of those means. <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:red">If a proxy service provides an email address in the WHOIS record but nothing is relayed or only emails that hit a very narrow criteria beyond the spam filters that
would not equate to reliable contact details in my opinion. </span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><br>
<span style="font-family:"Calibri","sans-serif"">Can the data the registrant be provided be relied upon? Of course, since the service provider needs to be able to contact them. In case of a full or partial reveal, the data will be revealed as reliable. Accurate
and reliable date does not suddenly become unreliable data by the mere fact that it is hidden. The data is just as reliable or unreliable whether it is public or hidden.</span><br>
<span style="font-family:"Calibri","sans-serif";color:red">Actually this is not my experience at all that the data provided by the underlying registrant is reliable. The information is often times inaccurate I would guess at the same inaccuracy rates of regular
domain name registrations. This may have changed recently with the validation process and people becoming more aware of the need to have accurate data but I do not think we could assume the information is accurate. I do find the proxy service information
to be accurate. </span><br>
<span style="font-family:"Calibri","sans-serif"">If I as a registrant wanted to build my details in a way that any mail sent to me would be met with an automated responder that instructs the sender to fill in a webform, that would be perfectly fine. Sure, I
cannot be reached through that address, but I can be contacted. Why should privacy services be different?</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:red">At least if you sent an email to admin email address and received an auto response that may act as confirmation of the email being received. A proxy vendor refusing
to accept email as required by the RAA and requiring a web form be filled out is changing the purposes imposed by the RAA. </span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""><br>
Best,<br>
<br>
Volker<br>
<br>
Am 18.08.2014 18:24, schrieb Susan Kawaguchi:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">What I do not understand is why a proxy registration should be treated so differently than the other 75% of gTld domain name registrations? </span><span style="font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">In the 2013 RAA section 3.7.7.1 it states the following:</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:20.0pt"><span style="font-family:"Calibri","sans-serif";color:#262626">3.7.7.1 The Registered Name Holder shall provide to Registrar<span style="background:yellow;mso-highlight:yellow">accurate and reliable contact
details</span> and correct and update them within seven (7) days of any change during the term of the Registered Name registration, including: the full name, postal address, e-mail address, voice telephone number, and fax number if available of the Registered
Name Holder; name of authorized person for contact purposes in the case of an Registered Name Holder that is an organization, association, or corporation; and the data elements listed in Subsections 3.3.1.2, 3.3.1.7 and 3.3.1.8.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:20.0pt"><span style="font-family:"Calibri","sans-serif"">Creating a new method of contacting the registered name holder and underlying licensee or not relaying communications via email or to the postal address does
not appear to fulfill the requirement of “accurate and reliable contact details”</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:20.0pt"><span style="font-family:"Calibri","sans-serif";color:#262626">A proxy registration information may be accurate but currently the information fails as reliable contact details.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:20.0pt"><span style="font-family:"Calibri","sans-serif";color:#262626">Requiring a webform be filled out and submitted to contact the Registered name holder and underlying licensee when the other 75% of gTld domain
name registrations are required to have a reliable email address and postal address sets the proxy registrations apart. The webform is not listed as a requirement in section 3. 7.7.1. Why would we afford this special treatment to the proxy registrations? </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:20.0pt"><span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#262626">I realize the service has developed in this manner but it is also the reason we are continuing to discuss this issue. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:20.0pt"><span style="font-size:13.5pt;font-family:"Calibri","sans-serif";color:#262626"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Susan Kawaguchi</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Domain Name Manager</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Facebook Legal Dept.</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Phone - 650 485-6064</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";mso-fareast-language:EN-US"><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";mso-fareast-language:EN-US">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-language:EN-US"><Williams>, Todd <<a href="mailto:Todd.Williams@turner.com">Todd.Williams@turner.com</a>><br>
<b>Date: </b>Monday, August 18, 2014 at 8:19 AM<br>
<b>To: </b>"James M. Bladel" <<a href="mailto:jbladel@godaddy.com">jbladel@godaddy.com</a>>, Volker Greimann <<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>>, "<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>Re: [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";mso-fareast-language:EN-US"><o:p> </o:p></span></p>
</div>
<div>
<div>
<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.”?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></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.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
TW. </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span><o:p></o:p></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""><a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">gnso-ppsai-pdp-wg-bounces@icann.org</a>
[<a href="mailto:gnso-ppsai-pdp-wg-bounces@icann.org">mailto:gnso-ppsai-pdp-wg-bounces@icann.org</a>]
<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; <a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso</a></span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">(most of our P/P customers engage the service to avoid being spammed).</span><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Subject:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Re: [Gnso-ppsai-pdp-wg] Proposal contactability</span><o:p></o:p></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"">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.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">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</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">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.
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">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.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Look forward to continuing our discussions on this point on Tuesday.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">Thanks—</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">J.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></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"">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">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</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif"">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>
<br>
</span><o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Mit freundlichen Grüßen,<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- Rechtsabteilung -<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre>
<pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Web: <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.key-systems.net&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=rsFCYyZQt%2BsXOx2xX91EkpDm0Bf86Akjt0kI7PeOKQc%3D%0A&s=4e44656b6cbaf5db47c35c0942dd8686b9a3c5b61a616dcf66ec92e0f2b2365c">www.key-systems.net</a> / <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.RRPproxy.net&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=rsFCYyZQt%2BsXOx2xX91EkpDm0Bf86Akjt0kI7PeOKQc%3D%0A&s=9f6208e6e8f1dac0b3f5ee9154870f7a5e52ad42b0bd13ae5241fab95f59dec7">www.RRPproxy.net</a><a href="https://urldefense.proofpoint.com/v1/url?u=http://www.domaindiscount24.com&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=rsFCYyZQt%2BsXOx2xX91EkpDm0Bf86Akjt0kI7PeOKQc%3D%0A&s=467ef77b19e86ea983963!%205601853bb74d4fc3%0Ac295fa9d207090fbae89c45c15a">www.domaindiscount24.com</a> / <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.BrandShelter.com&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=rsFCYyZQt%2BsXOx2xX91EkpDm0Bf86Akjt0kI7PeOKQc%3D%0A&s=9973e10c6103daf421cc592932f808958673ace58cec9628db00f8780f812776">www.BrandShelter.com</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<o:p></o:p></pre>
<pre><a href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><a href="https://urldefense.proofpoint.com/v1/url?u=http://www.twitter.com/key_systems&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=rsFCYyZQt%2BsXOx2xX91EkpDm0Bf86Akjt0kI7PeOKQc%3D%0A&s=f553929a498d60da6ca0d20730fca68ec4cd4b34da81d7f164a6eaae314073e5">www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Geschäftsführer: Alexander Siffrin<o:p></o:p></pre>
<pre>Handelsregister Nr.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
<pre>Umsatzsteuer ID.: DE211006534<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a href="https://urldefense.proofpoint.com/v1/url?u=http://www.keydrive.lu&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=rsFCYyZQt%2BsXOx2xX91EkpDm0Bf86Akjt0kI7PeOKQc%3D%0A&s=5823884812c16616b8974fd5b1dfd309e902a2b3547c612cfa7f2f4e2e317500">www.keydrive.lu</a> <o:p></o:p></pre>
<pre> <o:p></o:p></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.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>--------------------------------------------<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Should you have any further questions, please do not hesitate to contact us.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Best regards,<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- legal department -<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre>
<pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Web: <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.key-systems.net&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=rsFCYyZQt%2BsXOx2xX91EkpDm0Bf86Akjt0kI7PeOKQc%3D%0A&s=4e44656b6cbaf5db47c35c0942dd8686b9a3c5b61a616dcf66ec92e0f2b2365c">www.key-systems.net</a> / <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.RRPproxy.net&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=rsFCYyZQt%2BsXOx2xX91EkpDm0Bf86Akjt0kI7PeOKQc%3D%0A&s=9f6208e6e8f1dac0b3f5ee9154870f7a5e52ad42b0bd13ae5241fab95f59dec7">www.RRPproxy.net</a><a href="https://urldefense.proofpoint.com/v1/url?u=http://www.domaindiscount24.com&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=rsFCYyZQt%2BsXOx2xX91EkpDm0Bf86Akjt0kI7PeOKQc%3D%0A&s=467ef77b19e86ea983963!%205601853bb74d4fc3%0Ac295fa9d207090fbae89c45c15a">www.domaindiscount24.com</a> / <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.BrandShelter.com&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=rsFCYyZQt%2BsXOx2xX91EkpDm0Bf86Akjt0kI7PeOKQc%3D%0A&s=9973e10c6103daf421cc592932f808958673ace58cec9628db00f8780f812776">www.BrandShelter.com</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Follow us on Twitter or join our fan community on Facebook and stay updated:<o:p></o:p></pre>
<pre><a href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><a href="https://urldefense.proofpoint.com/v1/url?u=http://www.twitter.com/key_systems&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=rsFCYyZQt%2BsXOx2xX91EkpDm0Bf86Akjt0kI7PeOKQc%3D%0A&s=f553929a498d60da6ca0d20730fca68ec4cd4b34da81d7f164a6eaae314073e5">www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>CEO: Alexander Siffrin<o:p></o:p></pre>
<pre>Registration No.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
<pre>V.A.T. ID.: DE211006534<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a href="https://urldefense.proofpoint.com/v1/url?u=http://www.keydrive.lu&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=rsFCYyZQt%2BsXOx2xX91EkpDm0Bf86Akjt0kI7PeOKQc%3D%0A&s=5823884812c16616b8974fd5b1dfd309e902a2b3547c612cfa7f2f4e2e317500">www.keydrive.lu</a> <o:p></o:p></pre>
<pre> <o:p></o:p></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.<o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
<pre> <o:p></o:p></pre>
</div>
</div>
</div>
</div>
</blockquote>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";mso-fareast-language:EN-US"><br>
<br>
<o:p></o:p></span></p>
<pre>-- <o:p></o:p></pre>
<pre>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Mit freundlichen Grüßen,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- Rechtsabteilung -<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre>
<pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Web: <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.key-systems.net&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=irWKKupqbA8cE9%2FFBluniHq77PwyDkW0%2Fur%2BvTcFdUg%3D%0A&s=d1aff2ac4a5464b0e044c5bc116ef5e369bf18b3eb31478c211437a43fde11ce">www.key-systems.net</a> / <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.RRPproxy.net&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=irWKKupqbA8cE9%2FFBluniHq77PwyDkW0%2Fur%2BvTcFdUg%3D%0A&s=8352699c2bc91fb33eb654e83c025da311d36d76d2b54d8b76b19bed0900bbea">www.RRPproxy.net</a><a href="https://urldefense.proofpoint.com/v1/url?u=http://www.domaindiscount24.com&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=irWKKupqbA8cE9%2FFBluniHq77Pw!%20yDkW0%2Fur%2BvTcFdUg%3D%0A&s=e8d4ec608389c17b99e07c4e0d0aa7c5adc19aa1d8cea39ae155b7624fd1bbf6">www.domaindiscount24.com</a> / <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.BrandShelter.com&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=irWKKupqbA8cE9%2FFBluniHq77PwyDkW0%2Fur%2BvTcFdUg%3D%0A&s=037867275c5abfc576911e6044aa5700bc51f9aac38e8087c68efcfe2cc23d1f">www.BrandShelter.com</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<o:p></o:p></pre>
<pre><a href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><a href="https://urldefense.proofpoint.com/v1/url?u=http://www.twitter.com/key_systems&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=irWKKupqbA8cE9%2FFBluniHq77PwyDkW0%2Fur%2BvTcFdUg%3D%0A&s=57accdd26500a0aa084874e7002afdf095b65310d0c6ec11a3b36778b0f1360b">www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Geschäftsführer: Alexander Siffrin<o:p></o:p></pre>
<pre>Handelsregister Nr.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
<pre>Umsatzsteuer ID.: DE211006534<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a href="https://urldefense.proofpoint.com/v1/url?u=http://www.keydrive.lu&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=irWKKupqbA8cE9%2FFBluniHq77PwyDkW0%2Fur%2BvTcFdUg%3D%0A&s=277b31a50f6d64aa91c15708dde3488ce9e323365d324042fe8dcac7a7b9b0d9">www.keydrive.lu</a> <o:p></o:p></pre>
<pre><o:p> </o:p></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.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>--------------------------------------------<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Should you have any further questions, please do not hesitate to contact us.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Best regards,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Volker A. Greimann<o:p></o:p></pre>
<pre>- legal department -<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Key-Systems GmbH<o:p></o:p></pre>
<pre>Im Oberen Werk 1<o:p></o:p></pre>
<pre>66386 St. Ingbert<o:p></o:p></pre>
<pre>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre>
<pre>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre>
<pre>Email: <a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Web: <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.key-systems.net&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=irWKKupqbA8cE9%2FFBluniHq77PwyDkW0%2Fur%2BvTcFdUg%3D%0A&s=d1aff2ac4a5464b0e044c5bc116ef5e369bf18b3eb31478c211437a43fde11ce">www.key-systems.net</a> / <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.RRPproxy.net&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=irWKKupqbA8cE9%2FFBluniHq77PwyDkW0%2Fur%2BvTcFdUg%3D%0A&s=8352699c2bc91fb33eb654e83c025da311d36d76d2b54d8b76b19bed0900bbea">www.RRPproxy.net</a><a href="https://urldefense.proofpoint.com/v1/url?u=http://www.domaindiscount24.com&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=irWKKupqbA8cE9%2FFBluniHq77Pw!%20yDkW0%2Fur%2BvTcFdUg%3D%0A&s=e8d4ec608389c17b99e07c4e0d0aa7c5adc19aa1d8cea39ae155b7624fd1bbf6">www.domaindiscount24.com</a> / <a href="https://urldefense.proofpoint.com/v1/url?u=http://www.BrandShelter.com&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=irWKKupqbA8cE9%2FFBluniHq77PwyDkW0%2Fur%2BvTcFdUg%3D%0A&s=037867275c5abfc576911e6044aa5700bc51f9aac38e8087c68efcfe2cc23d1f">www.BrandShelter.com</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Follow us on Twitter or join our fan community on Facebook and stay updated:<o:p></o:p></pre>
<pre><a href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a><a href="https://urldefense.proofpoint.com/v1/url?u=http://www.twitter.com/key_systems&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=irWKKupqbA8cE9%2FFBluniHq77PwyDkW0%2Fur%2BvTcFdUg%3D%0A&s=57accdd26500a0aa084874e7002afdf095b65310d0c6ec11a3b36778b0f1360b">www.twitter.com/key_systems</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>CEO: Alexander Siffrin<o:p></o:p></pre>
<pre>Registration No.: HR B 18835 - Saarbruecken <o:p></o:p></pre>
<pre>V.A.T. ID.: DE211006534<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Member of the KEYDRIVE GROUP<o:p></o:p></pre>
<pre><a href="https://urldefense.proofpoint.com/v1/url?u=http://www.keydrive.lu&k=ZVNjlDMF0FElm4dQtryO4A%3D%3D%0A&r=cjstkpAuvAi4gqeqX5O18A%3D%3D%0A&m=irWKKupqbA8cE9%2FFBluniHq77PwyDkW0%2Fur%2BvTcFdUg%3D%0A&s=277b31a50f6d64aa91c15708dde3488ce9e323365d324042fe8dcac7a7b9b0d9">www.keydrive.lu</a> <o:p></o:p></pre>
<pre><o:p> </o:p></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.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
</div>
</div>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Gnso-ppsai-pdp-wg mailing list<o:p></o:p></pre>
<pre><a href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><br>
<br>
<o:p></o:p></span></p>
<pre>-- <o:p></o:p></pre>
<pre>_________________________<o:p></o:p></pre>
<pre>Graeme Bunton<o:p></o:p></pre>
<pre>Information Specialist<o:p></o:p></pre>
<pre>Tucows Inc.<o:p></o:p></pre>
<pre>PH: 416 535 0123 ext 1634<o:p></o:p></pre>
</div>
</body>
</html>