Hi chuck 

I just landed and going be me up till tomorrow then review. 

I thought long and I think that the overlaps are the connecting points but give me a few hours I will get the updates to you.

Kris

On 4 Nov 2017, at 18:38, Chuck <consult@cgomes.com> wrote:

I arrived home last night and am trying to catch up.  Can someone please send me the latest Word versions and the links to the Google Docs for both deliverables?

 

Also, regarding the definitions, I have been thinking about them and suspect that some WG members will have problem with the word ‘collected’ so I suggest that we consider using the word ‘used’ instead.  And for Contractual Enforcement I question whether we should refer to Private Party Contracts because ICANN Compliance does not have any enforcement ability with Private Party Contracts so I edited that.  They would then read as follows:

 

Contractual Enforcement

Information used to enable ICANN Compliance to monitor and enforce contracted parties’ agreements with ICANN, as well as resolving issues of compliance arising from issues raised by private parties.

 

Regulatory

Information used to enable contact between the registrant and/or their designated point of contact and regulatory entities to ensure compliance with applicable laws.

 

Please feel free to comment on these suggested edits before our call on Monday.

 

Finally, here is a listing from the Wednesday meeting that summarizes our tasks:

    • Summarize each purpose in one sentence: 
      “Information collected to enable contact between the registrant and <who> <to accomplish what>”
    • Think in terms of explaining to the data subject why data is being collected for this purpose – keep it concise and simple.
    • Are the tasks/users identified by your team so diverse and distinct that they may be more than one purpose? If so, split them up and describe each purpose separately.
    • Which purposes covered by other teams are closely related to or overlap the purpose(s) covered by your team?
    • Is there any data collected specifically for the stated purpose? Or does that purpose use only data collected for other purposes?

If anyone has thoughts about any of these items, please share them with the team; we will discuss them on our call.

Chuck

 

 

From: Kris Seeburn [mailto:seeburn.k@gmail.com]
Sent: Wednesday, November 1, 2017 10:37 PM
To: Chuck <consult@cgomes.com>
Cc: Metalitz, Steven <met@msk.com>; lisa@corecom.com; Bastiaan Goslings <bastiaan.goslings@ams-ix.net>; GNSO-RDS-pdp-5@icann.org
Subject: Re: [Gnso-rds-pdp-5] DT5 Update

 

Chuck looked up at your edits and made a few balancing facts. I am now forwarding the updated latest document that we have worked on. We will also be finding a way to work with the team who have worked on “Legal” and i think we may need at some point work with the “investigation” team which in reality also matches with both the enforcement and regulatory. Just some suggestions. They will be good additions to our work. In fact i feel there are areas that overlap which may be the connection points to the whole of each group. But that would be a later stage approach.

 

I think we need to update and push it to the google docs now so that everyone sees the same versioning as we move. Suggestions: Use cases as Appendix to the documents. Anything else to grow the document and understanding can be laid out as an appendix to each document. 

 

Another area that we may add at a later stage is “new gtld auction proceeds” they may be within contractual enforcement and some other groups.