<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hello Robin,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thank you very much for your contribution.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I have a difficulty with this sentence: “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”.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Could you be more specific: how would you define the “proportional share” of each component?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Olivier<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">De :</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org]
<b>De la part de</b> Robin Gross<br>
<b>Envoyé :</b> mardi, février 03, 2015 18:50<br>
<b>À :</b> Steve DelBianco; Jordan Carter; Accountability Cross Community; wp1@icann.org<br>
<b>Objet :</b> [CCWG-ACCT] Proposal for a Community Veto Process on Key Board Decisions via Bylaws Amendment<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal">Steve, Jordan, all,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></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. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Robin<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><b>Community Veto Process on Key Board Decisions via Bylaws Amendment</b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></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).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></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. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></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:white">§</span>5210), but we could significantly empower the community by creating a veto process with teeth behind it.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></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.<o:p></o:p></p>
</div>
</div>
<PRE>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</PRE></body>
</html>