Also note that even if no license of an IP is granted to a registrant of a domain name matching the string, the registrant may still have rights to use the string: - fair use - free speech - own IP - use in different categories not covered by IP - IP is generic/dictionary word/etc. Best, Volker Am 04.11.2014 22:45, schrieb Frank Michlick:
Hi Val,
On 2014-11-04 4:19 PM, Valeriya Sherman wrote:
Phil/Graeme -- An IP owner would know who they authorized to use the IP and who they did not. The issue is that they do not know whether a particular Customer, whose identity is hidden, needs authorization or not. In the example I provided earlier, where a Requestor has rights in US but not in the EU, it would be essential for him to know where the Customer is located to establish whether the Customer needs any authorization -- and that is some of the information that Disclosure would provide. IP owners could also track the domains where their customers are allowed to use their IP.
Remember, we're not really talking about any content here that is hosted on a site with a domain under privacy, as the privacy provider usually has no involvement with the hosting etc. There are existing paths that deal with infringements that can be applied, no matter if there is whois privacy or not.
But I also have to wonder if a partial disclosure of the registrant's country would satisfy your need in this case. Not that I support this either really.
Another point that came up during our call is that an authorized party would respond to a relay request. Lack of response to relays is evidence of bad faith, but it doesn't obviate the need for disclosure. As noted above, a Customer may not need any authorization, so his failure to reply to a relayed request is not conclusive evidence of his rights or lack thereof. Disclosure is still needed.
"Lack of response to relays is evidence of bad faith"? Why would someone be obliged to respond to a message they receive, be it via relay or not - and how do you ensure that its received?
Best regards, /FM
_______________________________________________ Gnso-ppsai-pdp-wg mailing list Gnso-ppsai-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-ppsai-pdp-wg
-- 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: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu 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: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu 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.