<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Trang and Dan,<div class="">I will only briefly respond to your e-mail now, but I would be more than happy to discuss all the aspects (and many more :-)) with you and Dan, but I am sure that there are more colleagues on the team that would like to join the discussion, if not the entire EPDP group. </div><div class=""><br class=""></div><div class="">To be quite honest, I did not read the Temp Spec as a document confirming that ICANN Org things all parties are independent controllers. It was not a natural evolution for me that since it was mentioned in the Cookbook it must also be true for the Temp Spec. I have quoted Becky confirming a joint controller situation - but let’s leave all that and the Hamilton memo, the Art. 29 WG letter aside:</div><div class=""><br class=""></div><div class="">How would an independent controller scenario play out? I guess we are aligned on all the parties involved. Have you given some thought to the travel of data elements between all these players, the legal basis for that (where required) and how this would be operationalized? I said in multiple occasions, and I will repeat it here: I am open to discussing other models than a JC scenario, but I would need more „flesh to the bones“ to consider alternatives. </div><div class=""><br class=""></div><div class="">Let’s look at your thinking more closely. Again, if you have sought legal advice, have internal memos, flow charts etc., please share so we can better understand. If there is no such documentation, please also say so. In order to review your suggestions, I guess we would need to get something in writing to consider. You might say its’s all in the Cookbook and the Temp Spec, but I do not think these documents contain enough information and analysis so I can make an informed decision.</div><div class=""><br class=""></div><div class="">I hope this helps. </div><div class=""><br class=""></div><div class="">Best,</div><div class="">Thomas</div><div class=""><br class=""></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 27.11.2018 um 01:41 schrieb Trang Nguyen <<a href="mailto:trang.nguyen@icann.org" class="">trang.nguyen@icann.org</a>>:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">Hello Thomas.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class=""><br class="">Thanks for your note and for your continuing collaboration on this issue. Your knowledge and experience with these issues is very valuable to all of us, and we appreciate this dialogue.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">The Temporary Specification identifies the existence of multiple controllers as part of the domain registration system. As we’ve discussed, it does not specify whether the controllers are joint or independent. ICANN org previously indicated that the controllers are independent and not joint (see Section 7.2.11.3 of the<span class="Apple-converted-space"> </span></span><a href="https://www.icann.org/en/system/files/files/gdpr-compliance-interim-model-08mar18-en.pdf" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(17, 85, 204);" class="">Cookbook</span></a><span style="" class="">), which is based on our understanding of the definition of independent versus joint controllers (see the<span class="Apple-converted-space"> </span></span><a href="https://mm.icann.org/pipermail/gnso-epdp-team/2018-November/000895.html" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(17, 85, 204);" class="">ICANN Org Feedback</span></a><span style="" class=""><span class="Apple-converted-space"> </span>on Roles and Responsibilities Memo).</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">In EPDP discussions, a view has been expressed that the parties are all joint controllers. ICANN org has said that position would be a significant change from the Temporary Specification and would require further review and discussion. Deciding whether or not the parties should act as joint controllers could have far reaching consequences, such as in relation to liability. To help the team move to finalizing its recommendation on this issue we believe it would be helpful to attempt to identify the specific facts and the precise application of the GDPR to these facts. If it’s true that the parties are all joint controllers then we should be able to describe exactly when and how the parties came together and continue to come together on a regular basis to jointly agree on all the relevant purposes and also all the variety of very specific means of processing. We’ve agreed to continue discussing this together further now that the initial report is published. Thanks for that.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">We agree with your note below, which pointed out that if the controllers are independent there still must be a mechanism to ensure an appropriate legal basis for any transfers of personal data of an EEA resident to another party that is not subject to the GDPR. This is addressed by section 6.3.2 of the Temporary Specification, which permits registry operators wherever necessary, and without further ICANN org approval, to amend their registry-registrar agreements to incorporate data processing terms and conditions, including the EU Model Clauses to govern international data transfers. ICANN org and the contracted parties already collaborated on and published “</span><a href="https://www.icann.org/en/system/files/files/rra-amendment-terms-temp-spec-02jul18-en.pdf" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(17, 85, 204);" class="">ICANN Temporary Specification Model Registry-Registrar Agreement Amendment Terms</span></a><span style="" class="">” which are posted on the<span class="Apple-converted-space"> </span></span><a href="https://www.icann.org/resources/pages/gtld-registration-data-specs-en" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(17, 85, 204);" class="">Temporary Specification web page</span></a><span style="" class="">.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">As a result, it at least appears to us that all of the formalities you mentioned are addressed under the framework of the Temporary Specification, but please let us know if and how you disagree.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">The current proposal in the initial report is to create a new policy binding on all registries, registrars, and ICANN org, requiring negotiations on a brand new separate “agreement” (not “arrangement”). Implementation of this policy recommendation would require approximately 1000+ simultaneous negotiations. Unlike the EU-approved Model Clauses for international data transfers there is no such agreed or even approved standard form for a joint controller agreement available at this point in time, and no such standard form is expected to become available any time soon.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">The community might collaborate on a template that could be used as a starting point for each of those negotiations, but each separate registry would then be free to make its own unique demands of ICANN org and its associated registrars. If this is the path that is decided upon, then numerous implementation questions would remain, as illustrated below.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">For example, there would inevitably be disagreements between the parties on how to divide and allocate the various obligations under GDPR from a data subject perspective and the associated responsibilities and risks. We believe that it would be very difficult to achieve a consistent framework across all gTLDs, since each of the 1000+ negotiations would be a blank slate, subject to the demands of individual registries and registrars. ICANN org would be required to treat all registries and registrars fairly, so presumably each registry would want to hold out for or renegotiate to get the best possible “deal” in its JCA. This scenario could also lead to legal uncertainty in the community and could therefore have a counterproductive effect.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">Presumably some registries might disagree that they even need a joint controller agreement at all. For example, how would we explain to a dot-brand TLD (outside or even inside of Europe) why they need a JCA?</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">Some registries might also propose terms for their JCA that the registrars or ICANN org (or both) would find to be unfair or otherwise objectionable. What if a registry were to demand in its proposed JCA that the registrars and ICANN org must indemnify the registry even for the registry’s own intentional misconduct in handling personal data?</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">If the parties failed to reach agreement, would ICANN org, the registrars, and the registry all be in violation of the proposed new policy? You said that such a “failure to agree” would be a violation of the policy and that it would be up to ICANN org’s contractual compliance team to enforce, so presumably at some point the parties could end up in arbitration to determine which parties were right and wrong in their negotiating positions?</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">These are just a few examples of questions we have identified. There are likely many more that will arise if this path is pursued. Contrary to what has been said, we are not trying to spread “fear, uncertainty, and doubt” in raising these implementation-related questions. Rather, we are trying to fulfill our roles as ICANN org liaisons. The EPDP charter states: “The ICANN Org GDD and Legal Liaisons are expected to provide timely input on issues that may require ICANN Org input such as implementation-related queries.”<span class="Apple-converted-space"> </span></span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span style="" class="">Thanks again for your continued openness to discussing this. We look forward to taking this conversation up again this week.</span><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Dan and Trang<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">ICANN org liaisons<o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-size: 12pt;" class="">From:<span class="Apple-converted-space"> </span></span></b><span style="font-size: 12pt;" class="">Thomas Rickert <<a href="mailto:epdp@gdpr.ninja" class="">epdp@gdpr.ninja</a>><br class=""><b class="">Date:<span class="Apple-converted-space"> </span></b>Wednesday, November 21, 2018 at 7:21 AM<br class=""><b class="">To:<span class="Apple-converted-space"> </span></b>Trang Nguyen <<a href="mailto:trang.nguyen@icann.org" class="">trang.nguyen@icann.org</a>><br class=""><b class="">Cc:<span class="Apple-converted-space"> </span></b>Thomas Rickert <<a href="mailto:epdp@gdpr.ninja" class="">epdp@gdpr.ninja</a>>, Marika Konings <<a href="mailto:marika.konings@icann.org" class="">marika.konings@icann.org</a>>, "<a href="mailto:gnso-epdp-team@icann.org" class="">gnso-epdp-team@icann.org</a>" <<a href="mailto:Gnso-epdp-team@icann.org" class="">Gnso-epdp-team@icann.org</a>><br class=""><b class="">Subject:<span class="Apple-converted-space"> </span></b>[Ext] Re: [Gnso-epdp-team] For Final Review - Initial Report - deadline Wednesday 21 November at 18.00 UTC<o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Hi Trang,<span class="Apple-converted-space"> </span><o:p class=""></o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Thanks so much for the additional comments. As you suggest, I think these should not stop us from releasing the report. <o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Let’s be clear, there will be work involved in getting the compliance done and we should try to get contracts as standardized as possible and use existing mechanisms to get the contracts in place (hence my idea to use the RRA). Maybe it is just me, but I read those comments like we are suggesting something that is overly cumbersome to implement, which suggests that you might have a envisaged solution that requires less efforts. If so, please do share. <o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Just to illustrate this:<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Where we have a joint controller situation, we need JCAs<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Where we have controller-processor situations, we need DPAs<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Where we have independent controller situations, we would at least need to cover (as for the other two scenarios) the non-EU transfers in writing<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">In sum, regardless what option we pursue, we will need to formalize the relationships. <o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">If anyone has an idea of how to avoid formalities, please share. If there is no way to avoid formalities, let’s just accept that and try to find the most efficient way to get that done.<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Best<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Thomas<o:p class=""></o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><br class=""><br class=""><o:p class=""></o:p></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite"><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Am 21.11.2018 um 06:42 schrieb Trang Nguyen <<a href="mailto:trang.nguyen@icann.org" style="color: purple; text-decoration: underline;" class="">trang.nguyen@icann.org</a>>:<o:p class=""></o:p></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Dear EPDP Team,<span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Regarding recommendation #13, as we flagged today in the chat and previously provided in the ICANN feedback<a href="https://mm.icann.org/pipermail/gnso-epdp-team/2018-November/000895.html" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(149, 79, 114);" class="">document</span></a>, there are implementation-related issues and concerns that we look forward to continuing to discuss with the Team. For example, the practicality as well as cost of negotiating, monitoring, supporting, and enforcing 1200+ different agreements with potentially different obligations. We’d also like to flag some additional suggestions and questions on recommendation #13. For easy viewing, we extracted recommendation #13 from the draft Initial report and provided the suggestions and questions in the comment fields. To be clear, we do not believe that these items should delay publication of the Initial Report. We look forward to continued discussion with the EPDP Team on this topic.<span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">The one thing that we do want to flag for the EPDP Team’s consideration prior to the publication of the Initial Report is the inconsistency in how recommendation #13 is displayed in Section 2 and Section 4 of the Initial Report. Section 2 only contains 2 paragraphs while Section 4 contains these two paragraphs plus several paragraphs of additional text. Since the additional text does not appear in Section 2 of the report, we assume it is not part of the recommendation. If this assumption is correct, it would be helpful to make the separation of the additional text clearer in Section 4 of the report.<span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Dan and Trang<span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">ICANN org liaisons<span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></div></div><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: 3pt 0in 0in;" class=""><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-size: 12pt;" class="">From:<span class="apple-converted-space"> </span></span></b><span style="font-size: 12pt;" class="">Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(149, 79, 114);" class="">gnso-epdp-team-bounces@icann.org</span></a>> on behalf of Marika Konings <<a href="mailto:marika.konings@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(149, 79, 114);" class="">marika.konings@icann.org</span></a>><br class=""><b class="">Date:<span class="apple-converted-space"> </span></b>Tuesday, November 20, 2018 at 11:46 AM<br class=""><b class="">To:<span class="apple-converted-space"> </span></b>"<a href="mailto:Gnso-epdp-team@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(149, 79, 114);" class="">Gnso-epdp-team@icann.org</span></a>" <<a href="mailto:Gnso-epdp-team@icann.org" style="color: purple; text-decoration: underline;" class=""><span style="color: rgb(149, 79, 114);" class="">Gnso-epdp-team@icann.org</span></a>><br class=""><b class="">Subject:<span class="apple-converted-space"> </span></b>[Gnso-epdp-team] For Final Review - Initial Report - deadline Wednesday 21 November at 18.00 UTC<o:p class=""></o:p></span></div></div></div><div class=""><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""> <span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></div></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><a name="_MailOriginalBody" class="">Dear EPDP Team,</a><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""> </span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="">We are pleased to share the proposed Initial Report for publication. Thank you again for attending and constructively contributing to the many hours of meetings over the past few days.</span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""> </span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><ul type="disc" style="margin-bottom: 0in; margin-top: 0in;" class=""><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span class="">Redline –<span class="apple-converted-space"> </span></span><span class=""></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_a_icann.org_file_d_171jOv42nahKFnPW1WhSE8ckr6K00i4RX_view-3Fusp-3Dsharing&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=NghSLFqweTwAOFMJpbYA3LcVJ0Vvvw6-wxrKoS5l6VY&m=EsM_gBHmxSFPAzJp3M67DbigIhZDtEFi7WicX3tz3RQ&s=3J4Yh6TGbOOGChMPq_9L97rAO_AHWQaBNjw03jVhv-s&e=" style="color: purple; text-decoration: underline;" class=""><span class=""><span style="color: rgb(149, 79, 114);" class="">https://drive.google.com/a/icann.org/file/d/171jOv42nahKFnPW1WhSE8ckr6K00i4RX/view?usp=sharing [drive.google.com]</span></span><span class=""></span></a><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></li><li class="MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;"><span class="">Clean –<span class="apple-converted-space"> </span></span><span class=""></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_a_icann.org_file_d_1OyG6ExIGkemW902jHYF7V88Y8mu-2DkObk_view-3Fusp-3Dsharing&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=NghSLFqweTwAOFMJpbYA3LcVJ0Vvvw6-wxrKoS5l6VY&m=EsM_gBHmxSFPAzJp3M67DbigIhZDtEFi7WicX3tz3RQ&s=ASqrI8ZnjDf6jUM_k0_3nQgyvS2Gam5oREH-MqPMaew&e=" style="color: purple; text-decoration: underline;" class=""><span class=""><span style="color: rgb(149, 79, 114);" class="">https://drive.google.com/a/icann.org/file/d/1OyG6ExIGkemW902jHYF7V88Y8mu-kObk/view?usp=sharing [drive.google.com]</span></span><span class=""></span></a><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></li></ul><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""> </span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="">Note that in the redline version, you will find highlighted in yellow the updates proposed by Thomas for the responsibilities section. He also spotted some inconsistencies in the related tables that have been updated accordingly (as well as the related data elements workbooks sections). Please also note that per Monday’s discussion, the summary has been split out into an Executive Summary and Overview of Preliminary Recommendations.</span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""> </span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="">For your convenience, you will also find attached the clean Word version. However, should you spot any minor issues or show stoppers, please use the line number reference in the pdf version to facilitate locating the language. Minor issues (e.g. grammatical, readability) can be sent to staff off list.</span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""> </span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="">Due to internal ICANN processing times and deadlines we require feedback<span class="apple-converted-space"> </span><b class="">by 1800 UTC, tomorrow, 21 Novembe</b>r. If you need additional time (not more than two hours), you must notify us before the 1800 cut off. </span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""> </span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="">Best regards,</span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""> </span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="">Caitlin, Berry and Marika</span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""> </span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""><b class=""><i class=""><span style="font-size: 10pt;" class="">Marika Konings</span></i></b></span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""><i class=""><span style="font-size: 10pt;" class="">Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) </span></i></span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""><i class=""><span style="font-size: 10pt;" class="">Email: </span></i></span><span class=""></span><a href="mailto:marika.konings@icann.org" style="color: purple; text-decoration: underline;" class=""><span class=""><i class=""><span style="font-size: 10pt; color: rgb(149, 79, 114);" class="">marika.konings@icann.org</span></i></span><span class=""></span></a><span class=""><i class=""><span style="font-size: 10pt;" class=""> </span></i></span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""><i class=""><span style="font-size: 10pt;" class=""> </span></i></span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""><i class=""><span style="font-size: 10pt;" class="">Follow the GNSO via Twitter @ICANN_GNSO</span></i></span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""><i class=""><span style="font-size: 10pt;" class="">Find out more about the GNSO by taking our </span></i></span><span class=""></span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses_gnso&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=Cg5uQf0yAfw-qlFZ0WNBfsLmmtBNUiH0SuI6Vg-gXBQ&e=" style="color: purple; text-decoration: underline;" class=""><span class=""><i class=""><span style="font-size: 10pt; color: rgb(149, 79, 114);" class="">interactive courses</span></i></span><span class=""></span></a><span class=""><i class=""><span style="font-size: 10pt;" class=""> and visiting the </span></i></span><span class=""></span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=tT-E2RoAucUb3pfL9zmlbRdq1sytaEf765KOEkBVCjk&e=" style="color: purple; text-decoration: underline;" class=""><span class=""><i class=""><span style="font-size: 10pt; color: rgb(149, 79, 114);" class="">GNSO Newcomer pages</span></i></span><span class=""></span></a><span class=""><i class=""><span style="font-size: 10pt;" class="">. </span></i></span><span class=""><span style="font-size: 12pt;" class=""><o:p class=""></o:p></span></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""><span style="font-size: 12pt;" class=""> <o:p class=""></o:p></span></span></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""><EPDP Team Preliminary Rec #13.docx></span><span class=""><span style="font-size: 9pt; font-family: Helvetica;" class="">_______________________________________________<br class="">Gnso-epdp-team mailing list<br class=""></span></span><span class=""></span><a href="mailto:Gnso-epdp-team@icann.org" style="color: purple; text-decoration: underline;" class=""><span class=""><span style="font-size: 9pt; font-family: Helvetica; color: rgb(149, 79, 114);" class="">Gnso-epdp-team@icann.org</span></span><span class=""></span></a><span class=""><span style="font-size: 9pt; font-family: Helvetica;" class=""><br class=""></span></span><span class=""></span><a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" style="color: purple; text-decoration: underline;" class=""><span class=""><span style="font-size: 9pt; font-family: Helvetica; color: rgb(149, 79, 114);" class="">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</span></span></a></div></div></blockquote></div></div></div></div></blockquote></div><br class=""></div></body></html>