[RDS-WHOIS2-RT] Comments about the Subgroup Report of Privacy/Proxy Services

Tue Jun 5 11:31:00 UTC 2018

Hi Lili,

thank you for your comments.

1) The question of reliability levels of data behind a privacy shield is 
very hard to measure, as no mechanism exists to properly conduct a study 
without violating the terms of the service. Possibly, an indication of 
reliability levels could be obtained from UDRP providers as they 
regularly deal with cases where the privacy service removes itself on 
the occurrence of a complaint, and therefore might have data on the 
reliability of the revealed data, however even then this sample would be 
skewed as most domains using whois privacy services are unlikely to be 
targets in a UDRP.

2) We assume that will be the case as touching all those existing 
customers is a near impossible task.

3) I reviewed your document, but I disagree with the assumptions 
therein. There was no indication or evidence of illegal use that I could 
determine. Porn and gambling, while distasteful are not necessarily 
illegal. So someone used a privacy service and registered a bunch of 
domains to serve such content to China. So what? Also, the fact that the 
redirect changed after a short while may point to the domains being 
parked with the incoming traffic being sold to the highest bidder, who 
at the time may have been a provider of such services.

I can see no abuse of a privacy service here.

Volker

Am 03.06.2018 um 05:21 schrieb SUN Lili:
>
> Dear Privacy & Proxy subgroup members,
>
> I went through the draft report of this subgroup on wiki page 
> (https://community.icann.org/pages/viewpage.action?pageId=71604717) 
> and step in with my concerns:
>
> 1.To the Data Accuracy subgroup, the Whois accuracy of domain names 
> that utilize Privacy and Proxy Services is invisible. And Volker also 
> mentioned that this will be dealt with in the Privacy & Proxy 
> subgroup. As such, I strongly support Susan’s comments on “6 
> Conducting periodic due diligence checks on customer contact 
> information” and “8 Providing clear and unambiguous guidance on the 
> rights and responsibilities of registered name holders, and how those 
> should be managed in the privacy/proxy environment.” There is no 
> reason for a customer who chose P/P service thus been protected from 
> responsibilities.
>
> 2.There is no indication about the legacy domain names that utilize 
> P/P Services before the provider been accredited. Will it be a similar 
> situation as Grandfathered domains?
>
> 3.Like the example I gave during the 2^nd F2F meeting, if there is not 
> enough regulation and overseeing in place, P/P service is very likely 
> to be abused. To be clear, I elaborated the example in a word document 
> (see attached). Do we really need this kind of fake prosperity of 
> domain industry?
>
> A response from this subgroup is much appreciated.
>
> Thanks,
>
> Lili
>
> ***************************************************************************************************
> This message, and any attachment contained, are confidential and 
> subject of legal privilege. It may be used solely for the designated 
> police/justice purpose and by the individual or entity to whom it is 
> addressed. The information is not to be disseminated to another agency 
> or third party without the author’s consent, and must not be retained 
> longer than is necessary for the fulfilment of the purpose for which 
> the information is to be used. All practicable steps shall be taken by 
> the recipients to ensure that information is protected against 
> unauthorised access or processing. INTERPOL reserves the right to 
> enquire about the use of the information provided.
> If you are not the intended recipient, be advised that you have 
> received this message in error. In such a case, you should not print 
> it, copy it, make any use of it or disclose it, but please notify us 
> immediately and delete the message from any computer.
> *************************************************************************************************
>
>
> _______________________________________________
> RDS-WHOIS2-RT mailing list
> RDS-WHOIS2-RT at icann.org
> https://mm.icann.org/mailman/listinfo/rds-whois2-rt

-- 
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 at 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 at 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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt/attachments/20180605/9d7a418b/attachment.html>