<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<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:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
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:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><a name="_MailEndCompose">Paul:<o:p></o:p></a></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose">I don’t believe you are an attorney, but even if you are I would respectfully disagree with your reading of the Swaine memo and its policy implications.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose">Regardless, while it is perfectly proper to discuss the Final Report language referencing the Swaine memo, excising it in its entirety would seem equivalent to consigning it to an Orwellian memory
hole. This WG suspended operations for a full year to conduct a search for an International law expert, obtained ICANN funding for the inquiry, and worked closely with Prof. Swaine in developing the final memo text. Once received the memo was a central reference
in our subsequent discussions. To remove it from the final report would be to distort the entire history of this WG.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose">You have drawn certain conclusions from your reading of the memo, and I have drawn different conclusions. I will likely quote from the memo in my individual statement to be filed as an appendix
to the Final Report. This WG member therefore strongly objects to the suggestion that it should not be contained in its uncensored entirety in the Final Report, believing that such decision would be shameful act of censorship.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-family:"Arial",sans-serif">Philip S. Corwin<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-family:"Arial",sans-serif">Policy Counsel<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-family:"Arial",sans-serif">VeriSign, Inc.<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span lang="EN" style="font-family:"Arial",sans-serif">12061 Bluemont Way<br>
Reston, VA 20190<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-family:"Arial",sans-serif">703-948-4648/Direct<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-family:"Arial",sans-serif">571-342-7489/Cell<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-family:"Arial",sans-serif"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><i><span style="font-family:"Arial",sans-serif">"Luck is the residue of design" -- Branch Rickey<o:p></o:p></span></i></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<p class="MsoNormal"><b>From:</b> Gnso-igo-ingo-crp [mailto:gnso-igo-ingo-crp-bounces@icann.org]
<b>On Behalf Of </b>Paul Tattersfield<br>
<b>Sent:</b> Sunday, May 13, 2018 7:52 PM<br>
<b>To:</b> gnso-igo-ingo-. <gnso-igo-ingo-crp@icann.org>; Heather Forrest <haforrestesq@gmail.com>; Austin, Donna <Donna.Austin@team.neustar>; rafik.dammak@gmail.com<br>
<b>Subject:</b> [EXTERNAL] [Gnso-igo-ingo-crp] Very serious issues with The Swaine Memo & the proposed Final Report<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">Further to our discussions on the call last Thursday:<br>
<br>
As Mary hasn’t yet had chance to post the latest version of the Swaine Memo I have used an extract from the version on the working group Wiki
<br>
<a href="https://community.icann.org/pages/viewpage.action?pageId=56131791">https://community.icann.org/pages/viewpage.action?pageId=56131791</a> which is marked final and dated 6/17/2016.
<br>
<br>
From that document:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<i><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif">“3. Discussion (Bottom of page 8)<br>
<br>
The core question is whether an IGO is “entitled to immunity,” but the baseline assumptions may be disaggregated.
<span style="color:green">The scope of IGO immunity would most clearly be at issue if the Mutual Jurisdiction provision were irrelevant and the IGO had not itself initiated judicial proceedings, since that would risk waiving any immunity to which it may be
entitled, including to counterclaims</span>. <sup>20</sup> <span style="color:blue">
This might be the case, for example, if a domain-name registrant sought a declaratory judgment against an IGO in relation to some actual or potential infringement</span>.
<sup>21</sup> <span style="color:red">That scenario, though not otherwise of concern here, does usefully isolate the question as to whether an IGO has a legitimate expectation that it would be entitled to immunity absent the UDRP</span>. If such immunity is
minimal or uncertain, then any compromises required by the UDRP loom less large; if the IGO would otherwise be entitled to immunity, however, its potential sacrifice seems more substantial.<br>
<br>
As explained in Part A, the answer depends. IGOs generally enjoy immunity under international law, but different jurisdictions apply the law differently, and even within the same jurisdiction different IGOs may be treated differently. Part B then introduces
the complication that any such immunity may be waived through the Mutual Jurisdiction provision, and affording such waiver is not the same thing as violating an IGO’s immunity. Part C then discusses alternative ways to resolve the situation. … “</span></i><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
<span style="color:green">Green </span>Initiating proceedings waives immunity including counterclaims<br>
<span style="color:blue">Blue </span>Scenario (a) below <br>
<span style="color:red">Red</span> Transfers those rights of scenario (a) to scenario (b)<br>
<br>
The rest of the memo is then based on the incorrect assumption that rights can be transferred between the two scenarios.<br>
<br>
<br>
<b>Proof</b><br>
<br>
Absent UDRP there are two possible ways the immunity question could come before a court:<span style="color:black"><br>
<br>
</span><span style="color:blue">(a) A TM owner seeks to acquire a domain which an IGO has registered<br>
</span><span style="color:red">(b) An IGO seeks to acquire a domain which a domain registrant has registered</span><span style="color:black"><br>
<br>
</span><span style="color:blue">In (a) the IGO would be entitled to raise an immunity defence</span><span style="color:black"><br>
</span><span style="color:red">In (b) the IGO would be required to waive immunity for the court to consider the matter.</span><span style="color:black"><br>
<br>
</span>As the UDRP is an administrative procedure to help take less complex cases out of the judicial system if UDRP is to afford the same protections as any other forum then UDRP needs to take into account both cases.<br>
<br>
<span style="color:blue">(a) A TM owner seeks to acquire a domain which an IGO has registered by bringing a UDRP</span><span style="color:black"><br>
</span><span style="color:red">(b) An IGO seeks to acquire a domain which a domain registrant has registered by bringing a UDRP<br>
<br>
<br>
</span><b>Conclusion<br>
</b><span style="color:red"><br>
</span>The working group has not considered (a) which hides the fact that in (b) an IGO is never entitled to jurisdictional immunity after choosing to initiate proceedings. The incorrect Swaine reasoning introduces irrelevant complexity which confuses rather
than clarifies and should therefore have no place in the working group’s final report.</span><o:p></o:p></p>
</div>
</div>
</body>
</html>