<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Hi Marika, hi all</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Thank you for sending this document. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">A couple of observations: legitimate interest was actually in force in the past in the European Directive and as indicated in the doc you shared as well there have been court cases about it. ICO has a lot of materials, but there are many other sources out there. </div><div class="gmail_default" style="font-family:verdana,sans-serif">I can see that in this sheet we have considered some of the criteria that are necessary to establish a legitimate interest in the response but looks like we might need to consider a couple of things</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">The set of pre-requisite that is needed to establish legitimate interest: - Disclosure is necessary to achieve the outcome that the third party has in mind (in this case, for trademark owners to bring legal action against violation of trademark through domain name registration)</div><div class="gmail_default" style="font-family:verdana,sans-serif">- There is no alternative to achieve the desired outcome other than disclosure (Is there no other alternative to establish rights and bring a lawsuit against the trademark infringing domain name registrant?)</div><div class="gmail_default" style="font-family:verdana,sans-serif">- Balancing test: The registrant reasonably expects that data will be disclosed in such cases, the data is not too sensitive, and safeguards have been put in place to mitigate risks. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">The contracted parties have been dealing with this so perhaps they know better how to legally deal with it. But I don't see alternatives to disclosure discussed in this document. can bringing legal action against the domain name registrants only happen if their personal data is known and disclosed? At least in the US there are some circumstances under which you don't have to identify the domain name registrant ( i.e. know their personal information) to bring legal action against them, in cases when it is about the cancellation and transfer of the domain names . The ICJ case that is cited in this document was about "identification" and tangible property and seeking damages. Because it was impossible to file a case against the defendant without identifying him the court ruling allowed disclosure. So I don't think it will help us to invoke the ICJ case for establishing all the rights.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">- I am not trying to make disclosure more difficult. I am just pointing out that we need to probably discuss more and make clarifications. for example in B) we could highlight that the disclosure should happen only in cases where legal action is not possible to commence or proceed without the disclosure of nonpublic registration data. </div><div class="gmail_default" style="font-family:verdana,sans-serif">The requestor can provide evidence of laws, procedural rules etc that proves the necessity. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">- I am not so sure about d). Especially this paragraph: "<span style="font-family:Calibri,sans-serif;font-size:11pt">In view of the alleged involvement of the
registrant in an infringement, it cannot be assumed that in these cases the
interests of the registrant in the protection of his data outweigh the interest
in the protection of IP rights. "</span><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">First , can we start using neutral pronouns or at least have he/she or even s/he. Women have started owning IP rights. </div><div class="gmail_default" style="font-family:verdana,sans-serif">Secondly, I really don't think we are justifying disclosure by applying the balancing test (data is not too sensitive, safeguards are in place to mitigate risk). We cannot just argue that because the registrant "allegedly" is involved with infringement we cannot assume.. that's kind of a vicious circle. It's like arguing that: I want to have access to the personal information because I want to take legal action and by the way such disclosure won't override the data subject rights because I want to take legal action against the defendant! </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Instead we need to say we have considered mitigating risks, such as the safeguards we underlined and have evaluated the sensitivity of data considering the context of the case.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">- Also on e) and f) h) it is better not to say safeguards "applicable" to the requestor and to the entity disclosing the data. It might be clearer to say safeguard the ---- must implement </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">- Last point. I do not think we should discuss accreditation before we actually talk about why we want to use accreditation as a part of disclosure policy.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Best </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div><div dir="ltr" class="m_-3401772290880086747m_3009992042096907663gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 25, 2019 at 5:45 PM Marika Konings <<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-3401772290880086747gmail-m_3009992042096907663gmail-m_1525670659659452238WordSection1">
<p class="MsoNormal"><span style="font-size:11pt">Dear EPDP Team,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Please find attached for your review the updated Trademark owners requesting data in the establishment, exercise or defense of legal claims for trademark infringement use case. In this updated version, we’ve
aimed to address the comments and suggestions made during today’s session, but we’ve also taken the liberty to reorganize some of the sections to make it clear to whom certain safeguards apply. We’ve attached both the redline and clean version, but as the
reorganization has resulted in a lot of redlines due to formatting and relocation of text, we would recommend you review the clean version. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Please review this version and share in advance of Thursday’s meeting any comments, edits or suggestions, especially in relation to the sections that were not specifically discussed yet.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Best regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt">Caitlin, Berry and Marika</span><span style="font-size:11pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><i><span style="font-size:10pt;color:black">Marika Konings</span></i></b><span style="font-size:10pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:10pt;color:black">Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) </span></i><span style="font-size:10pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:10pt;color:black">Email: <a href="mailto:marika.konings@icann.org" target="_blank"><span style="color:rgb(5,99,193)">marika.konings@icann.org</span></a> </span></i><span style="font-size:10pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:10pt;color:black"> </span></i><span style="font-size:10pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:10pt;color:black">Follow the GNSO via Twitter @ICANN_GNSO</span></i><span style="font-size:10pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><i><span style="font-size:10pt;color:black">Find out more about the GNSO by taking our <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=" target="_blank"><span style="color:rgb(5,99,193)">interactive
courses</span></a> and visiting the <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=" target="_blank"><span style="color:rgb(5,99,193)">GNSO
Newcomer pages</span></a>. </span></i><span style="font-size:10pt;color:black"><u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br>
Gnso-epdp-team mailing list<br>
<a href="mailto:Gnso-epdp-team@icann.org" target="_blank">Gnso-epdp-team@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a><br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div>