<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p><font size="+1"><font face="Lucida Grande">I appreciate this effort Kurt, it looks good. I hate to quibble, but I think this line is not quite accurate with respect to the law.
</font></font><br>
</p>
<div class="moz-cite-prefix">On 2019-02-08 13:25, Kurt Pritz wrote:<br>
</div>
<blockquote type="cite" cite="mid:36E986FF-5472-4867-BF5E-6FD0728FD59C@kjpritz.com">
by either one or multiple parties that determine the purpose and means of the processing.
</blockquote>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><font size="+1"><font face="Lucida
Grande">If a data processor is involved, they are not determining the purpose of the processing....the controller or JC is. Yet there needs to be an agreement with them, establishing
the responsibilities and liabilities, and indeed their carelessness in the event of a breach would be a material factor in the assessment by a DPA. Might I suggest the following instead:</font></font></div>
<div class="moz-cite-prefix"><br>
<blockquote><font size="+1"><font face="Lucida Grande">Indemnification clauses should ensure that the risk for
<strike>certain</strike> data processing is borne, to the extent appropriate, by <strike>
either one or multiple </strike><b>the </b>parties </font></font><b><font size="+1"><font face="Lucida Grande">that are involved</font></font></b><font size="+1"><font face="Lucida Grande"><b> in the processing</b>. Due consideration should be given to
the analysis carried out by the EPDP Team in its Final Report. </font></font></blockquote>
<div class=""><font size="+1">That is a bit vague ("involved") but all parties could be implicated in an investigation, from controller who sets policy, to the processor who pushed the wrong key...</font></div>
<div class=""><font size="+1"><br>
</font></div>
<div class=""><font size="+1">Cheers Stephanie</font></div>
<div class=""><font size="+1"><br>
</font></div>
<div class=""><font size="+1">PS I would note that some laws, especially some of the new post-GDPR drafts coming out, include criminal sanctions for employees of controllers/JCs/ processors. Needs to be kept in mind in the drafting of these agreements.<br class="">
</font></div>
<font size="+1"></font></div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2019-02-08 13:25, Kurt Pritz wrote:<br>
</div>
<blockquote type="cite" cite="mid:36E986FF-5472-4867-BF5E-6FD0728FD59C@kjpritz.com">
Hi Everyone:
<div class=""><br class="">
</div>
<div class="">To summarize this discussion:</div>
<div class=""><br class="">
</div>
<div class="">We have read Trang’s intervention carefully and recognize the wording referenced in the GDPR. In this email chain, we also recognized the research that Thomas (with Farzaneh) conducted in forming their advice to this team and Alan’s reference
to local laws and authoritative GDPR guidance. After considering that, </div>
<div class=""><br class="">
</div>
<div class="">1) I have not seen any team member representing a Stakeholder Group or Advisory Committee recommend a departure from the use of the word “agreement’ in the recommendation. I.e., I have not seen support for changing “agreement” to “arrangement.”
Kavouss has made a good faith offer of compromise in suggesting “mutually agreed upon…” but I don’t see the purpose of compromise at this juncture. Without describing the rationale for staying with “agreement,” I can easily see reasons why each SO/AC here
would appreciate that level of specificity. </div>
<div class=""><br class="">
</div>
<div class="">2) While I agree with the conclusions Thomas has reached regarding the requirement for JCAs, I think the wording currently proposed (by the contracted parities and supported by the GAC) is acceptable in order to provide the parties negotiating
the ability to determine which processing steps are best addressed with the parties as Joint Controllers, Controllers and Processors. </div>
<div class=""><br class="">
</div>
<div class="">3) With regard to concerns about the clause, “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," as raised by Chris,
I don’t read this as meaning that all liability is borne by the Controller, or as Chris states the ICANN Board concern, “by ICANN.” For example, negligence on the part of a processor should not raise liability in the Controller absent some specific circumstances. </div>
<div class=""><br class="">
</div>
<div class="">On this last topic, I think we ae waiting to hear more from the Board or elsewhere in ICANN. Itaking Chris recommendation into account and doing some type of mashup: “Indemnification clauses shall ensure that the risk for certain data processing
is borne, <i class=""><font class="" color="#0433ff">to the extent appropriate</font></i>, by either one or multiple parties that determine the purpose and means of the processing."</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">In total:</div>
<div class=""><br class="">
</div>
<div 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, to the extent appropriate, 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.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Please respond and let me know whether you believe this to be an appropriate solution. </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 style=""><br class="">
<blockquote type="cite" class="">
<div class="">On Feb 8, 2019, at 5:05 AM, Emily Taylor <<a href="mailto:emily.taylor@oxil.co.uk" class="" moz-do-not-send="true">emily.taylor@oxil.co.uk</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Hi all
<div class=""><br class="">
</div>
<div class="">I support Alan's point of view. While I understand the need to retain flexibility, and to avoid overly restrictive language that will cause problems later on, the word 'arrangement' could mean almost anything - from something that imposes legal
benefits and responsibilities to something that's very informal, undocumented and just a way of working.</div>
<div class=""><br class="">
So, I support use of the word 'agreement' instead of 'arrangement'.</div>
<div class=""><br class="">
</div>
<div class="">Best wishes</div>
<div class=""><br class="">
Emily</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Feb 8, 2019 at 1:02 PM Alan Woods <<a href="mailto:alan@donuts.email" class="" moz-do-not-send="true">alan@donuts.email</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">Just to be exceptionally clear and although I do not wish to belabor the point any farther, I still submit, on the record, that the correct term to be used in the recommendation is 'AGREEMENT'
<div class=""><br class="">
</div>
<div class="">Whereas I appreciate that ICANN have mirrored the GDPR language of Art 26 in their use of the word of 'arrangement' I believe it would make more sense to consider the subsequent interpretation of their lead DPA (i.e Belgium, as confirmed by the
Belgian Autorité de Protection des Données (APD) letter of <a href="https://www.icann.org/en/system/files/correspondence/debeuckelaere-to-marby-15jan19-en.pdf" target="_blank" class="" moz-do-not-send="true">
15th January 2019 </a> and the therein referenced letter of <a href="https://www.icann.org/en/system/files/correspondence/debeuckelaere-to-marby-26sep18-en.pdf" target="_blank" class="" moz-do-not-send="true">
September 26th, 2018</a> ).</div>
<div class=""><br class="">
</div>
<div class="">I would therefore respectfully submit that it remains more proper for our recommendation to therefore consider and mirror the Belgian legislatures and the APD's interpretation of the GDPR as being our guiding, if not determinative factor:
<div class=""><br class="">
</div>
<div class=""><b class="">1)</b> <b class="">Article 52</b> of the <a href="http://www.ejustice.just.fgov.be/cgi_loi/loi_a.pl?language=fr&dt=LOI&chercher=t&choix1=ET&fr=f&choix2=ET&numero=12&table_name=LOI&fromtab=loi_all&imgcn.x=32&DETAIL=2018073046/F&nm=2018040581&imgcn.y=3&ddda=2018&sql=dt+contains++%27LOI%27+and+dd+=+date%272018-07-30%27and+actif+=+%27Y%27&rech=12&tri=dd+AS+RANK+&trier=promulgation&dddj=30&cn=2018073046&row_id=1&caller=image_a1&dddm=07&la=F&pdf_page=10&pdf_file=http://www.ejustice.just.fgov.be/mopdf/2018/09/05_1.pdf" target="_blank" class="" moz-do-not-send="true"> Loi
relative à la protection des personnes physiques à l’égard des traitements de données à caractère personnel (30 July 2018)</a> (see page 27 of the Gazette as linked) requires</div>
<div class=""><br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px
0px 0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
" <b class=""><i class="">Un accord définit de manière transparente les obligations respectives des responsables conjoints de traitement</i></b>, " [emphasis added], </blockquote>
<div class=""><br class="">
</div>
<div class="">Which translates to "<b class=""><u class="">an agreement</u></b> which defines the respective obligations of the joint controllers" [emphasis added]</div>
<div class=""><br class="">
</div>
<div class=""><b class="">2)</b> The APD have also released a<a href="https://www.autoriteprotectiondonnees.be/sites/privacycommission/files/documents/Notions_RT_ST.pdf" target="_blank" class="" moz-do-not-send="true"> legal notation of the July 2018 law</a>,
and they note the joint controller requirement as being "<b class=""><i class="">par voie d’accord</i></b>' (see page three under heading or again to translate, is an "by agreement". (see page 3 under the heading "<b class="">Responsables conjoints de traitment"</b>)</div>
<div class=""><br class="">
</div>
<div class="">Therefore I still believe and submit that the ePDP teams original wording of "agreement" should stand, and I don't believe that ICANN's reference to their past statement i.e. "<span style="font-size:9pt" class=""><i class="">arrangement”</i>
could take the form of an agreement, a policy, or a specification" is sufficient as it dilutes the expectation of the APD. This is not sufficiently specific in the circumstances; nor does it provide the comfort that the ePDP team is seeking in this recommendation
from ICANN.</span></div>
<div class=""><span style="font-size:9pt" class=""><br class="">
</span></div>
<div class=""><span style="font-size:9pt" class="">Kind regards,</span></div>
<div class=""><span style="font-size:9pt" class=""><br class="">
</span></div>
<div class=""><span style="font-size:9pt" class="">Alan </span></div>
<div class=""><span style="font-size:9pt" class=""><br class="">
</span></div>
<div class=""><span style="font-size:9pt" class=""> </span></div>
<div class=""><span style="font-size:9pt" class=""><br class="">
</span></div>
<div class=""><span style="font-size:9pt" class=""> </span><br class="">
</div>
<div class="">
<div class=""><br class="">
</div>
<div class="">
<div class=""><br class="">
</div>
<div class=""><br class="">
<div class="">
<div class="">
<div dir="ltr" class="gmail-m_3375561262016247549gmail_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" class="" moz-do-not-send="true"><img alt="Donuts Inc." src="https://storage.googleapis.com/signaturesatori/customer-C02zzlf7k/images/-54f9d8ac97e7f575bf497d10ac1f1aafafddf8afceab5f269d49034f01b3217b.png" class="" moz-do-not-send="true" width="75" height="75"></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 class="" face="arial,
helvetica,
sans-serif" color="#333333"><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 class="" face="arial,
helvetica,
sans-serif" color="#333333"><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" class="" moz-do-not-send="true"><img src="http://storage.googleapis.com/signaturesatori/icons/facebook.png" class="" moz-do-not-send="true"></a> <a href="https://twitter.com/DonutsInc" rel="nofollow" target="_blank" class="" moz-do-not-send="true"><img src="http://storage.googleapis.com/signaturesatori/icons/twitter.png" class="" moz-do-not-send="true"></a> </span><a href="https://www.linkedin.com/company/donuts-inc" rel="nofollow" target="_blank" class="" moz-do-not-send="true"><span style="font-size:14px" class=""><img src="http://storage.googleapis.com/signaturesatori/icons/linkedin.png" class="" moz-do-not-send="true"></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>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Feb 8, 2019 at 11:28 AM Kavouss Arasteh <<a href="mailto:kavouss.arasteh@gmail.com" target="_blank" class="" moz-do-not-send="true">kavouss.arasteh@gmail.com</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div class="">Dear Kurt</div>
<div class="">I have indicated at several occasions that when we refer to an action to be performed by two parties / entities ,we need to indicated " as mutually agreed" The proposed text to be amended to read as below</div>
<div class="">
<div style="margin: 0px; text-align: left;
color: rgb(34, 34, 34); text-transform:
none; text-indent: 0px; letter-spacing:
normal; font-family: Arial, Helvetica,
sans-serif; font-size: 13.33px; font-style:
normal; font-variant-ligatures: normal;
font-variant-caps: normal;
font-variant-east-asian: normal;
font-variant-position: normal; font-weight:
400; text-decoration: none; word-spacing:
0px; white-space: normal; background-color:
transparent;" class="">
The EPDP Team recommends that ICANN Org negotiates and enters into required data protection agreements such as a
<s class="">Data Processing Agreement (GDPR Art. 28) or</s> 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, "AS MUTUALLY AGREED " 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>]</div>
<div style="margin: 0px; text-align: left;
color: rgb(34, 34, 34); text-transform:
none; text-indent: 0px; letter-spacing:
normal; font-family: Arial, Helvetica,
sans-serif; font-size: 13.33px; font-style:
normal; font-variant-ligatures: normal;
font-variant-caps: normal;
font-variant-east-asian: normal;
font-variant-position: normal; font-weight:
400; text-decoration: none; word-spacing:
0px; white-space: normal; background-color:
transparent;" class="">
<b class="">Action:</b> </div>
<div style="margin: 0px; text-align: left;
color: rgb(34, 34, 34); text-transform:
none; text-indent: 0px; letter-spacing:
normal; font-family: Arial, Helvetica,
sans-serif; font-size: 13.33px; font-style:
normal; font-variant-ligatures: normal;
font-variant-caps: normal;
font-variant-east-asian: normal;
font-variant-position: normal; font-weight:
400; text-decoration: none; word-spacing:
0px; white-space: normal; background-color:
transparent;" 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.</div>
<div style="margin: 0px; text-align: left;
color: rgb(34, 34, 34); text-transform:
none; text-indent: 0px; letter-spacing:
normal; font-family: Arial, Helvetica,
sans-serif; font-size: 13.33px; font-style:
normal; font-variant-ligatures: normal;
font-variant-caps: normal;
font-variant-east-asian: normal;
font-variant-position: normal; font-weight:
400; text-decoration: none; word-spacing:
0px; white-space: normal; background-color:
transparent;" class="">
Deadline: Monday, 28 January, additional email discussion might follow depending on responses. </div>
<div style="margin: 0px; text-align: left;
color: rgb(34, 34, 34); text-transform:
none; text-indent: 0px; letter-spacing:
normal; font-family: Arial, Helvetica,
sans-serif; font-size: 13.33px; font-style:
normal; font-variant-ligatures: normal;
font-variant-caps: normal;
font-variant-east-asian: normal;
font-variant-position: normal; font-weight:
400; text-decoration: none; word-spacing:
0px; white-space: normal; background-color:
transparent;" class="">
Please kindly insert that in the text</div>
<div style="margin: 0px; text-align: left;
color: rgb(34, 34, 34); text-transform:
none; text-indent: 0px; letter-spacing:
normal; font-family: Arial, Helvetica,
sans-serif; font-size: 13.33px; font-style:
normal; font-variant-ligatures: normal;
font-variant-caps: normal;
font-variant-east-asian: normal;
font-variant-position: normal; font-weight:
400; text-decoration: none; word-spacing:
0px; white-space: normal; background-color:
transparent;" class="">
Regards</div>
<div style="margin: 0px; text-align: left;
color: rgb(34, 34, 34); text-transform:
none; text-indent: 0px; letter-spacing:
normal; font-family: Arial, Helvetica,
sans-serif; font-size: 13.33px; font-style:
normal; font-variant-ligatures: normal;
font-variant-caps: normal;
font-variant-east-asian: normal;
font-variant-position: normal; font-weight:
400; text-decoration: none; word-spacing:
0px; white-space: normal; background-color:
transparent;" class="">
Kavouss </div>
</div>
</div>
</div>
<br class="">
<div class="gmail_quote">
<div class="gmail_attr" dir="ltr">On Thu, Jan 24, 2019 at 12:23 AM Kurt Pritz <<a href="mailto:kurt@kjpritz.com" target="_blank" class="" moz-do-not-send="true">kurt@kjpritz.com</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px
0px 0px 0.8ex;padding-left:1ex;border-left:1px
solid rgb(204,204,204)">
<div class="">
<div class="">
<div class="">
<p class="MsoNormal">Hi Everyone:</p>
<p class="MsoNormal">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.)</p>
<p class="MsoNormal"><b class="">Discussion</b> </p>
<p class="MsoNormal">The language below is the same language proposed by the small team that reviewed the comments, but modified: </p>
<ul class="gmail-m_3375561262016247549gmail-m_-2733901818341682331gmail-m_6983950863803071002MailOutline">
<li class="">a<span class="">s suggested by Diane during the meeting to reflect that GDPR Art 28 is unlikely to apply in this situation, and</span></li><li class=""><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.</span></li></ul>
<div class=""><br class="gmail-m_3375561262016247549gmail-m_-2733901818341682331gmail-m_6983950863803071002webkit-block-placeholder">
</div>
<p class="MsoNormal">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.</p>
<p class="MsoNormal">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.</p>
<p class="MsoNormal"><b class="">Proposed Recommendation #13 Language</b></p>
<p class="MsoNormal">The EPDP Team recommends that ICANN Org negotiates and enters into required data protection agreements such as a
<s class="">Data Processing Agreement (GDPR Art. 28) or</s> 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>]</p>
<p class="MsoNormal"><b class="">Action:</b> </p>
<p class="MsoNormal">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.</p>
<p class="MsoNormal">Deadline: Monday, 28 January, additional email discussion might follow depending on responses. </p>
<p class="MsoNormal">Sincerely,</p>
<p class="MsoNormal">Kurt</p>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
_______________________________________________<br class="">
Gnso-epdp-team mailing list<br class="">
<a href="mailto:Gnso-epdp-team@icann.org" target="_blank" class="" moz-do-not-send="true">Gnso-epdp-team@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" rel="noreferrer" target="_blank" class="" moz-do-not-send="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" class="" moz-do-not-send="true">Gnso-epdp-team@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" rel="noreferrer" target="_blank" class="" moz-do-not-send="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" class="" moz-do-not-send="true">Gnso-epdp-team@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" rel="noreferrer" target="_blank" class="" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></blockquote>
</div>
<br class="" clear="all">
<div class=""><br class="">
</div>
-- <br class="">
<div dir="ltr" class="gmail_signature">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div style="margin:
0px; font-weight:
bold;" class="">
<font class="" face="arial,
helvetica,
sans-serif">Emily Taylor</font></div>
<p style="margin-bottom:1.5em;margin-top:0px" class=""><font class=""><font class="" face="arial,
helvetica,
sans-serif">CEO, Oxford Information
Labs<br class="">
</font><i class=""><font style="font-size:12.8px" class="" face="arial, helvetica, sans-serif">MA (Cantab), Solicitor (non-practising), MBA, </font></i></font></p>
<p style="margin-bottom:1.5em;margin-top:0px" class=""><font class=""><i class=""><font style="font-size:12.8px" class="" face="arial,
helvetica,
sans-serif">A</font></i><i style="font-size:12.8px" class=""><font style="font-size:12.8px" class="" face="arial,
helvetica,
sans-serif">ssociate
Fellow, Chatham House; </font><span style="font-size:12.8px;font-family:arial,helvetica,sans-serif" class="">Editor, Journal of Cyber Policy</span></i></font></p>
<p style="font-size:12.8px;margin-bottom:60px" class=""><font class=""><span style="font-size:12.8px;font-family:arial,helvetica,sans-serif" class="">Lincoln House, Pony Road, Oxford OX4 2RD </span><span style="font-size:12.8px;font-family:arial,helvetica,sans-serif" class="">|
T:</span><span style="font-size:12.8px;font-family:arial,helvetica,sans-serif" class=""> 01865 582885 <br class="">
</span><span style="font-size:12.8px;font-family:arial,helvetica,sans-serif" class="">E:</span><span style="font-size:12.8px;font-family:arial,helvetica,sans-serif" class=""> </span><a href="mailto:emily.taylor@oxil.co.uk" style="font-size:12.8px;font-family:arial,helvetica,sans-serif" target="_blank" class="" moz-do-not-send="true">emily.taylor@oxil.co.uk</a><span style="font-size:12.8px;font-family:arial,helvetica,sans-serif" class=""> </span><span style="font-size:12.8px;font-family:arial,helvetica,sans-serif" class="">|
D:</span><span style="font-size:12.8px;font-family:arial,helvetica,sans-serif" class=""> 01865 582811 </span><span style="font-size:12.8px;font-family:arial,helvetica,sans-serif" class="">| M:</span><span style="font-size:12.8px;font-family:arial,helvetica,sans-serif" class=""> </span><a value="+447799766676" style="font-size:12.8px;font-family:arial,helvetica,sans-serif" class="" moz-do-not-send="true">+44
7540 049322</a></font></p>
<div style="margin-bottom:
60px;" class="">
<br class="webkit-block-placeholder">
</div>
<p style="margin-bottom:60px" class=""><a href="http://explore.tandfonline.com/cfp/pgas/rcyb-cfp-2017" style="font-size:12.8px" target="_blank" class="" moz-do-not-send="true"><img src="https://drive.google.com/a/oxil.co.uk/uc?id=1-3eDLYPfLpkj30Jc34NcbkD1xt8NQpU8&export=download" class="" moz-do-not-send="true" width="200" height="81"></a><a href="http://explore.tandfonline.com/cfp/pgas/rcyb-cfp-2017" style="font-size:12.8px" target="_blank" class="" moz-do-not-send="true"><img src="https://docs.google.com/a/oxil.co.uk/uc?id=0B7sS_6djDxsHNm92d21jM21HMDQ&export=download" alt="" class="" moz-do-not-send="true" width="420" height="63"></a></p>
<p style="margin-bottom:60px" class=""><font class="" face="arial,
helvetica,
sans-serif"><a value="+447799766676" class="" moz-do-not-send="true"><br class="">
</a></font></p>
<p style="font-size:small;color:rgb(170,170,170);font-family:arial,helvetica,san-serif" class="">
Registered office: Lincoln House, 4 Pony Road, Oxford OX4 2RD. Registered in England and Wales No. 4520925. VAT No. 799526263<br class="">
<br class="">
.<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br class="">
Gnso-epdp-team mailing list<br class="">
<a href="mailto:Gnso-epdp-team@icann.org" class="" moz-do-not-send="true">Gnso-epdp-team@icann.org</a><br class="">
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></div>
</blockquote>
</div>
<br class="">
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Gnso-epdp-team mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-epdp-team@icann.org">Gnso-epdp-team@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a></pre>
</blockquote>
</body>
</html>