<div dir="ltr"><div>De ar All,</div><div>I have cked the Matrix and the Memo</div><div>There is several inconsistencies between the two</div><div>Kavouss </div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-09-22 4:57 GMT+02:00 Aikman-Scalese, Anne <span dir="ltr"><<a href="mailto:AAikman@lrrlaw.com" target="_blank">AAikman@lrrlaw.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" vlink="purple" link="blue">
<div>
<p>Bruce,<u></u><u></u></p>
<p>The difficulty I see here is that the .africa case was focused on whether ICANN violated its own procedures and the panel held
<b>unanimously</b> that it did. There was also arguably "undue government influence" (against NTIA condition for transition) because the panel found unanimously that the NGPC (which was delegated full Board authority) failed to deal properly with the GAC recommendation
in several respects. In this regard, the panel appeared to rule that based on its By-laws, ICANN has an obligation to investigate the nature and basis of GAC consensus advice and also under certain circumstances to obtain an expert opinion in relation to
such advice. (I have no idea personally whether that is correct but the panel so held.)
<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>The panel also thought it inappropriate that ICANN filed arguments resisting live testimony before the panelists. They thus issued an interim ruling that the judges would be able to question the witnesses and ultimately did so. So
the Board was seen by the panel as uncooperative in this respect.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>My only point here it that it may be oversimplifying things to characterize the .africa case as one where the first party complained, the second party denied, then the first party won and the Board complied. We all have a community
interest in making sure that the Final Proposal as recommended to NTIA will pass scrutiny in this regard. In other words, Board compliance with ICANN’s own procedures and By-Laws must be RAPIDLY enforceable and not result in long, drawn-out proceedings like
.africa. (And of course Alan keeps asking about enforcement of the Articles of Incorporation – which I think reads Core Mission and Values.)<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>The beauty of the Sole Member structure is in the ability to exercise statutory Community Powers. The CCWG has been advised that the full scope of such powers is apparently only available within the membership structure so I think
many of us are still struggling with the MEM proposal in that it appears to be duplicative of the IRP, but moves the issue to an SO/AC level . However, I had thought that IRP was already available to SOs and ACs – perhaps not? Can you please clarify again
the FAQ as to why the MEM is not merely duplicative of the IRP? <u></u><u></u></p>
<p><u></u> <u></u></p>
<p>The other big issue lurking here is the time that existing procedures take in order to execute accountability measures. I think it is a significant weakness in the current structure and possibly also in the proposed MEM.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Thank you for your diligence in responding to all these questions from the CCWG. I agree with others that this is a very useful process and am, as you know from previous posts, quite concerned about finalizing a proposal that will pass
muster in Congress even in the face of the issues raised by .africa and .amazon (as well as contractual compliance.)
<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>In regard to the last item, there were many public comments to the effect that ICANN’s mission should include contractual compliance and this goes well beyond technical issues. (Disclosure: I participated in IPC comments on this point.)
Clearly ICANN has a responsibility to enforce contracts that include obligations on the registries that are not technical in nature. For example, PIC enforcement rests within ICANN. The PIC Dispute Resolution Process is not an outside process occurring
between two independent parties at WIPO or elsewhere. Further, it is clear there is interest on the part of community members to bring into play a Human Rights role for ICANN in its mission and core values which arguably could result in contractual obligations
for the registries that would need to be enforced by ICANN, either via PIC or other mechanism. Thus, contractual enforcement must be a part of ICANN’s mission. Certainly this goes well beyond a “limited technical” role.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>These are tough issues. Thanks for your willingness to “dive deep” in the analysis.<u></u><u></u></p><span>
<p><u></u> <u></u></p>
<p>Anne<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Anne E. Aikman-Scalese<u></u><u></u></p>
<p>Of Counsel<u></u><u></u></p>
<p>Lewis Roca Rothgerber LLP | <u></u><u></u></p>
<p>One South Church Avenue Suite 700<u></u><u></u></p>
<p>Tucson, Arizona 85701-1611<u></u><u></u></p>
<p>(T) <a href="tel:520.629.4428" target="_blank" value="+15206294428">520.629.4428</a> | (F) <a href="tel:520.879.4725" target="_blank" value="+15208794725">520.879.4725</a><u></u><u></u></p>
</span><p><a href="mailto:AAikman@lrrlaw.com" target="_blank">AAikman@lrrlaw.com</a> | <a href="http://www.LRRLaw.com" target="_blank">www.LRRLaw.com</a><u></u><u></u></p>
<p><u></u> <u></u></p>
<p><span>-----Original Message-----<br>
From: <a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a> [mailto:<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a>] On Behalf Of Bruce Tonkin<br></span><span>
Sent: Saturday, September 19, 2015 4:38 PM<br>
To: CCWG Accountability<br>
Subject: Re: [CCWG-ACCT] Your public comment re replacement of IANA provider</span></p>
<p><u></u> <u></u></p>
<p>Hello Eberhard,<u></u><u></u></p><div><div class="h5">
<p><u></u> <u></u></p>
<p><u></u> <u></u></p>
<p>>> in the .AFRICA case at least (and I don't remember the older ones well) ICANN was not the model for cooperation, was it now?
<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Well as I understand it - the two sides put forward their case, and the complainant won the case.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>The ICANN Board then complied with the outcome of the IRP.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Regards,<u></u><u></u></p>
<p>Bruce Tonkin<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>_______________________________________________<u></u><u></u></p>
<p>Accountability-Cross-Community mailing list <a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">
<span style="color:windowtext;text-decoration:none">Accountability-Cross-Community@icann.org</span></a><u></u><u></u></p>
<p><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank"><span style="color:windowtext;text-decoration:none">https://mm.icann.org/mailman/listinfo/accountability-cross-community</span></a><u></u><u></u></p>
<p><u></u> <u></u></p>
</div></div></div>
<br><span>
<hr>
<font color="gray" face="Arial" size="1"><br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message
or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying
to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.
<br>
</font>
</span></div>
<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>