Dear EPDP Team,

Please find below the proposed agenda for the next meeting which is scheduled for Tuesday 10 March at 14.00 UTC. Please take note of the outstanding action items:

1. EPDP Team to review the draft financial consideration answers. Becky, Amr, Volker, Franck, Marc A., and Mark Sv. to provide feedback on the draft answers by Wednesday, 11 March for the plenary Team’s review.
2. Re: City field redaction, Margie to propose, on-list, an automated use case for the disclosure of city field to share with the EPDP Team by Monday, 9 March.
3. Please identify concerns and suggestions using the tables at the bottom of each worksheet: 

Display of information of affiliated vs. accredited proxy / privacy providers – deadline: Monday 9 March

Data retention – deadline: Monday 9 March

Best regards,

Caitlin, Berry and Marika

EPDP Phase 2 - Meeting #46

Proposed Agenda

Tuesday, 10 March 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)

4. Display of information of affiliated vs. accredited proxy / privacy providers (priority 2) (15 minutes)

1. Review ‘cannot live with’ comments received, if any
2. Review minor edits received, if any
3. Confirm language for inclusion in the addendum to the Initial Report

5. Data Retention (priority 2) (15 minutes)

4. Review ‘cannot live with’ comments received, if any
5. Review minor edits received, if any
6. Confirm language for inclusion in the addendum to the Initial Report

6. Automation Use Cases (45 minutes)

1. Continue review of use case candidates for possible automation
2. Confirm next steps – following meeting, each group to identify:
   1. which of the use cases your group would be willing to support for inclusion on the list of types of requests that must be fully automated from day 1 as is,
   2. For those that your group did not indicate under i), please provide what changes / safeguards would need to be added to obtain your group's support
   3. Would your group’s responses change if under i) it would say 'MAY' be fully automated instead of 'MUST' be.

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-03may19-en.pdf
• 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 circulated an updated proposal to the EPDP Team mailing list on 4 March 2020: “Contributing to the maintenance of the security, stability, and resiliency of the Domain Name System in accordance with ICANN’s mission, specifically “maintenance of and access to accurate and up-to-date information concerning registered names and name servers.” (ICANN Bylaws, Annex G-1; ICANN Bylaws, Annex G-2)
• A number of EPDP Team members responded to this proposal on the mailing list.

1. EPDP Team to consider updated proposal and input received to date
2. Confirm next steps

8. Wrap and confirm next EPDP Team meeting (5 minutes):

1. Thursday 12 March 2020 Virtual ICANN67 Cancun EPDP Team meeting (10:45 – 12:45 local time (16:45 – 18:45 UTC) - https://67.schedule.icann.org/meetings/1152551. Topics to be addressed: Second / final reading: Feasibility of unique contacts to have a uniform anonymized email address (second/final reading), City field redaction (second/final reading), Accuracy and Whois ARS (first reading) and financial consideration answers.
2. Confirm action items
3. Confirm questions for ICANN Org, if any