Re: [RDS-WHOIS2-Privacy-Proxy] Confirmation needed asap - Final Questions - preparing for ICANN org briefing

March 19, 2018

      … sorry, and I just saw that we wanted to add these questions from the data accuracy subgroup, my apologies.

  1.  What’s the proportion of WHOIS inaccuracy complaints falling in Proxy & Privacy Service?
  2.  Have there been any measures for ICANN Org or Registrars or Proxy & Privacy Service Providers to validate and verify the WHOIS data collected from Registrants by Proxy & Privacy Service Providers?
  3.  Besides the PPSAI under implementation, are there any contractual requirements on Proxy & Privacy Service Providers through ICANN or Registrars?

All best
Cathrin

From: RDS-WHOIS2-Privacy-Proxy [mailto:rds-whois2-privacy-proxy-bounces@icann.org] On Behalf Of Alice Jansen
Sent: Monday, March 19, 2018 5:08 PM
To: rds-whois2-privacy-proxy@icann.org
Subject: Re: [RDS-WHOIS2-Privacy-Proxy] Confirmation needed asap - Final Questions - preparing for ICANN org briefing

Dear Privacy/Proxy Subgroup,

The SMEs have received the following list of questions in preparation for tomorrow’s call:

·         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 budget impact 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?

Note: please look for the new calendar invite from MSSI-Secretariat – we won’t be using Adobe Connect tomorrow (see here<https://www.icann.org/news/blog/update-on-icann61-adobe-connect-issues> for more information).

Thank you.
Best regards

Alice
From: Alice Jansen <alice.jansen@icann.org<mailto:alice.jansen@icann.org>>
Date: Thursday 15 March 2018 at 14:16
To: "rds-whois2-privacy-proxy@icann.org<mailto:rds-whois2-privacy-proxy@icann.org>" <rds-whois2-privacy-proxy@icann.org<mailto:rds-whois2-privacy-proxy@icann.org>>
Subject: Confirmation needed asap - Final Questions - preparing for ICANN org briefing

Dear Privacy/Proxy subgroup,
To ensure Subject Matter Experts have sufficient time to prepare for your discussion on Tuesday, please provide us with the final list of questions as soon as possible.
Thanks for your understanding.
Kind regards
Alice

From: Alice Jansen <alice.jansen@icann.org<mailto:alice.jansen@icann.org>>
Date: Wednesday 14 March 2018 at 11:37
To: Volker Greimann <vgreimann@key-systems.net<mailto:vgreimann@key-systems.net>>
Cc: "rds-whois2-privacy-proxy@icann.org<mailto:rds-whois2-privacy-proxy@icann.org>" <rds-whois2-privacy-proxy@icann.org<mailto:rds-whois2-privacy-proxy@icann.org>>
Subject: Reminder - Confirmation needed - Final Questions - preparing for ICANN org briefing

Dear Volker,
This is to kindly remind you to confirm whether the list of questions below is final.
Thanks!
Kind regards
Alice

From: Alice Jansen <alice.jansen@icann.org<mailto:alice.jansen@icann.org>>
Date: Monday 12 March 2018 at 14:10
To: Volker Greimann <vgreimann@key-systems.net<mailto:vgreimann@key-systems.net>>
Cc: "rds-whois2-privacy-proxy@icann.org<mailto:rds-whois2-privacy-proxy@icann.org>" <rds-whois2-privacy-proxy@icann.org<mailto:rds-whois2-privacy-proxy@icann.org>>
Subject: Confirmation needed - Final Questions - preparing for ICANN org briefing

Thank you, Susan.
Volker, please confirm whether the following is the final list of questions you will ask the Subject Matter Experts to address on your subgroup call, scheduled for 20 March.
Thanks
Kind regards
Alice
--
·         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 budget impact 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?

From: RDS-WHOIS2-Privacy-Proxy <rds-whois2-privacy-proxy-bounces@icann.org<mailto:rds-whois2-privacy-proxy-bounces@icann.org>> on behalf of Susan Kawaguchi <susankpolicy@gmail.com<mailto:susankpolicy@gmail.com>>
Date: Monday 12 March 2018 at 13:58
To: Volker Greimann <vgreimann@key-systems.net<mailto:vgreimann@key-systems.net>>
Cc: "rds-whois2-privacy-proxy@icann.org<mailto:rds-whois2-privacy-proxy@icann.org>" <rds-whois2-privacy-proxy@icann.org<mailto:rds-whois2-privacy-proxy@icann.org>>
Subject: Re: [RDS-WHOIS2-Privacy-Proxy] Final? Questions - preparing for ICANN org briefing

I agree, I reviewed the questions one more time after our last call and think all the questions in the list are appropriate.

On Mon, Mar 5, 2018 at 6:23 AM, Volker Greimann <vgreimann@key-systems.net<mailto:vgreimann@key-systems.net>> wrote:

As I have not heard any other suggestions, I would assume that it is.

Thanks,

Volker

Am 05.03.2018 um 10:47 schrieb Alice Jansen:
Dear Volker,
May we consider the list below as final?
Thanks
Best
Alice
From: RDS-WHOIS2-Privacy-Proxy <rds-whois2-privacy-proxy-bounces@icann.org><mailto:rds-whois2-privacy-proxy-bounces@icann.org> on behalf of Volker Greimann <vgreimann@key-systems.net><mailto:vgreimann@key-systems.net>
Date: Thursday 1 March 2018 at 17:58
To: "rds-whois2-privacy-proxy@icann.org"<mailto:rds-whois2-privacy-proxy@icann.org> <rds-whois2-privacy-proxy@icann.org><mailto:rds-whois2-privacy-proxy@icann.org>
Subject: Re: [RDS-WHOIS2-Privacy-Proxy] Questions - preparing for ICANN org briefing

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<mailto:vgreimann@key-systems.net>

Web: www.key-systems.net[key-systems.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.key-2Dsystems.net&d=...> / www.RRPproxy.net[RRPproxy.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.RRPproxy.net&d=DwMDa...>

www.domaindiscount24.com[domaindiscount24.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.domaindiscount24.com...> / www.BrandShelter.com[BrandShelter.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.BrandShelter.com&d=D...>

Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:

www.facebook.com/KeySystems[facebook.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_KeySyst...>

www.twitter.com/key_systems[twitter.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_key-5Fsy...>

Geschäftsführer: Alexander Siffrin

Handelsregister Nr.: HR B 18835 - Saarbruecken

Umsatzsteuer ID.: DE211006534

Member of the KEYDRIVE GROUP

www.keydrive.lu[keydrive.lu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.keydrive.lu&d=DwMDaQ...>

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<mailto:vgreimann@key-systems.net>

Web: www.key-systems.net[key-systems.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.key-2Dsystems.net&d=...> / www.RRPproxy.net[RRPproxy.net]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.RRPproxy.net&d=DwMDa...>

www.domaindiscount24.com[domaindiscount24.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.domaindiscount24.com...> / www.BrandShelter.com[BrandShelter.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.BrandShelter.com&d=D...>

Follow us on Twitter or join our fan community on Facebook and stay updated:

www.facebook.com/KeySystems[facebook.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_KeySyst...>

www.twitter.com/key_systems[twitter.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_key-5Fsy...>

CEO: Alexander Siffrin

Registration No.: HR B 18835 - Saarbruecken

V.A.T. ID.: DE211006534

Member of the KEYDRIVE GROUP

www.keydrive.lu[keydrive.lu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.keydrive.lu&d=DwMDaQ...>

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 list

RDS-WHOIS2-Privacy-Proxy@icann.org<mailto:RDS-WHOIS2-Privacy-Proxy@icann.org>

https://mm.icann.org/mailman/listinfo/rds-whois2-privacy-proxy

--