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

Fwd: Re: Frustration with no AC Chat.
by Stephanie Perrin Oct. 22, 2018

Oct. 22, 2018

-------- Forwarded Message -------- Subject: Re: [Gnso-epdp-team] Frustration with no AC Chat. Date: Mon, 22 Oct 2018 01:03:25 +0200 From: Stephanie Perrin <stephanie.perrin(a)mail.utoronto.ca> To: Alan Greenberg <alan.greenberg(a)mcgill.ca> I completely agree. Chat is the most economical, expeditious way to register or correct a fact, express support, or provide urls and references. WHy has it been cancelled? Stephanie Perrin On 2018-10-22 00:49, Alan Greenberg wrote: > I'd like to express my frustration with no Adobe Connect Chat. > > There are times when a repeat intervention would not be necessary if > we could enter a chat message into the formal meeting record. The > speaker queue would, I suspect, be far shorter. > > Is it not possible to use the regular AC room for the team Members?? > > Alan > > _______________________________________________ > Gnso-epdp-team mailing list > Gnso-epdp-team(a)icann.org > https://mm.icann.org/mailman/listinfo/gnso-epdp-team

2 1

Draft slides for High Interest Topic Session for your review
by Marika Konings Oct. 22, 2018

Oct. 22, 2018

Dear EPDP Team, Please find attached a first draft of the slide deck for the High Interest Topic (HIT) Session for your review. Please note that the leadership team did not have a chance to review this yet in detail, but in the interest of time agreed to already share this for your input. At a minimum, updates will need to be made to reflect any outcomes or updates from Saturday’s F2F meeting. Similarly, some of the more text heavy slides could be transformed into speaking points with only key bullets on the slide. For those that volunteered to represent the EPDP Team and present part of the presentation (Alan Woods, Diane Plaut, Thomas Rickert, Hadia Elminiawi, Emily Taylor, Milton Mueller, Ashley Heineman, Benedict Addis), please indicate if there is a specific part which you would be interested in presenting. We look forward to receiving your feedback. 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

4 3

Frustration with no AC Chat.
by Alan Greenberg Oct. 22, 2018

Oct. 22, 2018

I'd like to express my frustration with no Adobe Connect Chat. There are times when a repeat intervention would not be necessary if we could enter a chat message into the formal meeting record. The speaker queue would, I suspect, be far shorter. Is it not possible to use the regular AC room for the team Members?? Alan

2 1

Re: [Gnso-epdp-team] Frustration with no AC Chat.
by Margie Milam Oct. 22, 2018

Oct. 22, 2018

I share Alan's frustration as well. Margie On 10/22/18, 12:50 AM, "Gnso-epdp-team on behalf of Alan Greenberg" <gnso-epdp-team-bounces(a)icann.org on behalf of alan.greenberg(a)mcgill.ca> wrote: I'd like to express my frustration with no Adobe Connect Chat. There are times when a repeat intervention would not be necessary if we could enter a chat message into the formal meeting record. The speaker queue would, I suspect, be far shorter. Is it not possible to use the regular AC room for the team Members?? Alan _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_l…

1 0

Requested action - Small teams
by Marika Konings Oct. 21, 2018

Oct. 21, 2018

Dear EPDP Team, As discussed yesterday, the leadership team hopes to make progress on the small team topics during our meetings on Wednesday and Thursday. In order to do so, there are a couple of asks for those that participated in the small team: Small team #1: Applicability of Data Processing Requirements - natural vs. legal person (Charter Question H) Participants: Alan Greenberg (ALAC), Alex Deacon (IPC), Ashley Heineman (GAC), Ben Butler (SSAC), James Bladel (RrSG), Lindsay Hamilton-Reid (RrSG), Marc Anderson (RySG), Margie Milam (BC) Requested Action small team #1: representatives of the IPC, BC, GAC, RrSG and RySG to meet to further discuss possible draft policy recommendation in relation to this topic, factoring in positions expressed to date and using the original agreement from the first call as a starting point. The proposed policy recommendations are to be shared with the EPDP Team in advance of Wednesday’s meeting. Small team #2: Applicability of Data Processing Requirements - Geographic basis (Charter Question H) Participants: Amr Elsadr, Diane Plaut, Emily Taylor, Hadia Elminiawi, Kristina Rosette, Margie Milam, Rafik Dammak, Rahul Gosain, Thomas Rickert Requested Action small team #2: small team participants to further consider draft responses which includes the consideration of possible models for future implementation and consider how these could be translated into policy recommendations for inclusion into the Initial Report. The proposed policy recommendations are to be shared with the EPDP Team in advance of Wednesday’s meeting. Small team #3: Temporary Specification and Reasonable Access (Charter Question J) Participants: Alan Woods (RySG), Alex Deacon (IPC), Ashley Heineman (GAC), Benedict Addis (SSAC), Farzaneh Badii (NCSG), Hadia Elminiawi (ALAC), Kurt Pritz (Chair), Mark Svancarek (BC), Rafik Dammak (GNSO Council Liaison), Thomas Rickert (ISPCP), Volker Greimann (RrSG Alternate) Requested Action small team #3: small team members to socialize the draft policy recommendation developed by the small team with their respective groups with the objective of confirming the small team policy recommendations and/or share any concerns prior to Wednesday’s meeting. To review the small team summaries, please see: 13. Small teams #1 #2 #3 status update - 15 Oct 2018<https://community.icann.org/download/attachments/96207825/13.%20Small%20tea…>. 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

Re: [Gnso-epdp-team] CENTR Survey: Whois status and impacts from GDPR
by Margie Milam Oct. 18, 2018

Oct. 18, 2018

Hi- Thanks Georgios for sharing this document. This is really great information, and can help with several issues for the EPDP, including: * Legal/Natural person distinction * Geographic distinction * Accuracy * We would like to propose that Staff invite someone from Centr who can talk to us at Barcelona about these issues, to help inform our policy recommendations. We would also like to ensure that all of the issues that were “parked” at our F2F meeting are considered as part of our deliberations in Barcelona. Thanks, Margie From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of "Georgios.TSELENTIS(a)ec.europa.eu" <Georgios.TSELENTIS(a)ec.europa.eu> Date: Friday, October 12, 2018 at 1:33 AM To: "kurt(a)kjpritz.com" <kurt(a)kjpritz.com>, "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] CENTR Survey: Whois status and impacts from GDPR Dear Kurt, EPDP colleagues, Please find a recent survey among European ccTLDs on impacts from GDPR: The survey report can be found here: https://centr.org/library/library/survey-report/centr-report-whois-status-a…<https://urldefense.proofpoint.com/v2/url?u=https-3A__centr.org_library_libr…> The presentation has been uploaded at: https://centr.org/library/library/external-event/whois-status-and-the-impac…<https://urldefense.proofpoint.com/v2/url?u=https-3A__centr.org_library_libr…> The overview of data collected and published via the WHOIS is available at: https://stats.centr.org/pub_whois<https://urldefense.proofpoint.com/v2/url?u=https-3A__stats.centr.org_pub-5F…> Best regards, Georgios

2 2

FW: [Ext] Re: [GNSO-EPDP-Lead] Purpose B Small Team
by Caitlin Tubergen Oct. 17, 2018

Oct. 17, 2018

Thanks, Benedict. Given the proximity to ICANN63, we took the liberty of sending this language to the full team so that we can discuss in Barcelona. Thanks again for taking the lead on this! Best regards, Marika, Berry and Caitlin From: Benedict Addis <bee(a)theale.co.uk> Date: Tuesday, October 16, 2018 at 6:21 AM To: Kurt Pritz <kurt(a)kjpritz.com> Cc: Stephanie Perrin <stephanie.perrin(a)mail.utoronto.ca>, Thomas Rickert <epdp(a)gdpr.ninja>, Lindsay Hamilton-Reid <lindsay.hamilton-reid(a)fasthosts.com>, Caitlin Tubergen <caitlin.tubergen(a)icann.org>, "gnso-epdp-lead(a)icann.org" <gnso-epdp-lead(a)icann.org> Subject: [Ext] Re: [GNSO-EPDP-Lead] Purpose B Small Team Dear all, On Kurt’s suggestion, I propose the following Purpose B that relies directly on the language in Recitals 47, 49 and 50. [ICANN requires that registration data is processed for the purpose of...] maintaining the security, stability and resiliency of the Domain Name System. This will involve the disclosure of existing registration data to legitimate third parties, for the following reasons only: 1) fraud prevention; 2) network and information security; and 3) indicating possible criminal acts, or threats to public security. I think that for ICANN, disclosure will happen under 6(1)f. Third parties will require a lawful basis of their own for their processing, governed by a common set of standards that we’ll discuss when we come to the access discussion. Thoughts? B

5 4

ICANN63 Document package now available on EPDP Team Google Drive
by Marika Konings Oct. 17, 2018

Oct. 17, 2018

Dear EPDP Team, As discussed earlier today, a document package has been prepared for the EPDP Team to facilitate your preparation for ICANN63. You will find two folders on the EPDP Team Google drive – one with the individual documents and one with those same documents compiled in three batches so you can choose the best way for you to download and review these documents. Please note that in relation to the data elements workbooks, Purpose M does not yet contain the changes proposed by Kristina and Diane, these are in the process of being applied. Similarly, Purpose N is in the process of being transitioned to the new template. As soon as the updated versions are available, these will get shared as well as posted here: https://community.icann.org/x/5AC8BQ. Similarly, we are still waiting for Purpose E – Registry Escrow to be submitted. Do note that the data elements workbooks are still work in progress. To facilitate your review, you will find both a clean as well as a redline version included. The redline version denotes changes as well as were these changes derive from as well as any input and/or questions that may need further consideration. The hope is though that the group can commence its deliberations from the clean versions at ICANN63. However, to make sure that nothing is overlooked or forgotten about, please flag any issues that you think require further discussion and/or modification here: https://docs.google.com/document/d/1TjfVNLJrIDihe_CUQIZPcc3S4-OInwl025KOisM… by Friday 19 October at the latest so this can be taken into account for the F2F meeting. Note that some items are already included in this list. Those that requested to receive the documents via email will receive those shortly. Safe travels and see you all soon. 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 1

Notes and action items EPDP Team meeting #20
by Marika Konings Oct. 16, 2018

Oct. 16, 2018

Dear All, Please find below the notes and action items from today’s EPDP Team meeting. Best regards, Caitlin, Berry and Marika EPDP Team Meeting #20 Tuesday, 16 October 2018 Notes and Action Items High-level Notes/Actions: Action item #1: Staff to put together ICANN63 document package that will contain all materials to be reviewed prior to ICANN63. This will include revised Data Elements Workbooks and draft Initial Report chapter. Action item #2: EPDP Team members to review ICANN63 document package prior to ICANN63 Action item #3: Staff to prepare revised agenda and draft slide deck for HIT session. Questions for ICANN Org from the EPDP Team: Further input is requested to explore how WHOIS was used before the Temp Spec was adopted, in OCTO's activities. The original Org response does not address that issue. For example, did OCTO use WHOIS in its law enforcement training and outreach activities, or engagement with the cybersecurity community, or to facilitate or respond to large scale botnet attacks, such as Conficker or Avalanche? Individual members may follow up with the CTO for follow up questions, if available at ICANN63. Notes & Action items These high-level notes are designed to help the EPDP Team navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. The MP3, transcript, and chat are provided separately and are posted on the wiki at: https://community.icann.org/x/2IpHBQ. 1. Roll Call & SOI Updates (5 minutes) * Attendance will be taken from Adobe Connect * Please remember to mute your microphones when not speaking, and state your name before speaking for transcription purposes. * Please remember to review your SOIs on a regular basis and update as needed. Updates are required to be shared with the EPDP Team. 2. Welcome and Updates from EPDP Team Chair (5 minutes) a) Confirm status of small teams #1, #2 and #3 * Small teams met to tackle a number of topics that are not covered through the data elements workbooks (natural vs. legal, geographic application, reasonable access) * Summary note will be shared as part of the materials for ICANN63 which will serve as a starting point for further discussions. b) Confirm status of data elements workbooks * Work is still ongoing on the number of data elements workbooks * Latest versions of data elements workbooks are expected to be posted by the end of today * New template being developed to bring all different aspects of the conversation together. Action item #1: Staff to put together ICANN63 document package that will contain all materials to be reviewed prior to ICANN63. This will include revised Data Elements Workbooks and draft Initial Report chapter. Action item #2: EPDP Team members to review ICANN63 document package prior to ICANN63 c) Review of outstanding action items * See https://community.icann.org/x/NwSNBQ d) Other updates, if applicable 3. Planning for F2F Meetings at ICANN63 Objective of discussion: (1) Confirm topics to be addressed during ICANN63 (2) Confirm materials to be reviewed in preparation for ICANN63 F2F Meeting (3) Agree on approach for F2F meeting a) Review agenda for full day F2F meeting on Saturday & confirm materials to be reviewed prior to meeting (see draft attached) b) Review additional slots throughout the week and expected topics to be addressed * See slide 'drilling for data elements' that explains the thinking behind the updated templates. * Template will define the ICANN purpose, define the processing activities and include an inventory of data elements as well as a data elements map. * See also example shared for purpose E * All purposes will be converted to this new template for ICANN63. * What is referred to when it says 'ICANN Purpose'? Will Board liaisons provide input on this as well? * Is this level of detail needed? Yes, GDPR requires this level of detail to be provided. * Data retention periods are required to be stated with rationale to be provided for the data retention period requested. * It is ICANN ORG that signs the contract, therefore ICANN org is the valid party to be included here. * Need to make sure that responsible party is documented as well as referencing ICANN's Bylaws & Mission. * These completed data elements workbooks are an important part of the Initial Report as they address a large chunk of the charter questions. * For Saturday F2F meeting, please see proposed agenda shared. * Priority to finalize purpose A and B. Aim to document preliminary recommendations or if these are not agreed, document the different positions for inclusion in the Initial Reports. * In the afternoon consider conducting small group working sessions, purposes A and C, other purposes as identified. * Determine in the afternoon what to focus on for the remaining sessions at ICANN63. * Focus efforts on the goal of delivering Initial Report - may be worth to review the document that staff has started putting together and what is in there currently and what the gaps are. See latest version here: https://docs.google.com/document/d/10VIcHv1NqdVHZbAlhxuEZFi1f__UP-m7PU5P_aJ…. Work undertaken at ICANN63 is expected to feed into the open areas identified in the draft Initial Report. * Should OCTO be invited to talk about what data they need? What about parked issues? For natural vs. legal person - Centr report may help inform that discussion. Some noted that this report needs to be considered with care as it focuses on ccTLD world and an evolutionary process. Leadership team to further discuss how to build this in at appropriate time. * May not best used of time to get another report from ICANN Org about their use of data - could maybe be provided in writing? What is the status of those previous requests? More productive to create questions, get a response and then set up a meeting if there are follow up discussion. Need to be focused now on efficiency and effectiveness. * OCTO request - want to know how registration data factored into some of the previous security incidents (e.g. Confickr). Consider setting up follow up conversation with OCTA for those interested. Question for ICANN Org: Further input is requested to explore how WHOIS was used before the Temp Spec was adopted, in OCTO's activities. The original Org response does not address that issue. For example, did OCTO use WHOIS in its law enforcement training and outreach activities, or engagement with the cybersecurity community, or to facilitate or respond to large scale botnet attacks, such as Conficker or Avalanche? Individual members may follow up with the CTO for follow up questions, if available at ICANN63. 4. Planning for High Interest Topic (HIT) Session at ICANN63 Objective of discussion: (1) Agree on agenda for HIT session (2) Confirm speakers for High Interest Topic Session a) Review proposed agenda for High Interest Topic (HIT) Session b) Confirm presenters for HIT Session * See draft agenda for HIT session circulated. Topics track to the charter question sections. * Aim to spend more time on issues on which community input is expected - focus less on process. Consider splitting session in half - with half dedicated to Q & A. Consider if there are specific questions that should be put forward that would be meaningful for the EPDP Team as well as the audience. Consider framing questions around areas of disagreement in such a way that known positions are not restated, for example focusing on GDPR compliance. Need to factor in the general time available. * Presenters on behalf of the EPDP Team needed. Volunteers: Alan Woods, Diane Plaut, Thomas Rickert, Hadia Elminiawi, Emily Taylor, Milton Mueller, Ashley Heineman, Benedict Addis. * Volunteers asked to share in bullet point form their speaking points prior to the HIT - especially for those areas where there is no consensus (yet). * Staff to prepare draft slide deck for HIT session. * No advocacy - only presenting different viewpoints and state of play. * Need timer for interventions from the audience. * Need to make sure that the basic understanding of the approach taken is there so that the audience can follow along. * Need to give audience an opportunity to react to what EPDP Team is working on. Action item #3: Staff to prepare revised agenda and draft slide deck for HIT session. 5. Wrap and confirm next meeting to be scheduled for Saturday 20 October from 8.30 – 18.30 CET at ICANN63. a) Confirm action items b) Confirm questions for ICANN Org, if any 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<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

Recordings, Attendance & AC chat from the GNSO Temp Spec gTLD RD EPDP held Tuesday, 16 October 2018
by Andrea Glandon Oct. 16, 2018

Oct. 16, 2018

Dear all, Please find the attendance and AC chat attached to this email. The MP3 and AC recording below from the GNSO Temp Spec gTLD RD EPDP call held on Tuesday, 16 October 2018 at 13:00 UTC. These have also been posted on the agenda wiki page: https://community.icann.org/x/LwWrBQ MP3: https://audio.icann.org/gnso/gnso-epdp-gtld-registration-data-specs-16oct18… AC Recording: https://participate.icann.org/p9ndqxxixvt/<https://participate.icann.org/p9ndqxxixvt/?OWASP_CSRFTOKEN=5aed66bc9d5a449f…> ** Please let me know if your name has been left off the list ** Mailing list archives of the GNSO Temp Spec gTLD RD EPDP : https://mm.icann.org/pipermail/gnso-epdp-team/ Main wiki page for the working group: https://community.icann.org/x/IYEpBQ Thank you. Kind Regards, Andrea Glandon

1 0