<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</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>
<div>I am not a lawyer either. But I think that a lot of issues Samantha identifies are resolved if there’s only one member: a single legal entity containing the stakeholders roughly as in the „Community Council” or „permanent CCWG” proposals. The constituencies
represented in the single member, won’t have to become legal entities themselves. And we won’t have to add or remove members when we gain new insights as to what stakeholders should be represented, they would just be added to/removed from the group forming
the single member.</div>
<div><br>
</div>
<div>Maybe this single member should itself be an association?</div>
<div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><br>
</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Best,</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri"><br>
</font></font></div>
<div><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" face="Calibri">Roelof</font></font></div>
</div>
</div>
<div><br>
</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>Jordan Carter <<a href="mailto:jordan@internetnz.net.nz">jordan@internetnz.net.nz</a>><br>
<span style="font-weight:bold">Date: </span>woensdag 15 april 2015 09:41<br>
<span style="font-weight:bold">To: </span>Samantha Eisner <<a href="mailto:Samantha.Eisner@icann.org">Samantha.Eisner@icann.org</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:wp1@icann.org">wp1@icann.org</a>" <<a href="mailto:wp1@icann.org">wp1@icann.org</a>>, "<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] [WP1] Comments and questions on legal docs<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">Sam, I would just like to say thank you for this contribution. I think it is both thoughtful and helpful.
<div><br>
</div>
<div>I hope that this can be raised with the legal team and fed to their work. What I do not know is how much of this detail we will need to resolve in the prep for the first comment period report. We will be talking about how to deal with the slightly vexed
question of how to deal with that at our next call, coming up in about thirteen hours.</div>
<div><br>
</div>
<div>best,</div>
<div>Jordan</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 15 April 2015 at 13:58, Samantha Eisner <span dir="ltr">
<<a href="mailto:Samantha.Eisner@icann.org" target="_blank">Samantha.Eisner@icann.org</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;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>I have a group of questions, and share this with WP1 as well as the broader CCWG as well for consideration. Some of them are legal issues, some of them are more accountability related issues for CCWG consideration now that we have some guidance from the
lawyers.</div>
<div><br>
</div>
<div>To help illustrate my concerns, I’ve followed Robin’s Chart format and created two of my own, (though my excel powers clearly are nowhere near hers!). The first chart is based off of the slides that were presented on today’s CCWG call, in particular the
membership and the delegate slides. I have removed reference to the TLG as it no longer has a role in appointing Board members and is itself a collection of external groups. I have also included the ALAC, which was not fully referenced on those slides as
it is the At-Large Community that is the body that appoints to the Board, not the ALAC, therefore I think we need to look at how the ALAC is considered within this process.</div>
<div><br>
</div>
<div>Using the same 6 powers that Robin highlighted in her chart, I then took those powers and identified how I understand the powers to be exercised by the different Sos and Acs when relying on a membership or designator model, to get a better sense of where
the groups that are formally identified as members or designators could act, which then raises the questions of what happens to those groups that are not identified as members or designators. This seems to me to be a key area where we need to focus – how
does the move to a different structure actually impact the multistakeholder actors within ICANN? </div>
<div><br>
</div>
<div>Some of the key questions that I propose we need to consider are:</div>
<ol>
<li>If there is a move to member organization, what does it really mean in terms of exercising of community powers if some Sos/Acs are members and some aren’t? </li><li>If there are members/non-members how much of the relationships among the Sos and Acs in exercising community powers would be based in contract? Would non-members need to enter into contracts too, or would their powers just be expressed within the Bylaws
or Articles of incorporation?</li><li>If contracts are required, wouldn’t that also require the formation of some sort of legal entity (unincorporated association or otherwise) to enter into the agreements, even among non-members? Who are the parties to these contracts?</li><li>Would each of the groups that are members have be subject to California law once they form as an unincorporated association (or other legal entity)? Is this viable across the ICANN community? </li><li>How is a group such as the At-Large Community to be recognized as an unincorporated association? If the GAC wanted to be a member, is that something that is even possible for it to do? Or the ccNSO, keeping in mind the concerns that Chris Disspain raised
on our call? Or any other group? Is this feasible?</li><li>What are the mechanisms that the members will use to be accountable to each other, particularly when there is no fiduciary duty and the expectation of acting in personal interest? </li><li>Particularly if there are members/non-members, what accountability mechanisms will be in place to make sure that the members don’t act to the disadvantage of non-members? (Examples: blocking a budget that includes funds for the performance of the IANA
functions in service to the protocol parameters community, assuming the IETF is not a member; blocking a board action that is intended to enact a non-member advisory committee’s advice)</li><li>Where does the NomCom belong? Is it appropriate for a group that changes composition on a yearly basis to be a member? Is it a collective association of all entities that currently appoint delegates to the NomCom? Does that give some members more say
that others if there are members/non-members to ICANN (Ex: GNSO appoints multiple delegates through its Sgs and Constituencies – would those groups get to impact both NomCom exercise of membership as well as GNSO exercise of membership?)</li><li>To what extent does the designator model rely on the formation of associations and contracts to achieve the stated reforms?</li></ol>
<div><br>
</div>
<div><br>
</div>
<div>The second sheet (membership rights) are the enumerated powers of members that were set forth in Sidley’s 12 April memo to the CCWG. Understanding that each of these can be applicable to members, how are they applicable to non-members?</div>
<div><br>
</div>
<div>There are likely additional questions, but these are some of the hallmark ones that stand out to me if we look at how structural changes could actually be applied to ICANN, and not just look at it from the pure legal view of structures that would empower
the anticipated solutions.</div>
<div><br>
</div>
<div>Once we understand these a bit more, then we can turn to the more fundamental questions of whether the positives and negatives of what can be achieved through the proposed structural changes make those changes the best ways to achieve the reforms. That
can include issues of practicality of implementation, time for implementation, the ability for less complex measures to achieve many goals (such as developing robust Bylaws revisions) while identifying that if more major changes such as the systemic move to
membership is seen as appropriate after robust community debate, that the Board would be obligated to take that recommendation on (similar to how WS2 will be treated).</div>
<div><br>
</div>
<div>Thanks for your consideration of these issues. </div>
<div><br>
</div>
<div>Best, </div>
<div><br>
</div>
<div>Sam</div>
<div><br>
</div>
<span>
<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">
<br>
</div>
</span></div>
<br>
_______________________________________________<br>
WP1 mailing list<br>
<a href="mailto:WP1@icann.org">WP1@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/wp1" target="_blank">https://mm.icann.org/mailman/listinfo/wp1</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">Jordan Carter<br>
<br>
Chief Executive <br>
<b>InternetNZ</b><br>
<br>
04 495 2118 (office) | +64 21 442 649 (mob)<br>
<a href="mailto:jordan@internetnz.net.nz" target="_blank">jordan@internetnz.net.nz</a><br>
Skype: jordancarter<br>
<br>
<i>A better world through a better Internet </i><br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>