<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">The Chartering Organizations aren't legal entities, so they can't be signatories to the Community Agreement (whether by their Chairs or otherwise). Signing this agreement would not be in scope for the Empowered Community, so that doesn't work either. We have a legal entity that will be the signatory -- ICANN, which I believe has already agreed to do so. (Similarly, the IETF is not a legal entity, but rather an "activity" of ISOC, so I believe ISOC will be signing on behalf of the IETF as the "Protocol Parameters Community.")</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I don't know whether we <u>need</u> formal Chartering Organization approval for this set-up. That said, it would probably be good to inform the COs of this set-up and see if there are any objections.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 7, 2016 at 9:18 PM, Seun Ojedeji <span dir="ltr"><<a href="mailto:seun.ojedeji@gmail.com" target="_blank">seun.ojedeji@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Hello Chuck,</p>
<p dir="ltr">I think item 1 is required, though it may perhaps be good to hear from ICANN first on whether they would accept to act on behalf subject to the conditions stated(or a modification of it), before reaching the COs for an ack.</p>
<p dir="ltr">On another note, assuming we are not constraint on timing, it may be better for the Chair(s)(or their representatives in the EC) of the CO to sign the agreement instead. This would however not be possible until the EC is formerly setup. That would give more formality to it and may also address part of Kavouss concern which I sense is around getting an entity to sign.</p>
<p dir="ltr">Regards<br>
Sent from my LG G4<br>
Kindly excuse brevity and typos</p>
<div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 6 Sep 2016 15:14, "Gomes, Chuck" <<a href="mailto:cgomes@verisign.com" target="_blank">cgomes@verisign.com</a>> wrote:<br type="attribution"></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Pending input from Sidley, this looks pretty good to me. I do have two very important questions, assuming the CWG supports this letter of instruction as modified
by Greg and any subsequent revisions proposed by Sidley:<u></u><u></u></span></p>
<p><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><span>1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Won’t we have to get approval from the ccNSO, SSAC, GNSO, ALAC and GAC in advance of sending the letter?<u></u><u></u></span></p>
<p><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><span>2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><u></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Realizing that each of the five organizations have their own approval processes that can take considerable time, how will we get all five approvals
in the very short window we have?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">If the answer to question 1 is affirmative, I think we need to start working on question 2 immediately.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Chuck<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounces@icann.<wbr>org</a> [mailto:<a href="mailto:cwg-stewardship-bounces@icann.org" target="_blank">cwg-stewardship-bounce<wbr>s@icann.org</a>]
<b>On Behalf Of </b>Greg Shatan<br>
<b>Sent:</b> Monday, September 05, 2016 8:47 PM<br>
<b>To:</b> <a href="mailto:cwg-stewardship@icann.org" target="_blank">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> [CWG-Stewardship] Fwd: Letter of Instruction from CWG to ICANN re Community Agreement.DOCX<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">All,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">I've given a good deal of thought to this Letter of Instruction and how the Names Community will operate under the Community Agreement.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">The Community Agreement allows each of the Operational Communities to communicate to the IETF Trust through the CCG Co-Chair appointed by that community. Given this ability, it's actually
unnecessary to route any of the Names Community's actions through ICANN (as signatory) after the appointment of the Names Community co-chair.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">We really only need ICANN to do two things -- sign the agreement and communicate the appointment of the CCG Representatives (including the Co-Chair). Routing other actions through ICANN
just causes unnecessary complications.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">In order to implement this working model, I've proposed fairly extensive changes to the Letter of Instruction. I'm attaching a clean copy (easier to read) as well as a track changes copy
(to show the changes). The original version is also attached for convenience.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">We will still need to appoint the CCG reps, and figure out how the CWG (and the Chartering Organization Co-Chairs, when there is no CCG) instructs the CCG reps, and how the CCG reps carry
out their duties generally. But that is not part of this Letter of Instruction.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">I look forward to comments.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Best regards,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Greg<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">---------- Forwarded message ----------<br>
From: <b>Hofheimer, Joshua T.</b> <<a href="mailto:jhofheimer@sidley.com" target="_blank">jhofheimer@sidley.com</a>><br>
Date: Tue, Aug 30, 2016 at 12:05 AM<br>
Subject: Letter of Instruction from CWG to ICANN re Community Agreement.DOCX<br>
To: Client <<a href="mailto:cwg-client@icann.org" target="_blank">cwg-client@icann.org</a>>, Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>>, "<a href="mailto:jrobinson@afilias.info" target="_blank">jrobinson@afilias.info</a>" <<a href="mailto:jrobinson@afilias.info" target="_blank">jrobinson@afilias.info</a>>,
Lise Fuhr <<a href="mailto:lise.fuhr@difo.dk" target="_blank">lise.fuhr@difo.dk</a>><br>
Cc: "Flanagan, Sharon" <<a href="mailto:sflanagan@sidley.com" target="_blank">sflanagan@sidley.com</a>>, "Resnick, Yael" <<a href="mailto:yresnick@sidley.com" target="_blank">yresnick@sidley.com</a>>, "Gregory, Holly" <<a href="mailto:holly.gregory@sidley.com" target="_blank">holly.gregory@sidley.com</a>>,
"Grapsas, Rebecca" <<a href="mailto:rebecca.grapsas@sidley.com" target="_blank">rebecca.grapsas@sidley.com</a>><br>
<br>
<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="color:#1f497d">Dear Client Committee,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d">Attached is a draft letter of instruction from the “Names Community” to ICANN regarding it acting as the signatory to the Community Agreement. Per the
instruction from CWG, namely that we pursue Scenario 1 from the prior Sidley memo, we have drafted this request to come from the CWG co-chairs, and look to Greg Shatan to help with the description of the “Names Community”. We look forward to discussing on
our call on Thursday.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d">Cheers,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d">Josh</span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d">JOSHUA T. HOFHEIMER</span></b><span style="color:#1f497d"><br>
</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1f497d">Partner<br>
<br>
<b>SIDLEY AUSTIN LLP</b><br>
<a href="tel:%2B1%20650%20565%207561" target="_blank">+1 650 565 7561</a> (PA direct)<br>
<a href="tel:%2B1%20213%20896%206061" target="_blank">+1 213 896 6061</a> (LA direct)<br>
<a href="tel:%2B1%20323%20708%202405" target="_blank">+1 323 708 2405</a> (Cell)</span><span style="color:#1f497d"><br>
</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1f497d"><a href="mailto:jhofheimer@sidley.com" title="Click to send email to Hofheimer, Joshua T." target="_blank">jhofheimer@sidley.com</a></span><span style="color:#1f497d"><br>
<a href="http://www.sidley.com" title="www.sidley.com" target="_blank"><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">www.sidley.com</span></a></span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1f497d"><img border="0" width="126" height="54" src="http://www2.sidley.com/files/upload/signatures/SIDLEY_150-AUTOSIG.png" alt="SIDLEY"></span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="color:#1f497d"> </span><u></u><u></u></p>
</div>
<p> <u></u><u></u></p>
<p>******************************<wbr>******************************<wbr>******************************<wbr>**********<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>
******************************<wbr>******************************<wbr>******************************<wbr>**********<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
<br></div></div>______________________________<wbr>_________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/cwg-stewardship</a><br>
<br></blockquote></div></div>
</blockquote></div><br></div>