[CCWG-ACCT] Regarding members

[Burr, Becky]

Some details to work out but this seems workable

Becky Burr
Sent from my iPhone

On May 23, 2015, at 02:02, Chris Disspain <ceo at auda.org.au<mailto:ceo at auda.org.au>> wrote:

Bruce,

Agreed. If we go to a member structure this would be the simplest and easiest way of achieving it.

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.

Cheers,

Chris Disspain | Chief Executive Officer
.au Domain Administration Ltd
T: +61 3 8341 4111 | F: +61 3 8341 4112
E: ceo at auda.org.au<mailto:ceo at auda.org.au> | W: www.auda.org.au<http://www.auda.org.au>

auDA - Australia's Domain Name Administrator

On 23 May 2015, at 18:43, Bruce Tonkin <Bruce.Tonkin at melbourneit.com.au<mailto:Bruce.Tonkin at melbourneit.com.au>> wrote:

Hello All,

I have been reading the various discussions on the topic of using members as a way of holding ICANN accountable.

Speaking personally - I think the concept of members can work.

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.

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.

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.

Regards,
Bruce Tonkin

_______________________________________________
Accountability-Cross-Community mailing list
Accountability-Cross-Community at icann.org<mailto:Accountability-Cross-Community at icann.org>
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=
_______________________________________________
Accountability-Cross-Community mailing list
Accountability-Cross-Community at icann.org<mailto:Accountability-Cross-Community at icann.org>
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=
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20150523/7258fa50/attachment.html>