<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:569117089;
mso-list-type:hybrid;
mso-list-template-ids:1054505710 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1449474716;
mso-list-type:hybrid;
mso-list-template-ids:-1963698238 1193966806 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
color:black;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2
{mso-list-id:1626040266;
mso-list-type:hybrid;
mso-list-template-ids:-212797236 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l3
{mso-list-id:1991056162;
mso-list-type:hybrid;
mso-list-template-ids:-1569715600 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l3:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l3:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l3:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Brian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If you are being realistic, you are going to have to get yourself and your constituency mentally ready for the fact that TM challenges are never going to be automated. A TM-based disclosure request for domain
registration data will in all cases involve a balancing test of two fundamental rights: the IP owner’s property right and the registrant’s privacy right. It is impossible for automated disclosure to encompass a balancing test.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The logical basis of your argument is, “humans have failed us because they didn’t approve all of our requests.” With this argument, you could not be doing a better job of making my case for me. Your request for
automation is in essence a demand for all of your requests to be granted. It is founded on the notion that any disclosure request an IP owner makes is legitimate and cannot be wrong. We have already been told that this is not legal, because that is the old
Whois. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Can you answer a simple question for me? What is the point of having ANY redacted data if any TM or IP owner can get it automatically whenever they think they need it?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">--MM<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Gnso-epdp-team <gnso-epdp-team-bounces@icann.org>
<b>On Behalf Of </b>King, Brian via Gnso-epdp-team<br>
<b>Sent:</b> Sunday, February 2, 2020 9:39 PM<br>
<b>To:</b> gnso-epdp-team@icann.org<br>
<b>Subject:</b> Re: [Gnso-epdp-team] IPC Proposal for Day 1 Automation<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Milton, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have drafted what we think are legally sufficient safeguards, and despite our request, we note that you did not suggest any further safeguards. I take this to mean that you have legal comfort with the safeguards we have suggested, and
that you have policy (as opposed to legal) concerns with automating this use case. We’re happy to engage in constructive policy conversations around any additional safeguards you think are needed to minimize the potential for abuse – to be clear though, are
your concerns legal concerns, or policy concerns? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In case I’m mischaracterizing your concerns as policy-only, I tried to be clearly “legal” in my comments in line with your message below.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">“Policy” comments follow here: <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l1 level1 lfo1"><span style="color:black">Your assertion that prima facie reasonable requests will be granted is wholly inconsistent with IP owners’ experience under GDPR. MarkMonitor’s industry-best brand protection analysts
manually sent requests to over 50 registrars for over 1000 domain names infringing more than 15 of the most well-known brands in the world, and were ignored or denied over 85% of the time. With very few exceptions, humans have largely failed IP interests.
</span><o:p></o:p></li></ol>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoNormal" style="mso-list:l1 level1 lfo1"><span style="color:black">All parties (except some folks in NCSG, maybe?) prefer automation to maximize predictability and standardization, and minimize cost, so long as automation is legally sound. We think
in this case, it is. </span><o:p></o:p></li></ol>
<p class="MsoListParagraph"><o:p> </o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="mso-list:l1 level1 lfo1"><span style="color:black">In a broader sort of “balancing test,” we offer the following perspective: the DNS allows bad actors to infringe IP fundamental rights without manual preliminary review. The only
ex ante safeguard the DNS offers IP fundamental rights is that registrants must merely agree that they’re not infringing, and in some limited cases (for new gTLDs) they may be notified that their registration could be infringing. There is no benefit of manual
preliminary review to protect the fundamental rights of IP owners. </span><o:p></o:p></li></ol>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph"><span style="color:black">In seeking legal, automated access in limited cases, we are merely proposing closer-to-equal treatment for the fundamental rights our group represents. In fact, the IPC has actually proposed far greater
safeguards for infringing registrants than IP owners receive. Registrants are not subject to limits on how many domain names they can register; however, we are proposing reasonable limits requestors’ access. Registrants are not required to prove their identity
or become “accredited” before they can register a domain name; however, we are proposing that all SSAD users are accredited. Registrants are not subject to being “de-accredited” from the DNS for infringement; however, we are proposing de-accreditation from
SSAD for abusive users. <o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph"><span style="color:black">The fundamental rights we represent do not receive the benefit of manual ex ante review, and to be clear, we’re not asking for that here. We do, however, need to decide as a policy matter to come closer
to restoring balance to the force. We must do that by ensuring access that is not unnecessarily delayed or made unreliable by unnecessary manual review.
<o:p></o:p></span></p>
<p class="MsoListParagraph"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:10.0pt;color:black">Brian J. King
</span></b><span lang="EN-GB" style="font-size:10.0pt;color:black"> <br>
Director of Internet Policy and Industry Affairs<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;color:black">T +1 443 761 3726</span><u><span style="font-size:10.0pt;color:#0563C1"><a href="http://www.markmonitor.com"><span lang="EN-GB"><br>
</span>markmonitor.com</a></span></u><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:10.0pt;color:black">MarkMonitor<br>
</span></b><span lang="EN-GB" style="font-size:10.0pt;color:black">Protecting companies and consumers in a digital world<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org">gnso-epdp-team-bounces@icann.org</a>>
<b>On Behalf Of </b>Mueller, Milton L<br>
<b>Sent:</b> Friday, January 31, 2020 4:59 PM<br>
<b>To:</b> <a href="mailto:gnso-epdp-team@icann.org">gnso-epdp-team@icann.org</a><br>
<b>Subject:</b> [Gnso-epdp-team] FW: IPC Proposal for Day 1 Automation<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Brian:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">></span>Since the free speech example would not be trademark infringement, the
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">></span>requestor could not cite that basis to request data for a domain like this.
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">LOL. That’s the problem with automation, Brian. They could cite any basis they pleased and they would get the data. There would be no opportunity to challenge it. No one would even see it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal">-They really couldn’t. In this use case, we’re talking about limited cases where someone has a fundamental right to their intellectual property. That fundamental right further needs to be registered in a government registry (although many
IP rights do not require such registration), and their ownership of the trademark needs to be verified by the ICANN-run Accreditation Authority. Then, we’re proposing to limit their requests to domain names which contain exactly the string of characters to
which the requestor has a fundamental right to some exclusivity, and which they allege is infringing. So, the “they” is extremely limited to entities with established fundamental rights, and the “basis” is limited solely to pursuing the alleged TM infringement.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">> </span>Remember that in this use case we’re requiring that the requestor allege
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">> </span>infringement, and fraud or misrepresentation can result in deaccreditation.<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">></span>The additional noteworthy safeguards we mention below are tied to this
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">></span>representation: that the requestor has a good-faith belief that the domain name is infringing.
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">></span>Do you think additional safeguards are required? If so, why? Which ones would you suggest?
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Trademark owners often sincerely believe that any use of their mark in any circumstance is an infringement. I invite you to read 1,000 UDRP cases or so if you doubt this. This is no safeguard at all.
<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-You’re missing the value of this safeguard: <o:p></o:p></p>
<p class="MsoNormal">1. Requiring this representation allows ICANN to rely on it. This, coupled with the extensive upfront TM validation referenced above and the other safeguards, gives ICANN clear legal basis to disclose in the limited circumstances we’re
considering here. <o:p></o:p></p>
<p class="MsoNormal">2. Requiring this representation has three benefits vis-à-vis the requestor: a) it serves as grounds for de-accreditation of abusive requestors, b) it serves as a deterrent against the same (e.g. attorneys would be barred by ethics rules
from making bad-faith requests), and c) TM owners are required by law to police the use of their marks at the risk of losing legal protection, and losing this ability is an incredibly strong deterrent against abuse.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">And oh by the way, if the process is automated how is anyone supposed to know what was alleged and how well the allegations matched the actual case? By doing a laborious after the fact log check after millions
of disclosures have been made? </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-Yes, we have this covered in the logging and auditing portions of the initial report. Do you have any suggestions for improvements on those?
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Do we both understand the meaning of the term “automated” here? It means, you enter a query and you get results, no human intervention.
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">-Yes, this feature is cost-saving and risk-mitigating. The human intervention is actually quite extensive, and it’s done upfront in policy making, accreditation, etc.
<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">></span>As a final point on your note below, it seems like you think the legal standard for disclosure
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">></span>is proof of infringement.
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">No of course I do not think that. You do not need to prove infringement to get disclosure. But we are not having an argument about the criteria for disclosure, we are having an argument about when we can _<i>automate</i>_
disclosure. You seem to be assuming that if these requests are not automated there will be no disclosure. Clearly that is not the case. You will make a request, it will be reviewed by a human, and if it is prima facie reasonable, you will get disclosure.
I will even say that in most cases disclosure will be routine, because the pattern of a domain suspect of trademark infringing is quite common. But routinization is not automation. You can have the former but not the latter.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Dr. Milton L Mueller<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">School of Public Policy <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Georgia Institute of Technology<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><img border="0" width="193" height="41" style="width:2.0104in;height:.427in" id="Picture_x0020_1" src="cid:image001.jpg@01D5DA87.2D419310" alt="IGP_logo_gold block_email sig"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">Hi Milton, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The penultimate sentence in your note below is unhelpful, factually incorrect, and inconsistent with guidance we’ve been given repeatedly not to attribute motive to others’ positions. That said, we welcome substantive discussion on our
proposal and invite you to engage in that manner going forward. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Since the free speech example would not be trademark infringement, the requestor could not cite that basis to request data for a domain like this. Remember that in this use case we’re requiring that the requestor allege infringement, and
fraud or misrepresentation can result in deaccreditation. The additional noteworthy safeguards we mention below are tied to this representation: that the requestor has a good-faith belief that the domain name is infringing. Do you think additional safeguards
are required? If so, why? Which ones would you suggest? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As a final point on your note below, it seems like you think the legal standard for disclosure is proof of infringement. That’s not the case. GDPR allows processing for the “establishment, exercise or defence of legal claims” (emphasis
here on establishment, as opposed to proof). Processing for the establishment of legal claims is explicitly allowed above the data subject’s right to erasure, right to restriction of processing, and right to object.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Again, we welcome constructive suggestions as to what additional safeguards you think might be needed to ensure the data is requested for the establishment of a legal claim. Thank you.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:10.0pt;color:black">Brian J. King
</span></b><span lang="EN-GB" style="font-size:10.0pt;color:black"> <br>
Director of Internet Policy and Industry Affairs<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;color:black">T +1 443 761 3726</span><u><span style="font-size:10.0pt;color:#0563C1"><a href="http://www.markmonitor.com"><span lang="EN-GB"><br>
</span>markmonitor.com</a></span></u><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:10.0pt;color:black">MarkMonitor<br>
</span></b><span lang="EN-GB" style="font-size:10.0pt;color:black">Protecting companies and consumers in a digital world<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>From:</b> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org">gnso-epdp-team-bounces@icann.org</a>>
<b>On Behalf Of </b>Mueller, Milton L<br>
<b>Sent:</b> Thursday, January 30, 2020 1:14 PM<br>
<b>To:</b> <a href="mailto:gnso-epdp-team@icann.org">gnso-epdp-team@icann.org</a><br>
<b>Subject:</b> [Gnso-epdp-team] FW: IPC Proposal for Day 1 Automation<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Brian there are many holes in this call for automation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The most obvious being that the presence of an exact string match of a trademark is not by itself an infringement of a trademark.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">There are many cases of free expression use of a string, such as “don’t-buy-nike.TLD”
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">There are accidental string matches or generic uses. There are uses in different industries that are not confusingly similar.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Your mention of the so-called “noteworthy safeguards” is laughably irrelevant, as it basically presumes that the requestor’s interest in disclosure is proof of infringement. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">While MarkMonitor’s business interest in automatic searching, requesting and intimidation of domain name registrants via demand letters is clear, I do not think that our policies need to be built around those
business interests. If you believe a domain is infringing, file a UDRP. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Dr. Milton L Mueller<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">School of Public Policy <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Georgia Institute of Technology<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b>From:</b> Gnso-epdp-team <<a href="mailto:gnso-epdp-team-bounces@icann.org">gnso-epdp-team-bounces@icann.org</a>>
<b>On Behalf Of </b>King, Brian via Gnso-epdp-team<br>
<b>Sent:</b> Monday, January 27, 2020 3:52 PM<br>
<b>To:</b> <a href="mailto:gnso-epdp-team@icann.org">gnso-epdp-team@icann.org</a><br>
<b>Subject:</b> [Gnso-epdp-team] IPC Proposal for Day 1 Automation<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello EPDP Team,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please find below our first proposal for automated disclosure.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Trademark Infringement in Domain Name</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><i>Requestor Safeguards</i><o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo2">Accreditation Authority determines that the trademark is valid.
<o:p></o:p></li><li class="MsoNormal" style="mso-list:l0 level1 lfo2">Accreditation Authority determines that Requestor is the legal owner, agent, or service provider of the trademark.
<o:p></o:p></li></ol>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><i>Request Safeguards</i><o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l3 level1 lfo3">Requestor alleges that the domain name infringes Requestor’s trademark.
<o:p></o:p></li><li class="MsoNormal" style="mso-list:l3 level1 lfo3">Requestor states its own legal basis and purpose for processing the data. Requestor makes a syntactically correct and complete request, including any/all required Authorization Assertions. Requestor makes
all representations required by policy: use will be limited to stated purpose, data retention, etc.
<o:p></o:p></li><li class="MsoNormal" style="mso-list:l3 level1 lfo3">Domain string contains exact match of trademark string<span style="color:black"> (potentially including prefix or suffix, e.g. “nike-shoes.TLD” or “cheap-nike.TLD”)</span>.
<o:p></o:p></li></ol>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><i>Additional Noteworthy Safeguards</i><o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l2 level1 lfo4">Registrant committed not to infringe the rights of third parties in its registration agreement, as required by the RA and RAA.
<o:p></o:p></li><li class="MsoNormal" style="mso-list:l2 level1 lfo4">Registrant was informed at the time that its data was collected that it could be processed for third-party purposes, including intellectual property protection.
<o:p></o:p></li></ol>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">In these cases, disclosure can be automated. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:10.0pt;color:black">Brian J. King
</span></b><span lang="EN-GB" style="font-size:10.0pt;color:black"> <br>
Director of Internet Policy and Industry Affairs<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;color:black">T +1 443 761 3726</span><a href="http://www.markmonitor.com"><span lang="EN-GB" style="font-size:10.0pt"><br>
</span><span style="font-size:10.0pt">markmonitor.com</span></a><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:10.0pt;color:black">MarkMonitor<br>
</span></b><span lang="EN-GB" style="font-size:10.0pt;color:black">Protecting companies and consumers in a digital world<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
</div>
</body>
</html>