<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Hi Avri, </div>
<div><br>
</div>
<div>I share some of your same questions.</div>
<div><br>
</div>
<div>In terms of whether other components of an SO/AC would become Uas, that would really be a decision up to them. It would not be anything that is necessitated under the Bylaws or the structure. As I understand the advice to date, those that we wish to
identify as members in the Bylaws need to form a UA. For each of those groups, there may be other concerns that would drive the need for an “alter ego” UA as a companion to the policy or advisory work of the SO/AC, but I don’t know that it’s required – it’s
the proposed solve to allow those groups to get to member status.</div>
<div><br>
</div>
<div>If there are other groups within ICANN (such as the IPC, or a RALO, or the NCSG, for example) that think that they’d get some benefit from being a UA, that would not be because of any benefit provided under the Bylaws or membership structure. </div>
<div><br>
</div>
<div>In short, you need to be a UA (or other legal entity) to be a member, but forming a UA separately does NOT equal membership status.</div>
<div><br>
</div>
<div>Hope this helps more than confuses the situation.</div>
<div><br>
</div>
<div>Sam</div>
<span id="OLK_SRC_BODY_SECTION">
<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">avri@acm.org</a>><br>
<span style="font-weight:bold">Organization: </span>Technicalities<br>
<span style="font-weight:bold">Reply-To: </span>Avri Doria <<a href="mailto:avri@acm.org">avri@acm.org</a>><br>
<span style="font-weight:bold">Date: </span>Friday, May 1, 2015 at 9:14 AM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>" <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [CCWG-ACCT] Legal question<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF" text="#330033">Hi,<br>
<br>
So it is an option?<br>
<br>
A SOAC can become one<br>
Or set up a shadow puppet.<br>
<br>
And each would be free to pick its own way of doing it.<br>
<br>
Also regarding the GAC, is it correct to assume that since they do not (s)elect a director, they would not really need a UA if they did not wish, as their special status is guaranteed elsewhere in the bylaws.<br>
<br>
Also is it correct to assume that we have now almost 'decided' that UA are at the level of SOAC. The reference to IPC as a UA confused me. Is that stiill a possiblity that SGs and RALOs might become UAs as well if they wished.
<br>
<br>
Finally with regard to becoming UA, I suppose any ICANN component entity, at any level, could become one today if they wished, no bylaw prevents it as far as I know. Is that correct?<br>
<br>
thanks<br>
<br>
avri<br>
<br>
<br>
<div class="moz-cite-prefix">On 01-May-15 11:51, Greg Shatan wrote:<br>
</div>
<blockquote cite="mid:CA+aOHUSmSyXvNT-kofbo4qLhevuGgj1Dzaj2a-U+RDcjghtkEA@mail.gmail.com" type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-family:verdana,sans-serif">Avri,</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">This has to do with the fact that for certain SOACs, some or all of the current "members" may not want or be able to be members of a legal entity, much less one located outside their home jurisdiction.
Probably not a problem for IPC (which is only a piece of a SOAC, but the one I'm best positioned to speak to). More of a problem for GAC and ccNSO.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, May 1, 2015 at 11:26 AM, Avri Doria <span dir="ltr">
<<a moz-do-not-send="true" href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#330033">Hi,<br>
<br>
A tangent question.<span class=""><br>
<br>
<div>On 30-Apr-15 23:41, Greg Shatan wrote:<br>
</div>
<blockquote type="cite">
<div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:Verdana;font-size:13px"><font color="#000000"><br>
</font></span></div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:Verdana;font-size:13px"><font color="#000000">Finally, I have to say I disagree with your contention that each SO/ACs would need to become an unincorporated association
("UA") rather than merely create one. Admittedly, the issue of how each SO/AC can control its "alter ego" has not been fully fleshed out. However, I believe this was discussed at some length on the legal sub team call and it seems that between the bylaws
of the UA and the charter of the SO/AC there should be very tight control by the SO/AC over any actions of the UA.</font></span></div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:Verdana;font-size:13px"><font color="#000000"><br>
</font></span></div>
</blockquote>
<br>
</span>As a non-member of the legal sub-team, I am curuious, why wouldn't one of the SOAC want to just become an UA instead of creating an additional entity? What are the legal disadvantages of transforming into an UA? As opposed to being on.<br>
<br>
Or has this already been documented in one of the many docs and I just missed it?
<br>
<br>
thanks<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
avri</font></span><span class=""><br>
<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 moz-do-not-send="true" href="http://www.avast.com/" target="_blank"><img moz-do-not-send="true" 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 moz-do-not-send="true" href="http://www.avast.com/" target="_blank">www.avast.com</a></p>
</td>
</tr>
</tbody>
</table>
<br>
</span></div>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a moz-do-not-send="true" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a moz-do-not-send="true" 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>
</blockquote>
<br>
<br>
<br>
<hr style="border:none; color:#909090; background-color:#B0B0B0; 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/"><img border="0" src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo"></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/">www.avast.com</a> </p>
</td>
</tr>
</tbody>
</table>
<br>
</div>
</div>
</span>
</body>
</html>