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

High-level notes and action items - ICANN67 EPDP Meeting (2 of 2) - 12 March 2020
by Caitlin Tubergen March 12, 2020

March 12, 2020

Dear EPDP Team: Please find below the high-level notes and action items from today’s EPDP meeting. The next EPDP meeting will be Tuesday, 17 March at 14:00 UTC. Thank you. Best regards, Marika, Berry, and Caitlin -- Purpose 2: Following the EPDP Team’s non-objection to the Board’s proposed update to Purpose 2, EPDP Support Staff to circulate a proposed recommendation for updated Purpose 2 by Friday, 13 March. (complete) EPDP Team to provide feedback via the Google doc by Tuesday, 17 March. The EPDP Team agreed to the draft recommendation text for both the feasibility of unique contacts to have a uniform anonymized email address and city field redaction. Staff Support to include these draft recommendations in the addendum on Priority 2 items, which will be published for public comment. EPDP Support Staff to highlight within the Financial consideration questions document the specific areas where feedback is requested. Each EPDP group to provide additional feedback on the Financial consideration questions by Monday, 16 March; please provide feedback using side-bar comments within the Google Doc. The Small Team for Financial Considerations will meet on Tuesday, 17 March to discuss feedback received. Mark Sv. to review Automation Use Case #8 and update the text based on the today’s discussion by Tuesday, 17 March. Matthew Crossman to draft bullet points, regarding the suggestion to send the automation use cases to outside counsel for further guidance on liability and risk, for the Legal Committee’s review, by Tuesday, 17 March. Support Staff to provide a draft summary of the automation use cases topic based on today’s discussion by Monday, 16 March.

1 0

Input requested - Purpose 2 and Potential OCTO Purpose
by Marika Konings March 12, 2020

March 12, 2020

Dear EPDP Team, Following today’s meeting, please review the following proposed language for inclusion in the addendum to the Initial Report, by the deadline indicated. Similar to finalizing the recommendations for the Initial Report, each group is requested to identify whether there are any ‘cannot live with’ aspects of the text or the recommendations. If there is any ‘cannot live with’ language, please identify the language (and a proposed solution you can live with) by the deadlines indicated below. You may also flag minor edits. Please identify concerns and suggestions using the tables at the bottom of each worksheet. * Purpose 2<https://docs.google.com/document/d/1VwslSx0RKXQjf_eJFvQNQ3V0M_37sELl/edit> by 17 March 2020 * Potential OCTO Purpose<https://docs.google.com/document/d/174PSGgWB-UTTcqIA-NndIVDkP6WR701tzwjDsoz…> – deadline: Monday 16 March Best regards, Caitlin, Berry and Marika

1 0

Meeting Invitation / Observers / GNSO Temp Spec gTLD RD EPDP-P2 call / Tuesday, 17 March 2020
by Terri Agnew March 12, 2020

March 12, 2020

As a result of various requests to facilitate observers to follow the EPDP Phase 2 deliberations in real time, audio cast will be made available for the EPDP plenary meetings. Staff will be monitoring audio cast attendance numbers so that the EPDP leadership can assess its usage. As a reminder, the zoom recording, mp3 recording, chat transcript and transcript of the EPDP plenary meetings will be publicly posted as soon as available on the EPDP wiki page and GNSO master calendar. Dear all, The next meeting of the GNSO Temp Spec gTLD RD EPDP – Phase 2 is scheduled on Tuesday, 17 March 2020 at 14:00 UTC for 2 hours. For other times: https://tinyurl.com/wsufp84 Agenda Wiki: https://community.icann.org/x/oB_JBw The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> Meeting Audio Cast (for observers) To join the event, click on the link: Listen in browser: http://stream.icann.org:8000/stream01 Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> If needed, an option to join via telephone has been added for this meeting. **Join information - Conference Bridge: Toll-free access number (US and Canada): 800 550 6865 and Toll 213 233 3193 Other telephone numbers found here: http://www.adigo.com/icann Enter passcode on telephone: 7349 Kind Regards, Terri

1 0

Board letter on purpose 2
by Rafik Dammak March 11, 2020

March 11, 2020

Hi all, please find attached the letter from board regarding purpose 2. Best, Rafik

1 0

Re: [Gnso-epdp-team] [Ext] Re: Notes and action items - ICANN67 EPDP meeting (1 of 2)
by Caitlin Tubergen March 11, 2020

March 11, 2020

Hi James, Thanks for the question. As Janis explained last week, the entire team is invited to provide comments on financial considerations in the Google Doc. In order to ensure that some team members would review the document within the prescribed timeframe, Leadership requested the members who volunteered for the small team to commit to reviewing the document by the deadline. Following the Team’s initial discussion tomorrow, EPDP Leadership will allow additional time for groups to provide their feedback. Thank you. Best regards, Marika, Berry, and Caitlin From: "James M. Bladel" <jbladel(a)godaddy.com> Date: Wednesday, March 11, 2020 at 8:58 AM To: Caitlin Tubergen <caitlin.tubergen(a)icann.org>, "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Ext] Re: [Gnso-epdp-team] Notes and action items - ICANN67 EPDP meeting (1 of 2) Hi Caitlin & Team – Can you clarify Action Item #4? It looks like a small team is reviewing the financial assumptions by EOD today for discussion tomorrow, but Berry posted a note last Thursday (5 MAR) requesting that the entire group weigh in on these via the Google Doc. Speaking on behalf of Registrars – we have not had sufficient time to discuss the considerations in-depth with our ExCom or SG membership. However, the initial take of our EPDP delegation is that these assumptions (especially w.r.t. number of accredited users and traffic for non-LEA/non-UDRP responses) could be wildly underestimated, and result in dramatically increased costs and burdens to ICANN, CPs, Registrants, etc. Not to mention very long lead times for SSAD requestors to get accredited. So, in short, we’d like to request more time to review and discuss internally. Thx. J. ------------- James Bladel From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Caitlin Tubergen <caitlin.tubergen(a)icann.org> Date: Tuesday, March 10, 2020 at 11:02 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] Notes and action items - ICANN67 EPDP meeting (1 of 2) Notice: This email is from an external sender. Dear EPDP Team, Please find below the high-level notes and action items from today’s ICANN67 EPDP meeting (1 of 2). Thank you. Best regards, Marika, Berry, and Caitlin High-level Notes and Action Items GNSO - EPDP Phase 2 Meeting (1 of 2) 10 March 2020 The EPDP Team agreed on the draft recommendation text for the display of information for affiliated vs. accredited privacy/proxy providers and data retention. Staff Support to include these draft recommendations in the addendum on Priority 2 items, which will be published for public comment. Board liaisons to report back to the EPDP Team with further input re: the revised Purpose 2. For reference, revised purpose 2 (provided by Brian King) reads: “Enabling ICANN, in its role as data controller, to enforce policies related to the “maintenance of and access to accurate and up-to-date information concerning registered names and name servers,” including the Registration Data Policy and *Placeholder Name for Phase 2 Policy (if not also Registration Data Policy)*. (ICANN Bylaws, Annex G-1; ICANN Bylaws, Annex G-2)”. In advance of the next EPDP meeting on Thursday, 12 March, all EPDP Groups to review the draft automation use cases and fill out the may vs. must chart [docs.google.com] Specifically, each group to indicate, using the chart, whether they can live with the specific use case as a MAY automate, MUST automate, and, if applicable, what might be necessary to change convert the use case from MAY to MUST (either now or over a certain period of time – for example, some suggested to make it all MAY now, do a DPIA and then review again in the future). Reminder: EPDP Team to review the draft financial consideration answers [docs.google.com] 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. As a reminder, please complete these past-due action items by COB today, Tuesday March 10: Re: City field redaction [docs.google.com] 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. Re: Potential OCTO Purpose, [docs.google.com] EPDP Team to review ICANN org’s recent response and ICANN Org’s responses from Phase 1 re: the use of nonpublic registration data prior to effective date of GDPR. Following review of the questions and answers from Phase 1, EPDP Team members who believe an additional question/response from ICANN org is still necessary, to provide the draft question and rationale for the EPDP Team’s review by Monday, 9 March.

1 0

Notes and action items - ICANN67 EPDP meeting (1 of 2)
by Caitlin Tubergen March 11, 2020

March 11, 2020

Dear EPDP Team, Please find below the high-level notes and action items from today’s ICANN67 EPDP meeting (1 of 2). Thank you. Best regards, Marika, Berry, and Caitlin High-level Notes and Action Items GNSO - EPDP Phase 2 Meeting (1 of 2) 10 March 2020 The EPDP Team agreed on the draft recommendation text for the display of information for affiliated vs. accredited privacy/proxy providers and data retention. Staff Support to include these draft recommendations in the addendum on Priority 2 items, which will be published for public comment. Board liaisons to report back to the EPDP Team with further input re: the revised Purpose 2. For reference, revised purpose 2 (provided by Brian King) reads: “Enabling ICANN, in its role as data controller, to enforce policies related to the “maintenance of and access to accurate and up-to-date information concerning registered names and name servers,” including the Registration Data Policy and *Placeholder Name for Phase 2 Policy (if not also Registration Data Policy)*. (ICANN Bylaws, Annex G-1; ICANN Bylaws, Annex G-2)”. In advance of the next EPDP meeting on Thursday, 12 March, all EPDP Groups to review the draft automation use cases and fill out the may vs. must chart. Specifically, each group to indicate, using the chart, whether they can live with the specific use case as a MAY automate, MUST automate, and, if applicable, what might be necessary to change convert the use case from MAY to MUST (either now or over a certain period of time – for example, some suggested to make it all MAY now, do a DPIA and then review again in the future). Reminder: 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. As a reminder, please complete these past-due action items by COB today, Tuesday March 10: 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. Re: Potential OCTO Purpose, EPDP Team to review ICANN org’s recent response and ICANN Org’s responses from Phase 1 re: the use of nonpublic registration data prior to effective date of GDPR. Following review of the questions and answers from Phase 1, EPDP Team members who believe an additional question/response from ICANN org is still necessary, to provide the draft question and rationale for the EPDP Team’s review by Monday, 9 March.

2 1

Re: [Gnso-epdp-team] Purpose 2
by Margie Milam March 10, 2020

March 10, 2020

We support Brian’s proposed Purpose 2 below, and note that without it – there are many gaps, including: * Operationalizing and implementing new policies and contract provisions (RDAP, transfers, TM Clearinghouse, etc.) * Conducting research using the contacts * Coordinating cyber-attack responses such as Conficker & other cyber attacks * Publishing Accuracy Reporting System (ARS) reports * Conducting testing of new registrar/registries to ensure that the WHOIS systems work in the manner required by the contract * Implementing & testing escrow deposits with 3rd party escrow providers All the best, Margie, Mark & Steve On behalf of the BC [https://facebook.design/public/images/logo.gif] Margie Milam IP Enforcement & DNS Policy Lead | Facebook Legal NOTICE: This email (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. Unless you are the intended recipient, you may not use, copy, or retransmit the email or its contents. From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of "King, Brian via Gnso-epdp-team" <gnso-epdp-team(a)icann.org> Reply-To: "brian.kingATmarkmonitor.com" <brian.king(a)markmonitor.com> Date: Wednesday, March 4, 2020 at 10:12 AM To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] Purpose 2 Hi all, Following last week’s conversation about some EPDP members’ desire to have a bit more specificity in Purpose 2 (the irony of which is not lost on the IPC 😊), I propose the below: 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) Brian J. King Director of Internet Policy and Industry Affairs T +1 443 761 3726 markmonitor.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.markmonitor.com&d=D…> MarkMonitor Protecting companies and consumers in a digital world

7 12

Proposed agenda for EPDP Team Meeting #47 - Thursday 12 March at 15.45 UTC
by Marika Konings March 10, 2020

March 10, 2020

Dear EPDP Team, Please find below the proposed agenda for the next EPDP Team meeting which is scheduled for Thursday 12 March at 15.45 UTC. As a reminder, please identify concerns and suggestions using the tables at the bottom of each worksheet. · Feasibility of unique contacts to have a uniform anonymized email address<https://docs.google.com/document/d/1meyuNRsq4sMOI6pefJk4jZevaKUsTkVf8_XyW1t…> – deadline: Wednesday 11 March · City field redaction<https://docs.google.com/document/d/1rdtRLaNm5DiWR_EPei4Oi64FaDauIXEQhnF2Lm_…> – deadline: Wednesday 11 March Also, 1. In advance of the next EPDP meeting on Thursday, 12 March, all EPDP Groups to review the draft automation use cases and fill out the may vs. must chart<https://docs.google.com/document/d/1d8ZvAyPS0_SiyGiskjxsgtukDSzNK0aA/edit>. Specifically, each group to indicate, using the chart, whether they can live with the specific use case as a MAY automate, MUST automate, and, if applicable, what might be necessary to change convert the use case from MAY to MUST (either now or over a certain period of time – for example, some suggested to make it all MAY now, do a DPIA and then review again in the future). 2. Reminder: EPDP Team to review the draft financial consideration answers<https://docs.google.com/document/d/1YtLHw4ASPOLwI_77bXGJrGypCHzYePQ5vaIWXzP…>. 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. Best regards, Caitlin, Berry and Marika EPDP Phase 2 - Meeting #47 Proposed Agenda Thursday, 12 March 2020 at 15.45 UTC 1. Roll Call & SOI Updates (5 minutes) 2. Confirmation of agenda (Chair) 3. Welcome and housekeeping issues (Chair) (5 minutes) 4. Feasibility of unique contacts to have a uniform anonymized email address<https://docs.google.com/document/d/1meyuNRsq4sMOI6pefJk4jZevaKUsTkVf8_XyW1t…> (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. City Field Redaction<https://docs.google.com/document/d/1rdtRLaNm5DiWR_EPei4Oi64FaDauIXEQhnF2Lm_…> (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 6. Accuracy and Whois ARS<https://docs.google.com/document/d/1pS9Pibanj-Hp6LztZpeERtxdoLsnp4y_-do0vU5…> (priority 2) (15 minutes) 1. See status of legal committee questions and request for clarification to GNSO Council (see https://mm.icann.org/pipermail/gnso-epdp-team/2020-March/003170.html) 2. Consider GNSO Council feedback, if any 3. Confirm next steps 7. Financial consideration questions<https://docs.google.com/document/d/1YtLHw4ASPOLwI_77bXGJrGypCHzYePQ5vaIWXzP…> (30 minutes) 1. Consider feedback from Becky, Amr, Volker, Franck, Marc A., and Mark Sv. on the draft answers 2. EPDP Team feedback 3. Confirm next steps 8. Automation<https://community.icann.org/x/BhSJBw> Use Cases (if time allows) 1. Continue review of use case candidates for possible automation 2. Review input received from each group on which use cases MAY or MUST be automated 3. Confirm next steps 9. Wrap and confirm next EPDP Team meeting (5 minutes): 1. Tuesday 17 March at 14.00 UTC. Topics to be addressed: Purpose 2 (Consider Board Liaison input), Potential OCTO Purpose, Automation Use Cases. 2. Confirm action items 3. Confirm questions for ICANN Org, if any

1 0

ICANN Remote Meeting in the news
by Mark Svancarek (CELA) March 9, 2020

March 9, 2020

https://www.seattletimes.com/business/can-everyone-mute-coronavirus-means-w…

1 0

Proposed agenda for next EPDP Team meeting Tuesday 10 March at 14.00 UTC
by Marika Konings March 9, 2020

March 9, 2020

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<https://docs.google.com/document/d/1YtLHw4ASPOLwI_77bXGJrGypCHzYePQ5vaIWXzP…>. 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<https://docs.google.com/document/d/1rdtRLaNm5DiWR_EPei4Oi64FaDauIXEQhnF2Lm_…>, 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<https://docs.google.com/document/d/1izpX2C-RrfAdRgRDwBO9tQuJIBA9Xt38p1MTJgQ…> – deadline: Monday 9 March Data retention<https://docs.google.com/document/d/1xlw1N7omlgPKjag_FnOy03NRvByol8IaJma5zNP…> – 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<https://docs.google.com/document/d/1izpX2C-RrfAdRgRDwBO9tQuJIBA9Xt38p1MTJgQ…> (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<https://docs.google.com/document/d/1xlw1N7omlgPKjag_FnOy03NRvByol8IaJma5zNP…> (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 6. Automation<https://community.icann.org/x/BhSJBw> Use Cases (45 minutes) 1. Continue review of use case candidates for possible automation 2. Confirm next steps – following meeting, each group to identify: * 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, * 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 * 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-03ma… * 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

1 0