<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">Appreciation also to Robin, and i have a follow-up to Pedro's useful comments below:<br><br>On Tue, Feb 3, 2015 at 8:33 PM, Pedro Ivo Ferraz da Silva <span dir="ltr"><<a href="mailto:pedro.ivo@itamaraty.gov.br" target="_blank">pedro.ivo@itamaraty.gov.br</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div link="blue" vlink="purple" lang="PT-BR">
<div><br> <p><u></u><span style="font-size:11pt;font-family:Symbol;color:rgb(31,73,125)" lang="EN-US"><span>·<span style="font:7pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US">In the following extract, do you really propose the Board would have the ability to veto the community's veto or did I get it wrong?
"</span><span lang="EN-US">The board would then be required to adopt this Decision of the Community unless it voted (unanimous or super-majority) to reject the Decision of the Community that was reached via this process and which would be stipulated to in
bylaws and/or articles of incorporation.</span><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US">"</span></p></div></div></blockquote><div><br>I guess that is how i also understand it and i think its normal to give the board such option in this process and watch them take it ;-). If they then decide to take the route of rejecting then i guess that would be when the second community tool will kick-in, i.e recall of recalcitrant board members. What i think needs to be clarified is whether just empowering the community (a CCWG perhaps) through the bylaw (without formal creation of any membership structure) will be binding. (I guess it will be useful to get legal advice on that)<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div link="blue" vlink="purple" lang="PT-BR"><div><p><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US"><u></u><u></u></span></p>
<p><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US"><u></u> <u></u></span></p>
<p><u></u><span style="font-size:11pt;font-family:Symbol;color:rgb(31,73,125)" lang="EN-US"><span>·<span style="font:7pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US">What exactly do you mean by "relevant Community"? I believe this concept would definitely need to be nailed down, as it may include many
different actors. All SOs and ACs would be an ideal initial list of sub- communities, but we would also need to consider IANA customers and other important actors part of the greater "Internet multistakeholder community" which obviously do have a stake in
what ICANN does. </span></p></div></div></blockquote><div>Hmm...i think going beyond ICANN SOs/ACs could further complicate the task especially as the "Internet multistakeholder community" can mean "infinity" ;-). However i would expect that any SO/AC process will be open enough to accommodated those who are not entirely involved with ICANN community. For instance, I would expect the ccNSO process to provide mechanism that allows non-ccNSO ccTLD to raise their view on a critical issue like this one.<br><br></div>Regards!<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div link="blue" vlink="purple" lang="PT-BR"><div><p><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US">Kind regards,
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)" lang="EN-US"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">Sec. Pedro Ivo Ferraz da Silva</span><span style="color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">Divisão de Sociedade da Informação (DI)<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">Ministério das Relações Exteriores<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)">T: <a href="tel:%2B%2055%2061%202030-6609" value="+556120306609" target="_blank">+ 55 61 2030-6609</a><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"Calibri","sans-serif";color:rgb(31,73,125)"><u></u> <u></u></span></p>
<div>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) -moz-use-text-color -moz-use-text-color;padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10pt;font-family:"Tahoma","sans-serif"">De:</span></b><span style="font-size:10pt;font-family:"Tahoma","sans-serif""> <a href="mailto:wp1-bounces@icann.org" target="_blank">wp1-bounces@icann.org</a> [mailto:<a href="mailto:wp1-bounces@icann.org" target="_blank">wp1-bounces@icann.org</a>]
<b>Em nome de </b>Robin Gross<br>
<b>Enviada em:</b> terça-feira, 3 de fevereiro de 2015 15:50<br>
<b>Para:</b> Steve DelBianco; Jordan Carter; Accountability Cross Community; <a href="mailto:wp1@icann.org" target="_blank">wp1@icann.org</a><br>
<b>Assunto:</b> [Party1] Proposal for a Community Veto Process on Key Board Decisions via Bylaws Amendment<u></u><u></u></span></p>
</div>
</div><div><div class="h5">
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Steve, Jordan, all,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">As promised on this morning's call, below is a further elaboration of the community empowerment proposal to amend the bylaws to create a community veto process. Thank you in advance for including this proposal along with the other suggestions
for community empowerment mechanisms in the group inventory for further consideration. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Best,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Robin<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><b>Community Veto Process on Key Board Decisions via Bylaws Amendment</b><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Amend the existing corporate bylaws (and /or articles of incorporation) to create a new mechanism that empowers the Community to overturn board decisions on a limited number of specific, enumerated issues and also to recall nonperforming
board members. This community veto process would be fashioned such that a decision to over-rule the board is determined via aggregation of decisions of the existing ICANN community structures. Each individual component of the relevant Community (for example,
GAC, GNSO, At-Large, CCNSO, etc.) would have a proportional share in the over-all Decision of the Community (to veto or not to veto the board). Each of these individual structures already has internal mechanisms to make decisions through which the larger
Decision of the Community could ultimately be determined. We must scope what specific enumerated decisions can trigger such a community veto process (ex: the list developed in Frankfurt) and also a specific mechanism for triggering the veto process (ex: complaint
supported by relevant 2 community components).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">The ombudsman (or neutral 3rd-party) could act as the facilitator of this community veto process in a purely administrative role: accept the matter for review, call the question to community vote, and collect the decisions of the individual
components to reach the overall Decision of the Community (to veto or not to veto). The board would then be required to adopt this Decision of the Community unless it voted (unanimous or super-majority) to reject the Decision of the Community that was reached
via this process and which would be stipulated to in bylaws and/or articles of incorporation. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Coupled with another bylaws revision providing for the ability of the community to recall recalcitrant board members, it would be difficult for the board to disregard the bottom-up Decision of the Community on a few specific matters. Larry
Strickling's speech last week hinted that an ability to recall board members would be part of the solution NTIA is looking for in the transition. Under this community veto model, the board would still maintain the requisite ultimate direction and control
that is required by California corporations law (<span style="background:none repeat scroll 0% 0% white">§</span>5210), but we could significantly empower the community by creating a veto process with teeth behind it.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Amending the bylaws allows us to create the ability to overturn board decisions and thus empower the community without the need to create complicated new membership organizations or super-structures to be representational of the community.
Creating a community veto process is a simpler and lighter approach to achieving the same community powers and would use the existing organizational structure. This would be a more bottom-up method of reaching a decision of the community to overturn a particular
board decision and it wouldn't require a radical remaking of ICANN's organizational and legal structure, but rather, a couple key bylaws amendments. The creation of this community veto process is not without challenges, but I think most concerns can be addressed
as we hammer it out and further develop the community veto model as a possibility to consider for empowering the community with respect to key board decisions.<u></u><u></u></p>
</div>
</div></div></div>
</div>
<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">------------------------------------------------------------------------<br><font color="#888888"><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;font-family:garamond,serif">
<i><span style="color:rgb(0,102,0)">Seun Ojedeji,<br style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">Federal University Oye-Ekiti<br style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">web: </span><a href="http://www.fuoye.edu.ng" target="_blank">http://www.fuoye.edu.ng</a><br>
<span style="color:rgb(0,102,0)"></span><span style="color:rgb(0,102,0)">Mobile: <a value="+2348035233535">+2348035233535</a></span><span style="color:rgb(0,102,0)"></span><br></i><i><span style="color:rgb(0,102,0)">alt email:<a href="http://goog_1872880453" target="_blank"> </a><a href="mailto:seun.ojedeji@fuoye.edu.ng" target="_blank">seun.ojedeji@fuoye.edu.ng</a></span></i><br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The key to understanding is humility - my view !<br></blockquote></blockquote></font><br></div></div>
</div></div>