<div dir="ltr">A quick view specifically on "rights of inspection".<div><br></div><div>I think enabling that some entity gets this right would be one of the most useful of all possible accountability improvements. </div><div><br></div><div>It would - perhaps over time - pull out any motivations that might exist for ICANN to be misleading or less than truthful in its reporting. This is going to be especially important as ICANN receives increasingly large amounts of revenue and particularly given its current weak financial controls.</div><div><br></div><div>(See: <a href="http://www.ionmag.asia/2015/07/icann-finances-swallow-the-money/">http://www.ionmag.asia/2015/07/icann-finances-swallow-the-money/</a>)</div><div><br></div><div>I predict that ICANN corporate will fight hard to prevent any entity from gaining this right. And that it will continue to fight hard even when someone has that right. That in itself should be a good indicator for why it should be a redline for the accountability group.</div><div><br></div><div>To my mind, not allowing ICANN to hide information is the epitome of actual accountability. If you can't hide it, then to save on embarrassment you consider how best to share it. Over time, everyone gains.</div><div><br></div><div><br></div><div>Kieren</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 22, 2015 at 9:51 AM, Greg Shatan <span dir="ltr"><<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Roelof:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:arial,sans-serif;font-size:12.8000001907349px">Derivative rights and the right of inspection are statutory rights of members under California law. Under a multiple member model, each member could choose to exercise these rights individually. Under a single member model, only the single statutory member would have these rights. Maybe this could be "fixed" so that individual SOACs could exercise these rights in the name of the single member, but I don't know if that works.</span><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:arial,sans-serif;font-size:12.8000001907349px"><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:arial,sans-serif;font-size:12.8000001907349px">If we don't care to have those rights (or any of the rights that members have individually), then a single member set-up might work. I would note that the right to inspect ICANN documents (currently only available in a DIDP) has been an issue of concern. I would also note that derivative rights are a powerful tool for enforcement against an entity.</span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:arial,sans-serif;font-size:12.8000001907349px"><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:arial,sans-serif;font-size:12.8000001907349px">I agree that when it comes to spilling the whole board, or other powers intended to be exercised by the community as a whole,, the single member model has the least issues vis a vis the multiple member model. But when it comes to recalling an individual board member or other powers to be exercised by a single member, the single member model raises substantial issues.</span></div><span class="HOEnZb"><font color="#888888"><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:arial,sans-serif;font-size:12.8000001907349px"><br></span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:arial,sans-serif;font-size:12.8000001907349px">Greg</span></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 22, 2015 at 11:28 AM, Roelof Meijer <span dir="ltr"><<a href="mailto:Roelof.Meijer@sidn.nl" target="_blank">Roelof.Meijer@sidn.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
Hi Ed,</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<div><font face="Calibri,sans-serif">Although I have no clue about what it actually means, I am quite positive that “components of the community” .. “</font>be[ing] able to avail itself of derivative rights or the right of inspection” is not a requirement that
we formulated as a power, nor a criterium we formulated for the selection of a mechanism. So I am at a bit of a loss where that comes from.</div>
<div><br>
</div>
<div>Additionally, I do not see why stakeholders represented “in a single tent” requiring a specified majority among those representatives to execute a specific power (let’s say spilling the board) would have less vitality and more blob, than stakeholders in
separate legal entities equally requiring the same specified majority among those entities to execute a specific power.</div>
<div><span style="font-size:14px"><br>
</span></div>
<div><span style="font-size:14px">Best,</span></div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<div><font color="#000000"><font face="Calibri"><br>
</font></font></div>
<div><font color="#000000"><font face="Calibri">Roelof</font></font></div>
</div>
</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<span style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>Edward Morris <<a href="mailto:egmorris1@toast.net" target="_blank">egmorris1@toast.net</a>><br>
<span style="font-weight:bold">Date: </span>woensdag 22 april 2015 16:24<br>
<span style="font-weight:bold">To: </span>Matthew Shears <<a href="mailto:mshears@cdt.org" target="_blank">mshears@cdt.org</a>><br>
<span style="font-weight:bold">Cc: </span>Roelof Meijer <<a href="mailto:roelof.meijer@sidn.nl" target="_blank">roelof.meijer@sidn.nl</a>>, "<a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>" <<a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>>, "<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>"
<<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>><div><div><br>
<span style="font-weight:bold">Subject: </span>Re: [CCWG-ACCT] member organization and single membership structure<br>
</div></div></div>
<div><br>
</div>
<div>
<div dir="auto"><div><div>
<div>I look forward to independent counsel's analysis of this proposal.</div>
<div><br>
</div>
<div>Certainly my principle objection with this model is the nullification of many of the benefits membership would bring to components of the community. If the GNSO, for example, felt strongly about an issue it would not be able to avail itself of derivative
rights or the right of inspection without the consent of the greater community. Diversity is the strength of the multistakeholder model and folding all rights into a single tent would dampen the vitality of the diverse bottom up process and instead submerge
it into a giant blob like unit.</div>
<div><br>
</div>
<div>I do remain open, though, to others thoughts on the matter and thank Roelof for bringing it up.</div>
<div><br>
</div>
<div>Ed<br>
<br>
Sent from my iPad</div>
<div><br>
On Apr 22, 2015, at 3:02 PM, Matthew Shears <<a href="mailto:mshears@cdt.org" target="_blank">mshears@cdt.org</a>> wrote:<br>
<br>
</div>
</div></div><blockquote type="cite">
<div><div><div><br>
If this would achieve the same result as the broader membership model and at the same time be simpler to implement shouldn't it be looked at again? Was there a specific reason it was discounted?<br>
<br>
Matthew<br>
<br>
<div>On 4/22/2015 2:56 PM, Roelof Meijer wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div>
<div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
Hi Avri,</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
The sole membership construction, is a possibility described in the legal document in several places: the comments by the legal experts on the PCCWG mechanism template (page 64) and the Community Council mechanism template (page 69). I sent <font face="Calibri,sans-serif">several
emails about it to the WP1 list, suggesting to look in the possibility as indeed it would not necessitate every SO and AC to become a legal entity. And, as you do, suggesting: "</font><span>make the „Community Council” the sole
member of ICANN (and thus a formal legal entity), consisting of either the SO and AC chairs or SO/AC elected representatives” (from an email of 14 April).</span></div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<span><br>
</span></div>
<div><span><font face="Calibri,sans-serif">And I would think it would enable the SO’s and AC’s themselves to continue appointing directors, as they do now. But that’s just guessing, based on the fact that the SO’s and AC’s themselves
would not change status</font></span></div>
</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<div><font color="#000000"><font face="Calibri"><br>
</font></font></div>
<div><font color="#000000"><font face="Calibri">Best,</font></font></div>
<div><font color="#000000"><font face="Calibri"><br>
</font></font></div>
<div><font color="#000000"><font face="Calibri">Roelof</font></font></div>
</div>
</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<br>
</div>
<span style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>Avri Doria <<a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>><br>
<span style="font-weight:bold">Organization: </span>Technicalities<br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>" <<a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>><br>
<span style="font-weight:bold">Date: </span>woensdag 22 april 2015 15:09<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>" <<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [CCWG-ACCT] member organization and single membership structure<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF" text="#330033">Hi,<br>
<br>
<div>On 22-Apr-15 08:26, Roelof Meijer wrote:<br>
</div>
<blockquote type="cite"><span>
<div>2)</div>
<div>What I find quite frustrating is that I have raised the point of the possibility (or not) of a single membership structure – an option mentioned by Sidley and Adler & Colving in their legal advice – several times by now without getting any substantial
reaction. I am not aware that any serious effort to investigate this has led to a formal write-off.</div>
</span></blockquote>
<br>
In some way that might lessen the complexity of making most SOAC an individual legal entity.
<br>
<br>
How would it work? Would we continue to appoint Directors just as we do now?<br>
<br>
Or would there need to be some sort of Members Council that took actions, working simliarly to the the executive board or community council idea?<br>
<br>
thanks<br>
<br>
avri<br>
<br>
<br>
<br>
<hr style="border:none;color:#909090;background-color:#b0b0b0;min-height:1px;width:99%">
<table style="border-collapse:collapse;border:none">
<tbody>
<tr>
<td style="border:none;padding:0px 15px 0px 8px"><a href="http://www.avast.com/" target="_blank"><img src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" border="0"></a></td>
<td>
<p style="color:#3d4d5a;font-family:"Calibri","Verdana","Arial","Helvetica";font-size:12pt">
This email has been checked for viruses by Avast antivirus software. <br>
<a href="http://www.avast.com/" target="_blank">www.avast.com</a> </p>
</td>
</tr>
</tbody>
</table>
<br>
</div>
</div>
</span><br>
<fieldset></fieldset> <br>
</div></div><pre>_______________________________________________
Accountability-Cross-Community mailing list
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></pre>
</blockquote><span>
<br>
<pre cols="72">--
Matthew Shears
Global Internet Policy and Human Rights
Center for Democracy & Technology (CDT)
<a href="tel:%2B%2044%20%280%29771%20247%202987" value="+447712472987" target="_blank">+ 44 (0)771 247 2987</a></pre>
</span></div>
</blockquote><span>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Accountability-Cross-Community mailing list</span><br>
<span><a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a></span><br>
<span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br>
</div>
</blockquote>
</span></div>
</div>
</span>
</div>
<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>
</div></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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>