<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
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. <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>
<br>
<div class="moz-cite-prefix">Am 28.10.2014 17:30, schrieb Phil
Corwin:<br>
</div>
<blockquote
cite="mid:8E84A14FB84B8141B0E4713BAFF5B84E0E541494@Exchange.sierracorporation.com"
type="cite">
<pre wrap="">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.
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.
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.
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.
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.
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.
Thank you for taking these views into account.
Philip S. Corwin, Founding Principal
Virtualaw LLC
1155 F Street, NW
Suite 1050
Washington, DC 20004
202-559-8597/Direct
202-559-8750/Fax
202-255-6172/cell
Twitter: @VlawDC
"Luck is the residue of design" -- Branch Rickey
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-ppsai-pdp-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-ppsai-pdp-wg@icann.org">Gnso-ppsai-pdp-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
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.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated" href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a> / <a class="moz-txt-link-abbreviated" href="http://www.RRPproxy.net">www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated" href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> / <a class="moz-txt-link-abbreviated" href="http://www.BrandShelter.com">www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated" href="http://www.facebook.com/KeySystems">www.facebook.com/KeySystems</a>
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/key_systems">www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated" href="http://www.keydrive.lu">www.keydrive.lu</a>
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>
</body>
</html>