<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div>Some details to work out but this seems workable<br>
<br>
Becky Burr
<div><span style="font-size: 13pt;">Sent from my iPhone</span></div>
</div>
<div><br>
On May 23, 2015, at 02:02, Chris Disspain <<a href="mailto:ceo@auda.org.au">ceo@auda.org.au</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span>Bruce,</span><br>
<span></span><br>
<span>Agreed. If we go to a member structure this would be the simplest and easiest way of achieving it.</span><br>
<span></span><br>
<span>And by indemnity I assume you mean an indemnity as to any personal liability the member may incur by, say, being sued in their capacity as a member etc.. I think that's both necessary and workable in such a structure.
</span><br>
<span></span><br>
<span>Cheers,</span><br>
<span></span><br>
<span>Chris Disspain | Chief Executive Officer</span><br>
<span>.au Domain Administration Ltd</span><br>
<span>T: +61 3 8341 4111 | F: +61 3 8341 4112</span><br>
<span>E: <a href="mailto:ceo@auda.org.au">ceo@auda.org.au</a> | W: <a href="http://www.auda.org.au">
www.auda.org.au</a></span><br>
<span></span><br>
<span>auDA - Australia's Domain Name Administrator</span><br>
<span></span><br>
<blockquote type="cite"><span>On 23 May 2015, at 18:43, Bruce Tonkin <<a href="mailto:Bruce.Tonkin@melbourneit.com.au">Bruce.Tonkin@melbourneit.com.au</a>> wrote:</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Hello All,</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>I have been reading the various discussions on the topic of using members as a way of holding ICANN accountable.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Speaking personally - I think the concept of members can work.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>My advice though would be to try to keep it simple. The idea of creating separate unincorporated versions of the GAC, ccNSO etc - just adds complexity that makes it more and more difficult for outsiders to really understand
how ICANN works. It already takes years to understand how the GNSO or ALAC processes work.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>From my personal perspective - we should just allow the SOs and ACs to appoint their chairs/vice-chairs or nominated representatives as "members" of ICANN for a term that matches the term of their office. This seems to require
minimal change in ICANN's existing structure.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Each individual that is selected to become a member of ICANN could then sign an agreement with ICANN that ensures that ICANN provides some indemnity for the member, provided that the member operates in accordance with the direction
of their SO and AC through a properly constituted motion according to the procedures of that group. Ie the member would have a very narrow role to basically convey the decision of the respective SO and AC.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Regards,</span><br>
</blockquote>
<blockquote type="cite"><span>Bruce Tonkin</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>_______________________________________________</span><br>
</blockquote>
<blockquote type="cite"><span>Accountability-Cross-Community mailing list</span><br>
</blockquote>
<blockquote type="cite"><span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a></span><br>
</blockquote>
<blockquote type="cite"><span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=AwICAg&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=I6N22Kpb51uwvTS691MCITRpdzBF3OlLgIKXyEihkPc&s=sLgtbOJPvshX2V7c4aRbrNAM29SzQa_mud_46DjejHA&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=AwICAg&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=I6N22Kpb51uwvTS691MCITRpdzBF3OlLgIKXyEihkPc&s=sLgtbOJPvshX2V7c4aRbrNAM29SzQa_mud_46DjejHA&e=</a>
</span><br>
</blockquote>
<span>_______________________________________________</span><br>
<span>Accountability-Cross-Community mailing list</span><br>
<span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a></span><br>
<span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=AwICAg&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=I6N22Kpb51uwvTS691MCITRpdzBF3OlLgIKXyEihkPc&s=sLgtbOJPvshX2V7c4aRbrNAM29SzQa_mud_46DjejHA&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=AwICAg&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=I6N22Kpb51uwvTS691MCITRpdzBF3OlLgIKXyEihkPc&s=sLgtbOJPvshX2V7c4aRbrNAM29SzQa_mud_46DjejHA&e=</a>
</span><br>
</div>
</blockquote>
</body>
</html>