- Gnso-epdp-team - lists.icann.org

Meeting duration
by Arasteh Sept. 11, 2018

Sept. 11, 2018

Dear Kurt I wish to once again reiterate my initial request repeated several time that A) Having two meeting each two hours with one day in between us bothering B) the two hours duration is not supported since after 90 mints everybody ,in particular,yourself becomes tired and the efficiency of the meeting diminished Pls seriously consider that and at least reduce the duration to 90 mints Regards Kavouss Sent from my iPhone

2 1

GDPR course credentials
by Caitlin Tubergen Sept. 11, 2018

Sept. 11, 2018

Dear All, All EPDP Team Members, Alternates and Liaisons will shortly receive an email from SalesSupport(a)itgovernance.co.uk. The email will include instructions for how to take the IT Governance GDPR course. As a reminder, the course is an online, self-paced introductory course on the principles, roles, responsibilities and processes under the GDPR. All EPDP Team Members, Alternates and Liaisons are required to take the course. As mentioned on yesterday’s call, the Leadership Team is in the process of scheduling an additional GDPR Q&A session, targeting the week of 17 September. Accordingly, please try to take the IT Governance GDPR course before 17 September 2018. If you do not receive an email from SalesSupport(a)itgovernance.co.uk by Tuesday, 11 September, please contact the ICANN Support Team. Thank you. Best regards, Marika, Berry, and Caitlin

5 5

Proposal Regarding Appendix C - Data Processing Requirements
by Margie Milam Sept. 11, 2018

Sept. 11, 2018

Hi- With regard Appendix C- I was asked to explain why this Appendix should be retained, and identify whether there are sections that could be deleted. We think that some portions should be retained, some sections could be deleted, and, we propose one additional section. Rationale for Retention of Appendix C In general, Appendix C contains a commitment to processing personal data in accordance with the principles laid out in the Appendix that are not included elsewhere in the Temporary Specification. Some of these sections provide the specificity needed to apply GDPR to the different activities identified in the matrix. It’s not sufficient to say that the Appendix is not needed because the controllers/processors will simply comply with GDPR, because there are different interpretations of how GDPR applies to RDDS/WHOIS data. Keeping Appendix C will ensure that there is transparency and accountability for the broader ICANN community, as well as the registrants, regarding what is expected by controllers, processors, and third party accessors with legitimate purposes. Sections to Delete or Rewrite to be More Specific: I agree with James that some sections in Appendix C lack sufficient detail for how GDPR applies to RDDS/WHOIS, and seem to be merely recitals of GDPR. These could be deleted or be rewritten to be more specific. Examples are: Sections 3.1.1-3.1.6, 3.2, 3.3, 3.6, 3.7., 3.10 & 3.11. Sections to Retain: * Section 1 * Section 2 – Replace it with something like – “processing will take place in accordance with the purposes described in Section 4 of the Temp. Spec.” * Section 3 – * 3.1 & 3.9: Replace references to GDPR with “applicable data protection law” * Section 3.4 – ICANN should clarify what types of records should be maintained with regard to RDDS/WHOIS records * Section 3.5 – Replace with a commitment to provide a standard notice to be developed by ICANN that is concise, transparent, plain language, etc. for RDDS/WHOIS. * Section 3.8 – Delete the specific operational details in 3.8.1, but retain the high level principles in the first few sentences, ending the paragraph with “….alteration or disclosure.” In the implementation stage, ICANN should identify specific operational requirements appropriate for the RDDS/WHOIS data, and include them in the applicable contract. Additional Terms for Appendix C: There should be standard terms applicable to the Third parties who access non-public data, similar to requirements in Section 1. Just like RAA Section 3.7.7’s requirements for registration agreements with registrants, standard access agreement terms should be specified in the RAA to apply to the 3rd parties who access the data (specify their legitimate purposes for accessing the data, agree that they won’t use that data in a manner incompatible with those purposes, etc.). Without standard T&Cs, each controller/processer could come up with its own access agreement that is either too lax or too onerous. I’ll be happy to talk about this more tomorrow. Margie

3 2

Slides for Tuesday's meeting
by Marika Konings Sept. 11, 2018

Sept. 11, 2018

Dear all, Attached are the slides for Tuesday's call. Leadership has taken onboard the recommendation to get right into the substance. With that in mind, the slides on the introductory material (e.g., scheduling) were left somewhat long and can be discussed via email as this discussion regime is put into practice. Best regards, Caitlin, Berry and Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

4.4. purpose overview
by Thomas Rickert Sept. 10, 2018

Sept. 10, 2018

Dear all, Benedict and I have been working over the last few days to specify which parties pursue which purposes. Please find attached a table with our results so far. We will talk you through what we did and why, so no need to spend much time on studying this. We know the document is sent to the list shortly before our upcoming call. The table: - lists the purposes as found in the Temp Spec - lists the refined purposes based on the exchanges on the list so far. We have also made some edits - lists additional purposes which we think are relevant, but which are not covered by the Temp Spec. You would need to let us know if there are additional purposes that we need to include - has 4 columns for Registries, Registrars, ICANN and third parties. We have ticket the boxes of those groups which we think pursue a certain purpose Looking at the list, we can then determine what purposes are pursued by individual parties only versus by multiple parties. Note that the fact that a purpose ist listed there does not mean that the purpose will make it to our final recommendations. Not only will the language of certain purposes need to be refined, but we will also need to legally assess whether the purposes are sufficiently specific etc. Also, we will need to find a legal basis to support the purposes. So there will be much more discussion needed, but we think this might serve as a good starting point for our debate. Note that whilst I have been on the phone with Benedict this evening (our time zone) to discuss things, he did not see the attached version, so he might have comments when we discuss this tomorrow. All the best, Benedict and Thomas

2 1

For your information - Final Version Triage Report
by Marika Konings Sept. 10, 2018

Sept. 10, 2018

Dear All, On behalf of the leadership team, thank you for the input on the Triage Report. Attached you will find the updated version that will be submitted to the GNSO Council tomorrow. For your convenience, you will find attached a redline and clean version. The full comments will be submitted as a separate document. Best regards, Caitlin, Berry and Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

3 3

Triage Report
by Kurt Pritz Sept. 10, 2018

Sept. 10, 2018

Hi Everyone: Attached is a redline and clean version of the Triage report. There is no need to review this before today’s meeting. I have taken out all the Issue Summaries in order to simplify the report and amended the high-level themes in line with the comments. Let me know your thoughts. I plan to send this out this week. Kurt

4 3

**REMINDER** Meeting Invitation / Alternates & Observers / GNSO Temp Spec gTLD RD EPDP call / Tuesday, 11 September 2018 at 13:00 UTC
by Julie Bisland Sept. 10, 2018

Sept. 10, 2018

Dear all, Non-members can follow the EPDP call taking place on Tuesday's and Thursday's at 13:00 UTC via the audio cast or view only Adobe Connect room. As requested and discussed on Tuesday's (14 August 2018) meeting, please note that an additional Adobe Connect room has been created for use by interested alternates and observers to be able to view-only the main EPDP Team Adobe Connect room. The view-only room will also broadcast the audio of the EPDP Team AC room, however, those in the view-only room will not be heard. Note that the audio cast stream will also remain available for now for those that prefer to use that option to listen live to the EPDP Team meeting. View-Only Adobe Connect room for alternates and observers: https://participate.icann.org/gnso-epdp-observers Meeting Audio Cast (for alternates and observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream01 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Agenda wiki page: https://community.icann.org/x/1gONBQ Kind Regards, Andrea Glandon

1 0

Re: [Gnso-epdp-team] [GNSO-EPDP-Lead] TARAVEL SUPPORT
by Kavouss Arasteh Sept. 7, 2018

Sept. 7, 2018

Dear Marika, I have been asked to post it. But I do not know where should I do that. May you kindly post it as a request for support by a member Regards On Thu, Sep 6, 2018 at 10:50 PM Kavouss Arasteh <kavouss.arasteh(a)gmail.com> wrote: > > - as best as they can determine at the time of making the application, > - Reply > - I fully meet the requied condition > - I am not not eligible for other community travel support.I > Acknowlede that deadlines for other community travel support programs and > this pilot is overlap, > - I have not appled for any other potential sources of funding > neither considred or will consider to apply > - No partial funding will be provided by another source, > - I confirm that I will attend as member . I also confirm that no > one would replace me during the F2F meeting; > - I have not applied for any option in the past and, > - I am a member and I confirm that my attendance ,like other members > is critical to the success of the EPDP Team meeting or an aspect of the > meeting If remote participation could replace the f2f IT SHOULD BE APPLIED > TO EVERY ONE AND NOT ONLY ME.. > - Regards > - Kavouss > > > On Thu, Sep 6, 2018 at 10:30 PM Marika Konings <marika.konings(a)icann.org> > wrote: > >> Dear Kavouss, >> >> >> >> Per the travel support application requirements (see attached), please >> provide further information on how you meet the eligibility criteria, >> namely: >> >> >> >> - must be a recognized member of the EPDP Team; >> - must be able to demonstrate their active participation in the >> proceedings of the EPDP Team (e.g. minimum attendance of 75% of all >> scheduled meetings directly relevant to the candidate; >> - as best as they can determine at the time of making the >> application, should not be eligible for other community travel support. >> Acknowledging that deadlines for other community travel support programs >> and this pilot may overlap, candidates *must* identify any other >> potential sources of funding they are considering/have considered/have >> applied for/will apply for and an explanation for why they believe they >> will be ineligible or otherwise unable to receive funding through those >> sources. If partial funding will be provided by another source, this must >> be noted to enable the most effective allocation; >> - must confirm that no alternates are expected to be in attendance >> who could replace the candidate during the F2F meeting; >> - should disclose recent past funding options and explain why >> those options are no longer available, if applicable; and, >> - must demonstrate that their attendance is critical to the >> success of the EPDP Team meeting or an aspect of the meeting that cannot be >> achieved by participating remotely. >> >> >> >> Note that we already have the necessary information in relation to bullet >> one and two, so please provide the necessary information in relation to the >> remaining bullet points. >> >> >> >> Best regards, >> >> >> >> Marika >> >> >> >> *From: *GNSO-EPDP-Lead <gnso-epdp-lead-bounces(a)icann.org> on behalf of >> Kavouss Arasteh <kavouss.arasteh(a)gmail.com> >> *Date: *Thursday, September 6, 2018 at 14:18 >> *To: *"gnso-epdp-lead(a)icann.org" <gnso-epdp-lead(a)icann.org> >> *Subject: *[GNSO-EPDP-Lead] TARAVEL SUPPORT >> >> >> >> Further to the discussion took place at 11TH meeting of EPDP Team, pls >> kindly consider my formal application for travel support to ICANN 63 based >> on the consdition applied by ICANN regarding my tarvel and hotel booking >> >> I am a member of the Team and would attend the meeting from 20-25 October. >> >> I will travel on 19 October Geneva -Barcelona and reurn back Barelona to >> Geneva on 25 evening >> >> Regards >> >> Kavouss Arasteh >> >

2 1

Re: [Gnso-epdp-team] RySG Early Input on the Temporary Specification
by Marika Konings Sept. 7, 2018

Sept. 7, 2018

Thanks, Kristina. The RySG early input has now been posted here: https://community.icann.org/x/Ag9pBQ. Best regards, Caitlin, Berry and Marika From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of "Rosette, Kristina via Gnso-epdp-team" <Gnso-epdp-team(a)icann.org> Reply-To: "Rosette, Kristina" <rosettek(a)amazon.com> Date: Friday, September 7, 2018 at 15:14 To: "Gnso-epdp-team(a)icann.org" <Gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] RySG Early Input on the Temporary Specification All, Attached is the RySG’s Early Input on the Temporary Specification. K Kristina Rosette Senior Corporate Counsel, IP – Domains rosettek(a)amazon.com<mailto:rosettek@amazon.com> | 703.407.1354

1 0