<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>Hmm. An April 1 RFC as a model solution for our issues with the board. Might indeed be the right approach.</div><div><br></div><div>Or was that just by way of comment. For example an explanation of why putting things in ws2 is just silly and won't work.</div><div><br></div><div><br></div><div style="font-size:75%">avri</div><div style="font-size:75%"><br></div><div style="font-size:75%">Sent from a T-Mobile 4G LTE Device</div><br><br><div>-------- Original message --------</div><div>From: Chris Disspain <ceo@auda.org.au> </div><div>Date:09/28/2015 8:42 PM (GMT-05:00) </div><div>To: Jonathan Zuck <jzuck@actonline.org> </div><div>Cc: CCWG Accountability <accountability-cross-community@icann.org> </div><div>Subject: Re: [CCWG-ACCT] CSMM as WS2 </div><div><br></div><span style="font-family: 'Verdana'; font-size: 13px; color: rgb(102, 102, 102);">Thanks Jonathan.<div class=""><br class=""></div><div class="">I find RFC 1925 most instructive when dealing with circumstances such as the one we currently find ourselves in.</div><div class=""><br class=""></div><div class=""><a href="https://www.rfc-editor.org/rfc/rfc1925.txt" class="">https://www.rfc-editor.org/rfc/rfc1925.txt</a> <br class=""><div class=""><br class="webkit-block-placeholder"></div><div apple-content-edited="true" class="">
<p class="p1" style="margin: 0px; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-family: Helvetica; min-height: 14px; color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class="Apple-interchange-newline"><span style="color: rgb(148, 67, 251); font-family: Verdana; font-size: 13px;" class="">Cheers,</span></p><p class="p3" style="margin: 0px; font-style: normal; font-variant: normal; font-weight: normal; font-size: 13px; line-height: normal; font-family: Verdana; color: rgb(148, 67, 251); min-height: 16px; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br class=""></p><p class="p2" style="margin: 0px; font-style: normal; font-variant: normal; font-weight: normal; font-size: 13px; line-height: normal; font-family: Verdana; color: rgb(148, 67, 251); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Chris</p>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 29 Sep 2015, at 09:29 , Jonathan Zuck <<a href="mailto:jzuck@actonline.org" class="">jzuck@actonline.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Here's a flyer. How about we make the determination that converting ICANN to a membership organization is a WS2 initiative and design a stress test for whatever we come up with in the interim that examines the community's ability to make this transformation post transition. With the right set of bylaws changes, the ability to spill the board, etc. we might be able to meet the WS1 requirements of "sufficient leverage to accomplish WS2." We could keep it pretty simple, eliminate the deadline, the NTIA, etc. and work towards a membership model over the following year and spill the board if they resist. I know that spilling the board is something we don't regard as practical leverage for some random policy decision but I think it's pretty credible for a restructuring. Thoughts?<br class=""><br class="">Jonathan<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>