<div dir="ltr"><div><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 0pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="color:rgb(34,34,34);font-family:"Arial","sans-serif";font-size:8pt">Dear holly,</span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 0pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="color:rgb(34,34,34);font-family:"Arial","sans-serif";font-size:8pt">Thank you very much for your clear legal view:</span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="color:rgb(34,34,34);font-family:"Arial","sans-serif";font-size:8pt">There is a
proverb in Persian language which could roughly translated as follows:</span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="color:rgb(34,34,34);font-family:"Arial","sans-serif";font-size:8pt">“Whatever,
the junior observes in a Mirror, the senior ( age) <span> </span>could observe in the Stone”</span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="color:rgb(34,34,34);font-family:"Arial","sans-serif";font-size:8pt">I <span> </span>submitted exactly in one of message to the
mailing list several weeks ago the same argument <span> </span>that that you described in this message that</span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="color:rgb(34,34,34);font-family:"Arial","sans-serif";font-size:8pt">Article 1 of
Fundamental Bylaws including Mission <span> </span>is
the supreme / highest level of text in the ICANN text and thus issues such as MoU
which as it self-described itself is merely </span><span lang="EN-US" style="color:red;font-family:"Arial","sans-serif";font-size:8pt">Memorandum
and nothing more than that should not appear in the highest level of the ICANN
TEXT.</span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="font-family:"Arial","sans-serif";font-size:8pt"><font color="#000000">I went even beyond your
suggestion in arguing that cross reference in the legal document would almost
provide the same level of the main text to the crossed referenced text.</font></span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="font-family:"Arial","sans-serif";font-size:8pt"><font color="#000000">I therefore suggest ,
should we all agree by consensus to cross reference ANY MoU, paraphrase that by
a term;” See also MoU XXX as an informative reference thus would not give a
formative status to any MoU due to the fact that MoU does not have any
mandatory status as it is a “ Memorandum of </font><span style="color:red">Understanding</span><font color="#000000">
only. Something which has a memorandum status is just for memorandum “aide
memoire “, In French, and nothing more than that.</font></span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="font-family:"Arial","sans-serif";font-size:8pt"><font color="#000000">I have noticed that many
such arguments that I have made were simply rejected for other grounds than
professional</font></span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="font-family:"Arial","sans-serif";font-size:8pt"><font color="#000000">But I am used to it and do
not take it serious.</font></span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="font-family:"Arial","sans-serif";font-size:8pt"><font color="#000000">Another Persian Proverb says</font></span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="font-family:"Arial","sans-serif";font-size:8pt"><font color="#000000">“ I have told you whatever
should I had told you , it is up to you to take it or reject it “ </font></span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="font-family:"Arial","sans-serif";font-size:8pt"><font color="#000000">I do not wish to argue with
anybody as I accept many thing that are not disturbing but I can not agree that
mandatory legal terms / provisions contains or cross reference to non mandatory
provisions due to the fact that the non-mandatory provision such as MoU may change
with time thus the mandatory provisions would be subordinated with something
which could easily change such as MoU.</font></span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="font-family:"Arial","sans-serif";font-size:8pt"><font color="#000000">I SPENT 40 YEARS IN <span> </span>dealing with such DOMAIN</font></span></p><font color="#000000" face="Times New Roman" size="3">
</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="font-family:"Arial","sans-serif";font-size:8pt"><font color="#000000">Kavouss </font></span></p><font color="#000000" face="Times New Roman" size="3">
</font></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-01-18 21:27 GMT+01:00 Gregory, Holly <span dir="ltr"><<a href="mailto:holly.gregory@sidley.com" target="_blank">holly.gregory@sidley.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" vlink="purple" link="blue">
<p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Dear CCWG ACCT Co-Chairs, Members, Participants and ICANN Staff, <u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:1in"><span style="font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">We are writing to raise with you a high-level concern regarding the proposal to reference the 2004 Address Supporting Organization MOU (the “MOU”) in ICANN’s Mission Statement (Bylaws Article
I, Section 1), which was discussed on CCWG-ACCT Call #77 (January 14).<u></u><u></u></span></p>
<p><span style="font-family:"Calibri","sans-serif"">In defining ICANN’s role in coordinating allocation and assignment at the top-most level of IP and AS numbers, Annex 05 from the Third Proposal provided as follows: “</span><span style="font-family:"Calibri","sans-serif"">ICANN’s
Mission is described in the ASO MoU between ICANN and RIRs.” <u></u><u></u></span></p>
<p><i><span style="font-family:"Calibri","sans-serif"">We </span></i><i><span style="font-family:"Calibri","sans-serif"">recommend against trying to further define ICANN’s Mission through cross-reference to the MOU in the Bylaws and suggest that any specific
language that you deem of critical import to defining ICANN’s Mission be actually incorporated. (We could not find a clear statement of the ICANN Mission in the MOU.)<u></u><u></u></span></i></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">As a general matter, referencing all or part of an external agreement in bylaws presents a number of problems. For example:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p style="margin-right:0in;margin-bottom:0pt;margin-left:0.25in">
<u></u><span style="font-family:Symbol"><span>·<span style="font:7pt/normal "Times New Roman";font-size-adjust:none;font-stretch:normal">
</span></span></span><u></u><span style="font-family:"Calibri","sans-serif"">The bylaws may require a different process, parties, and threshold for amendment than the referenced agreement, and it is unclear legally which rules apply. This problem is certainly
present here. Although the Mission will be a fundamental bylaw, the parties to the MOU could amend it on their own, circumventing the fundamental bylaw amendment process entirely. Alternatively, perhaps the MOU’s amendment provisions would be superceded
by the fundamental bylaw amendment process. At a minimum, if the reference remains despite our advice, this issue should be addressed explicitly.
<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0pt;margin-left:0.25in">
<span style="font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p style="margin-right:0in;margin-bottom:0pt;margin-left:0.25in">
<u></u><span style="font-family:Symbol"><span>·<span style="font:7pt/normal "Times New Roman";font-size-adjust:none;font-stretch:normal">
</span></span></span><u></u><span style="font-family:"Calibri","sans-serif"">Referencing an outside agreement in bylaws may have the legal effect of incorporating it into the bylaws, putting all its terms on an equal footing with the bylaws, which can create
problems if its provisions conflict with the bylaws in any way. This issue has a greater chance of arising where an entire agreement is incorporated by reference, and is clearly a problem here. For example, ICANN’s Bylaws are ultimately governed by California
law, but the MOU provides that it will be governed by International Chamber of Commerce rules in Bermuda. Again, if the reference remains despite our advice, the CCWG should decide which document governs in case of conflict (either generally or on a topic-by-topic
basis).<u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0pt;margin-left:0.25in">
<span style="font-family:"Calibri","sans-serif""><u></u><u></u></span></p>
<p style="margin-right:0in;margin-bottom:0pt;margin-left:0.25in">
<u></u><span style="font-family:Symbol"><span>·<span style="font:7pt/normal "Times New Roman";font-size-adjust:none;font-stretch:normal">
</span></span></span><u></u><span style="font-family:"Calibri","sans-serif"">Although we generally recommend against it, clients have insisted on incorporating an entire existing agreement in their governing documents, essentially freezing the agreement
as incorporated. It was suggested on the CCWG call that the Bylaws could reference the version of the MOU as of a specific date, excluding from the Bylaws future amendments to the MOU unless the community amended the Bylaws to update the reference in the
Mission. While this strategy partially solves one problem, it leads to others. Assuming that the MOU incorporated in the Bylaws continues to evolve over time outside of the Bylaws, there will be two versions of the MOU -- the one in the Bylaws, and the one
that documents the current understandings between the ASO and ICANN. At a minimum, this would be confusing; in a worst-case scenario, it could undermine the enforceability of the post-reference MOU.<u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:0.25in"><span style="font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p style="margin-right:0in;margin-bottom:0pt;margin-left:0.25in">
<u></u><span style="font-family:Symbol"><span>·<span style="font:7pt/normal "Times New Roman";font-size-adjust:none;font-stretch:normal">
</span></span></span><u></u><span style="font-family:"Calibri","sans-serif"">Any outside agreement to be referenced in bylaws must be carefully reviewed to assess and address the sorts of consequences noted above. We have briefly reviewed a version of the
MOU, and note that the MOU itself incorporates other documents by reference, including the earlier 2003 version of the ICANN Bylaws, creating a circularity in terms of providing legal advice on this provision in the future.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">While we originally thought it might be possible to work around these problems by inserting text from the MOU into the Bylaws describing this aspect of ICANN’s Mission, after our brief review
of the MOU, it is not clear to us where or how it describes ICANN’s mission in any narrative text. As we read it the MOU sets out processes and mechanisms for developing policies but does not itself describe substantive limits on ICANN or purport to define
ICANN’s Mission. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Bylaws may of course include a process for developing a scope of corporate activities within the bounds of a larger mission, and the mission can be updated as appropriate to reflect developments
that come out of this process, but the process itself cannot logically become part of the mission.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">We hope further CCWG discussion in light of our concern, regarding the goal that the ASO and the community seek by referencing the MOU in the Mission Statement, may provide a way forward
without referencing the MOU itself in the Bylaws.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif"">Holly and Rosemary<a name="717621676__GoBack"></a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><b><span style="color:rgb(31,73,125);font-family:"Arial","sans-serif";font-size:9pt">HOLLY J. GREGORY</span></b><span style="color:rgb(31,73,125);font-family:"Arial","sans-serif";font-size:9pt"><br>
Partner and Co-Chair<br>
Global Corporate Governance & Executive Compensation Practice<u></u><u></u></span></p>
<p class="MsoNormal"><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: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" value="+12128395853">+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>
</div>
<p style="margin-left:1in"><u></u> <u></u></p>
</div>
<p></p>
<p> </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>
****************************************************************************************************</p>
</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" rel="noreferrer">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>