<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>
<div>Thanks Jordan, that’s very helpful. My observation is that the visions have a common strategic line: shifting some of the powers of the ICANN board to another structure and that structure containing customers/stakeholders. How this structure is „filled”
and positioned in the governance structure of ICANN, is where the differences occur. One could consider that to be details, indeed to be explored and developed</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">Regards,</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 Meijer</font></font></div>
</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>maandag 19 januari 2015 16:00<br>
<span style="font-weight:bold">To: </span>Accountability Cross Community <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>[CCWG-Accountability] Membership thoughts<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">Hi all
<div><br>
</div>
<div>I wanted to explain a bit more why I thought implementing a membership system might be an addition to accountability.</div>
<div><br>
</div>
<div>The main point is in building an ICANN that is less centralised.</div>
<div><br>
</div>
<div>At the moment, in respect of policymaking, the ICANN bylaws set out various requirements. E.g. my understanding is that the ICANN Board can't make generally policy for ccTLDs except in endorsing the outcome of a PDP from the ccNSO (I caveat it with the
fact I haven't researched the bylaws).</div>
<div><br>
</div>
<div>There are other areas of ICANN work where there isn't external control of the board. E.g. the budget-setting process, governing scope, and so on.</div>
<div><br>
</div>
<div>A lightweight membership structure that gave representatives from the SOs and ACs (and maybe more widely, though at this point I don't see the argument for that) a particular role at a particular general meeting (e.g. approving the budget, approving new
members, ratifying changes to the bylaws) would provide new accountability in a fairly straightforward manner. </div>
<div><br>
</div>
<div>Such an approach doesn't change the fact the ICANN Board governs the organisation between general meetings; it doesn't create a split board unlike Roeolf's proposal; it works regardless of whether IANA stewardship is concentrated solely within ICANN or
is distributed between organisations as it is today. It's a model most people are familiar with. </div>
<div><br>
</div>
<div>In the discussion this morning some people offered feedback that it would be complicated. I agree that there are some design decisions that would need to be made:</div>
<div><br>
</div>
<div>a) what classes of membership are available</div>
<div>b) what powers do the members collectively have and how do they make use of them</div>
<div>c) what majorities are required in order for decisions to stick</div>
<div><br>
</div>
<div>It would be straightforward and possible to make e.g. SO and AC chairs effective "members" of ICANN (we define our own membership system). It would be harder to allow individuals with some standing to join stakeholder constituencies of voters and then
allocate shares of total votes across these in a fair way. It would be possible but mad to have a "one member one vote" system where a ccTLD manager had the same say as an Internet user.</div>
<div><br>
</div>
<div>If this is a concept to explore and develop further as part of our work, I am happy to help. I have direct experience of this at InternetNZ, and through other organisations. I know many of you would too. </div>
<div><br>
</div>
<div><br clear="all">
<div>cheers</div>
<div>Jordan</div>
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<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>To promote the Internet's benefits and uses, and protect its potential.</i><br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>