<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=us-ascii">
<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 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:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
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:543717874;
mso-list-type:hybrid;
mso-list-template-ids:188748190 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.5in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.0in;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.5in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.0in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.5in;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.0in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.5in;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:5.0in;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:1886873320;
mso-list-type:hybrid;
mso-list-template-ids:520279450 67698703 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><a name="_MailEndCompose">Re Board concerns #1 and 2 I am ok with Alex’s proposal. With respect to the Bona Fides, I don’t think these will be effective as they rely on assumptions and judgment calls. I think that generally we should avoid
solutions/mechanisms that require ICANN to make judgement calls as we have seen in the past that this has often not turned out well and will almost certainly result in disputes which junk up and delay the process. Jim mentions protection of ICANN the institution
in his comments on the ability of ICANN to refer to competition authorities. First, I do not think that protecting ICANN org is within the remit of, or should be a concern for this group and that ICANN can clearly take care of itself, but if this was a concern
then we are doing ICANN no favors by having them decide Bon Fides and are doing no one else any favors to create a whole new process or panels to decide this. This doesn’t even get into the issue of what to do if you don’t meet the Bona Fides test which is
a whole separate can of worms. <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">Re ICANN’s ability to refer to competition authorities why are we still wasting time on this? Adding in a provision has no effect on ICANN’s (or anyone else’s) ability to refer applications to
competition authorities which they can do at any time. Also, why would we even want ICANN to do this? What expertise does ICANN have to make this call and why would ICANN want to jump on the grenade and do this? Finally, as I mentioned above, protecting
ICANN org is not a concern of this group, but if it was, I fail to see how including a right for ICANN to refer applications to relevant competition authorities provides any legal protection whatsoever to ICANN org from charges that it is fostering anticompetitive
behavior.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><b><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:#003359">Marc H. Trachtenberg</span></b></span><span style="mso-bookmark:_MailEndCompose"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:black"><br>
Shareholder </span></span><span style="mso-bookmark:_MailEndCompose"><span style="color:#1F497D"><br>
</span></span><span style="mso-bookmark:_MailEndCompose"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:black">Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601<br>
Tel 312.456.1020 <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:black">Mobile 773.677.3305<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"></span><a href="mailto:trac@gtlaw.com"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:blue">trac@gtlaw.com</span></span><span style="mso-bookmark:_MailEndCompose"></span></a><span style="mso-bookmark:_MailEndCompose"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:black">
| </span></span><a href="http://www.gtlaw.com/"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:#003359">www.gtlaw.com</span></span><span style="mso-bookmark:_MailEndCompose"></span></a><span style="mso-bookmark:_MailEndCompose"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:black">
<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><span style="color:#1F497D"><img border="0" width="185" height="30" style="width:1.927in;height:.3125in" id="Picture_x0020_1" src="cid:image001.jpg@01D663F0.D324BF30" alt="Greenberg Traurig"><o:p></o:p></span></span></p>
</div>
<p class="MsoNormal"><span style="mso-bookmark:_MailEndCompose"><o:p> </o:p></span></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org]
<b>On Behalf Of </b>Alexander Schubert<br>
<b>Sent:</b> Monday, July 27, 2020 8:14 AM<br>
<b>To:</b> gnso-newgtld-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Additional thoughts on Proposal 5<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="color:#0E0E3F">*EXTERNAL TO GT*</span></b><o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D">Jim,<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">I agree with you. <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">And essentially “Board Concern #1” and “Board Concern #2” are identical:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">The board is concerned that applicants are trying to facilitate financial gain by strategically losing private auctions. For whatever reason:
<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:#1F497D;mso-list:l0 level1 lfo2">either just to bath in cash<o:p></o:p></li><li class="MsoListParagraph" style="color:#1F497D;mso-list:l0 level1 lfo2">or to finance other applications
<o:p></o:p></li></ul>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">and in the end it doesn’t matter. It’s one and the same concern.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">It is however still beneficial to factor them in separately as the countermeasure to Concern #2 can be easily mitigated by having all auctions for clear cut cases (no objections, etc)
all at once. Don’t forget: “sealed bid auctions” are now essentially just “reveals” – all of them can be facilitated in a millisecond; whereas in the past we had to create auction slots and auctions were time and resource consuming. The only real difference
between Board Concerns #1 and #2 is (as you indicate) “timing”.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l1 level1 lfo4">
Applicants apply for their strings.<o:p></o:p></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l1 level1 lfo4">
After the application window closes those who face contention resolution are requested to submit a sealed bid (the only information they have at this point is that they face some kind of contention – which could be identical or similar strings. They don’t know
how many contention set members or their identity or string names).<o:p></o:p></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l1 level1 lfo4">
That bid is valid for both auction types: the one where proceeds are shared among losers – and the one where losers won’t benefit (formerly: “auction of last resort”).
<o:p></o:p>
<ul style="margin-top:0in" type="circle">
<li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l1 level2 lfo4">
The latter one is very important, as applicants may announce upfront that they will not allow losers to financially benefit (this deters fortune seekers).
<o:p></o:p></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l1 level2 lfo4">
Example: dotAIRPORT, LLC will make it crystal clear, that it won’t participate in any scheme where auction proceeds are distributed to losers.
<o:p></o:p></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l1 level2 lfo4">
In fact we could have applicants OPT OUT of the private auction right in the application – then contention set members would be informed that one member opted out of auction fee distribution: the affected applicants could quickly withdraw their application
to maximize their application fee refunds (overall loss); as they are now facing a mandatory ICANN auction of last resort.
<o:p></o:p></li></ul>
</li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l1 level1 lfo4">
Auction deposits are due a few days before auction reveal (regardless how auction proceeds are distributed).
<o:p></o:p></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0in;mso-list:l1 level1 lfo4">
Failure to pay the winning bid (2<sup>nd</sup> highest) results in losing the deposit and any potential application fee refund.<o:p></o:p></li></ol>
<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">Thanks,<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">Alexander<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>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Gnso-newgtld-wg [<a href="mailto:gnso-newgtld-wg-bounces@icann.org">mailto:gnso-newgtld-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>Jim Prendergast<br>
<b>Sent:</b> Montag, 27. Juli 2020 14:28<br>
<b>To:</b> <a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a><br>
<b>Subject:</b> [Gnso-newgtld-wg] Additional thoughts on Proposal 5<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Apologies in advance. I will not be able to join the call later today as I am cohosting a workshop at RightsCon at the same time. I will review the notes and recording and respond on list as necessary.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">As Jeff noted during the last call, this is complicated because we are now allowing the resolution of contention sets in ways that were not allowed in the 2012 round. A very simple, clean way to settle contention
sets without these measures is to have them all go to an ICANN auction of last resort or a random draw. But some people insist that losers should get paid so those are off the table.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">I also believe that we have to address BOTH Board concerns -
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt">Board Concern #1 - applications submitted for the sole purpose of receiving a payout for losing private auctions</span></b><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">We have made good progress in addressing #1 and I think we can get there with some tweaks.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Transparency requirements are good but they should not be rolled back for the creation of JVs. Not suggesting trade secrets be divulged but we should know who the operator of the JV is and we should also
know the circumstances around what caused members of the contention set who are not part of the JV to drop out.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">I also believe that the Bona Fide proffers should be reviewed and enforced by ICANN, not just the outside evaluators. Rationale is that at some point, the evaluators will disappear. They are temporary help.
ICANN has the ultimate responsibility to administer this program so they should be the ones reviewing theses Bona Fide requirements.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">And along these lines – ICANN should oversee all auctions, not just the Auction of Last resort. As currently constructed in Paul’s edit – there are too many steps for revealing the results of private auctions.
With ICANN overseeing this, it’s a much cleaner process. ICANN involvement also adds a level of assurance that these auctions are being conducted in an aboveboard manner.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">As far as penalties for violations of the Bona Fide requirements – loss of registry has to be there. That is a major deterrent and should not be cast aside.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt">Board Concern #2 - gaming for the purposes of financing other applications.</span></b><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">The base Proposal 5 does nothing to address Concern #2. Donna stated that she’s “not convinced that means we have to address it.” I couldn’t disagree more.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">If we fail to address this now, there is a strong likely hood that the Board will either 1) come back to us and ask us to develop a plan (slowing things down again) or 2) develop a solution themselves. Neither
is an ideal outcome so we have to do something to stop the gaming for purposes of financing other applications. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">I and others believe that the Bona Fide requirements do not go far enough here. Others believe my sealed bid requirement goes too far. So what are alternative solutions that are enforceable and prevent this
type of activity?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Auction proceeds held in escrow? All auction conducted at once?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Timing on when these auctions happen is the key to stop this gaming and that is why I proposed the submission of all bids upfront. With bids upfront, auctions could be conducted whenever but there is a constraint
on the ability to roll funds over and over.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt">ICANN’s right to refer to competition authority.
<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">We never got around to discussing why Paul felt the need to delete this section completely and since the call there was a brief discussion on list about whether ICANN has this as an inherent right or whether
it should be spelled out.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">My proposal was based upon the RSEP process which is already in force of all registry operators and will be required for all future operators. It specifically calls out competition authority referral if ICANN
makes a determination such referral is necessary. I was surprised how representatives of contracted parties reacted so negatively to that since it is in existing registry agreements.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">My rationale for including this provision and calling it out specifically is simple – if a JV or other form of private resolution raises competition concerns for ICANN, they should have the right to refer
it to relevant competition authorities to ensure they are ok with it. This protects ICANN the institution from charges that it is fostering anticompetitive behavior.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Jim Prendergast<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">The Galway Strategy Group<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">+1 202-285-3699<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
</div>
<HR>If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at postmaster@gtlaw.com, and do not use or disseminate the information.<BR>
</body>
</html>