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

EPDP Status update & Next Steps
by Rafik Dammak April 17, 2019

April 17, 2019

Dear EPDP Team, I hope you have enjoyed the relative peace and quiet over the last couple of weeks. Behind the scenes, the leadership team has been working hard to prepare materials that are intended to lay the groundwork for the next steps in our phase 2 preparations. As such, we thought it would be helpful to provide you with a brief status update on these different items as well as request your feedback for some of these: 1. EPDP Team Chair selection – as you will have probably seen, the call for expressions of interest was extended to Monday 8 April. Council leadership, together with the leadership of the GNSO Council Standing Selection Committee, will meet shortly after that to review the applications received, in view of a confirmation by the GNSO Council during its meeting on 18 April. 1. EPDP Team Member / Alternate Confirmations – I’ve reached out to the chairs of the various appointing organizations to ask them to provide a confirmation of when vacant EPDP Team member and alternate slots are expected to be filled. Ideally, any empty slots are filled as soon as possible – accordingly, please work with your respective groups to ensure appointments are confirmed in a timely manner. 1. ICANN65 Meeting Planning / Resource request – as you know, we did submit a request for a possible day zero meeting. Although we have not received confirmation yet on whether or not this is possible, I have also been working with Council leadership and support staff to see how the EPDP Team could get as much time as possible within the confines of the policy meeting. However, this will require the flexibility of other groups as there is limited meeting time and space during the Policy Forum. If it is possible to carve out substantial time during the ICANN meeting, I am leaning toward that approach as several of you have indicated potential challenges with arriving a day earlier, and an extra day would obviously involve additional costs. I expect that a decision on whether or not there will be a day zero meeting will be made shortly (by 15 April at the latest) so, if possible, please hold off on booking your travel until that date. In parallel, I have also reached out to the chairs of the appointing organizations to confirm which members would need travel support to attend (and have no available alternate to replace them) to help inform the Council’s request to the ICANN Board for resources to support the initial part of our work (see also https://mm.icann.org/pipermail/council/2019-March/022442.html) I expect this request to be finalized shortly. 1. Work plan development – thank you to those of you who responded to the different questions that came out of ICANN64. We have reviewed all of your input closely and would like to put the following recommendations forward (see also collated version attached): Working methods / prioritization: The leadership team recommends splitting the work into two work tracks/areas: 1) System for Standardized Access to Non-Public Registration Data; and 2) all other remaining issues (remaining issues from Annex: Important Issues for Further Community Action and Issues deferred from phase 1 - as outlined in the mind map updated on 10 March 2019). Priority will be given to work track / area 1, and it would be foreseen that a separate Initial Report and Final Report would be prepared for work track / area 1 and work track / area 2 items so that progress in work track / area 1 is not held up. For both work track / areas, the EPDP Team will first work online / on-list to complete the worksheets which will detail: • scope / issues to be discussed, • information to be gathered, • briefings to be planned, • legal questions to be answered, and • dependencies identified. Once the bulk of work on work track / area 1 and the implementation of Phase 1 recommendations has been completed, the EPDP Team will start focusing on work track / area 2 items. Note, however, certain work track / area 2 items contain dependencies that may need to be addressed before work can even start (for example, completion of the study in relation to natural vs. legal as foreseen in the phase 1 recommendations). If there is discrete work that can be undertaken in parallel in relation to the work track / area 2 items and there are no dependencies identified, the EPDP Team will identify these items in the worksheets so that the leadership team and EPDP Team can further review these and determine whether it is feasible to carry out this work in parallel to work track / area 1 deliberations. The leadership recommends that the EPDP Team remains flexible in its approach to dealing with the items in phase 2. Everyone seems to agree that the work on a system for standardized access to non-public registration data should be prioritized, and as such, that should be the primary focus at the start. However, there may be circumstances that could dictate a change in approach - accordingly, we ask the EPDP Team to remain open minded and work in a collaborative manner to ensure that the maximum amount of progress can be made without overloading the group and risking burn-out. Dependencies: The worksheets for each topic will be used to (1) further define the dependencies, (2) establish the expected timeframe, and (3) assign or designate responsible parties. As noted above, the worksheets should facilitate identifying discrete items for the EPDP Team or others that could be moved forward in relation to any dependencies for work track / area 2 items so that when the EPDP Team commences its deliberations on these items, all necessary information is available. Legal guidance next steps: The leadership team recommends that the legal committee is reconstituted as soon as possible, with meetings commencing shortly after reconstitution. In order to make the committee more effective, it is recommended that members have proven legal experience. Their role is not to advocate for their respective groups or positions, but to assess whether issues / questions raised by the EPDP Team are legal questions, have already been addressed elsewhere and channel any follow up to the EPDP Team's legal counsel. If at any point any member of the EPDP Team is of the view that the legal committee is going outside of its remit and/or individual members are not working for the best interest of the EPDP Team as a whole, the leadership team will review the membership structure. Target date for Initial Report: Although it is difficult to set a firm timeline at this stage due to dependencies and the complexity of work, the leadership team does believe it will be helpful to set a target date to work towards for the delivery of an Initial Report for work stream 1 for public comment. At a minimum, the target date would assist in the development of a detailed work plan based on the information in the work sheets and make a determination of whether that goal is realistic or not. At this stage, the leadership team is of the view that between 12 and 18 months is hopefully a realistic and desirable timeframe for all. Of course, this is also dependent on the resources that the group has requested and may request and whether or not these will be made available. We look forward to receiving your feedback on these recommendations. Worksheets: As outlined in the previous section, in order to further inform the development of the work plan, the staff support team has developed the attached worksheet template for your review and consideration. The idea is that by ensuring that the proper groundwork is done up front, we will have a solid basis to move forward on the different issues and will be able to work through them in a systematic way. You will find attached a completed template for one of the topics so you have a better idea of what we have in mind. Please let us know if you have any comments or suggestions for the template – I would like to request the staff support team to start developing worksheets for each of the topics on our list so we can shortly review these and make sure that we are all aligned when it comes to scope, expected deliverable, legal questions, required reading, dependencies as well as approach. 1. Review of legal guidance provided to date: Several of you indicated that as a first step, the EPDP Team should review the legal guidance provided to date in order to identify if/how it applies to the work in phase 2 as well as identify any possible follow up questions. I believe this is something that should be done with the full team, but I would like to receive your input on how this is best done. Do we schedule a couple of sessions prior to which everyone is expected to have read the memo so we can discuss? Should one member be appointed / volunteer to brief the group on a memo? I look forward to receiving your suggestions. 1. Next meeting – we do not have a confirmed time / date yet for our next meeting as I am hoping that we get confirmation soon on a couple of the items on the list above (especially items 1 and 2). However, that does not mean we cannot continue our preparations on list, so please make sure you provide your input on the mailing list and contribute to requests for input that have been circulated to date (see for example the reminder on input on the legal questions: https://docs.google.com/document/d/11fCpx_FxuQSS89Z6H1pGsHy1qZJpSbUSiOzZeEe…) Looking forward to receiving your feedback. Best Regards, Rafik Dammak, interim chair and Council liaison to the EPDP Team

5 8

ICANN Org response to question re. TSG report
by Marika Konings April 13, 2019

April 13, 2019

Dear EPDP Team, Please find hereby the ICANN Org response to a question raised during the ICANN64 meeting in Kobe: Question: Does ICANN org plan to share the TSG’s report with the EPBD/DPAs? If so, please provide more information on the timeline. Response: Dear EPDP Team, Thank you for your question. As you may know, the Technical Study Group<https://www.icann.org/tsg> has been exploring technical solutions for authenticating, authorizing, and providing access to non-public registration data for third parties with legitimate interests. More information regarding ICANN org’s next steps following the draft technical model<https://www.icann.org/en/system/files/files/draft-technical-model-access-no…> shared during ICANN 64 can be found on Göran’s blog post<https://www.icann.org/news/blog/next-steps-for-the-technical-study-group-ep…> published on 5 April 2019. We’ll also add this question and response to the Q & A page on the wiki. 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…>.

2 1

Fw: [ccwg-internet-governance] CCWG IG BRIEFING ON "ICANN, GDPR AND WHOIS"; WSIS FORUM; GENEVA; 11TH APRIL
by Ayden Férdeline April 13, 2019

April 13, 2019

Dear all, I am sharing the attached staff-prepared summary for information purposes. This is a summary of the session held at WSIS last week where our work was mentioned. Thanks. Best wishes, Ayden Férdeline ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, April 13, 2019 12:31 AM, Nigel Hickson <nigel.hickson(a)icann.org> wrote: > Colleagues > > Good evening. Please find attached a Note of this Session held yesterday. > > Full Agenda of the Forum at https://www.itu.int/net4/wsis/forum/2019/Agenda > > Best > > Nigel

1 0

PLEASE READ: Transitioning to Zoom
by Nathalie Peregrine April 10, 2019

April 10, 2019

Dear all, As you may already know<https://www.icann.org/news/blog/transitioning-icann-s-remote-participation-…>, ICANN is replacing the Adobe Connect tool with Zoom. As with all transitions, there will be a learning curve for community members as well as for staff but through the tools, information and proposed next steps outlined below, we hope we can make this transition is as smooth as possible. The complete roll out is expected to be finalized by ICANN65, Marrakech, however many groups will be noticing their calls scheduled on Zoom as of next week. Please see below a few pointers which we hope will help get everyone ready. How is staff preparing for the transition? Staff has received training, has viewed training videos and has had the opportunity to go through practice runs in Zoom rooms. This should facilitate our assistance in getting you all up to speed and work with the different groups on transitioning existing practices to the zoom environment. What is available to the community to prepare for the transition? Staff is reaching out to Stakeholder Group and Constituency, as well as PDP Working Group, leadership teams to introduce them to Zoom and ensure they will be comfortable running their first sessions with this new tool. Staff will also present Zoom to community members at the beginning of each conference call to ensure all understand the different functions and how to use them. The attached Welcome to Zoom! document will be presented at the same time. SOAC Support staff will be present during each call to assist. What stays the same? (please open the Welcome to Zoom! document for a visual) Zoom rooms still show participant and chat pods. The public chat pods will be archived and circulated as per usual, the private chat content remains inaccessible to ICANN Org staff). Documents can still be viewed in the Zoom room but please note that this sharing is a screen share which means it is no longer possible to scroll through documents unless the person who is sharing their screen does so. It is possible to join the audio via audio bridge (telephone) or via the computer. Zoom VoIP quality is excellent. It will still be possible to get a dial out for those unable to connect to the Zoom room. What changes? (please open the Welcome to Zoom! And the FAQ documents) Participants need to click on the participant list and the chat to activate them. This just takes two seconds. The content of the chat only appears from participant connection time. This means if you joins 4 mins late, you will not be able to access the first 4 mins of the chat. Zoom is notified of this and is looking into resolving the issue. The entire content of the chat transcript will however be available immediately after the end of the call once it gets posted / circulated by the host. Several documents can be viewed at the same time if several staff members are screensharing, this will allow you to navigate (as applicable) to Notes, Agenda and Documents in your own time during the call. Documents will be able to be shared via the chat to allow all to download materials to their computers during the call. The mobile app does not require you to remain in the app in order to hear the zoom room audio. Please open the attached FAQ document for any additional queries you may have. If you have any comments, questions or suggestions, please let us know – our objective is to make sure this transition is as smooth as possible. Kind regards, The GNSO Team Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/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

Update on Day 0 Meeting
by Rafik Dammak April 9, 2019

April 9, 2019

Dear EPDP Team, I am sending this to inform you that decision was made to not have an EPDP meeting in Day 0 prior to ICANN65. We just got an update that only half a day (in the morning) can be accommodated instead of a full day as requested. That did not make it worth the time and effort so instead Council leadership team has committed to find and allocate substantial time during policy forum in close co-ordination with other groups. Best Regards, Rafik Dammak

2 1

FW: Reminder - input on mind map and questions coming out of ICANN64 meeting
by Georgios.TSELENTIS＠ec.europa.eu April 8, 2019

April 8, 2019

Dear EPDP colleagues, Apologies for the lateness of our response. The GAC supports what Alex from the IPC articulated in his email from March 29. We would like to further propose that Work Stream 1 (Standardized Access) be given priority. Also, the GAC suggests that the EPDP immediately identify the scope of Work Stream 1 and develop a work plan for completing work no later than 12 months from the appointment of the new EPDP Chair. It should also be the expectation that considerable and demonstrable progress be made by ICANN 66 in Montreal. Such an approach and timeframe would meet the community feedback from Kobe asking for Phase 2 of the EPDP to move forward quickly given the importance of the issues involved. Further, we felt it worth noting GAC advice from Kobe specific to this effort: WHOIS and Data Protection Legislation a. The GAC advises the Board to: i. Take necessary steps to ensure that the GNSO EPDP on the Temporary Specification for gTLD Registration Data institutes concrete milestones, progress reports and an expeditious timeline, similar to Phase 1, for concluding Phase 2 activities; ii. Take necessary steps to ensure that the scope of phase 2 activities is clearly defined with a view to expeditious conclusion and implementation; iii. Make available the necessary resources for Phase 2 to expeditiously advance on the complex legal issues deferred from Phase 1; iv. Consider instituting additional parallel work efforts on technical implementations, such as that carried out by the Technical Study Group, for purposes of informing and complementing the EPDP’s Phase 2 activities; v. Facilitate swift implementation of the new Registration Directory Services policies as they are developed and agreed, including by sending distinct parts to implementation as and when they are agreed, such as the questions deferred from Phase 1; vi. Consider re-starting implementation processes for relevant existing policies, such as the Privacy Proxy Services Accreditation Issues Policy. RATIONALE The GAC has consistently advised on the necessity of finding a swift solution to ensuring timely access to non-public registration data for legitimate third party purposes that complies with the requirements of the GDPR and other data protection and privacy laws, in view of the significant negative impact of the changes in WHOIS accessibility on users with legitimate purposes. The GAC has previously noted that such legitimate purposes include civil, administrative and criminal law enforcement, cybersecurity, consumer protection and IP rights protection. The GAC also notes that the European Data Protection Board, in its guidance, has expressly encouraged ICANN and the community to develop a comprehensive model covering the entirety of the data processing cycle, from collection to access. As already highlighted in the GAC’s Puerto Rico Communiqué, the GDPR provides for mechanisms to balance the various legitimate public and private interests at stake, including privacy and accountability. We note that the legitimate interests reflected in ICANN’s Bylaws are consistent with the recitals to the GDPR, which provide examples such as “preventing fraud”; “ensuring network and information security,” including the ability to resist “unlawful or malicious actions” and reporting possible “criminal acts or threats to public security” to authorities (see GDPR Recitals 47, 49 and 50). The GAC will closely monitor and assess the progress reports prepared by the GNSO EPDP, and reserves the possibility of providing further guidance if the pace of progress so requires. The GAC notes that the time and resources necessary to complete Phase 2 are considerable and require focused scoping of the activity to ensure the expeditious conclusion of the activity. The GAC would therefore encourage a judicious definition of the scope of the Phase 2 efforts, giving consideration to elements that could be provided by Community efforts in parallel and may not need to be included in the scope, such as accreditation models. The GAC received a briefing on the work of the Technical Study Group. The GAC considers that the development of options for technical implementation demonstrates how a future system for RDS access could be implemented, also with a view to data security and privacy considerations. The Phase 2 considerations could benefit from further exploration of technical implementation options. In addition, engaging in such considerations in parallel can help ensure that policies - once agreed - are swiftly put into practice. Kind regards, Georgios Tselentis [cid:image001.gif@01D40705.22489500] European Commission Directorate-General for Communication Networks, Content and Technology E3: Next-Generation Internet BU31 05/70 B-1049 Brussels/Belgium Office: +32 229 99923 Mobile: +32 498 999923 https://ec.europa.eu/digital-single-market/en/policies/next-generation-inte… ________________________________ From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org<mailto:gnso-epdp-team-bounces@icann.org>> on behalf of Alex Deacon <alex(a)colevalleyconsulting.com<mailto:alex@colevalleyconsulting.com>> Sent: Friday, March 29, 2019 1:39 AM To: Marika Konings Cc: gnso-epdp-team(a)icann.org<mailto:gnso-epdp-team@icann.org> Subject: Re: [Gnso-epdp-team] Reminder - input on mind map and questions coming out of ICANN64 meeting Thanks Marika, Here are the IPCs thoughts on your questions and how to best proceed with the Phase 2 work. Method We believe the Phase 2 work should occur in two separate and concurrent work streams. · Work Stream 1 will focus on issues and questions related to the system for standardized access to non-public registration data, as defined in the EPDP charter and the overlapping EPDP Team Recommendation #3. · Work Stream 2 will focus on completing Phase 1 issues. We also believe that the "legal small team" should continue to meet concurrent with the two work streams described above, with the focus of drafting questions to our legal resource specific to our phase 2 work and analyzing responses received (both existing and TBD). Additional thoughts · Each work stream should set and work forward on its own schedule and work plan. In fact we suggest that a separate report should be generated for each work stream. · Each work stream should schedule its own separate weekly 90min meeting. Access to these meetings is open to all EPDP members (and alternates per the charter). · In a lesson learned from phase 1, consensus calls should happen early and often. Prioritization Legal Small Group Priorities · We suggest the first priority for this team is to answer the controllership and legal basis question for a system for Standardized for Standardized Access to Non-Public Registration Data, assuming a technical framework consistent with the TSG, and in a way that sufficiently addresses issues related to liability and risk mitigation with the goal of decreasing liability risks to Contracted Parties through the adoption of a system for Standardized Access. Work Stream One Priorities · Answer the gating question in Rec #3 - "Whether such a system should be adopted" · Identify the various legitimate purposes for third parties to access registration data · Move on to answering the charter questions on Access (a), (b) and (c) in the order listed. (We note that several of these questions have been answered in Phase 1 and also by the TSG work.) Work Stream Two Priorities · Issues related to Legal vs Natural distinction as identified in Rec #17 · Potential additional purposes to facilitate ICANN's Office of the Chief Technology Officer as identified in Rec #2 · Retention period issues and data collection as identified in Rec #15 · The rest. We note that several issues in this work stream are dependent on legal advice (see below). Dependencies Any large project with parallel work streams is subject to dependencies, however we believe it is important that the EPDP team avoid serializing its work and steer clear of (while still recognizing) potential deadlocks in the process. Specifically, we appreciate the important legal issues related to controllership, risk and liability and agree that these questions must be addressed in a way that results in a win-win situation whereby risks are diminished for contracted parties and authenticated/accredited users have reliable access to requests for non-public registration data. As above, we believe that this important discussion happen in parallel with the work outlined in the work streams. ___________ Alex Deacon Cole Valley Consulting alex(a)colevalleyconsulting.com<mailto:alex@colevalleyconsulting.com> +1.415.488.6009 On Tue, Mar 19, 2019 at 12:50 PM Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>> wrote: Dear EPDP Team, As a reminder, please share any input you may have on the phase 2 mind map (see attached) by Thursday 28 March. In addition, your input is requested on the following questions: · How should the team prioritize going forward? · What next steps should be taken in relations to the dependencies identified? · What should be the next steps in relation to the legal guidance to date? · What is the target date for publication of the Initial Report that the EPDP Team is aiming to work toward? Please share any feedback you may have with the mailing list. 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://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefens…> and visiting the GNSO Newcomer pages<https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefens…>. _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org<mailto:Gnso-epdp-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-team<https://gcc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.…> As of March 18, 2019, all NTIA email addresses will change to username(a)ntia.gov<mailto:username@ntia.gov>

1 0

Re: [Gnso-epdp-team] Reminder - input on mind map and questions coming out of ICANN64 meeting
by Alan Greenberg April 7, 2019

April 7, 2019

I support the path laid out by Alex. I once more register dissatisfaction that the Phase 2 roadmap does not include the issue of geographic differentiation. This was clearly deferred to Phase 2 in Toronto (see the discussion ending on page 34 of the Friday 3rd transcript) and at an extensive discussion on 19 Feb (ending on page 52 of the transcript) saying that there would be a study and further discussion in phase 2. Alan At 29/03/2019 01:39 AM, Alex Deacon wrote: Thanks Marika, Here are the IPCs thoughts on your questions and how to best proceed with the Phase 2 work. Method We believe the Phase 2 work should occur in two separate and concurrent work streams. * Work Stream 1 will focus on issues and questions related to the system for standardized access to non-public registration data, as defined in the EPDP charter and the overlapping EPDP Team Recommendation #3. * Work Stream 2 will focus on completing Phase 1 issues. We also believe that the "legal small team" should continue to meet concurrent with the two work streams described above, with the focus of drafting questions to our legal resource specific to our phase 2 work and analyzing responses received (both existing and TBD). Additional thoughts * Each work stream should set and work forward on its own schedule and work plan. In fact we suggest that a separate report should be generated for each work stream. * Each work stream should schedule its own separate weekly 90min meeting. Access to these meetings is open to all EPDP members (and alternates per the charter). * In a lesson learned from phase 1, consensus calls should happen early and often. Prioritization Legal Small Group Priorities * We suggest the first priority for this team is to answer the controllership and legal basis question for a system for Standardized for Standardized Access to Non-Public Registration Data, assuming a technical framework consistent with the TSG, and in a way that sufficiently addresses issues related to liability and risk mitigation with the goal of decreasing liability risks to Contracted Parties through the adoption of a system for Standardized Access. Work Stream One Priorities * Answer the gating question in Rec #3 - "Whether such a system should be adopted" * Identify the various legitimate purposes for third parties to access registration data * Move on to answering the charter questions on Access (a), (b) and (c) in the order listed. (We note that several of these questions have been answered in Phase 1 and also by the TSG work.) Work Stream Two Priorities * Issues related to Legal vs Natural distinction as identified in Rec #17 * Potential additional purposes to facilitate ICANN's Office of the Chief Technology Officer as identified in Rec #2 * Retention period issues and data collection as identified in Rec #15 * The rest. We note that several issues in this work stream are dependent on legal advice (see below). Dependencies Any large project with parallel work streams is subject to dependencies, however we believe it is important that the EPDP team avoid serializing its work and steer clear of (while still recognizing) potential deadlocks in the process. Specifically, we appreciate the important legal issues related to controllership, risk and liability and agree that these questions must be addressed in a way that results in a win-win situation whereby risks are diminished for contracted parties and authenticated/accredited users have reliable access to requests for non-public registration data. As above, we believe that this important discussion happen in parallel with the work outlined in the work streams. ___________ Alex Deacon Cole Valley Consulting alex(a)colevalleyconsulting.com<mailto:alex@colevalleyconsulting.com> +1.415.488.6009 On Tue, Mar 19, 2019 at 12:50 PM Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org> > wrote: Dear EPDP Team, As a reminder, please share any input you may have on the phase 2 mind map (see attached) by Thursday 28 March. In addition, your input is requested on the following questions: How should the team prioritize going forward? What next steps should be taken in relations to the dependencies identified? What should be the next steps in relation to the legal guidance to date? What is the target date for publication of the Initial Report that the EPDP Team is aiming to work toward? Please share any feedback you may have with the mailing list. Best regards, Caitlin, Berry and Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation ffor 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…>. _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org<mailto:Gnso-epdp-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-team _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-team

3 2

Blog post: Next Steps for the Technical Study Group & EPDP
by Marika Konings April 6, 2019

April 6, 2019

For your information: https://www.icann.org/news/blog/next-steps-for-the-technical-study-group-ep…. 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

NEW LINK--Update Observers--Call for Volunteers: Registration Data Policy Implementation - pre-IRT
by Andrea Glandon April 5, 2019

April 5, 2019

My apologies, Please use this link for observers to join: https://docs.google.com/forms/d/e/1FAIpQLSdqyFFrSFXIpwwpUoYCTqfnekQf9-m9pAB… Thank you! Kind Regards, Andrea Glandon From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Andrea Glandon <andrea.glandon(a)icann.org> Date: Friday, April 5, 2019 at 14:55 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Update Observers--Call for Volunteers: Registration Data Policy Implementation - pre-IRT Dear all, Observers will now be able to sign up in a read only status to the pre-IRT email list. Any community members who would like to join the email list as an observer, should complete this form: https://drive.google.com/open?id=1VBLejg2GvisYuqWjsa34_84nBYaenZMWG2TITxaxa… [drive.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-…> Please let me know if you have any questions. Thank you. Kind Regards, Andrea Glandon From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Andrea Glandon <andrea.glandon(a)icann.org> Date: Friday, March 29, 2019 at 13:27 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Call for Volunteers: Registration Data Policy Implementation - pre-IRT Call for Volunteers: Registration Data Policy Implementation - Informal pre-IRT ICANN org is currently seeking volunteers to participate in an informal Pre-Implementation Review Team, or “pre-IRT.” The pre-IRT will assist the ICANN implementation project team in planning implementation work for the EPDP Team’s policy recommendations. As background, the GNSO Council approved and EPDP Team recommended that the GNSO Council and ICANN Org should informally convene the Implementation Review Team to allow for the necessary planning to take place before ICANN Board consideration of its Final Report, following which the IRT would be formally convened (See EPDP Team Recommendation 28). This pre-IRT will act as a temporary implementation review team, which will assist with the gTLD registration data policy implementation planning until the formal Implementation Review Team is officially convened. All members of the pre-IRT are expected to transition to the IRT. The work of the pre-IRT will consist of the following: * Review the proposed implementation plan as drafted by ICANN org * Assist where questions or clarifications from ICANN org arise * Advise on technical and operational details related to the implementation of EPDP recommendations For this pre-IRT, ICANN org is seeking volunteers who are current or former EPDP Team members and assisted in the Team’s Phase 1 work, and accordingly, possess a deep understanding of the EPDP Team’s policy recommendations and accompanying rationale. All volunteers responding to this call are expected to understand the role and remit of the IRT for the implementation project. The work of the pre-IRT is estimated to last until May 2019 when the IRT is expected to convene to take over the work. The pre-IRT is anticipated to have weekly teleconferences starting in early April 2019 for one hour each. Between the meetings, the pre-IRT will be working using collaborative tools. The expected time commitment for supporting the implementation is about three hours per week. How to apply To participate, please send an email to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. If you wish to join the IRT and not the Pre-IRT, please wait to respond to the Call for IRT, which will come later. Background On 17 May 2018, the ICANN Board of Directors (ICANN Board) adopted the Temporary Specification for generic top-level domain (gTLD) Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> ("Temporary Specification") pursuant to the procedures for the establishment of temporary policies in ICANN's agreements with Registry Operators and Registrars ("Contracts"). The Temporary Specification provides modifications to existing requirements in the Registrar Accreditation and Registry Agreements in order to comply with the European Union's General Data Protection Regulation ("GDPR"). Following adoption of a temporary specification, the procedure for Temporary Policies as outlined in the Registrar Accreditation and Registry Agreements provides the Board "shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws." Additionally, the procedure provides this Consensus Policy development process on the Temporary Specification must be carried out within a one-year period as the Temporary Specification can only remain in force for up to one year; from the effective date of 25 May 2018, i.e., the Temporary Specification will expire on 25 May 2019. On 19 July 2018, the GNSO Council initiated<https://community.icann.org/display/gnsocouncilmeetings/Motions+19+July+2018> an Expedited Policy Development Process (EPDP) and chartered [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> the EPDP on the Temporary Specification for gTLD Registration Data team. Unlike other GNSO PDP efforts, which are open for anyone to join, the GNSO Council chose to limit the membership composition of this EPDP, primarily in recognition of the need to complete the work in a relatively short timeframe and to resource the effort responsibly. GNSO Stakeholder Groups, the Governmental Advisory Committee (GAC), the Country Code Names Supporting Organization (ccNSO), the At-Large Advisory Committee (ALAC), the Root Server System Advisory Committee (RSSAC), and the Security and Stability Advisory Committee (SSAC) were each invited to appoint up to a set number of members and alternates, as outlined in the charter<https://community.icann.org/display/EOTSFGRD/EPDP+Team+Charter?preview=/885…>. In addition, the ICANN Board and ICANN Org were invited to assign a limited number of liaisons to this effort. A call for volunteers to the aforementioned groups was issued in July and the EPDP Team held its first meeting on 1 August 2018<https://community.icann.org/display/EOTSFGRD/2018-08-01+EPDP+Team+call+%231>. On 4 March 2019, the GNSO Council adopted the EPDP Team’s Final Report and submitted it to the Board for their consideration. The Board is currently conducting a public comment that is scheduled to close on 17 April 2019.

1 0

Update Observers--Call for Volunteers: Registration Data Policy Implementation - pre-IRT
by Andrea Glandon April 5, 2019

April 5, 2019

Dear all, Observers will now be able to sign up in a read only status to the pre-IRT email list. Any community members who would like to join the email list as an observer, should complete this form: https://drive.google.com/open?id=1VBLejg2GvisYuqWjsa34_84nBYaenZMWG2TITxaxa… Please let me know if you have any questions. Thank you. Kind Regards, Andrea Glandon From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Andrea Glandon <andrea.glandon(a)icann.org> Date: Friday, March 29, 2019 at 13:27 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Call for Volunteers: Registration Data Policy Implementation - pre-IRT Call for Volunteers: Registration Data Policy Implementation - Informal pre-IRT ICANN org is currently seeking volunteers to participate in an informal Pre-Implementation Review Team, or “pre-IRT.” The pre-IRT will assist the ICANN implementation project team in planning implementation work for the EPDP Team’s policy recommendations. As background, the GNSO Council approved and EPDP Team recommended that the GNSO Council and ICANN Org should informally convene the Implementation Review Team to allow for the necessary planning to take place before ICANN Board consideration of its Final Report, following which the IRT would be formally convened (See EPDP Team Recommendation 28). This pre-IRT will act as a temporary implementation review team, which will assist with the gTLD registration data policy implementation planning until the formal Implementation Review Team is officially convened. All members of the pre-IRT are expected to transition to the IRT. The work of the pre-IRT will consist of the following: * Review the proposed implementation plan as drafted by ICANN org * Assist where questions or clarifications from ICANN org arise * Advise on technical and operational details related to the implementation of EPDP recommendations For this pre-IRT, ICANN org is seeking volunteers who are current or former EPDP Team members and assisted in the Team’s Phase 1 work, and accordingly, possess a deep understanding of the EPDP Team’s policy recommendations and accompanying rationale. All volunteers responding to this call are expected to understand the role and remit of the IRT for the implementation project. The work of the pre-IRT is estimated to last until May 2019 when the IRT is expected to convene to take over the work. The pre-IRT is anticipated to have weekly teleconferences starting in early April 2019 for one hour each. Between the meetings, the pre-IRT will be working using collaborative tools. The expected time commitment for supporting the implementation is about three hours per week. How to apply To participate, please send an email to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. If you wish to join the IRT and not the Pre-IRT, please wait to respond to the Call for IRT, which will come later. Background On 17 May 2018, the ICANN Board of Directors (ICANN Board) adopted the Temporary Specification for generic top-level domain (gTLD) Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> ("Temporary Specification") pursuant to the procedures for the establishment of temporary policies in ICANN's agreements with Registry Operators and Registrars ("Contracts"). The Temporary Specification provides modifications to existing requirements in the Registrar Accreditation and Registry Agreements in order to comply with the European Union's General Data Protection Regulation ("GDPR"). Following adoption of a temporary specification, the procedure for Temporary Policies as outlined in the Registrar Accreditation and Registry Agreements provides the Board "shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws." Additionally, the procedure provides this Consensus Policy development process on the Temporary Specification must be carried out within a one-year period as the Temporary Specification can only remain in force for up to one year; from the effective date of 25 May 2018, i.e., the Temporary Specification will expire on 25 May 2019. On 19 July 2018, the GNSO Council initiated<https://community.icann.org/display/gnsocouncilmeetings/Motions+19+July+2018> an Expedited Policy Development Process (EPDP) and chartered [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> the EPDP on the Temporary Specification for gTLD Registration Data team. Unlike other GNSO PDP efforts, which are open for anyone to join, the GNSO Council chose to limit the membership composition of this EPDP, primarily in recognition of the need to complete the work in a relatively short timeframe and to resource the effort responsibly. GNSO Stakeholder Groups, the Governmental Advisory Committee (GAC), the Country Code Names Supporting Organization (ccNSO), the At-Large Advisory Committee (ALAC), the Root Server System Advisory Committee (RSSAC), and the Security and Stability Advisory Committee (SSAC) were each invited to appoint up to a set number of members and alternates, as outlined in the charter<https://community.icann.org/display/EOTSFGRD/EPDP+Team+Charter?preview=/885…>. In addition, the ICANN Board and ICANN Org were invited to assign a limited number of liaisons to this effort. A call for volunteers to the aforementioned groups was issued in July and the EPDP Team held its first meeting on 1 August 2018<https://community.icann.org/display/EOTSFGRD/2018-08-01+EPDP+Team+call+%231>. On 4 March 2019, the GNSO Council adopted the EPDP Team’s Final Report and submitted it to the Board for their consideration. The Board is currently conducting a public comment that is scheduled to close on 17 April 2019.

1 0