<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)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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.apple-tab-span
{mso-style-name:apple-tab-span;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:black;
font-weight:normal;
font-style:normal;}
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:10.0pt;font-family:"Arial","sans-serif";color:black'>All,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>I can’t for the life of me figure out in the string below which text is Val’s, which is Phil’s, and which is David’s. Can we agree that if we’re going to provide an inline reply that we’ll somehow flag (initials, brackets, etc.) when we’re adding text? <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Thanks.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>K<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","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 style='margin-left:.5in'><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>David Cake<br><b>Sent:</b> Wednesday, October 29, 2014 2:58 AM<br><b>To:</b> Valeriya Sherman<br><b>Cc:</b> gnso-ppsai-pdp-wg@icann.org<br><b>Subject:</b> Re: [Gnso-ppsai-pdp-wg] Mandatory Reveal in Context of Allegations that a Domain Name is Infringing Trademark<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-left:.5in'>On 29 Oct 2014, at 3:38 am, Valeriya Sherman <<a href="mailto:VSherman@sgbdc.com">VSherman@sgbdc.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal style='margin-left:.5in'><br><br><o:p></o:p></p><div><div><div><p class=MsoNormal style='margin-left:.5in'>Phil,<o:p></o:p></p></div><div><div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>With respect to Reveal in the context of allegations that a domain name is infringing, we advocate Disclosure (to the Requestor only) of information sufficient to help the Requestor determine if further action against the Customer is warranted. This is especially important in the context of IP rights enforcement. <o:p></o:p></p></div></div></div></div></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>Allegations are not proof. If the domain name itself is regarded as possibly infringing, we have the UDRP and URS to determine it a domain name is actually infringing. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><br><br><o:p></o:p></p><div><div><div><div><div><p class=MsoNormal style='margin-left:.5in'>Disclosure of the Customer's identity would help the Requestor determine, before having to file a URS or UDRP, whether or not the Customer:<o:p></o:p></p></div></div></div></div></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>Sure. But being helpful to the Requestor is not, by itself, sufficient to justify disclosure.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><br><br><o:p></o:p></p><div><div><div><div><p class=MsoNormal style='margin-left:.5in'>-has legitimate rights in the domain name;<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>-is a cybersquatter; <o:p></o:p></p></div></div></div></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>These are the exact questions the UDRP/URS are designed to answer. Wanting to know the answers to them before filing is putting the cart before the horse somewhat. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><br><br><o:p></o:p></p><div><div><div><div><p class=MsoNormal style='margin-left:.5in'>-is stockpiling domain names, without adding any website content; or<o:p></o:p></p></div></div></div></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>The UDRP ultimately should succeed or fail based on the use of the domain in question, not what the registrant does with their other domains. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>And as Michele notes, website content is not the only use for domain names. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>( eg I have a few friends who have used the adorably geeky rcpt.to domain for email only for over a decade now). <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>Also, if the domain owner is actively using sub-domains of their domain, it may not necessarily be obvious to the requester.<o:p></o:p></p></div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span><br><br><o:p></o:p></p><div><div><div><div><p class=MsoNormal style='margin-left:.5in'>-has prior UDRP decisions against him or her.<o:p></o:p></p></div></div></div></div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span><o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>Again, sure, helpful to know before filing your UDRP, but is helpful to potential filers sufficient to overrule the obvious desire of the registrant for privacy? <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>A desire to disassociate particular domains used for specific purposes from their general domaining business may even be the reason for using a PPP. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><br><br><o:p></o:p></p><div><div><div><div><p class=MsoNormal style='margin-left:.5in'>All of the foregoing indicate bad faith registration and use of the domain name.<o:p></o:p></p></div></div></div></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>Your first two criteria are decisions that the UDRP/URS will rule on. Your second two criteria might indicate a general pattern of bad behaviour by the registrant, but do not mean that an individual domain is part of that pattern of behaviour. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><br><br><o:p></o:p></p><div><div><div><div><p class=MsoNormal style='margin-left:.5in'> As Paul pointed out on today's call, the Requestor must be able to ascertain this information before it is obliged undergo the time and expense of bringing a UDRP or other legal proceeding. <o:p></o:p></p></div></div></div></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>I do not think this follows at all. There is a big difference between the requestor would like to, and the Requestor must be able to. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>I absolutely think that the Requestor should be able to use relay to request relevant information from the registrant. If the registrant wants to reply to a relayed request asserting their legitimate right to the domain, good. But it is not obvious to me that disclosure is necessary, and I can think of many cases in which it might be problematic. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><br><br><o:p></o:p></p><div><div><div><div><p class=MsoNormal style='margin-left:.5in'>In that way, it can possibly avoid the need for a UDRP. And if it has to bring a UDRP, it can do so in good faith. That is why Disclosure is valuable in cases involving infringing domain names, not just infringing website content. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><div><p class=MsoNormal style='margin-left:.5in'>To address another point that has come up in the past, Disclosure does not equate to a finding of guilt. Disclosure is not a remedy of the UDRP or the URS; it would occur before a case is decided on the merits. <o:p></o:p></p></div></div></div></div></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>Of course - but avoiding disclosure is, presumably, often a major reason for retaining a PPP in the first place, so we should not let it happen just because it would be beneficial to the requestor. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>Regards<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><span class=apple-tab-span> </span>David<o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><br><br><o:p></o:p></p><div><div><div><div><div><p class=MsoNormal style='margin-left:.5in'>It is my understanding that once a UDRP is filed, one or both of the following generally happens: 1) registrar receives a request for information to confirm registrant, which it then sends to the Complainant to amend the Complaint; or 2) the P/P Provider named in the complaint discloses or publishes the information. So under the status quo, there generally is a Reveal before a decision on the merits, but only after the Requestor is forced to file a complaint, without essential information, at a high cost. As you correctly observed, not all allegations are successful -- we don't want to encourage more with a policy that requires premature legal actions. <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>Best regards,<o:p></o:p></p></div><div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'>Val<o:p></o:p></p></div></div></div></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><div><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;margin-left:.5in'>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><a href="mailto:vsherman@law.gwu.edu" target="_blank"><span style='color:#1155CC'>vsherman@sgbdc.com</span></a><o:p></o:p></p></div></div></div></div></div></div><div><div class=MsoNormal align=center style='margin-left:.5in;text-align:center'><hr size=2 width="100%" align=center></div><div id=divRpF527131><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span class=apple-converted-space><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span></span><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">gnso-ppsai-pdp-wg-bounces@icann.org</a>] on behalf of Volker Greimann [<a href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>]<br><b>Sent:</b><span class=apple-converted-space> </span>Tuesday, October 28, 2014 12:37 PM<br><b>To:</b><span class=apple-converted-space> </span><a href="mailto:gnso-ppsai-pdp-wg@icann.org">gnso-ppsai-pdp-wg@icann.org</a><br><b>Subject:</b><span class=apple-converted-space> </span>Re: [Gnso-ppsai-pdp-wg] Mandatory Reveal in Context of Allegations that a Domain Name is Infringing Trademark</span><o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in'>Hi Phil,<br><br>I agree that a mere allegation is never enough for any form of required result. The bar needs to be set a lot higher, such as a sworn statement that includes legal consequences in case any part of it is incorrect that would allow the injured party and the provider to sue the pants off of the complainant.<span class=apple-converted-space> </span><br><br>Also, the violation must be clear and obvious to an untrained third party observer, which is usually not the case in trademark violation due to the fact that trademark law is simply too complex for a layman to understand. And frankly, there also is no need for an immediate reveal as there are, as you point out, already sufficient means to deal with such cases.<br><br>As for content, that is a hosting issue outside the realm of ICANN. Go to the hosting provider instead. Infringing content has nothing to do with the domain name whatsoever.<br><br>Best,<br><br>Volker<br><br><o:p></o:p></p><div><p class=MsoNormal style='margin-left:.5in'>Am 28.10.2014 17:30, schrieb Phil Corwin:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre style='margin-left:.5in'>I want to reiterate the concerns I raised during today's call about recommending a policy that would require a privacy/proxy provider (PPP) to reveal/disclose a registrant's identity and contact information based on a mere allegation that the domain name is infringing a trademark.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>ICANN has established the URDP and URS to deal with such allegations. And every day WIPO, NAF, and other providers deny complainant allegations. In fact, it appears that instances of attempted reverse domain hijacking are on the rise.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>A registrant who is targeted in a UDRP or URS has a choice of responding (in which case they will be revealing their identity) or to default and let the provider decide the allegation based solely upon the complaint. The proposed policy would compel disclosure of registrant data even when no UDRP, URS, or trademark infringement litigation was filed, or even if the allegation was subsequently found to fail to meet the required burden of proof.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>I am not convinced by arguments that such mandatory disclosure might facilitate resolution absent the filing of arbitration or litigation. That can be accomplished by requiring the PPP to relay a cease-and-desist letter or other communication to the registrant. Mandatory disclosure based on an unproven allegation does not further the claimed goal.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Summing up, I believe that our WG should not create any new policy related to allegations of TM infringement by a domain name but should leave this issue to the new gTLD RPM and UDRP review that will be commencing next spring.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>As for allegations of trademark infringement based upon a website's content that is a separate matter. However, I believe our discussions should recognize that PPPs are unlikely to weigh the merits of an allegation and that their likely default position will be to reveal registrant data once a complaint addresses all the relevant points required by any new policy on this subject. Given that likelihood, we should certainly consider the extent to which such a policy might be abused by a private sector or governmental actor.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Thank you for taking these views into account.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Philip S. Corwin, Founding Principal<o:p></o:p></pre><pre style='margin-left:.5in'>Virtualaw LLC<o:p></o:p></pre><pre style='margin-left:.5in'>1155 F Street, NW<o:p></o:p></pre><pre style='margin-left:.5in'>Suite 1050<o:p></o:p></pre><pre style='margin-left:.5in'>Washington, DC 20004<o:p></o:p></pre><pre style='margin-left:.5in'>202-559-8597/Direct<o:p></o:p></pre><pre style='margin-left:.5in'>202-559-8750/Fax<o:p></o:p></pre><pre style='margin-left:.5in'>202-255-6172/cell<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Twitter: @VlawDC<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>"Luck is the residue of design" -- Branch Rickey<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><p class=MsoNormal style='margin-left:.5in'><br><br><o:p></o:p></p><pre style='margin-left:.5in'>_______________________________________________<o:p></o:p></pre><pre style='margin-left:.5in'>Gnso-ppsai-pdp-wg mailing list<o:p></o:p></pre><pre style='margin-left:.5in'><a href="mailto:Gnso-ppsai-pdp-wg@icann.org" target="_blank">Gnso-ppsai-pdp-wg@icann.org</a><o:p></o:p></pre><pre style='margin-left:.5in'><a href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a><o:p></o:p></pre></blockquote><p class=MsoNormal style='margin-left:.5in'><br><br><o:p></o:p></p><pre style='margin-left:.5in'>-- <o:p></o:p></pre><pre style='margin-left:.5in'>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Mit freundlichen Grüßen,<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Volker A. Greimann<o:p></o:p></pre><pre style='margin-left:.5in'>- Rechtsabteilung -<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Key-Systems GmbH<o:p></o:p></pre><pre style='margin-left:.5in'>Im Oberen Werk 1<o:p></o:p></pre><pre style='margin-left:.5in'>66386 St. Ingbert<o:p></o:p></pre><pre style='margin-left:.5in'>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre><pre style='margin-left:.5in'>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre><pre style='margin-left:.5in'>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>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><o:p></o:p></pre><pre style='margin-left:.5in'><a href="http://www.domaindiscount24.com/" target="_blank">www.domaindiscount24.com</a> / <a href="http://www.brandshelter.com/" target="_blank">www.BrandShelter.com</a><o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:<o:p></o:p></pre><pre style='margin-left:.5in'><a href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><o:p></o:p></pre><pre style='margin-left:.5in'><a href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a><o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Geschäftsführer: Alexander Siffrin<o:p></o:p></pre><pre style='margin-left:.5in'>Handelsregister Nr.: HR B 18835 - Saarbruecken <o:p></o:p></pre><pre style='margin-left:.5in'>Umsatzsteuer ID.: DE211006534<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Member of the KEYDRIVE GROUP<o:p></o:p></pre><pre style='margin-left:.5in'><a href="http://www.keydrive.lu/" target="_blank">www.keydrive.lu</a> <o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>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 style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>--------------------------------------------<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Should you have any further questions, please do not hesitate to contact us.<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Best regards,<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Volker A. Greimann<o:p></o:p></pre><pre style='margin-left:.5in'>- legal department -<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Key-Systems GmbH<o:p></o:p></pre><pre style='margin-left:.5in'>Im Oberen Werk 1<o:p></o:p></pre><pre style='margin-left:.5in'>66386 St. Ingbert<o:p></o:p></pre><pre style='margin-left:.5in'>Tel.: +49 (0) 6894 - 9396 901<o:p></o:p></pre><pre style='margin-left:.5in'>Fax.: +49 (0) 6894 - 9396 851<o:p></o:p></pre><pre style='margin-left:.5in'>Email: <a href="mailto:vgreimann@key-systems.net" target="_blank">vgreimann@key-systems.net</a><o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>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><o:p></o:p></pre><pre style='margin-left:.5in'><a href="http://www.domaindiscount24.com/" target="_blank">www.domaindiscount24.com</a> / <a href="http://www.brandshelter.com/" target="_blank">www.BrandShelter.com</a><o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Follow us on Twitter or join our fan community on Facebook and stay updated:<o:p></o:p></pre><pre style='margin-left:.5in'><a href="http://www.facebook.com/KeySystems" target="_blank">www.facebook.com/KeySystems</a><o:p></o:p></pre><pre style='margin-left:.5in'><a href="http://www.twitter.com/key_systems" target="_blank">www.twitter.com/key_systems</a><o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>CEO: Alexander Siffrin<o:p></o:p></pre><pre style='margin-left:.5in'>Registration No.: HR B 18835 - Saarbruecken <o:p></o:p></pre><pre style='margin-left:.5in'>V.A.T. ID.: DE211006534<o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>Member of the KEYDRIVE GROUP<o:p></o:p></pre><pre style='margin-left:.5in'><a href="http://www.keydrive.lu/" target="_blank">www.keydrive.lu</a> <o:p></o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'>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 style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre><pre style='margin-left:.5in'><o:p> </o:p></pre></div></div></div><p class=MsoNormal style='margin-left:.5in'><span style='font-size:9.0pt;font-family:"Helvetica","sans-serif"'>_______________________________________________<br>Gnso-ppsai-pdp-wg mailing list<br><a href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a><br><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></span></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p></div></body></html>