Resending on list Agree with Brian on all counts: 1. Thanks for the efforts, it helps 2. Concern remains with the original wording, despite the mitigation 3. I don’t think I am anyone’s first choice as a presenter, but given the shortage I am willing to step up. I am most interested in the Natural/Legal topic /marksv From: Gnso-epdp-team <gnso-epdp-team-bounces@icann.org<mailto:gnso-epdp-team-bounces@icann.org>> On Behalf Of King, Brian via Gnso-epdp-team Sent: Monday, June 14, 2021 7:32 AM To: Drazek, Keith <kdrazek@verisign.com<mailto:kdrazek@verisign.com>>; gnso-epdp-team@icann.org<mailto:gnso-epdp-team@icann.org> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org> Subject: [EXTERNAL] Re: [Gnso-epdp-team] EPDP 2A - Initial Report Status and ICANN 71 Session Coordination Hello Keith, Thank you and thanks to staff for taking these concerns on board. I am truly grateful for your understanding and your efforts to address this. At the risk of sounding ungrateful – though I assure you I truly am grateful – the issue remains with the wording of the Preliminary Recommendation 1 as worded. That said, if you still need volunteers for Wednesday’s session, I would raise my hand to provide an unbiased view in a report to the community on our work. If you think we need to limit this to one speaker per group, I defer to Jan. Thank you for your consideration. Brian King He/Him/His Head of Policy and Advocacy ​ T +1 443 761 3726 Time zone: US Eastern clarivate.com<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.clarivate.com%2F&data=04%7C01%7Cmarksv%40microsoft.com%7Cd46226d73a1e4fec43b808d92f412b2b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637592779222067905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mObgurdyV4zdo2uazEwcDjOzfwlCJydXALix4g45%2Frs%3D&reserved=0> | Accelerating innovation Follow us on LinkedIn<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fclarivate&data=04%7C01%7Cmarksv%40microsoft.com%7Cd46226d73a1e4fec43b808d92f412b2b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637592779222077853%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=dVi0C22EbxStYO%2F7WWafENEMbsfyLcL7LksiGp2fpVw%3D&reserved=0>, Twitter<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Fclarivate%3Fref_src%3Dtwsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor&data=04%7C01%7Cmarksv%40microsoft.com%7Cd46226d73a1e4fec43b808d92f412b2b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637592779222077853%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=neqzWWpWIqiYUcBsfJd%2FSibTrqQamZOPVpKumA4d3II%3D&reserved=0>, Facebook<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2Fclarivate%2F&data=04%7C01%7Cmarksv%40microsoft.com%7Cd46226d73a1e4fec43b808d92f412b2b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637592779222077853%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=abhgCdGk4cPEXDV96Zbvw5gDU5qs7II%2FoOdhvKh%2BM6w%3D&reserved=0> and Instagram<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.instagram.com%2Fclarivateofficial%2F%3Fhl%3Den&data=04%7C01%7Cmarksv%40microsoft.com%7Cd46226d73a1e4fec43b808d92f412b2b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637592779222087811%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=IUhRRfxKILEQtqcs3ogr5eGRyS17RAVC6vfSQS5Rkno%3D&reserved=0> From: Gnso-epdp-team <gnso-epdp-team-bounces@icann.org<mailto:gnso-epdp-team-bounces@icann.org>> On Behalf Of Drazek, Keith via Gnso-epdp-team Sent: Saturday, June 12, 2021 8:49 PM To: gnso-epdp-team@icann.org<mailto:gnso-epdp-team@icann.org> Cc: gnso-secs@icann.org<mailto:gnso-secs@icann.org> Subject: [Gnso-epdp-team] EPDP 2A - Initial Report Status and ICANN 71 Session Coordination Dear EPDP Team, As agreed during our call on Thursday, I’ve consulted with our Staff colleagues on how to best address the concerns expressed around how the text of preliminary recommendation #1, in isolation, might be interpreted by the community. As indicated during the call, I am hesitant to make changes to the Initial Report as this may set an unhelpful precedent. It could also lead to confusion as there would be different versions of the Initial Report circulating. As some of you noted, those interested in commenting on the Initial Report will be focusing on the public comment announcement as well as the public comment input form. As a result, the leadership team and Staff have decided to proceed as follows. * The following sentence will be added to 1) the public comment forum, 2) the public comment input form, and 3) the slides for the EPDP outreach session: “For clarity, preliminary recommendation #1 aims to reflect that there is currently no consensus on whether there should be changes to the phase 1 recommendation. The EPDP Team will consider this question further following the close of the public comment period”. I hope this approach achieves the goal that several of you wanted to achieve, namely, a clear communication to the broader community about how preliminary recommendation #1 should be interpreted. Thank you again for all your comments and suggestions. I do hope that we now can start looking forward to the next phase of our work; focusing on how we can bridge the gaps and difference of opinion that still exist. On a separate note, as we did not get additional volunteers for the ICANN71 outreach session, our Staff colleagues will start reaching out to a number of you for your support. If anyone would like to volunteer, please advise ASAP as the session is on Wednesday. I hope you are able to make the time to assist with this session. Best regards, Keith Confidentiality note: This e-mail may contain confidential information from Clarivate. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this e-mail is strictly prohibited. If you have received this e-mail in error, please delete this e-mail and notify the sender immediately.