<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 everyone:<div class=""><br class=""></div><div class="">You have seen Chris’ suggested language for Recommendation 13 below (and Kavouss’ response). The result is a less prescriptive or precise recommendation but also alerts us to possible reaction by the ICANN Board. </div><div class=""><br class=""></div><div class="">Please let me know if you disagree with or wish to discuss Chris’ recommendation. It would be great to receive feedback today so that we can schedule a discussion if need be, but please respond by tomorrow at the latest. </div><div class=""><br class=""></div><div class="">Thanks and regards,</div><div class=""><br class=""></div><div class="">Kurt</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 4, 2019, at 1:58 AM, Chris Disspain <<a href="mailto:chris.disspain@board.icann.org" class="">chris.disspain@board.icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div style="font-family: 'Verdana', 'Verdana'; font-size: 10pt; color: rgba(102, 102, 102, 1.0);" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Kurt,<div class=""><br class=""></div><div class=""><div style="margin: 0in 0in 0.0001pt;" class=""><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt;" class="">I think your suggested language below brings together all of the points of view. </div><div style="margin: 0in 0in 0.0001pt;" class=""><br class=""></div><div style="margin: 0in 0in 0.0001pt;" class="">I do have one concern regarding the indemnification language “Indemnification clauses shall ensure that the risk for certain data processing is borne by either one or multiple parties that determine the purpose and means of the processing”. This goes beyond my understanding of ICANN’s plan to explore ways to possibly reduce risk to the contracted parties with respect to providing access to non-public WHOIS data through a unified access model. As currently drafted, I think the language might prove challenging when it comes time for the Board to consider this recommendation. </div><div style="margin: 0in 0in 0.0001pt;" class=""><br class=""></div><div style="margin: 0in 0in 0.0001pt;" class="">Trang also raised a related question about indemnification where she noted that it’s not clear that liability should necessarily always rest with the party or parties that determine the purposes and means of processing, for example in the case of a data breach.</div><div style="margin: 0in 0in 0.0001pt;" class=""><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt;" class=""><o:p class=""> </o:p></div><div style="margin: 0in 0in 0.0001pt;" class="">I think both of these points could be addressed if the sentence were edited to say something to the effect of: “Indemnification should be addressed as appropriate as part of the arrangements between ICANN, registries, and registrars.” </div><div style="margin: 0in 0in 0.0001pt;" class=""><br class=""></div><div style="margin: 0in 0in 0.0001pt;" class="">I hope this makes sense. Happy to discuss as always. <o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt;" class=""><o:p class=""></o:p></div><div style="margin: 0in 0in 0.0001pt;" class=""><br class=""></div><div style="margin: 0in 0in 0.0001pt;" class=""><br class=""></div><div class=""><span id="um_signature_marker_begin" class=""><div style="color: rgb(102, 102, 102);" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); 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; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div style="color: rgb(102, 102, 102);" class=""><div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="margin: 0px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-position: normal; font-weight: normal; line-height: normal; color: rgb(148, 67, 251); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Cheers,</div><div style="margin: 0px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-position: normal; font-weight: normal; line-height: normal; color: rgb(148, 67, 251); min-height: 16px; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="margin: 0px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-east-asian: normal; font-variant-position: normal; font-weight: normal; line-height: normal; color: rgb(148, 67, 251); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">CD</div></div></div></div></div></div></div>
<span id="um_signature_marker_end" class=""></span></span></div>
<div class=""><br class=""><blockquote type="cite" class=""><div class="">On 30 Jan 2019, at 19:53, Kurt Pritz <<a href="mailto:kurt@kjpritz.com" class="">kurt@kjpritz.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Everyone: <div class=""><br class=""></div><div class="">To me, it seems as if we are in agreement with a set of principles and a variety of wordings will suit our purpose. </div><div class=""><br class=""></div><div class="">I believe we need to point directly to the thorough work done by several of our team that indicates that JCAs are an appropriate solution in many of the data processing cases. Before we made any recommendation, we started with this analysis of data, purposes, etc. </div><div class=""><br class=""></div><div class="">I also have learned that the responsibilities of the parties (contracted parties and ICANN) will vary for each purpose even for each data processing step. There is analysis left to go. </div><div class=""><br class=""></div><div class="">Taking into account the Initial Report Recommendation, the work of the small group subsequent to that, and the comments on this list, I’d like to settle on the following wording: </div><div class=""><br class=""></div><div class="">"The EPDP Team recommends that ICANN Org develop and implement any required data protection arrangements, as appropriate, with the Contracted Parties. In addition to the legally required components of such agreement, the agreement shall clearly specify the responsibilities of the respective parties for the processing activities as described therein. Indemnification clauses shall ensure that the risk for certain data processing is borne by either one or multiple parties that determine the purpose and means of the processing. Due consideration should be given to the analysis carried out by the EPDP Team ("Processors, Controllers, Co-Controllers and Joint Controllers," above in this Final Report).”</div><div class=""><br class=""></div><div class="">In addition, if Thomas or others wish to augment the analysis in the Initial Report with his email that are part of this chain (about avoiding liability), we should include that as an individual contribution to the team analysis.</div><div class=""><br class=""></div><div class="">It’s my hope we can accept this as a team.</div><div class=""><br class=""></div><div class="">Thanks for letting me weigh in on this and thank for the energy that’s gone into this discussion and the others.</div><div class=""><br class=""></div><div class="">Best regards,</div><div class=""><br class=""></div><div class="">Kurt</div><div class=""><br class=""></div><div class=""><br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Jan 30, 2019, at 11:22 AM, Heineman, Ashley <<a href="mailto:AHeineman@ntia.doc.gov" class="">AHeineman@ntia.doc.gov</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div id="divtagdefaultwrapper" dir="ltr" style="caret-color: rgb(0, 0, 0); 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; font-size: 12pt; font-family: Calibri, Helvetica, sans-serif;" class=""><div style="margin-top: 0px; margin-bottom: 0px;" class="">I won't belabor this, but just to correct the record, the USG does not ask that the recommendation be deleted. It does however specifically express concern about the EPDP proposing a "specific legal vehicle (i.e., Joint Controller Agreement)."</div><br class=""><br class=""><div style="" class=""><hr tabindex="-1" style="display: inline-block; width: 785.953125px;" class=""><div id="divRplyFwdMsg" dir="ltr" class=""><font face="Calibri, sans-serif" style="font-size: 11pt;" class=""><b class="">From:</b><span class="Apple-converted-space"> </span>farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com" class="">farzaneh.badii@gmail.com</a>><br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Wednesday, January 30, 2019 1:57 PM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>Heineman, Ashley<br class=""><b class="">Cc:</b><span class="Apple-converted-space"> </span>Thomas Rickert; <a href="mailto:gnso-epdp-team@icann.org" class="">gnso-epdp-team@icann.org</a><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [Gnso-epdp-team] Recommendation 13 - Responsibilities of the Parties - email list discussion</font><div class=""> </div></div><div class=""><div dir="ltr" class=""><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><div class="x_gmail_default"> it seems like USG has suggested deleting the whole recommendation. I do not see any other opposition against JCA. h<a id="LPlnk803711" class="OWAAutoLink" previewremoved="true" style="color: rgb(17, 85, 204);">ttps://community.icann.org/display/EOTSFGRD/Public+Comment+Review+Tool?preview=/102139731/102139865/gnso-EPDP-pcrt-Initial-Report-REC13_20181228.docx</a></div><div class="x_gmail_default"><br class=""></div><div class="x_gmail_default">Unless you <span class="x_gmail-gr_330 x_gmail-gr_ x_gmail-gr_inline_cards x_gmail-multiReplace x_gmail-Grammar x_gmail-gr-alert x_gmail-replaceWithoutSep x_gmail-only-ins x_gmail-gr_gramm x_gmail-gr_run_anim" id="x_gmail-330" style="display: inline; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: transparent; color: inherit; font-size: inherit; background-repeat: no-repeat no-repeat;">agreed</span><span class="Apple-converted-space"> </span>on something during the F2F, I don't think we should remove JCA because of a single entity opposition - maybe staff can tell us if there have been other public comments specifically against JCA. </div><div class="x_gmail_default"><br class=""></div></div><div class=""><div dir="ltr" class="x_gmail_signature"><div dir="ltr" class=""><div class=""><font face="verdana, sans-serif" class="">Farzaneh<span class="Apple-converted-space"> </span></font></div></div></div></div><br class=""></div><br class=""><div class="x_gmail_quote"><div dir="ltr" class="x_gmail_attr">On Wed, Jan 30, 2019 at 1:48 PM Heineman, Ashley <<a href="mailto:AHeineman@ntia.doc.gov" id="LPlnk778282" class="OWAAutoLink" previewremoved="true">AHeineman@ntia.doc.gov</a>> wrote:<br class=""></div><blockquote class="x_gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div class=""><div class="">Attaching the narrative version of the USG comments should it be of interest.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div id="x_gmail-m_7180990775729884537composer_signature" class=""><div dir="auto" style="font-size: 13.600000381469727px; color: rgb(87, 87, 87);" class="">Sent from my Verizon, Samsung Galaxy smartphone</div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">-------- Original message --------</div><div class="">From: "Heineman, Ashley" <<a href="mailto:AHeineman@ntia.doc.gov" target="_blank" id="LPlnk296270" class="OWAAutoLink" previewremoved="true">AHeineman@ntia.doc.gov</a>></div><div class="">Date: 1/30/19 13:44 (GMT-05:00)</div><div class="">To: farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com" target="_blank" id="LPlnk307409" class="OWAAutoLink" previewremoved="true">farzaneh.badii@gmail.com</a>>, Thomas Rickert <<a href="mailto:epdp@gdpr.ninja" class="">epdp@gdpr.ninja</a>></div><div class="">Cc:<span class="Apple-converted-space"> </span><a href="mailto:gnso-epdp-team@icann.org" target="_blank" id="LPlnk551405" class="OWAAutoLink" previewremoved="true">gnso-epdp-team@icann.org</a></div><div class="">Subject: Re: [Gnso-epdp-team] Recommendation 13 - Responsibilities of the Parties - email list discussion</div><div class=""><br class=""></div><div class=""><div class="">For what it is worth, the USG comments caution against getting into legal specifics as they pertain to agreements. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div id="x_gmail-m_7180990775729884537composer_signature" class=""><div dir="auto" style="font-size: 13.600000381469727px; color: rgb(87, 87, 87);" class="">Sent from my Verizon, Samsung Galaxy smartphone</div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">-------- Original message --------</div><div class="">From: farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com" target="_blank" id="LPlnk278139" class="OWAAutoLink" previewremoved="true">farzaneh.badii@gmail.com</a>></div><div class="">Date: 1/30/19 13:36 (GMT-05:00)</div><div class="">To: Thomas Rickert <<a href="mailto:epdp@gdpr.ninja" class="">epdp@gdpr.ninja</a>></div><div class="">Cc:<span class="Apple-converted-space"> </span><a href="mailto:gnso-epdp-team@icann.org" target="_blank" id="LPlnk553879" class="OWAAutoLink" previewremoved="true">gnso-epdp-team@icann.org</a></div><div class="">Subject: Re: [Gnso-epdp-team] Recommendation 13 - Responsibilities of the Parties - email list discussion</div><div class=""><br class=""></div><div class=""><div dir="ltr" class=""><div class="x_gmail_default" style="font-family: verdana, sans-serif;">I agree with Thomas.</div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"> I do not agree that we should be after giving "flexibility" to ICANN org and CPs. But since some public comments asked for such flexibility, then I think we should provide them a framework, the framework should consider ( as I gather from Alan and Thomas emails) legal, binding instruments that minimize the risk of fine and provides the appropriate and legal level of data protection for domain name registrants[ - sorry I am being sinful today].</div><div class="x_gmail_default" style="font-family: verdana, sans-serif;">I can live with what Kristina has proposed [Personal opinion] But I also want to point out that no one in the public comments is against having JCA. So why we are changing that I do not know. I don't think JCA will take away flexibility (as .Chris suggests). If we want to give flexibility to org and CPs that is fine but we have to provide them with a set of criteria to work with. Otherwise, what is the point of this recommendation? They would have done agreements and contracts even without it. The law asks them to! <br class=""></div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="x_gmail_default" style="font-family: verdana, sans-serif;">As to Trang's point about indemnification, I am a little confused. I didn't see any ICANN legal concern raised in the public comment, is this a new issue being raised now? Are we bringing new issues to the table? </div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"> </div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class="x_gmail_default" style="font-family: verdana, sans-serif;"><br class=""></div><div class=""><div dir="ltr" class="x_gmail-m_7180990775729884537gmail_signature"><div dir="ltr" class=""><div class=""><font face="verdana, sans-serif" class="">Farzaneh<span class="Apple-converted-space"> </span></font></div></div></div></div><br class=""></div><br class=""><div class="x_gmail_quote"><div dir="ltr" class="x_gmail_attr">On Wed, Jan 30, 2019 at 12:41 PM Thomas Rickert <<a href="mailto:epdp@gdpr.ninja" class="">epdp@gdpr.ninja</a>> wrote:<br class=""></div><blockquote class="x_gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div class="">All,<div class="">I still think it is a mistake to dilute the language from where we were before we published the initial report. We are in in the process of analyzing public comment and establishing whether the comments received require us to amend our report / recommendations. What we heard and read were primarily implementation issues, which - as I hope we can agree by now - must not guide our decision, but the actually circumstances. Additionally, we heard and read about concerns, but no alternative has been suggested that would be a better solution to what we agreed on earlier. To me, that does not require a change of our recommendation. We are replacing a concrete recommendation with something vague without good reason.</div><div class=""><br class=""></div><div class="">Also, the language in our initial report allows for a change of model as we had the language in there that our recommendation is subject to further legal analysis (or something to that effect).</div><div class=""><br class=""></div><div class="">Thus, the JCA approach should be the starting point and only be deviated from if there is a sufficiently robust alternative.</div><div class=""><br class=""></div><div class="">I trust what unites us is the interest in ensuring that no-one in the ICANN ecosystem will be fined. Let’s just imagine two scenarios:</div><div class=""><br class=""></div><div class="">1. We say joint controllers and in fact the parties are independent controllers</div><div class=""><br class=""></div><div class="">In this scenario, there should not be any risk for the parties at all. </div><div class=""><br class=""></div><div class="">The reason for this assumption is that the data flows between joint controllers need to be legally sound as between third parties (or independent controller for that matter). Also, JCAs provide probably the highest protection level for data subjects. </div><div class=""><br class=""></div><div class="">2. We go for independent controllers and in fact a joint controller scenario is present</div><div class=""><br class=""></div><div class="">In this case, legal requirements would not be fulfilled. There would be a breach that could be sanctioned. In a proceeding with a supervisory authority, the authority will surely review the documents publicly available, which are eg.:</div><div class=""><br class=""></div><div class="">- a letter from the Art 29 WP suggesting a joint controller scenario might be present</div><div class="">- a memo from Wilson Sonsini pointing in the direction of joint controllers</div><div class="">- a memo from Hamilton suggesting a joint controller scenario</div><div class="">- a memo from ICANN quoting from the above and concluding that it should be independent controllers nonetheless.</div><div class=""><br class=""></div><div class="">I am afraid that the authorities will then say that we could have known that joint controllers should be the way to go and that we increase the liability risk for everyone by not doing so. </div><div class=""><br class=""></div><div class="">In other words, we would need to have very good reasons not to go for a joint controller scenario. The language in the initial report ensures that. The revised language not much so.</div><div class=""><br class=""></div><div class="">Thanks for reading all this.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Thomas</div><div class=""><br class=""></div><div class="">PS - In practical terms, I think joint controller agreements can be operationalized without insurmountable difficulties. In the long run, we should apply for a code of conduct anyway and we could present a different approach than joint controllers. If there is blessing for an alternative form the authorities via that route or by means of a guidance or other confirmation, we can certainly take a different and potentially more light-weight approach.</div><div class=""><br class=""></div><div class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">Am 30.01.2019 um 14:40 schrieb Alan Woods <<a href="mailto:alan@donuts.email" target="_blank" id="LPlnk599829" class="OWAAutoLink" previewremoved="true">alan@donuts.email</a>>:</div><br class="x_gmail-m_7180990775729884537gmail-m_8182687114185143488Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class="">Dear all, <div class=""><br class=""></div><div class="">I am perplexed, if not a little bit frustrated by continuous tendency to wordsmith matters out of existence here. </div><div class=""><br class=""></div><div class="">So this end, and regardless of the ultimate settling of Roles and Responsibilities can we just go back to basic principles and remind ourselves of the GDPR's requirements: </div><div class=""><br class=""></div><div class=""><b class="">Art 28:</b><span class="Apple-converted-space"> </span>(processor) "Processing by a processor shall be governed<span class="Apple-converted-space"> </span><b class=""><u class="">by a contract or other legal act</u></b>"<i class="">[emphasis added] </i></div><div class=""><b class="">Art 26:</b><span class="Apple-converted-space"> </span>(Joint Controllers) "They shall in a transparent manner determine their respective responsibilities for compliance with the obligations under this Regulation, in particular as regards the exercising of the rights of the data subject and their respective duties to provide the information referred to in Articles 13 and 14,<span class="Apple-converted-space"> </span><b class=""><u class="">by means of an arrangement between them</u></b>" <i class="">[emphasis added] </i></div><div class=""><br class=""></div><div class="">I appreciate this is likely where Trang's suggestion is deriving from and I have no real issue with the concept of 'Arrangement' - but can we please be very clear, that as a contracted party, who's lead DPA is clearly going to be Ireland (as will also be the case for a number of other CPs), my interpretation MUST be led by the laws which will be applicable to me, which is the<span class="Apple-converted-space"> </span><a href="http://www.irishstatutebook.ie/eli/2018/act/7/section/79/enacted/en/html#sec79" target="_blank" id="LPlnk535997" class="OWAAutoLink" previewremoved="true">Data Protection Act, 2018</a>. Section 79. which states: </div><div class=""><br class=""></div><div class="">" Where 2 or more controllers jointly determine the purposes and means of the processing of personal data (in this Part referred to as “joint controllers”), they shall determine their respective responsibilities for compliance with this Part in a transparent manner<b class=""><u class=""><span class="Apple-converted-space"> </span>by means of an agreement in writing between them</u></b>, save in so far as the said responsibilities are determined by the law of the European Union or the law of the State. <i class="">[emphasis added] </i></div><div class=""><br class=""></div><div class="">So regardless of whether or not we are considered Processors, Controllers or Joint controllers at some point in time, CPs will require a Contract (or more correctly an addendum to our existing contracts) with ICANN, in writing, that governs the processing of data. </div><div class=""><br class=""></div><div class="">So long as it is clear, on the record, that whatever word is used, be it agreement, arrangement, or Ketubah, it means a legally binding instrument, then I'm fine with it. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Kind regards,</div><div class=""><br class=""></div><div class="">Alan</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br clear="all" class=""><div class=""><div dir="ltr" class="x_gmail-m_7180990775729884537gmail-m_8182687114185143488gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><table style="padding: 0px; margin: 10px 0px; border: none;" class=""><tbody class=""><tr class=""><td style="vertical-align: middle; padding: 0px 7px 0px 0px;" class=""><a href="http://donuts.domains/" rel="nofollow" target="_blank" id="LPlnk825832" class="OWAAutoLink" previewremoved="true"><img alt="Donuts Inc." height="75" width="75" src="https://storage.googleapis.com/signaturesatori/customer-C02zzlf7k/images/-54f9d8ac97e7f575bf497d10ac1f1aafafddf8afceab5f269d49034f01b3217b.png" class=""></a></td><td style="vertical-align: middle; padding: 0px 7px 0px 0px; text-align: left;" class=""><div style="font-family: tahoma, sans-serif; font-size: 14px; line-height: 17px; font-weight: bold;" class=""><span style="font-size: 12px;" class=""><span style="font-family: arial, helvetica, sans-serif;" class=""><span style="color: rgb(51, 51, 51);" class="">Alan Woods</span></span></span></div><div class=""><span style="font-size: 12px;" class=""><span style="font-family: arial, helvetica, sans-serif;" class=""><span style="color: rgb(51, 51, 51);" class="">Senior Compliance & Policy Manager, Donuts Inc.</span></span></span><hr class=""><span style="font-size: 11px;" class=""><span style="font-family: arial, helvetica, sans-serif;" class=""><span style="color: rgb(51, 51, 51);" class="">The Victorians, </span></span></span></div><div class=""><font color="#333333" face="arial, helvetica, sans-serif" class=""><span style="font-size: 11px;" class="">15-18 Earlsfort Terrace<br style="background-color: rgb(34, 34, 34);" class="">Dublin 2, County Dublin</span></font><br style="color: rgb(214, 214, 214); font-family: "open sans"; font-size: 12px; background-color: rgb(34, 34, 34);" class=""><font color="#333333" face="arial, helvetica, sans-serif" class=""><span style="font-size: 11px;" class="">Ireland</span></font><br class=""><span style="font-size: 11px;" class=""><span style="font-family: arial, helvetica, sans-serif;" class=""></span></span><br class=""><span style="line-height: 36px;" class=""><a href="https://www.facebook.com/donutstlds" rel="nofollow" target="_blank" id="LPlnk697040" class="OWAAutoLink" previewremoved="true"><img src="http://storage.googleapis.com/signaturesatori/icons/facebook.png" class=""></a> <a href="https://twitter.com/DonutsInc" rel="nofollow" target="_blank" id="LPlnk806449" class="OWAAutoLink" previewremoved="true"><img src="http://storage.googleapis.com/signaturesatori/icons/twitter.png" class=""></a> </span><a href="https://www.linkedin.com/company/donuts-inc" rel="nofollow" target="_blank" id="LPlnk495124" class="OWAAutoLink" previewremoved="true"><span style="font-size: 14px;" class=""><img src="http://storage.googleapis.com/signaturesatori/icons/linkedin.png" class=""></span></a></div></td></tr></tbody></table><br class=""></div><div class=""><span style="font-size: 12pt; font-family: Cambria, serif;" class="">Please NOTE: This electronic message, including any attachments, may include privileged, confidential and/or inside information owned by Donuts Inc. . </span><span style="font-size: 12pt; font-family: Cambria, serif;" class="">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.</span><br class=""></div></div></div></div></div></div></div></div></div></div><br class=""></div></div></div></div></div><br class=""><div class="x_gmail_quote"><div dir="ltr" class="x_gmail_attr">On Tue, Jan 29, 2019 at 1:18 AM Trang Nguyen <<a href="mailto:trang.nguyen@icann.org" target="_blank" id="LPlnk939217" class="OWAAutoLink" previewremoved="true">trang.nguyen@icann.org</a>> wrote:<br class=""></div><blockquote class="x_gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div lang="EN-US" class=""><div class="x_gmail-m_7180990775729884537gmail-m_8182687114185143488gmail-m_6441758728418381503WordSection1"><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: windowtext;" class="">Thank you, Sarah and Kristina for circulating revised text for recommendation 13. We would like to make one additional suggestion: replace “…negotiates and enters into required data protection agreements…” with “…develop and implement any required data protection arrangements…” Referring to an “arrangement” instead of an “agreement” would provide greater flexibility during implementation, which might take the form of an agreement, a policy, or a specification. Accordingly, the following sentence should also refer to “arrangement” instead of “agreement.”<u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: windowtext;" class=""><u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: windowtext;" class="">Also, we would like to ask for clarity on the sentence regarding indemnification. Implementation discussions will work out the details of allocation of responsibility and liability and it’s not clear that liability should necessarily always rest with the party or parties that determine(s) the purposes and means of processing, for example in the case of a data breach. We look forward to additional discussions with the EPDP Team on this. <span class="Apple-converted-space"> </span><u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: windowtext;" class=""><u class=""></u> <u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: windowtext;" class="">Dan and Trang<u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: windowtext;" class="">ICANN Org Liaisons<u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: windowtext;" class=""><u class=""></u> <u class=""></u></span></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-top: 0px; margin-bottom: 0px;" class=""><b class=""><span style="font-size: 20pt;" class="">From:<span class="Apple-converted-space"> </span></span></b><span style="font-size: 20pt;" class="">Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org" target="_blank" id="LPlnk987638" class="OWAAutoLink" previewremoved="true">gnso-epdp-team-bounces@icann.org</a>> on behalf of "Rosette, Kristina via Gnso-epdp-team" <<a href="mailto:gnso-epdp-team@icann.org" target="_blank" id="LPlnk770849" class="OWAAutoLink" previewremoved="true">gnso-epdp-team@icann.org</a>><br class=""><b class="">Reply-To:<span class="Apple-converted-space"> </span></b>"Rosette, Kristina" <<a href="mailto:rosettek@amazon.com" target="_blank" id="LPlnk452123" class="OWAAutoLink" previewremoved="true">rosettek@amazon.com</a>><br class=""><b class="">Date:<span class="Apple-converted-space"> </span></b>Monday, January 28, 2019 at 5:14 PM<br class=""><b class="">To:<span class="Apple-converted-space"> </span></b>"<a href="mailto:gnso-epdp-team@icann.org" target="_blank" id="LPlnk541157" class="OWAAutoLink" previewremoved="true">gnso-epdp-team@icann.org</a>" <<a href="mailto:gnso-epdp-team@icann.org" target="_blank" id="LPlnk243770" class="OWAAutoLink" previewremoved="true">gnso-epdp-team@icann.org</a>><br class=""><b class="">Subject:<span class="Apple-converted-space"> </span></b>Re: [Gnso-epdp-team] Recommendation 13 - Responsibilities of the Parties - email list discussion<u class=""></u><u class=""></u></span></div></div><div class=""><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span style="font-size: 20pt; color: windowtext;" class=""><u class=""></u> <u class=""></u></span></div></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><a name="x_m_7180990775729884537_m_8182687114185143488_m_6441758728418381503__MailOriginalBody" id="LPlnk543729" class="OWAAutoLink" previewremoved="true"><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">All,</span></a><span class=""><span style="font-size: 20pt;" class=""><u class=""></u><u class=""></u></span></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""> </span></span><span class=""><span style="font-size: 20pt;" class=""><u class=""></u><u class=""></u></span></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Subject to a friendly amendment, RySG supports the RrSG proposed text for Recommendation 13. Our friendly amendment is to change “shall” to “should” in the 3<sup class="">rd</sup>sentence. <span class="Apple-converted-space"> </span></span></span><span class=""><span style="font-size: 20pt;" class=""><u class=""></u><u class=""></u></span></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""> </span></span><span class=""><span style="font-size: 20pt;" class=""><u class=""></u><u class=""></u></span></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">As revised, Recommendation 13 reads:</span></span><span class=""><span style="font-size: 20pt;" class=""><u class=""></u><u class=""></u></span></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""> </span></span><span class=""><span style="font-size: 20pt;" class=""><u class=""></u><u class=""></u></span></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><span style="font-size: 20pt; font-family: Verdana, serif;" class="">The EPDP Team recommends that ICANN Org negotiates and enters into required data protection agreements, as appropriate, with the Contracted Parties. In addition to the legally required components of such agreement, the agreement shall specify the responsibilities of the respective parties for the processing activities as described therein. Indemnification clauses should ensure that the risk for certain data processing is borne by either one or multiple parties that determine the purpose and means of the processing. Due consideration should be given to the analysis carried out by the EPDP Team in its Final Report.</span></span><span class=""><span style="font-size: 20pt;" class=""><u class=""></u><u class=""></u></span></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><span style="font-size: 20pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Kristina</span></span><span class=""><span style="font-size: 20pt;" class=""><u class=""></u><u class=""></u></span></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""> </span><u class=""></u><u class=""></u></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class=""><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: windowtext;" class="">From:</span></b></span><span class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: windowtext;" class=""><span class="Apple-converted-space"> </span>Gnso-epdp-team [mailto:<a href="mailto:gnso-epdp-team-bounces@icann.org" target="_blank" id="LPlnk364445" class="OWAAutoLink" previewremoved="true">gnso-epdp-team-bounces@icann.org</a>]<span class="Apple-converted-space"> </span><b class="">On Behalf Of<span class="Apple-converted-space"> </span></b>Sarah Wyld<br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Monday, January 28, 2019 3:29 PM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span><a href="mailto:gnso-epdp-team@icann.org" target="_blank" id="LPlnk454019" class="OWAAutoLink" previewremoved="true">gnso-epdp-team@icann.org</a><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [Gnso-epdp-team] Recommendation 13 - Responsibilities of the Parties - email list discussion</span><u class=""></u><u class=""></u></span></div></div></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""> <u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><span style="font-size: 10pt; font-family: Verdana, serif;" class="">Hello All,</span><u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><span style="font-size: 10pt; font-family: Verdana, serif;" class="">Here is the RrSG's proposed text for Rec 13:</span><u class=""></u><u class=""></u></span></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class=""><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><span style="font-size: 10pt; font-family: Verdana, serif;" class="">The EPDP Team recommends that ICANN Org negotiates and enters into required data protection agreements, as appropriate, with the Contracted Parties. In addition to the legally required components of such agreement, the agreement shall specify the responsibilities of the respective parties for the processing activities as described therein. Indemnification clauses shall ensure that the risk for certain data processing is borne by either one or multiple parties that determine the purpose and means of the processing. Due consideration should be given to the analysis carried out by the EPDP Team in its Final Report.</span><u class=""></u><u class=""></u></span></div></blockquote><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">The RrSG is aware that ICANN's status as controller, joint or independent, is not yet fully determined. As such, this proposed wording allows the flexibility to determine the appropriate type of data protection agreement following further input.<u class=""></u><u class=""></u></span></div><pre class=""><span class="">-- <u class=""></u><u class=""></u></span></pre><pre class=""><span class="">Sarah Wyld<u class=""></u><u class=""></u></span></pre><pre class=""><span class="">Domains Product Team<u class=""></u><u class=""></u></span></pre><pre class=""><span class="">Tucows<u class=""></u><u class=""></u></span></pre><pre class=""><span class="">+1.416 535 0123 Ext. 1392<u class=""></u><u class=""></u></span></pre><pre class=""><span class=""> <u class=""></u><u class=""></u></span></pre><pre class=""><span class=""> <u class=""></u><u class=""></u></span></pre><div class=""><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">On 1/23/2019 6:22 PM, Kurt Pritz wrote:<u class=""></u><u class=""></u></span></div></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class=""><div class=""><div class=""><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">Hi Everyone:<u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">With the goal of progressing on issues via email, the leadership team has considered the discussion provided during the Toronto meeting and suggests the following compromise language to address the different positions expressed. (This is a resend of an earlier email with only the subject line of the email updated.)<u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><b class="">Discussion</b> <u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">The language below is the same language proposed by the small team that reviewed the comments, but modified: <u class=""></u><u class=""></u></span></div><ul type="disc" class=""><li class="x_MsoNormal"><span class="">as suggested by Diane during the meeting to reflect that GDPR Art 28 is unlikely to apply in this situation, and<u class=""></u><u class=""></u></span></li><li class="x_MsoNormal"><span class="">by an addition (bracketed & bolded below) to reference the analysis in the Final Report that this team recommends the creation of Joint Controller Agreements, to appropriately influence the negotiation of GDPR-compliant agreements.<u class=""></u><u class=""></u></span></li></ul><div class=""><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""> <u class=""></u><u class=""></u></span></div></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">This language is intended to strike a balance between those preferring to leave some flexibility for ICANN Org and Contracted Parties to consider the appropriate agreements and those preferring to be specific about the type of agreement to be pursued.<u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">I understand this is a complex topic that might require additional discussion but it is also possible that we cannot be dispositive on this issue prior to a lengthy contract formation discussion that extends well beyond our time frames. For that reason, we are taking the liberty of making this recommendation and hope you accept it in the spirit it is offered.<u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><b class="">Proposed Recommendation #13 Language</b><u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">The EPDP Team recommends that ICANN Org negotiates and enters into required data protection agreements such as a<span class="Apple-converted-space"> </span><s class="">Data Processing Agreement (GDPR Art. 28) or</s><span class="Apple-converted-space"> </span>Joint Controller Agreement (Art. 26), as appropriate, with the Contracted Parties. In addition to the legally required components of such agreement, the agreement shall specify the responsibilities of the respective parties for the processing activities as described therein. Indemnification clauses shall ensure that the risk for certain data processing is borne by either one or multiple parties that determine the purpose and means of the processing. [<b class="">Due consideration should be given to the analysis carried out by the EPDP Team in its Final Report.</b>]<u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><b class="">Action:</b> <u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">Please indicate on the mailing list whether you have any concerns about these modifications and/or what other aspects of this recommendation should be discussed.<u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">Deadline: Monday, 28 January, additional email discussion might follow depending on responses. <u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">Sincerely,<u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">Kurt<u class=""></u><u class=""></u></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""> <u class=""></u><u class=""></u></span></div></div></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><br class=""><br class=""><br class=""><u class=""></u><u class=""></u></span></div><pre class=""><span class="">_______________________________________________<u class=""></u><u class=""></u></span></pre><pre class=""><span class="">Gnso-epdp-team mailing list<u class=""></u><u class=""></u></span></pre><pre class=""><span class=""></span><a href="mailto:Gnso-epdp-team@icann.org" target="_blank" id="LPlnk915732" class="OWAAutoLink" previewremoved="true"><span class="">Gnso-epdp-team@icann.org</span><span class=""></span></a><span class=""><u class=""></u><u class=""></u></span></pre><pre class=""><span class=""></span><a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" target="_blank" id="LPlnk995341" class="OWAAutoLink" previewremoved="true"><span class="">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</span><span class=""></span></a><span class=""><u class=""></u><u class=""></u></span></pre></blockquote></div></div>_______________________________________________<br class="">Gnso-epdp-team mailing list<br class=""><a href="mailto:Gnso-epdp-team@icann.org" target="_blank" id="LPlnk599245" class="OWAAutoLink" previewremoved="true">Gnso-epdp-team@icann.org</a><br class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" rel="noreferrer" target="_blank" id="LPlnk202388" class="OWAAutoLink" previewremoved="true">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></blockquote></div>_______________________________________________<br class="">Gnso-epdp-team mailing list<br class=""><a href="mailto:Gnso-epdp-team@icann.org" target="_blank" id="LPlnk756210" class="OWAAutoLink" previewremoved="true">Gnso-epdp-team@icann.org</a><br class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" target="_blank" id="LPlnk500276" class="OWAAutoLink" previewremoved="true">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">Gnso-epdp-team mailing list<br class=""><a href="mailto:Gnso-epdp-team@icann.org" target="_blank" id="LPlnk797866" class="OWAAutoLink" previewremoved="true">Gnso-epdp-team@icann.org</a><br class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" rel="noreferrer" target="_blank" id="LPlnk429427" class="OWAAutoLink" previewremoved="true">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></blockquote></div></div></div></div></blockquote></div></div></div></div><span style="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; float: none; display: inline !important;" class="">_______________________________________________</span><br style="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;" class=""><span style="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; float: none; display: inline !important;" class="">Gnso-epdp-team mailing list</span><br style="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;" class=""><span style="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; float: none; display: inline !important;" class=""><a href="mailto:Gnso-epdp-team@icann.org" class="">Gnso-epdp-team@icann.org</a></span><br style="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;" class=""><span style="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; float: none; display: inline !important;" class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" class="">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></span></div></blockquote></div><br class=""></div></div>_______________________________________________<br class="">Gnso-epdp-team mailing list<br class=""><a href="mailto:Gnso-epdp-team@icann.org" class="">Gnso-epdp-team@icann.org</a><br class=""><a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" class="">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></div></blockquote></div><br class=""></div></div></div></div>
</div></blockquote></div><br class=""></div></body></html>