Proposed agenda - EPDP Team meeting #44 - Thursday, 27 February
Dear EPDP Team: Please find below the proposed agenda for EPDP Team Meeting #44. Thank you. Best regards, Marika, Berry, and Caitlin -- EPDP Phase 2 - Meeting #44 Proposed Agenda Thursday, 27 February 2020 at 14.00 UTC 1. Roll Call & SOI Updates (5 minutes) 2. Confirmation of agenda (Chair) 3. Welcome and housekeeping issues (Chair) (5 minutes) Meeting with Belgian DPA – feedback from Janis ICANN67 Virtual Meeting – current state of planning / discussions 4. Timeline review and priority 2 worksheet compilation (10 minutes) a) Consider any input provided by EPDP Team by Tuesday 25 February b) Confirm next steps 5. Data retention (priority 2) (30 minutes) EPDP Team to review ICANN Org feedback (see https://mm.icann.org/pipermail/gnso-epdp-team/2019-November/002747.html and https://mm.icann.org/pipermail/gnso-epdp-team/attachments/20191102/e8cd309e/... Consider Support Staff proposed recommendation: EPDP Team to consider whether updates are needed to phase 1 data retention recommendation (EPDP Team meeting - 27 Feb 2020). At a minimum, the EPDP Team would need to reconfirm its original recommendation, which was adopted on an interim basis, that registration data must be retained for a period of fifteen months following the life of the registration plus three months to implement the deletion, i.e., 18 months. Confirm next steps 6. Feasibility of unique contacts (priority 2) (30 minutes) EPDP Team to review Legal Committee proposal Confirm next steps 7. Purpose 2, Phase 1 (30 minutes) As a reminder, the EPDP Team recommended in phase 1 the following purpose ICANN Purpose for processing gTLD Registration Data: “Contributing to the maintenance of the security, stability, and resiliency of the Domain Name System in accordance with ICANN’s mission through enabling responses to lawful data disclosure requests”. “ICANN Purpose” is used to describe purposes for processing personal data that should be governed by ICANN Org via a Consensus Policy. The ICANN Board did not adopt this purpose noting that: “The Board does not adopt this Recommendation at this time in light of the EPDP Team’s characterization of this as a placeholder and the need to consider recent input from the European Commission. Based on the views presented in the recent letters from the European Commission, Purpose 2, as stated in the EPDP Team’s Final Report, may require further refinement to ensure that it is consistent with and facilitates ICANN’s ability to deliver a predictable and consistent user experience compliant with applicable law. The Board’s concern is that if the wording of purpose 2 is deemed inconsistent with applicable law, the impact might be elimination of an ICANN purpose. There are clear ICANN purposes that ICANN should be able to employ under existing legal frameworks to deploy a unified method to enable those with a legitimate and proportionate interest to access non-public gTLD registration data, although such purposes may need to be restated or further refined based on additional legal, regulatory or other input. The Board directs ICANN org to continue to evaluate this proposed purpose and to request additional guidance from the DPAs, regarding the legitimate and proportionate access to registrant data and ICANN’s SSR mission”. To review the European Commission letter on this topic, see https://www.icann.org/en/system/files/correspondence/odonohue-to-marby-03may... In a recent motion concerning the non-adoption of purpose 2, the GNSO Council noted that: “The GNSO Council has concluded that concerning Recommendation 1, Purpose 2, this is firmly within the scope of the EPDP Team to address as part of its phase 2 deliberations as the original language was already flagged as a placeholder pending further consideration during phase 2.” Brian King has proposed that the EPDP Team consider recommending the following ICANN purpose: “Contributing to the maintenance of the security, stability, and resiliency of the Domain Name System in accordance with ICANN’s mission”. Brian to introduce proposal EPDP Team feedback Confirm next steps 8. Wrap and confirm next EPDP Team meeting (5 minutes): Thursday 5 March 2020 at 14.00 UTC (topics: City field redaction and Automation Use Cases – small team recommendations) Confirm action items Confirm questions for ICANN Org, if any
Dear EPDP Team, For agenda item 3b and 4, please find attached an updated version of the timetable document. Highlighted in yellow are those meetings that have been added or modified as a result of ICANN67 moving to a virtual meeting. Best regards, Caitlin, Berry and Marika From: Gnso-epdp-team <gnso-epdp-team-bounces@icann.org> on behalf of Caitlin Tubergen <caitlin.tubergen@icann.org> Date: Monday, February 24, 2020 at 09:34 To: "gnso-epdp-team@icann.org" <gnso-epdp-team@icann.org> Subject: [Gnso-epdp-team] Proposed agenda - EPDP Team meeting #44 - Thursday, 27 February Dear EPDP Team: Please find below the proposed agenda for EPDP Team Meeting #44. Thank you. Best regards, Marika, Berry, and Caitlin -- EPDP Phase 2 - Meeting #44 Proposed Agenda Thursday, 27 February 2020 at 14.00 UTC 1. Roll Call & SOI Updates (5 minutes) 2. Confirmation of agenda (Chair) 3. Welcome and housekeeping issues (Chair) (5 minutes) 1. Meeting with Belgian DPA – feedback from Janis 2. ICANN67 Virtual Meeting – current state of planning / discussions 4. Timeline review<https://mm.icann.org/pipermail/gnso-epdp-team/2020-February/003076.html> and priority 2 worksheet compilation<https://community.icann.org/download/attachments/126422841/Next%20steps%20-%20priority%202%20worksheets%20-%20updated%2010Feb2020.pdf?version=1&modificationDate=1582042762000&api=v2> (10 minutes) a) Consider any input provided by EPDP Team by Tuesday 25 February b) Confirm next steps 5. Data retention<https://docs.google.com/document/d/1xlw1N7omlgPKjag_FnOy03NRvByol8IaJma5zNPkWaY/edit> (priority 2) (30 minutes) 1. EPDP Team to review ICANN Org feedback (see https://mm.icann.org/pipermail/gnso-epdp-team/2019-November/002747.html and https://mm.icann.org/pipermail/gnso-epdp-team/attachments/20191102/e8cd309e/... 2. Consider Support Staff proposed recommendation: * EPDP Team to consider whether updates are needed to phase 1 data retention recommendation (EPDP Team meeting - 27 Feb 2020). * At a minimum, the EPDP Team would need to reconfirm its original recommendation, which was adopted on an interim basis, that registration data must be retained for a period of fifteen months following the life of the registration plus three months to implement the deletion, i.e., 18 months. 1. Confirm next steps 6. Feasibility of unique contacts<https://docs.google.com/document/d/1meyuNRsq4sMOI6pefJk4jZevaKUsTkVf8_XyW1tRaiA/edit> (priority 2) (30 minutes) 1. EPDP Team to review Legal Committee proposal 2. Confirm next steps 7. Purpose 2, Phase 1 (30 minutes) * As a reminder, the EPDP Team recommended in phase 1 the following purpose ICANN Purpose for processing gTLD Registration Data: “Contributing to the maintenance of the security, stability, and resiliency of the Domain Name System in accordance with ICANN’s mission through enabling responses to lawful data disclosure requests”. * “ICANN Purpose” is used to describe purposes for processing personal data that should be governed by ICANN Org via a Consensus Policy. * The ICANN Board did not adopt this purpose noting that: “The Board does not adopt this Recommendation at this time in light of the EPDP Team’s characterization of this as a placeholder and the need to consider recent input from the European Commission. Based on the views presented in the recent letters from the European Commission, Purpose 2, as stated in the EPDP Team’s Final Report, may require further refinement to ensure that it is consistent with and facilitates ICANN’s ability to deliver a predictable and consistent user experience compliant with applicable law. The Board’s concern is that if the wording of purpose 2 is deemed inconsistent with applicable law, the impact might be elimination of an ICANN purpose. There are clear ICANN purposes that ICANN should be able to employ under existing legal frameworks to deploy a unified method to enable those with a legitimate and proportionate interest to access non-public gTLD registration data, although such purposes may need to be restated or further refined based on additional legal, regulatory or other input. The Board directs ICANN org to continue to evaluate this proposed purpose and to request additional guidance from the DPAs, regarding the legitimate and proportionate access to registrant data and ICANN’s SSR mission”. * To review the European Commission letter on this topic, see https://www.icann.org/en/system/files/correspondence/odonohue-to-marby-03may... * In a recent motion concerning the non-adoption of purpose 2, the GNSO Council noted that: “The GNSO Council has concluded that concerning Recommendation 1, Purpose 2, this is firmly within the scope of the EPDP Team to address as part of its phase 2 deliberations as the original language was already flagged as a placeholder pending further consideration during phase 2.” * Brian King has proposed<https://mm.icann.org/pipermail/gnso-epdp-team/2020-February/003118.html> that the EPDP Team consider recommending the following ICANN purpose: “Contributing to the maintenance of the security, stability, and resiliency of the Domain Name System in accordance with ICANN’s mission”. 1. Brian to introduce proposal 2. EPDP Team feedback 3. Confirm next steps 8. Wrap and confirm next EPDP Team meeting (5 minutes): 1. Thursday 5 March 2020 at 14.00 UTC (topics: City field redaction and Automation Use Cases – small team recommendations) 2. Confirm action items 3. Confirm questions for ICANN Org, if any
participants (2)
-
Caitlin Tubergen -
Marika Konings