March 2019 - Gnso-epdp-team

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

EPDP Team mailing list page has incomplete list of subscribers
by Ayden Férdeline April 4, 2019

April 4, 2019

Hi all, I believe the [EPDP mailing list page](https://community.icann.org/pages/viewpage.action?pageId=88574688), which includes the names of observers, is incomplete. I note this because a recent email I sent to our list received a response directly from someone whose name is not listed on this webpage. I am unable to view the subscribers list, because unusually, [this functionality has been disabled](https://mm.icann.org/mailman/listinfo/gnso-epdp-team) in Mailman. We work in the open and our mailing list discussions should, of course, be accessible to everyone. But we should also be clear about whose inboxes are correspondence will be reaching. I'd like to request that we please update the EPDP mailing list page to include the names of all observers. Many thanks, Ayden Férdeline

5 10

Re: [Gnso-epdp-team] [Ext] Re: Bridging Mechanism Proposal
by Trang Nguyen March 30, 2019

March 30, 2019

Hi James, Thank you for your response. Typically, advisories explain ICANN org’s interpretation of obligations under ICANN Consensus Policies and/or contracts rather than create new obligations. Therefore, ICANN org believes that we must create a new Policy document to implement the EPDP Team’s recommendation 28 regarding the transition period. Regards, Dan and Trang ICANN Org Liaisons From: "James M. Bladel" <jbladel(a)godaddy.com> Date: Thursday, March 28, 2019 at 4:54 PM To: Trang Nguyen <trang.nguyen(a)icann.org>, Rafik Dammak <rafik.dammak(a)gmail.com>, Alan Woods <alan(a)donuts.email> Cc: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Ext] Re: [Gnso-epdp-team] Bridging Mechanism Proposal Thank you, Trang. With regard to your last paragraph, what other documents would ICANN consider ‘enforceable’? Could it issue an Advisory in conjunction with the new Consensus Policy? Just trying to keep things lightweight here. Thanks- J. ------------- James Bladel GoDaddy ________________________________ From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Trang Nguyen <trang.nguyen(a)icann.org> Sent: Thursday, March 28, 2019 18:11 To: Rafik Dammak; Alan Woods Cc: gnso-epdp-team(a)icann.org Subject: Re: [Gnso-epdp-team] Bridging Mechanism Proposal Dear Colleagues, Thanks for the clarification. Based on the clarification, ICANN org understands that the EPDP Team’s Recommendation 28 has three stages: Stage 1: As of 20 May 2019, contracted parties must continue to implement measures consistent with the Temp Spec until the development of the Consensus Policy based on recommendations by the EPDP Team is completed. Stage 2: Once the Consensus Policy document is completed, contracted parties must either continue to implement the Temp Spec or the new Consensus Policy. Stage 3: As of the Consensus Policy’s effective date (which the EPDP Team recommended to be 29 February 2020), contracted parties must comply with the new Consensus Policy. Based on this understanding, ICANN org foresees the implementation of Recommendation 28 taking the form of a Policy document that would reflect the above requirements. This form of implementation would allow for an enforceable mechanism to be in place until the new Consensus Policy goes into effect. Regards, Dan and Trang ICANN Org Liaisons From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Rafik Dammak <rafik.dammak(a)gmail.com> Date: Monday, March 18, 2019 at 5:51 PM To: Alan Woods <alan(a)donuts.email> Cc: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: Re: [Gnso-epdp-team] Bridging Mechanism Proposal Hi, The deadline we agreed on during our meeting (end of the week) already passed and there was no objection. Best, Rafik Le mer. 13 mars 2019 à 11:46, Alan Woods <alan(a)donuts.email> a écrit : Thanks Alan, taking into account your note, here is another suggested update.... maybe we can get this sorted by day's end (hope springs eternal). [Note: the removal of "Compliance" is to allow ICANN to figure out from whom they would like such an advisory to emanate from.] Suggested update: The effective date of the gTLD Registration Data Policy shall be [February 29, 2020]. All gTLD Registry Operators and ICANN-accredited registrars will be required to comply with the gTLD Registration Data Policy as of that date. Until such date [February 29, 2020], ICANN [Compliance] directs Contracted Parties that registries and registrars are required EITHER to comply with the[policy resulting from] the recommendations contained in the Final Report OR continue to implement measures consistent with the Temporary Specification (as adopted by the ICANN Board on 17 May 2018, and expired on 25 May 2019). Registries and registrars who continue to implement measures compliant with the expired Temporary Specification will not be subject to Compliance penalty specifically related to those measures until February 29, 2020. Failure to respond within 30 days of this notice shall be considered acceptance of the terms herein will be considered acceptance. Kind regards, Alan Please NOTE: This electronic message, including any attachments, may include privileged, confidential and/or inside information owned by Donuts Inc. . Any distribution or use of this communication by anyone other than the intended recipient(s) is strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by replying to this message and then delete it from your system. Thank you. On Wed, Mar 13, 2019 at 11:21 AM Alan Greenberg <alan.greenberg(a)mcgill.ca<mailto:alan.greenberg@mcgill.ca>> wrote: I think that the intent of this is exactly right, and keeping it lightweight is important. The problematic part of the wording is that it implies that contracted parties can interpret the Recs on their own prior to ICANN publishing the new Consensus Policy (CP) (presumably 6 months prior to 29 Feb 2020). For the period from xx May 2019 until the CP is published, the Temp Spec is the rule (properly phrased). After the CP is published, the new CP may apply and must apply no later than 29 Feb. Alan At 12/03/2019 12:42 AM, Elizabeth Bacon wrote: Hello Team, In Sunday?s session, ICANN noted that they feel they need a temporary policy to bridge between the expiration of the Temporary Specification and the completion of the EPDP Consensus Policy. There was some consensus in the room that the Team had anticipated this and provided that mechanism via Recommendation 28. In addition, the idea of what a ?temporary policy? might be raised several questions and concerns. In an effort to not recreate the wheel or implement an overly heavy solution, we proposed to Dennis that a formal notice/advisory from ICANN Compliance to Contracted Parties to operationalize the language we previously agreed for Recommendation 28 would be sufficient and appropriate. The language is below for your review. I look forward to your thoughts before I share with Dennis. Thanks, Beth The effective date of the gTLD Registration Data Policy shall be [February 29, 2020]. All gTLD Registry Operators and ICANN-accredited registrars will be required to comply with the gTLD Registration Data Policy as of that date. Until such date [February 29, 2020], ICANN Compliance directs Contracted Parties that registries and registrars are required EITHER to comply with the recommendations contained in the Final Report OR continue to implement measures consistent with the Temporary Specification (as adopted by the ICANN Board on 17 May 2018, and expired on 25 May 2019). Registries and registrars who continue to implement measures compliant with the expired Temporary Specification will not be subject to Compliance penalty specifically related to those measures until February 29, 2020. Failure to respond within 30 days of this notice shall be considered acceptance of the terms herein will be considered acceptance. Elizabeth Bacon Senior Director, Policy and Privacy Public Interest Registry Direct: +1 703-956-3962 | Mobile: +1 571-352-5029| Find us on www.pir.org [pir.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.pir.org_&d=DwMFaQ&c…> | Facebook [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_pir.or…> | Twitter [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_PIRegistry&…> | Instagram [instagram.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__instagram.com_piregistr…> | Celebrating 15 years of operating the .org domain _______________________________________________ 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<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<mailto:Gnso-epdp-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-team

1 0

Call for Volunteers: Registration Data Policy Implementation - pre-IRT
by Andrea Glandon March 29, 2019

March 29, 2019

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<https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#temp…> ("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<https://gnso.icann.org/sites/default/files/file/field-file-attach/temp-spec…> 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

Reminder - input on mind map and questions coming out of ICANN64 meeting
by Marika Konings March 29, 2019

March 29, 2019

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://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…>.

6 5

Re: [Gnso-epdp-team] Bridging Mechanism Proposal
by Alan Greenberg March 28, 2019

March 28, 2019

I think that the intent of this is exactly right, and keeping it lightweight is important. The problematic part of the wording is that it implies that contracted parties can interpret the Recs on their own prior to ICANN publishing the new Consensus Policy (CP) (presumably 6 months prior to 29 Feb 2020). For the period from xx May 2019 until the CP is published, the Temp Spec is the rule (properly phrased). After the CP is published, the new CP may apply and must apply no later than 29 Feb. Alan At 12/03/2019 12:42 AM, Elizabeth Bacon wrote: Hello Team, In Sunday?s session, ICANN noted that they feel they need a temporary policy to bridge between the expiration of the Temporary Specification and the completion of the EPDP Consensus Policy. There was some consensus in the room that the Team had anticipated this and provided that mechanism via Recommendation 28. In addition, the idea of what a ?temporary policy? might be raised several questions and concerns. In an effort to not recreate the wheel or implement an overly heavy solution, we proposed to Dennis that a formal notice/advisory from ICANN Compliance to Contracted Parties to operationalize the language we previously agreed for Recommendation 28 would be sufficient and appropriate. The language is below for your review. I look forward to your thoughts before I share with Dennis. Thanks, Beth The effective date of the gTLD Registration Data Policy shall be [February 29, 2020]. All gTLD Registry Operators and ICANN-accredited registrars will be required to comply with the gTLD Registration Data Policy as of that date. Until such date [February 29, 2020], ICANN Compliance directs Contracted Parties that registries and registrars are required EITHER to comply with the recommendations contained in the Final Report OR continue to implement measures consistent with the Temporary Specification (as adopted by the ICANN Board on 17 May 2018, and expired on 25 May 2019). Registries and registrars who continue to implement measures compliant with the expired Temporary Specification will not be subject to Compliance penalty specifically related to those measures until February 29, 2020. Failure to respond within 30 days of this notice shall be considered acceptance of the terms herein will be considered acceptance. Elizabeth Bacon Senior Director, Policy and Privacy Public Interest Registry Direct: +1 703-956-3962 | Mobile: +1 571-352-5029| Find us on www.pir.org<http://www.pir.org/> | Facebook<http://www.facebook.com/pir.org> | Twitter<http://twitter.com/PIRegistry> | Instagram<http://instagram.com/piregistry> | Celebrating 15 years of operating the .org domain _______________________________________________ Gnso-epdp-team mailing list Gnso-epdp-team(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-team

5 4

FW: [Ext] Re: Reminder - input on mind map and questions coming out of ICANN64 meeting
by Marika Konings March 28, 2019

March 28, 2019

Forwarding on behalf of the Registrar Team. From: Sarah Wyld <swyld(a)tucows.com> Date: Thursday, March 28, 2019 at 19:22 To: Marika Konings <marika.konings(a)icann.org> Cc: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Ext] Re: [Gnso-epdp-team] Reminder - input on mind map and questions coming out of ICANN64 meeting Hello all, the RrSG response to the Mind Map is attached, thank you. -- Sarah Wyld Tucows +1.416 535 0123 Ext. 1392 On 2019-03-19 15:49, Marika Konings 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://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

1 0

REMINDER Re: Reminder - input on mind map and questions coming out of ICANN64 meeting
by Marika Konings March 28, 2019

March 28, 2019

Reminder! From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Tuesday, March 19, 2019 at 20:50 To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] Reminder - input on mind map and questions coming out of ICANN64 meeting 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://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

Diane Plaut - EPDP Team position
by Plaut, Diane March 28, 2019

March 28, 2019

Dear EPDP Team Members- I wanted to let you know that I will not be acting as the EPDP IPC Rep going forward to Phase 2. During the Kobe Meeting I handed in my resignation for this post formally to the IPC and I shared this with certain team members and have now formally shared this with Staff. I am pleased to say that based on the encouragement of many of you, I will be part of the IRT for the EPDP and will look forward to seeing our work through in this capacity and using my legal background and passion around the important issues of our work through the implementation process. I want to thank everyone for the wonderful friendships formed and, the environment of mutual respect, hard work and dedication. I look forward to working with everyone going forward as friends and colleagues on this work stream, through other ICANN work streams and in other avenues in the future. Best, Diane Diane Plaut General Counsel and Privacy Officer [cid:image001.png@01D3CA70.18FC1D40] Direct +1 646-899-2806  diane.plaut(a)corsearch.com<mailto:diane.plaut@corsearch.com> 220 West 42nd Street, 11th Floor, New York, NY 10036, United States www.corsearch.com<http://www.corsearch.com/> Join Corsearch on Twitter<https://twitter.com/corsearch> Linkedin<https://www.linkedin.com/company/2593860/> Trademarks + Brands<http://trademarksandbrands.corsearch.com/> Customer Service/Platform Support: 1 800 SEARCH1™ (1 800 732 7241) Corsearch.USCustomerService(a)corsearch.com<mailto:Corsearch.USCustomerService@corsearch.com> Confidentiality Notice: This email and its attachments (if any) contain confidential information of the sender. The information is intended only for the use by the direct addressees of the original sender of this email. If you are not an intended recipient of the original sender (or responsible for delivering the message to such person), you are hereby notified that any review, disclosure, copying, distribution or the taking of any action in reliance of the contents of and attachments to this email is strictly prohibited. If you have received this email in error, please immediately notify the sender at the address shown herein and permanently delete any copies of this email (digital or paper) in your possession.

3 2

FYI - blog post: Technical Study Group Engages with Community in Kobe
by Marika Konings March 27, 2019

March 27, 2019

FYI: https://www.icann.org/news/blog/technical-study-group-engages-with-communit… 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