<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Michele,</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">It's much deeper.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">I think that DCA has no claim to .AFRICA, whatsoever, but, they have the right to be treated fairly AND to challenge ICANN's conduct.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">And THAT is what this Preliminary Injunction is about. Whether DCA can prevail on the merits or (most certainly) not, they have some very compelling arguments, such as:</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">A monopolist awarding a contract that only it can award only under the condition that you can not sue them for whatever reason (which is very wide and includes, technically, intent, which DCA is using, hence they HAVE to allege intent, ie fraud) is not only amoral (as I have said before) but it also may violate (Californian) law. In the current proceedings DCA have led evidence in this regards which ICANN had opportunity to contradict by its own evidence. The Court, decided that the balance of probability on the evidence (submitted by DCA and ICANN) favored DCA. This may well change in the main action because there/then the burden of proof is higher.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">ICANN has tried to present the Court with a fait accompli, by trying to delegate during this Court case. Courts don't like this as a general rule from a fairness perspective, and I read the Order as the Court being displeased. It is indeed unfair to DCA and as little as I am a fanboy of Sockpuppy, I am a very firm believer in fundamental fairness.</div><div id="AppleMailSignature"><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div id="AppleMailSignature"><span style="background-color: rgba(255, 255, 255, 0);">Never mind that the justification given by ICANN sounds silly. Which is another issue. Either is Jones Day stupid and/or arrogant or ICANN is resistant to JD's advice. Or both, of course. The delay is clearly caused by ICANN, whether by ineptness (as I suspect) or intentionally (as alleged by DCA).</span></div><div id="AppleMailSignature"><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div id="AppleMailSignature"><span style="background-color: rgba(255, 255, 255, 0);">I think the AUC issue is a red herring, but the IRP comments are also worrying.</span></div><div id="AppleMailSignature"><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div id="AppleMailSignature"><span style="background-color: rgba(255, 255, 255, 0);">Now, this is just a Preliminary Injunction to maintain the status quo ante, but it does support what I have been concerned about with regards to ICANN's Accountability and the Transition. </span><span style="background-color: rgba(255, 255, 255, 0);">I remain unconvinced that the measures proposed by the CCWG Accountability could prevent this challenged conduct from happening.</span></div><div id="AppleMailSignature"><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div id="AppleMailSignature"><span style="background-color: rgba(255, 255, 255, 0);">greetings, el</span></div><div id="AppleMailSignature"><div><br></div></div><div id="AppleMailSignature"><br>-- <div>Sent from Dr Lisse's iPad mini 4</div></div><div><br>On 13 Apr 2016, at 22:28, Michele Neylon - Blacknight <<a href="mailto:michele@blacknight.com">michele@blacknight.com</a>> wrote:<br><br></div><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div>
<div>
<div>Maybe when it’s <span style="font-style: italic;">reported</span> somewhere as opposed to just a press release .. </div>
<div><br>
</div>
<div>In any case I don’t see how this ridiculous case dragging on and on and on helps anyone</div>
<div><br>
</div>
<div>Maybe ICANN should simply give the applicants the strings they <span style="font-weight: bold;">
originally</span> applied for – this would solve the problem and there’d be no conflicts</div>
<div><br>
</div>
<div>Regards</div>
<div><br>
</div>
<div>Michele</div>
<div><br>
</div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE">
<div>--</div>
<div>Mr Michele Neylon</div>
<div>[...]</div></div></div></div></div></blockquote></body></html>