Questions - preparing for ICANN org briefing
Thank you, Susan, for providing these questions. Volker, please advise what the deadline is for edits. We recommend finalizing the list by the end of this week/early next week so we may provide these questions to Subject Matter Experts to inform the briefing request. Thanks Best Alice From: RDS-WHOIS2-Privacy-Proxy <rds-whois2-privacy-proxy-bounces@icann.org> on behalf of Susan Kawaguchi <susankpolicy@gmail.com> Date: Tuesday 27 February 2018 at 06:16 To: "rds-whois2-privacy-proxy@icann.org" <rds-whois2-privacy-proxy@icann.org> Subject: [RDS-WHOIS2-Privacy-Proxy] WHOIS1 Rec #10 Privacy/Proxy questions for ICANN staff Hello All, 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. Challenges your team has identified with the implementation? What internal systems will this implementation impact? Is there budget allocated for this implementation? Any part of the implementation that will require new technology? Will this require modification of the RAA? What plans does the compliance team have for ensuring compliance? How long do you estimate it will take for the implementation? Susan
Thank you indeed, Susan, that is a good start. I added a few small notes. Anyone else want to chime in before we finalize? Volker
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.
Challenges your team has identified with the implementation?
What internal systems will this implementation impact?
Is there budget allocated for this implementation?
What impact will the implementation have on existing providers from a cost-impact perspective?
Any part of the implementation that will require new technology?
Will this require modification of the RAA?
What plans does the compliance team have for ensuring compliance?
What is the expected the budget impact be for ongoing operations for this compliance work.
How long do you estimate it will take for the implementation?
e.g. what is the estimated remaining timeline for the implementation? With regard to the RAA spec: Please provide information on the volume and content of compliance report regarding the privacy / proxy RAA spec. 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? Has ICANN ORG identified any challenges with regard to implementation or compliance of this spec? -- 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.
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? Alan At 01/03/2018 11:57 AM, Volker Greimann wrote:
Thank you indeed, Susan, that is a good start. I added a few small notes. Anyone else want to chime in before we finalize?
Volker
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.
Challenges your team has identified with the implementation?
What internal systems will this implementation impact?
Is there budget allocated for this implementation? What impact will the implementation have on existing providers from a cost-impact perspective?
Any part of the implementation that will require new technology?
Will this require modification of the RAA?
What plans does the compliance team have for ensuring compliance? What is the expected the budget impact be for ongoing operations for this compliance work.
How long do you estimate it will take for the implementation? e.g. what is the estimated remaining timeline for the implementation?
With regard to the RAA spec: Please provide information on the volume and content of compliance report regarding the privacy / proxy RAA spec.
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?
Has ICANN ORG identified any challenges with regard to implementation or compliance of this spec?
-- 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: <mailto:vgreimann@key-systems.net>vgreimann@key-systems.net
Web: <http://www.key-systems.net>www.key-systems.net / www.RRPproxy.net <http://www.domaindiscount24.com>www.domaindiscount24.com / www.BrandShelter.com
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: <http://www.facebook.com/KeySystems>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 <http://www.keydrive.lu>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: <mailto:vgreimann@key-systems.net>vgreimann@key-systems.net
Web: <http://www.key-systems.net>www.key-systems.net / www.RRPproxy.net <http://www.domaindiscount24.com>www.domaindiscount24.com / www.BrandShelter.com
Follow us on Twitter or join our fan community on Facebook and stay updated: <http://www.facebook.com/KeySystems>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 <http://www.keydrive.lu>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.
Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Microsoft-Exchange-Diagnostics:
1;YTXPR0101MB1600;27:42iGKvXBFNXAXUKCKae7rmbLbmPGOfiLve4ubuyV6dwvStaiX1Td0vMV+Qbi6hxRXz3B/ivlAy6VJx8LeotnqjLkuqNFXg1Rg6i3iAxO76XEcDoDxY6KYhI36aYvzufW X-Microsoft-Antispam-Message-Info:
B2FTWxO0eTjvkMhhYohOc5Xb8Sg79dpMsTpg6IG/2r6RqofncUe6Nv0PROuCxwN9xFMhGgBBI2NOWSkrEvlOaK7IzzmazbTWk2SdZchwwGHkxR7jZ0yAE8+JpTLsYT4ySbkkH+m+SCKaHwJ/PDLsCA==
_______________________________________________ RDS-WHOIS2-Privacy-Proxy mailing list RDS-WHOIS2-Privacy-Proxy@icann.org https://mm.icann.org/mailman/listinfo/rds-whois2-privacy-proxy
participants (3)
-
Alan Greenberg -
Alice Jansen -
Volker Greimann