Dear EPDP Team, Please find below the proposed agenda for the next EPDP Team meeting which has been scheduled for Tuesday 31 August at 14.00 UTC. As a reminder, please provide your groups input on the four asks by today, Monday, at 17.00 UTC (see https://docs.google.com/document/d/1knSKHXt0njWqXMmpiDKA76amycenNBUl/edit). Also note the slightly revised timeline under agenda item #3 to reflect where the group is at, with minority statements now due on 2 September (or 10 September if it is to be included in the updated version that will be submitted to the GNSO Council . Best regards, Caitlin, Berry and Marika EPDP Phase 2A - Meeting #40 Proposed Agenda Tuesday 31 August 2021 at 14.00 UTC 1. Roll Call & SOI Updates (5 minutes) 2. Welcome & Chair updates (Chair) (5 minutes) 3. Consider and resolve remaining four “cannot live with” items for section 3 of Final Report - Responses to Council Questions & Recommendations (75 minutes) – see https://docs.google.com/document/d/1knSKHXt0njWqXMmpiDKA76amycenNBUl/edit As a reminder: updated timeline to get to Final Report 31 August – finalize outstanding issues Final Report. Following EPDP Team meeting, circulation of consensus designations & chair statement (by Keith) 1 September – deadline for flagging minor edits and objections to consensus designations 2 September – placeholder for EPDP Team meeting to allow for resolution of any remaining issues and/or objections to consensus designations 2 September – deadline for submission of minority statements 3 September – submission of Final Report to GNSO Council 10 September – final deadline for minority statements (any minority statements submitted after 2 September will be added to the Final Report, with the updated version to be submitted to the Council in time for the September meeting document deadline) * Review ask #1: Ask #1: EPDP Team to consider if this section (lines 100-104), as well as footnote 5, 20 and 21, can be removed if the Chair statement on consensus designations makes clear that there was significant disagreement within the group on a number of these issues and that readers are encouraged to review the minority statements to better understand the different views and perspectives. * Consider EPDP Team input provided * Confirm next steps * Review ask #2: Do the updates and the reorganization of recommendation #1 address the cannot live with items flagged? If not, how can these be addressed, factoring in the discussions to date. * Consider EPDP Team input provided * Confirm next steps * Review ask #3: Considering the org input (“because this recommendation is for guidance only (and thus not subject to compliance enforcement), the use of should vs may wouldn’t be expected to have a significant impact from the org perspective"), can the group live with leaving this as “SHOULD” (lines 261-265). If not, please provide alternative suggestions that take into account the EPDP Team’s discussion. * Consider EPDP Team input provided * Confirm next steps * Review ask #4: please consider the updates proposed by the RrSG (lines 322-329 - “any future work within ICANN by the ….”) & RySG team (“any future work by ICANN by the relevant controllers and processors in relation…”. Also, please provide further input on what these changes would mean or imply as work on a Code of Conduct was not part of phase 1 or phase 2 recommendations. Also consider additional language suggested by IPC (late submission): “For the avoidance of doubt, RDS data requestors are relevant controllers and processors and must be included in any such future work.” * Consider EPDP Team input provided * Confirm next steps * Agree on next steps 4. Wrap and confirm next EPDP Team meeting (5 minutes): a. EPDP Team Meeting #41 Thursday 2 September at 14.00 UTC (placeholder, if necessary) b. Confirm action items c. Confirm questions for ICANN Org, if any