<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;" class=""><span style="font-family: 'Verdana'; font-size: 13px; color: rgb(102, 102, 102);">Hi Alan,<div class=""><br class=""></div><div class="">This sounds/looks like a really interesting idea. On the face of it, it’s something we could buy in to. I look forward to having this fleshed out in the CCWG.<br class=""><div class="">
<style type="text/css" class="">
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Verdana; color: #424242}
p.p3 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Verdana; color: #424242; min-height: 16.0px}
p.p4 {margin: 0.0px 0.0px 0.0px 0.0px; font: 13.0px Verdana; color: #103ffb}
p.p5 {margin: 0.0px 0.0px 0.0px 0.0px; font: 9.0px Verdana; color: #ffa827; min-height: 11.0px}
p.p6 {margin: 0.0px 0.0px 0.0px 0.0px; font: 10.0px Verdana; color: #424242}
span.s1 {color: #000000}
span.s2 {color: #ff9324}
span.s3 {text-decoration: underline}
span.s4 {color: #424242}
span.s5 {text-decoration: underline ; color: #0000ee}
span.s6 {color: #ffa827}
span.s7 {color: #6c6c6c}
span.s8 {text-decoration: underline ; color: #103ffb}
</style>
<p class="p1"><br class=""></p>
<p class="p2">Cheers,</p>
<p class="p3"><br class=""></p>
<p class="p2">Chris Disspain<span class="s1"> </span><span class="s2">|</span><span class="s1"> </span>Chief Executive Officer</p>
<p class="p2">.au Domain Administration Ltd</p>
<p class="p2">T: <span class="s3">+61 3 8341 4111</span><span class="s1"> </span><span class="s2">|</span><span class="s1"> </span>F: <span class="s3">+61 3 8341 4112</span></p>
<p class="p4"><span class="s4">E:</span><span class="s1"> <a href="mailto:ceo@auda.org.au" class=""><span class="s5">ceo@auda.org.au</span></a> </span><span class="s6">|</span><span class="s1"> </span><span class="s4">W:</span><span class="s7"> <a href="http://www.auda.org.au/" class=""><span class="s8">www.auda.org.au</span></a></span><span class="Apple-converted-space"> </span></p>
<p class="p2">auDA – Australia’s Domain Name Administrator</p>
<p class="p5"><br class=""></p>
<p class="p6"><span class="s6"><b class="">Important Notice</b></span><span class="s1"><b class=""> </b></span><b class="">- </b>This email may contain information which is confidential and/or subject to legal privilege, and is intended for the use of the named addressee only. If you are not the intended recipient, you must not use, disclose or copy any part of this email. If you have received this email by mistake, please notify the sender and delete this message immediately. Please consider the environment before printing this email.</p>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 19 Jun 2015, at 11:17 , Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" class="">alan.greenberg@mcgill.ca</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Given the spread between those who believe that we need ultimate accountability, and those who are willing to trust that the community wishes will be honoured, allow me to put a new variation on the table. We have talked about all of the parts before, but perhaps the combination is new.<br class=""><br class="">This proposal involves no Unincorporated Associates, no Designators and no Members.<br class=""><br class="">Up to now, we have been working with Bylaws that we are now told have no real basis in law, but which so far, have worked. I specifically refer to things like the SOs, ALAC and the NomCom appointing Board members, powers that under California law are only given to Members or Designators, but our less formal entities are granted these powers under the ICANN Bylaws and for whatever reasons, it works.<br class=""><br class="">I propose that we do the same with all of the community powers that we want (including the requirement that Bylaws and certainly fundamental Bylaws be approved), with the exception of formal budget approval (which impinges on Board fiduciary responsibility). In lieu of the latter, we could have a process by which and AC/SO lodges a formal objection to a budget or budget item, and the Board has an obligation to follow-up (I am not going to go into any further details here).<br class=""><br class="">Every Director, as a requirement of being seated signs an irrevocable letter saying that if by specified procedure, they are requested to step down, they will. The procedure might include the formal action of the AC/SO that appointed them, or a more widespread community request passing a specified level of AC/SO support - the details would need to be defined, but do not alter this proposal. The letter would also make reference to an enforcement mechanism that could be invoked. The enforcement mechanism might be to give the ICANN Ombudsman (or some other trustworthy and trusted individual) the right to take court action to require the requested resignation be honoured, or could give that right to the people occupying the AC/SO Chairs. Any such action would be funded by ICANN and funds held in escrow to ensure that this can be carried out.<br class=""><br class="">In unlikely event that a removal included the entire Board, or some number such that the remaining Board members do not meet minimum quorum requirements, the AC/SO Chairs will on an interim basis be added to the Board on an interim basis. This augmented interim Board would have caretaker responsibilities and have only limited rights (to be specified).<br class=""><br class="">Board member removals would be unconditional and not appealable.<br class=""><br class="">I believe that the threat of invoking removal will likely be sufficient to ensure that the community is given good control. And should that fail, the actual removal of the Board member(s) who do not support the community position can actually be removed.<br class=""><br class="">There are many details to be determined but I believe that this is workable. It allows for the most of the powers that have been requested with a minimum number of changes and does not create significant new potential vulnerabilities.<br class=""><br class="">Alan<br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">Accountability-Cross-Community mailing list<br class=""><a href="mailto:Accountability-Cross-Community@icann.org" class="">Accountability-Cross-Community@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community<br class=""></div></blockquote></div><br class=""></div></span></body></html>