<div dir="ltr">Dear all, dear Kavouss<div><br></div><div>I don't feel any questions on my part are missing.</div><div><br></div><div>I am clear and I think from this whole thread, it is clear to everyone that there is one entity - the Empowered Community. It is established as an unincorporated association, and it has all the powers we will give it through the ICANN bylaws. One of those powers is appointment and removal of directors. It can back those powers up in Court if need be because it is recognised as a Designator under the law of California.</div><div><br></div><div>So: the powers are set out in the bylaws as per our report. The single entity is the Empowered Community. It is the Sole Designator.</div><div><br></div><div>I'm happy and don't need any legal input, and my reading is that we are all on the same page.</div><div><br></div><div><br></div><div>bests</div><div>Jordan</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 28 January 2016 at 03:44, Kavouss Arasteh <span dir="ltr"><<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Dear Holly</div><div>No ,you have not said any thingabout the claim of Some people providing all and every power for the " Empowred Community"/" Sole Designator " versus what Bruce said and versus what Jordan said ( with which I fuklly agreed ) .</div><div>You said the following </div><div>Quote</div><span class=""><div>"<em> does not adequately describe the other important roles for the new entity, which extend well beyond the rights given to designators by California corporate law</em>" </div></span><div>Unquote</div><div>The wexpression / part of what you have said " which extend well beyond the rights given to designators by California corporate law"</div><div>This portion is totally vague and does not any thing as requested</div><div>Pls kindly and specifically , if you wish and if you respect me what is the role, responsibilities and authorities of the " <font color="#ff0000"><strong>Empowred Community"/" Sole Designator " in regard </strong><font color="#000000">with what contained in the Article of incorporation, and proposed Bylaws.</font></font></div><div><font color="#000000">As you have noted the views of ICANN is ,for instance, right of ispection is reserved for the COMMUNITY AND NOT the Sole designtor . See read ICANN Comments ( Bruce as well ), Grec's Comments and Jordan Comments</font></div><div><font color="#000000">Regards</font></div><span class="HOEnZb"><font color="#888888"><div><font color="#000000">Kavouss </font></div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2016-01-27 15:20 GMT+01:00 Seun Ojedeji <span dir="ltr"><<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Hello Kavous,</p>
<p dir="ltr">I don't understand what other study is required in this. The lawyers have provided the clarification required(indicating theroles and the relevant vehicles to exercise them) and if the 3 you mentioned have a different opinion then they would have indicated it (I note that Greg already acknowledged the response from legal).</p>
<p dir="ltr">I don't think there is need(neither is it economical) to further utilise legal hours on this unless you specifically indicate what area is not clear to you as a person (which is yet to be explained).</p>
<p dir="ltr">Regards</p><div><div>
<div class="gmail_quote">On 27 Jan 2016 14:58, "Kavouss Arasteh" <<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div dir="ltr"><div>Dear Holly</div><div>Dear Rosemary</div><div>Thank you very much for definition</div><div>However, the problem that was raised was not the definition but the scope of responsibility and mandate</div><div>There were three options</div><div>View one; From Bruce</div><div>View Two FromGrec</div><div>View three;From Jordan</div><div>Please kindly carefully study these three and comment in favour of one or other or a combination of those three.</div><div>The three designator came first from you in APRIL 2015</div><div>tHE eMPOWERED cOMMUNITY CASE FROM THE ccwg discussion.</div><div>I agree that the latter is more appropriate but the problem raised was different as described above.</div><div>Either you wish to reply or not but please kindly reply to the question raised </div><div>Regards</div><div>Kavouss </div><div> </div><div> </div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-01-27 6:53 GMT+01:00 Seun Ojedeji <span dir="ltr"><<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><p dir="ltr">Thanks a lot Rosemary that answers my question perfectly.</p>
<p dir="ltr">Regards</p><div><div>
<div class="gmail_quote">On 27 Jan 2016 6:47 a.m., "Rosemary E. Fei" <<a href="mailto:rfei@adlercolvin.com" target="_blank">rfei@adlercolvin.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<div lang="EN-US" vlink="purple" link="blue">
<div>
<p class="MsoNormal"><span style="color:black;font-family:"Arial","sans-serif";font-size:10pt">Dear Sean and all:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black;font-family:"Arial","sans-serif";font-size:10pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:black;font-family:"Arial","sans-serif";font-size:10pt">You are correct. The power to designate (and correspondingly to remove) directors is one of the powers that will be given to the Empowered Community in the Bylaws.
You could also say that acting as ICANN’s “sole designator” is one of the Empowered Community’s roles in the proposed accountability structure, along with other roles and powers that will also be given to the Empowered Community in the Bylaws.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black;font-family:"Arial","sans-serif";font-size:10pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:black;font-family:"Arial","sans-serif";font-size:10pt">The Empowered Community could be given the other powers (except the removal right) without giving it the power to designate directors – those other powers can legally
be given to any third party, not just one that holds designator powers.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black;font-family:"Arial","sans-serif";font-size:10pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:black;font-family:"Arial","sans-serif";font-size:10pt">I hope that answers your question.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black;font-family:"Arial","sans-serif";font-size:10pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:black;font-family:"Arial","sans-serif";font-size:10pt">Rosemary<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:black;font-family:"Arial","sans-serif";font-size:10pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-family:"Tahoma","sans-serif";font-size:10pt">From:</span></b><span style="font-family:"Tahoma","sans-serif";font-size:10pt"> Seun Ojedeji [mailto:<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>]
<br>
<b>Sent:</b> Tuesday, January 26, 2016 9:41 PM<br>
<b>To:</b> Holly Gregory<br>
<b>Cc:</b> Thomas Rickert; ACCT-Staff; ICANN-Adler; Sidley ICANN CCWG; <a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>; León Felipe Sánchez Ambía; Mathieu Weill<br>
<b>Subject:</b> Re: [CCWG-ACCT] Nomenclature re "Empowered Community": ICANN Board comments - Recommendation 3 - Fundamental Bylaws<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p>Thank you Holly for the clarification. This has been my understanding as well.<u></u><u></u></p>
<p>One other thing that I would appreciate if clarified is to know whether the "empowered community" is able to carry out the other roles (like approval of bylaws et all) because it is the designator or just because it is the unincorporated entity setup as
the third party to perform those roles in the bylaw.<u></u><u></u></p>
<p>In other words the unincorporated entity doubles as both the designator (with the power as described under California law) and the "enhanced community" (with the other powers as described in the bylaw).<u></u><u></u></p>
<p>Regards<u></u><u></u></p>
<div>
<p class="MsoNormal">On 26 Jan 2016 9:38 p.m., "Gregory, Holly" <<a href="mailto:holly.gregory@sidley.com" target="_blank">holly.gregory@sidley.com</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:1.5in">
<span style="font-family:"Arial","sans-serif";font-size:10pt">Dear CCWG-ACCT Co-Chairs, Members, Participants and Staff,
</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in">
<span style="font-family:"Arial","sans-serif";font-size:10pt"> </span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in">
<span style="font-family:"Arial","sans-serif";font-size:10pt">We have been monitoring the recent discussion on the CCWG-ACCT listserv about the use of the terms “community”, “Empowered Community”, and “Sole Designator” in the draft Proposal, and we wish to
share our understanding of these terms.</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in">
<span style="font-family:"Arial","sans-serif";font-size:10pt"> </span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in">
<span style="font-family:"Arial","sans-serif";font-size:10pt">We agree that the word “community” as used in the draft Proposal encompasses not only ICANN’s Board and all of its SOs and ACs and their individual members, but also those who participate in ICANN
meetings and processes, as explained by Bruce Tonkin in his January 24 email.</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in">
<span style="font-family:"Arial","sans-serif";font-size:10pt"> </span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in">
<span style="font-family:"Arial","sans-serif";font-size:10pt">“Empowered Community” is the name to be given to an unincorporated association to be created in ICANN’s Bylaws. This new entity has also been described as the “Sole Designator,” but that term
-- which arose from the new entity’s function as ICANN’s sole designator -- does not adequately describe the other important roles for the new entity, which extend well beyond the rights given to designators by California corporate law. Therefore, the “Empowered
Community” is a more appropriate reference, and it has been used interchangeably with “Sole Designator” to date.
</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in">
<span style="font-family:"Arial","sans-serif";font-size:10pt"> </span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in">
<span style="font-family:"Arial","sans-serif";font-size:10pt">As a global final edit, we recommend using “Empowered Community” consistently to refer to the new legal entity, after the first discussion of the sole designator concept.
</span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in">
<span style="font-family:"Arial","sans-serif";font-size:10pt"> </span><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in">
<span style="font-family:"Arial","sans-serif";font-size:10pt">Kind regards, </span>
<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:1.5in">
<span style="font-family:"Arial","sans-serif";font-size:10pt">Hlly and Rosemary</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="color:rgb(31,73,125);font-family:"Arial","sans-serif";font-size:10pt">HOLLY</span></b><span style="color:rgb(31,73,125);font-family:"Arial","sans-serif";font-size:9pt"> </span><b><span style="color:rgb(31,73,125);font-family:"Arial","sans-serif";font-size:10pt">GREGORY</span></b><span style="color:rgb(31,73,125);font-family:"Arial","sans-serif";font-size:9pt"><br>
Partner<br>
<br>
</span><b><span style="color:rgb(31,73,125);font-family:"Arial","sans-serif";font-size:10pt">Sidley Austin LLP</span></b><b><span style="color:rgb(31,73,125);font-family:"Arial","sans-serif";font-size:9pt"><br>
</span></b><span style="color:rgb(31,73,125);font-family:"Arial","sans-serif";font-size:9pt"><a href="tel:%2B1%20212%20839%205853" target="_blank">+1 212 839 5853</a><br>
<a title="Click to send email to Gregory, Holly" href="mailto:holly.gregory@sidley.com" target="_blank">holly.gregory@sidley.com</a></span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Arial","sans-serif";font-size:10pt"> </span><u></u><u></u></p>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0in 0in">
<p class="MsoNormal" style="margin-left:0.5in">
<b><span style="font-family:"Tahoma","sans-serif";font-size:10pt">From:</span></b><span style="font-family:"Tahoma","sans-serif";font-size:10pt">
<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">
accountability-cross-community-bounces@icann.org</a> [mailto:<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">accountability-cross-community-bounces@icann.org</a>]
<b>On Behalf Of </b>Greg Shatan<br>
<b>Sent:</b> Monday, January 25, 2016 11:42 PM<br>
<b>To:</b> Jordan Carter<br>
<b>Cc:</b> <a href="mailto:accountability-cross-community@icann.org" target="_blank">
accountability-cross-community@icann.org</a><br>
<b>Subject:</b> Re: [CCWG-ACCT] ICANN Board comments - Recommendation 3 - Fundamental Bylaws</span><u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-left:0.5in">
<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Verdana","sans-serif"">Recommendation 1 states:</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Verdana","sans-serif""> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Helvetica","sans-serif";font-size:11pt">. The entity created using the Sole Designator model will be referred to as the “Empowered Community.”</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Helvetica","sans-serif";font-size:11pt">(Summary, Page 1, bullet point 3).</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Verdana","sans-serif""> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Helvetica","sans-serif";font-size:11pt">In other words the Sole Designator is the Empowered Community, and vice versa. You are introducing a dichotomy where none exists.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Helvetica","sans-serif";font-size:11pt">Greg</span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
On Mon, Jan 25, 2016 at 5:39 PM, Jordan Carter <<a href="mailto:jordan@internetnz.net.nz" target="_blank">jordan@internetnz.net.nz</a>> wrote:<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:0.5in">
This isn't quite right - as far as I am aware the entity that is the Sole Designator will have the right to appoint and remove directors, and be the 'third party' that can approve changes to Icann fundamental bylaws or block changes to Icann standard bylaws.<u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
I'm not sure this is a revelation of any sort, or causes any confusion at all. These powers along with all the others will be set out in the bylaws, as has been the case all along. The only distinguishing feature is that the legislation in California gives
designators the director rights, and gives the right of the articles / bylaws to include third party approvals.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
Even if people are confused about this, there is no problem in substance to resolve.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
Cheers<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
Jordan <u></u><u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<br>
<br>
On Monday, 25 January 2016, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>> wrote:<u></u><u></u></p>
<p style="margin-left:0.5in">Hi Greg,<u></u><u></u></p>
<p style="margin-left:0.5in">I don't think we are in disagreement in the substance of all these. It's just the naming we are in disagreement upon and I am still of the opinion that a designator only has the statutory power to remove/add board members.
<u></u><u></u></p>
<p style="margin-left:0.5in">All other powers/process we have managed to put in the bylaw may need to be called/named something else as they are not made possible because of the designator but rather because of the fact that they are now written in the bylaw
and the board normally would want to respect such a document.<u></u><u></u></p>
<p style="margin-left:0.5in">In anycase, unless there is any other change you think has been proposed other than giving inspection rights to the community (which you and I are in agreement) that affects the current proposal, I don't see any reason to still
consider this open as such.<u></u><u></u></p>
<p style="margin-left:0.5in">Regards<u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
On 24 Jan 2016 18:02, "Greg Shatan" <<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>> wrote:<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Verdana","sans-serif"">Seun,</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Verdana","sans-serif""> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Verdana","sans-serif"">You misunderstand me. The Designator does more than "enforce" powers. Under our proposal, the designator is also the vehicle for
<u>exercising</u> a number of the powers (e.g., approving/rejecting bylaws). The exercise of the new powers by the designator will be a much more common occurrence than the enforcement of those powers by removing directors. I anticipate the latter will rarely
(if ever) occur, though the fact it can occur is part of our accountability framework. There are other reasons for the Board to comply with the community's exercise of its powers, aside from sheer terror at being removed. For one thing, these powers are
enshrined in the bylaws, and the Board (like any Board) will not take the prospect of violating our Bylaws lightly.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Verdana","sans-serif""> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Verdana","sans-serif"">We have had a tendency to overemphasize the enforcement end of things, and I think this is one more action in that vein. Let's try to avoid that. Just like our proposal is about far more than "enforcement,"
so is the Single Designator.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Verdana","sans-serif""> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Verdana","sans-serif"">So, no, your statement did not "close this particular item." Rather, it demonstrates exactly why this item is not really closed.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Verdana","sans-serif""> </span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="font-family:"Verdana","sans-serif"">Greg</span><u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
<u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-left:0.5in">
On Sun, Jan 24, 2016 at 10:48 AM, Seun Ojedeji <<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>> wrote:<u></u><u></u></p>
<p style="margin-left:0.5in">On 24 Jan 2016 16:15, "Greg Shatan" <<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>> wrote:<br>
><br>
> I agree with the result the Board came to (at least in part), but not the reasoning. Each SO or AC should have the right to inspect. However, the role of the Designator is not merely to "add or remove Board members." The Designator plays a critical role
in the exercise of several of the powers, in addition to its role in enforcing those powers via director removal. <br>
><br>
SO: I guess Bruce was rightly mentioning the powers of the designator. I believe we we will only be getting those powers enforced as a result of the "add/remove" power of the designator.
<u></u><u></u></p>
<p style="margin-left:0.5in">So in summary we don't get enforcement of the various powers because it's a role of the designator but on the basis that the designator may use its only statutory power, which is to add/remove board members.<u></u><u></u></p>
<p style="margin-left:0.5in">I generally agree with the result and would have even preferred that a threshold be required for inspection. However, on the basis that each SO/AC may need access to certain information to make informed/independent decisions, it
makes sense to allow such right to each SO/AC.<u></u><u></u></p>
<p style="margin-left:0.5in">Hopefully this close this particular item.<u></u><u></u></p>
<p style="margin-left:0.5in">Regards<u></u><u></u></p>
<div>
<div>
<p style="margin-left:0.5in"> on Recommendation 1.<br>
>><br>
>> Just to provide a little more context in response to questions on the list.<br>
>><br>
>> The role of the designator is to add or remove Board directors. This role is enforceable under California law.<br>
>><br>
>> The inspection right is a right for the ACs and SOs. An AC or SO can exercise this right independently of the legal entity that will be the sole designator. If ICANN doesn't respond to an appropriate request from an SO or AC, it would be in breach
of its bylaws. The community can then use the IRP to get a binding decision. In the unlikely event that the Board does not comply with the outcome of the IRP decision, then the designator has the power to remove Board members.<br>
>><br>
>> In the bylaws we want to make sure that we don't confuse the role of the designator (add or remove Board members) with the various roles of the SO and ACs in the bylaws. The bylaws are primarily enforced by the IRP, and then the designator (via removal
of Board directors) if the IRP is not complied with, and then the courts if the decision of the designator is not complied with. This is a clear escalation path that applies to all bylaws.<br>
>><br>
>> Regards,<br>
>> Bruce Tonkin<br>
>><br>
>> _______________________________________________<br>
>> Accountability-Cross-Community mailing list<br>
>> <a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
>> <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=CwMFaQ&c=Od00qP2XTg0tXf_H69-T2w&r=1-1w8mU_eFprE2Nn9QnYf01XIV88MOwkXwHYEbF2Y_8&m=du2OD2nYZAU6l2XqEbv_LKsFVqwjXyksiXMKhZ3VDQk&s=v4A3ZwzM9FERJEYcFy5L5NNJvUY3v00O8niOIrVLuSg&e=" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Accountability-Cross-Community mailing list<br>
> <a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
> <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=CwMFaQ&c=Od00qP2XTg0tXf_H69-T2w&r=1-1w8mU_eFprE2Nn9QnYf01XIV88MOwkXwHYEbF2Y_8&m=du2OD2nYZAU6l2XqEbv_LKsFVqwjXyksiXMKhZ3VDQk&s=v4A3ZwzM9FERJEYcFy5L5NNJvUY3v00O8niOIrVLuSg&e=" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
><u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-left:0.5in">
<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-left:0.5in">
<span style="color:rgb(136,136,136)"><br>
<br>
-- <br>
Jordan Carter<br>
Chief Executive, InternetNZ</span><u></u><u></u></p>
<p style="margin-left:0.5in"><span style="color:rgb(136,136,136)"><a href="tel:%2B64-21-442-649" target="_blank">+64-21-442-649</a> |
<a href="mailto:jordan@internetnz.net.nz" target="_blank">jordan@internetnz.net.nz</a></span><u></u><u></u></p>
<p style="margin-left:0.5in"><span style="color:rgb(136,136,136)">Sent on the run, apologies for brevity</span><u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-left:0.5in">
<u></u><u></u></p>
</div>
</div>
<p> <u></u><u></u></p>
<p>****************************************************************************************************<br>
This e-mail is sent by a law firm and may contain information that is privileged or confidential.<br>
If you are not the intended recipient, please delete the e-mail and any attachments and notify us<br>
immediately.<br>
<br>
****************************************************************************************************<u></u><u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12pt"><br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">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><u></u><u></u></p>
</div>
</div>
</div>
</blockquote></div>
</div></div><br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div>
</div></div></blockquote></div><br></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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr" style="font-size:small">Jordan Carter<br><br>Chief Executive <br><b>InternetNZ</b><br></div><div dir="ltr" style="font-size:small"><br>+64-4-495-2118 (office) | +64-21-442-649 (mob)<br>Email: <a href="mailto:jordan@internetnz.net.nz" style="color:rgb(17,85,204)" target="_blank">jordan@internetnz.net.nz</a> <br>Skype: jordancarter<br></div><div style="font-size:small">Web: <a href="http://www.internetnz.nz" target="_blank">www.internetnz.nz</a> </div><div dir="ltr" style="font-size:small"><br><i>A better world through a better Internet </i></div><br></div></div></div></div></div></div></div></div>
</div>