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

Thu Jun 7 17:20:51 UTC 2018

Hi Volker

I disagree that our only option is to say thank you.  This recommendation
is 6 years old so it would make sense that as an RT we would review the
policy created by the PDP and make a recommendation in view of what has
transpired in the last 6 years.

The Temp Spec addresses accuracy of data.  What is being recommended is
that a registrar treat the underlying registrant data the same way it is
required to validate registrant data now.  A registrar knows who their
customer is and can ensure that the data under the PP is accurate without
disclosing that to the world.

Your claim this would violate the underlying registrant's privacy I do not
follow that line of thinking at all.

We should continue to discuss this recommendation.

Susan

On Thu, Jun 7, 2018 at 7:37 AM, Volker Greimann <vgreimann at key-systems.net>
wrote:

> I do not support any attempt to introduce an obligation for service
> providers to violate the privacy of their customers simply for purposes of
> "checks".
>
> The PPSAI WG has made very specific decisions regarding the obligations of
> service providers regarding data quality. It is not our place to question
> these decisions which have been approved by the GNSO and the board and are
> now on their final stretch of implementation.
>
> Our report should only say: "thank you ICANN, job well done!"
>
> Anything beyond that is a job for the review of the policy after it has
> been implemented for a while.
>
> Volker
>
> Am 06.06.2018 um 20:21 schrieb Carlton Samuels:
>
> Hi Lili:
> See my comments in line.
>
>
> ==============================
> *Carlton A Samuels*
>
> *Mobile: 876-818-1799 Strategy, Process, Governance, Assessment &
> Turnaround*
> =============================
>
> On Sat, Jun 2, 2018 at 10:21 PM, SUN Lili <L.SUN at interpol.int> wrote:
>
>> 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.
>>
> Under current rules, the accredited P/P provider is obliged to ensure
> contactability of customer of his service. That this is the case cannot be
> verified independently and some of us have argued from inception this is a
> major hole in the agreement. We have alternately argued that there should
> be graded penalties for this violation after the fact.
>
>> 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.
>>
> See above. We expect that the risk triage will allow the cost of
> violation to pass to the customer.
>
>
>>
>>
>> 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?
>>
> Some of us have argued that there should be a Privacy/Proxy Data Accuracy
> Reminder policy along the line of the WHOIS Data reminder. It was not
> accepted. But there is no reason the P/P provider cannot be obliged and
> bound to it in terms of the accreditation for renewals. 
>
>
>>
>>
>> 3.       Like the example I gave during the 2nd 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.
>>
>>
>>
> Best,
> -Carlton
>
>
>> 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
>>
>>
>
>
> _______________________________________________
> RDS-WHOIS2-RT mailing listRDS-WHOIS2-RT at icann.orghttps://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.netwww.domaindiscount24.com / www.BrandShelter.com
>
> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:www.facebook.com/KeySystemswww.twitter.com/key_systems
>
> Geschäftsführer: Alexander Siffrin
> Handelsregister Nr.: HR B 18835 - Saarbruecken
> Umsatzsteuer ID.: DE211006534
>
> Member of the KEYDRIVE GROUPwww.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.netwww.domaindiscount24.com / www.BrandShelter.com
>
> Follow us on Twitter or join our fan community on Facebook and stay updated:www.facebook.com/KeySystemswww.twitter.com/key_systems
>
> CEO: Alexander Siffrin
> Registration No.: HR B 18835 - Saarbruecken
> V.A.T. ID.: DE211006534
>
> Member of the KEYDRIVE GROUPwww.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.
>
>
>
>
>
> _______________________________________________
> RDS-WHOIS2-RT mailing list
> RDS-WHOIS2-RT at icann.org
> https://mm.icann.org/mailman/listinfo/rds-whois2-rt
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt/attachments/20180607/f20dadc4/attachment-0001.html>