Thanks, Farell With regard to the current google-doc version (I assume that is what I need to look at, and that anything else on the list will be incorporated if applicable - if not then I’m not sure what I can reflect on): I am slightly lost when it comes to the structure. As far as I am aware the Purpose (Name) we are meant to deal with is ‘Regulatory or Contractual Enforcement’. And the IP example that Steve provided would then be one Use Case related to this purpose. I do not know who it put there but as is now the Google doc introduces another purpose on page 2, i.e. ‘Provide services to clients to provide threat intelligence and guard against DNS system attacks.’ Besides the fact that I do not understand what ‘providing to provide’ means, the above IMO does not fit the ‘Regulatory or Contractual Enforcement’ scope. Just like e.g. CERTS and LEAs do not fall within our purpose, as was established earlier, so called ’security groups’ and ‘illegal groups’ don’t either… Maybe I am missing something here?
On 25 Oct 2017, at 14:36, Farell Folly <farellfolly@gmail.com> wrote:
Dear All,
In attach a compiled list of data elements that may be required by a government agency, a regulatory or controlling authority to ensure contractual compliance. I used the gdpr-dataflow-matrix-whois-11sep17-en report which was very useful. There is also a good categorization of users types.
I hope it helps us.
Le mar. 24 oct. 2017 à 22:22, <consult@cgomes.com> a écrit : I think that will work Bastian as long as you are able to respond as early as possible tomorrow afternoon your time.
Chuck
-----Original Message----- From: Bastiaan Goslings [mailto:bastiaan.goslings@ams-ix.net] Sent: Tuesday, October 24, 2017 9:08 AM To: Kris Seeburn <seeburn.k@gmail.com> Cc: Bastiaan Goslings <bastiaan.goslings@ams-ix.net>; consult@cgomes.com; gnso-rds-pdp-5@icann.org Subject: Re: [Gnso-rds-pdp-5] Draft Input Document
Hi all,
Thanks, and sorry for the radio silence - if it works in terms of our time-/deadline, I can reserve time to look closer at the text tomorrow afternoon (UTC +4, I’m in Dubai for RIPE75)
-Bastiaan
On 24 Oct 2017, at 18:53, Kris Seeburn <seeburn.k@gmail.com> wrote:
I think we just need to read through and accept and properly incorporate all as one. Let us jus agree what is kept what goes away. I think time to synthesize and fully agree. Most are fine i think it foes to fully integrate and agree and the full language to reflect.
Kris
On Oct 24, 2017, at 18:09, <consult@cgomes.com> <consult@cgomes.com> wrote:
Thanks for the great work.
All – Please review and comment on the draft with Steve’s edits.
Chuck
From: gnso-rds-pdp-5-bounces@icann.org [mailto:gnso-rds-pdp-5-bounces@icann.org] On Behalf Of Beth Bacon Sent: Tuesday, October 24, 2017 6:51 AM To: Metalitz, Steven <met@msk.com>; gnso-rds-pdp-5@icann.org Subject: Re: [Gnso-rds-pdp-5] Draft Input Document
Hi Steve, Thanks! Our emails wouldn’t have zipped right past each other.
I’ll send this version around. Thanks, Beth
From: Metalitz, Steven [mailto:met@msk.com] Sent: Tuesday, October 24, 2017 9:19 AM To: Beth Bacon <bbacon@pir.org>; gnso-rds-pdp-5@icann.org Subject: RE: Draft Input Document
Thanks Beth. I have dropped into this document the “Purpose definition” language I drafted and which I circulated a few minutes ago. (Apologies that I evidently failed to hit send on this text yesterday!)
<image001.gif> Steven J. Metalitz | Partner, through his professional corporation T: 202.355.7902 | met@msk.com Mitchell Silberberg & Knupp LLP | www.msk.com 1818 N Street NW, 8th Floor, Washington, DC 20036
THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE IS INTENDED ONLY FOR THE PERSONAL AND CONFIDENTIAL USE OF THE DESIGNATED RECIPIENTS. THIS MESSAGE MAY BE AN ATTORNEY-CLIENT COMMUNICATION, AND AS SUCH IS PRIVILEGED AND CONFIDENTIAL. IF THE READER OF THIS MESSAGE IS NOT AN INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY REVIEW, USE, DISSEMINATION, FORWARDING OR COPYING OF THIS MESSAGE IS STRICTLY PROHIBITED. PLEASE NOTIFY US IMMEDIATELY BY REPLY E-MAIL OR TELEPHONE, AND DELETE THE ORIGINAL MESSAGE AND ALL ATTACHMENTS FROM YOUR SYSTEM. THANK YOU.
From: gnso-rds-pdp-5-bounces@icann.org [mailto:gnso-rds-pdp-5-bounces@icann.org] On Behalf Of Beth Bacon Sent: Tuesday, October 24, 2017 8:55 AM To: gnso-rds-pdp-5@icann.org Subject: [Gnso-rds-pdp-5] Draft Input Document
Hello All, I’ve compiled the edits and contributions into one word document. I’ve not taken any license to edit and have merely dropped the original language into the various sections of the template document and into the chart (one for each use case provided). I’m not sure if the chart was illustrative in the template or meant to be used in our inputs, but I do think helps to present the use cases provided in a visually digestible way.
Go forth and edit! Best, Beth
Elizabeth Bacon Policy Manager, Public Interest Registry Office: +1 703-956-3962 | Mobile:+1 571-352-5029 www.pir.org | Facebook | Twitter | Instagram | YouTube
_______________________________________________ Gnso-rds-pdp-5 mailing list Gnso-rds-pdp-5@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-5
Kris Seeburn seeburn.k@gmail.com • www.linkedin.com/in/kseeburn/
<KeepItOn_Social_animated.gif>
_______________________________________________ Gnso-rds-pdp-5 mailing list Gnso-rds-pdp-5@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-5
_______________________________________________ Gnso-rds-pdp-5 mailing list Gnso-rds-pdp-5@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-5 -- Regards @__f_f__ https://www.linkedin.com/in/farellf <Data-elements-regulatory-and-contractual.docx><gdpr-dataflow-matrix-whois-11sep17-en.pdf>