<html>
<body>
One comment. I understand that the existance of P/P providers is
effectively to hide WHOIS information, but I am less sure that once we
have decided to have P/P providers, are all of the issues being addressed
by these questions really WHOIS related?<br><br>
Alan<br><br>
At 01/03/2018 11:57 AM, Volker Greimann wrote:<br><br>
<blockquote type=cite class=cite cite="">Thank you indeed, Susan, that is
a good start. I added a few small notes. Anyone else want to chime
in before we finalize?<br>
<br>
Volker<br><br>
<blockquote type=cite class=cite cite="">Here are a few questions for
ICANN staff on the Privacy Proxy recommendation hopefully, this will
spark more ideas from the rest of the subgroup. <br><br>
Challenges your team has identified with the implementation? <br><br>
What internal systems will this implementation impact? <br><br>
Is there budget allocated for this implementation? </blockquote>What
impact will the implementation have on existing providers from a
cost-impact perspective?<br>
<blockquote type=cite class=cite cite=""><br>
Any part of the implementation that will require new technology?<br><br>
Will this require modification of the RAA? <br><br>
What plans does the compliance team have for ensuring
compliance?</blockquote>What is the expected the budget impact be for
ongoing operations for this compliance work.<br>
<blockquote type=cite class=cite cite=""><br>
How long do you estimate it will take for the implementation?
</blockquote>e.g. what is the estimated remaining timeline for the
implementation?<br><br>
With regard to the RAA spec:<br>
Please provide information on the volume and content of compliance report
regarding the privacy / proxy RAA spec. <br><br>
Has the RAA spec achieved the objectives set by ICANN ORG when it
included this as a new requirement for the 2013 RAA? What were these
objectives?<br><br>
Has ICANN ORG identified any challenges with regard to implementation or
compliance of this spec?<br><br>
<br><br>
<br>
<pre>--
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 href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a href="http://www.key-systems.net">www.key-systems.net</a> /
<a href="http://www.rrpproxy.net/" eudora="autourl">www.RRPproxy.net</a>
<a href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> /
<a href="http://www.brandshelter.com/" eudora="autourl">
www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a href="http://www.facebook.com/KeySystems">
www.facebook.com/KeySystems</a>
<a href="http://www.twitter.com/key_systems" eudora="autourl">
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 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 href="mailto:vgreimann@key-systems.net">vgreimann@key-systems.net</a>
Web: <a href="http://www.key-systems.net">www.key-systems.net</a> /
<a href="http://www.rrpproxy.net/" eudora="autourl">www.RRPproxy.net</a>
<a href="http://www.domaindiscount24.com">www.domaindiscount24.com</a> /
<a href="http://www.brandshelter.com/" eudora="autourl">
www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay
updated:
<a href="http://www.facebook.com/KeySystems">
www.facebook.com/KeySystems</a>
<a href="http://www.twitter.com/key_systems" eudora="autourl">
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 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><br>
Content-Type: text/plain; charset="us-ascii"<br>
Content-Transfer-Encoding: 7bit<br>
Content-Disposition: inline<br>
X-Microsoft-Exchange-Diagnostics:<br>
<x-tab> </x-tab>
1;YTXPR0101MB1600;27:42iGKvXBFNXAXUKCKae7rmbLbmPGOfiLve4ubuyV6dwvStaiX1Td0vMV+Qbi6hxRXz3B/ivlAy6VJx8LeotnqjLkuqNFXg1Rg6i3iAxO76XEcDoDxY6KYhI36aYvzufW<br>
X-Microsoft-Antispam-Message-Info:<br>
<x-tab> </x-tab>
B2FTWxO0eTjvkMhhYohOc5Xb8Sg79dpMsTpg6IG/2r6RqofncUe6Nv0PROuCxwN9xFMhGgBBI2NOWSkrEvlOaK7IzzmazbTWk2SdZchwwGHkxR7jZ0yAE8+JpTLsYT4ySbkkH+m+SCKaHwJ/PDLsCA==<br>
<br>
_______________________________________________<br>
RDS-WHOIS2-Privacy-Proxy mailing list<br>
RDS-WHOIS2-Privacy-Proxy@icann.org<br>
<a href="https://mm.icann.org/mailman/listinfo/rds-whois2-privacy-proxy" eudora="autourl">
https://mm.icann.org/mailman/listinfo/rds-whois2-privacy-proxy</a>
</blockquote></body>
</html>