[RDS-WHOIS2-Privacy-Proxy] Draft 4 - Privacy Proxy subgroup report
Volker Greimann
vgreimann at key-systems.net
Thu Jun 7 15:09:40 UTC 2018
Hi Lisa and subgroup members,
I reviewed the comment but the content in the final report
recommendation does not contradict the original statement. Periodic
checks are not envisioned, instead the same standards as in the RAA
apply, where re-checks would only occur upon occurrence of certain
trigger events.
To clarify, we may want to include a line along those lines:
"Instead, the validation and verification requirements included in the
2013 RAA or its successor agreements will be applied in a consistent
manner."
Any objections to this?
As for the rationale question in the second bullet, it had been decided
early on in the work that the obligations of registrars would be used as
a model for service provider so not to hold them to a different
standard. The second bullet could therefore be rephased as follows:
"The IRT decided against periodic due diligence checks as no such checks
are envisioned in the 2013 RAA, the standards of which served as a model
for service provider obligations, thereby harmonizing the obligations of
both registrars and service providers."
Any objections?
Regarding the request for clarification, I had responded on May 02:
regarding the issues you requested clarification:
Issue #1 is directed at the current discussions in the PPSAI IRT
regarding the fee structure proposed by ICANN for such service
providers. ICANN currently proposes fees to be charged by ICANN to
service providers for the accreditation that are comparable to the
annual fees payable by accredited registrars, minus the variable
component. As many providers are offering this service for free or
nominal fees, any cost increase would significantly impact their ability
to contiue to provide the service, more so than any of the formal or
practice requirements. Contracted parties have argued that this program
providers no actual benefit to the providers and is essentially only an
additional set of obligations. Adding additional costs ontop of that may
cause unaffiliated providers to attempt to circumvent the policy by
various means, rendering the policy useless. It was argued that it is in
the best interest of the ICANN community to ensure broad adoption of the
program by providers and as its benefits solely the community, it should
be the ICANN community, not the service providers that pick up the bill,
by means of the ICANN budget.
Additionally ICANN has continually claimed that these fees were on a
cost recovery basis, yet has failed to provide any itemized details on
how that figure has been arrived at, especially considering statements
from ICANN compliance that no additional personnel is expected to be
needed for this program and statements from ICANN that these costs would
remain the same regardless of whether only one or one million providers
sought accreditation.
Issue #2 revolves around the expectation that GDPR compliance would take
care of many of the reasons why registrants opt for privacy services in
the first place. This is expected to cause an industry-wide drop in the
use of these services as many of its functions would now be available
"for free" as the default. Many have questioned the need for the
continued existence of such services after May 25. As a result, the
recommendation may have outlived its usefulness. I am sure this impact
will not be fully visible by the time we finalize our report, but we
should be cognisant in it of the ongoing changes and their potential
impacts.
I hope this helps to understand the background on these issues.
Volker
Am 06.06.2018 um 06:31 schrieb Lisa Phifer:
> Hi Volker and Rec10 subgroup,
>
> As requested, attached is an updated draft for the subgroup's
> consideration which adds language suggested by Volker in 25 May email.
> Please confirm that the redlined insertion at the bottom of page 6
> accurately reflects your intent.
>
> In addition, to help focus attention on open areas, previous redlines
> were accepted, except for unresolved in-line comments:
>
> - Page 5, Objective 6: See "DISAGREE" and redlined text that follows
> - Page 7, Issues 1 & 2: At the F2F, the RT requested Volker clarify these
>
> Closure on these open areas is still needed before finalizing this
> subgroup report.
>
> Best,
> Lisa
>
>
> At 07:37 AM 6/5/2018, Volker Greimann wrote:
>
>> Hi Lisa,
>>
>> if there are no objections from Susan or the other team members, I
>> would propose to update the draft to include these changes.
>>
>> I am aware that Lili made a reference to the general question of
>> accuracy of underlying data, but that is not something that we have
>> or can reasonable expect to obtain reliable data on, so I would
>> suggest leaving that out.
>>
>> Best,
>>
>> Volker
>>
>> Am 02.06.2018 um 22:03 schrieb Lisa Phifer:
>>> Hi Volker and Susan,
>>>
>>> Following up on this report as well...
>>>
>>> I haven't seen anything further from the privacy/proxy subgroup
>>> since Susan's latest draft:
>>>
>>> http://mm.icann.org/pipermail/rds-whois2-privacy-proxy/attachments/20180523/a85bdc75/SKadditionalinputSubgroup1-Rec10PrivacyProxy-Report-Draft2-0001.docx
>>>
>>>
>>> Do you plan to update the draft as Volker suggested below and then
>>> send the subgroup-agreed report to the full RT?
>>>
>>> Thanks for your confirmation. As always, if I can be of help, do let
>>> me know -
>>>
>>> Best, Lisa
>>>
>>>
>>> At 10:08 AM 5/25/2018, Volker Greimann wrote:
>>>
>>>> Hi Susan,
>>>>
>>>> I have no further comments. As we are basically looking at work in
>>>> progress, there is little to say on this issue. We may want to
>>>> include language that between the RAA 2013 Spec and this policy,
>>>> the original recommendation seems to have been adressed. Anything
>>>> not adressed was clearly not deemed to be important for inclusion
>>>> by the community, the GNSO and the board who all approved the PDP
>>>> final report.
>>>>
>>>> Volker
>>>>
>>>> Am 24.05.2018 um 03:41 schrieb Susan Kawaguchi:
>>>>> Hello All,ÂÂ
>>>>>
>>>>> I made a few edits to the report. Please review and let's see
>>>>> if we can get this draft submitted tomorrow.Â
>>>>>
>>>>> SusanÂ
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> RDS-WHOIS2-Privacy-Proxy mailing list
>>>>> RDS-WHOIS2-Privacy-Proxy at icann.org
>>>>> <mailto:RDS-WHOIS2-Privacy-Proxy at icann.org>
>>>>>
>>>>> https://mm.icann.org/mailman/listinfo/rds-whois2-privacy-proxy
>>>>
>>>>
>>>>
>>>> --
>>>> 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 <mailto:vgreimann at key-systems.net>
>>>>
>>>> Web:www.key-systems.net <http://www.key-systems.net> /
>>>> www.RRPproxy.net <http://www.RRPproxy.net>
>>>> www.domaindiscount24.com <http://www.domaindiscount24.com> /
>>>>
>>>> www.BrandShelter.com <http://www.BrandShelter.com>
>>>>
>>>> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
>>>>
>>>> www.facebook.com/KeySystems <http://www.facebook.com/KeySystems>
>>>>
>>>> www.twitter.com/key_systems <http://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 <http://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 <mailto:vgreimann at key-systems.net>
>>>>
>>>> Web:www.key-systems.net <http://www.key-systems.net> /
>>>> www.RRPproxy.net <http://www.RRPproxy.net>
>>>> www.domaindiscount24.com <http://www.domaindiscount24.com> /
>>>>
>>>> www.BrandShelter.com <http://www.BrandShelter.com>
>>>>
>>>> Follow us on Twitter or join our fan community on Facebook and stay
>>>> updated:
>>>>
>>>> www.facebook.com/KeySystems <http://www.facebook.com/KeySystems>
>>>>
>>>> www.twitter.com/key_systems <http://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 <http://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.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> RDS-WHOIS2-Privacy-Proxy mailing
>>>> listRDS-WHOIS2-Privacy-Proxy at icann.org
>>>> <mailto:RDS-WHOIS2-Privacy-Proxy at icann.org>
>>>> https://mm.icann.org/mailman/listinfo/rds-whois2-privacy-proxy
>>
>>
>> --
>> 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 <mailto:vgreimann at key-systems.net>
>>
>> Web:www.key-systems.net <http://www.key-systems.net> /
>> www.RRPproxy.net <http://www.RRPproxy.net>
>> www.domaindiscount24.com <http://www.domaindiscount24.com> /
>> www.BrandShelter.com <http://www.BrandShelter.com>
>>
>> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
>> www.facebook.com/KeySystems <http://www.facebook.com/KeySystems>
>> www.twitter.com/key_systems <http://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 <http://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 <mailto:vgreimann at key-systems.net>
>>
>> Web:www.key-systems.net <http://www.key-systems.net> /
>> www.RRPproxy.net <http://www.RRPproxy.net>
>> www.domaindiscount24.com <http://www.domaindiscount24.com> /
>> www.BrandShelter.com <http://www.BrandShelter.com>
>>
>> Follow us on Twitter or join our fan community on Facebook and stay
>> updated:
>> www.facebook.com/KeySystems <http://www.facebook.com/KeySystems>
>> www.twitter.com/key_systems <http://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 <http://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.
>>
>>
>>
--
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-privacy-proxy/attachments/20180607/ecc178ce/attachment-0001.html>
More information about the RDS-WHOIS2-Privacy-Proxy
mailing list