Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

PROPOSED AGENDA


  1. Roll Call & SOI Updates 
2.
  1. Welcome and Updates from EPDP Team
Chair 
  1. Chair
3.
  1. Review proposed next steps and action items on
Section
  1. 4.4
- Lawfulness and Purposes of Processing gTLD Registration Data

a. For Registrar-Registry-ICANN Contract Purposes (for collection), all, but registrars specifically, are asked to provide input on whether there are additional legitimate reasons why ICANN may need to require contracted parties to collect data from registrants? Should these purposes be re-grouped in some way to better capture their relevance, necessity and the data needed to support them?

b. For Third Party Purposes (for access), the EPDP Team is expected to weigh in on whether the purposes enumerated here are valid and legitimate? Do those purposes have a corresponding legal basis? Do these purposes need to be reviewed for clarity? Note that any discussion on the safeguards and limitations in relation to access necessary to ensure GDPR compliant disclosures would happen after the gating questions have been answered.

c. Once step 2 and 3 have been completed, the EPDP Team will need to review how this separation of purposes is to be reflected in 4.4 and what updates, if any, need to be made to the preceding sections (4.1 – 4.3), if these are still deemed necessary and relevant in light of the separation. 

4. Begin review of data elements table 

5. Begin discussion on Appendix C – Data Processing Requirements

a. Deliberate on Preamble 

Consider any input form the EPDP team that would include specific recommendation for amendments to the temporary specification for:

1) Registrar / Registry / ICANN processing of data: clarifying the elements proposed in the ICANN-developed specification

2) Third party processing where more specificity was requested

b. Absent that input, or as a next step,

1) agree on certain preparations for the next meeting, or if direction is lacking,

2) review the sections against triage survey results and comments as a basis for suggested amendments.

4. Begin discussion on Appendix C: for each section, we will refer to the Triage survey and meeting comments as a guide for considering to amend the specification section. We might then form a rough consensus for the content of edits and assign a small team (1-3) people to create a revised version for the next meeting. Breaking the Appendix into its parts:

a. Preamble

b. gTLD Processor Activity Chart

c. b. Deliberate on Section 1 (Principles for Processing)

c. Deliberate on Section 2 (Lawfulness of Processing)

d. Deliberate on Sections 3.1, 3.1.1 – 3.1.6 (Specific Controller Processing requirements)

e. Deliberate on 3.2 – 3.11 (Specific Controller Processing requirements)

f. Deliberate on Sections 3.8 – 3.11 (Specific Controller Processing requirements)

g. Discuss next steps for dealing with input on Appendix C

65. Confirm action items and questions for ICANN Org, if any any

76. Wrap and confirm next meeting to be scheduled for Tuesday , 4 September at 13.00 UTC.  )     


BACKGROUND DOCUMENTS


EPDP Team DSI Appendix Cv2.docx

AUDIO CAST INFORMATION AND VIEW ONLY ADOBE CONNECT FOR ALTERNATES AND OBSERVERS


To join the event, click on the link: 

Listen in browser: http://stream.icann.org:8000/stream01

Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u

View-Only Adobe Connect room for alternates and observers: https://participate.icann.org/gnso-epdp-observers

...