<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=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma",sans-serif;}
p.c4a0c8ff-067a-402c-bfec-95ed9cd1c28e, li.c4a0c8ff-067a-402c-bfec-95ed9cd1c28e, div.c4a0c8ff-067a-402c-bfec-95ed9cd1c28e
{mso-style-name:c4a0c8ff-067a-402c-bfec-95ed9cd1c28e;
mso-style-priority:99;
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma",sans-serif;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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=EN-IE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'>Thank-you Sam,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'>We will need to provide the Nom Com with criteria for these directors.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'>Their skill set and experience will not be the same as for the GNSO Council or the ICANN Board for example.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'>This may be able to be covered as an implementation point but it does need to be recognised.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'>Jonathan<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Grace Abuhamad [mailto:grace.abuhamad@icann.org] <br><b>Sent:</b> 15 April 2016 14:40<br><b>To:</b> Client Committee <cwg-client@icann.org><br><b>Subject:</b> [client com] FW: Chuck Gomes Comments<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><div><div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;color:black'>Forwarding this note on behalf of Samantha Eisner. <o:p></o:p></span></p></div></div></div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;color:black'><o:p> </o:p></span></p></div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='color:black'>From: </span></b><span lang=EN-US style='color:black'>Samantha Eisner <<a href="mailto:Samantha.Eisner@icann.org">Samantha.Eisner@icann.org</a>><br><b>Date: </b>Thursday, April 14, 2016 at 10:16 PM<br><b>To: </b>Sharon Flanagan <<a href="mailto:sflanagan@sidley.com">sflanagan@sidley.com</a>>, Client Committee <<a href="mailto:cwg-client@icann.org">cwg-client@icann.org</a>><br><b>Subject: </b>Re: [client com] Chuck Gomes Comments</span><span lang=EN-US style='font-size:12.0pt;color:black'><o:p></o:p></span></p></div><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;color:black'><o:p> </o:p></span></p></div><div><div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'>As a follow up to the PTI Board selection issue, the NomCom portion of the ICANN Bylaws (Article 8.1) also specifies that the NomCom will be responsible for nominating 2 directors to the PTI Board. The PTI Bylaws will then confirm what ICANN is to do with those nominated directors (I.e., to seat them on the Board).<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'><o:p> </o:p></span></p></div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='color:black'>From: </span></b><span style='color:black'><<a href="mailto:cwg-client-bounces@icann.org">cwg-client-bounces@icann.org</a>> on behalf of "Flanagan, Sharon" <<a href="mailto:sflanagan@sidley.com">sflanagan@sidley.com</a>><br><b>Date: </b>Thursday, April 14, 2016 at 8:05 AM<br><b>To: </b>Client Committee <<a href="mailto:cwg-client@icann.org">cwg-client@icann.org</a>><br><b>Subject: </b>[client com] Chuck Gomes Comments<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;color:black'><o:p> </o:p></span></p></div><div><div><p class=MsoNormal><span lang=EN-US style='color:black'>Dear All,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:black'>Chuck’s comments were forwarded to us and our notes and responses are below.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:black'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:black'>Sharon<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p><p style='margin-left:72.0pt'><span lang=EN-US style='color:black'>> In my personal review of the Bylaws I noted the following issues that I don’t think were covered in the CWG Bylaws Review meeting today:<br>><br>> · There are several acronyms or terms that are used before they are defined:<br>><br>SO: Observed that as well, but considering that their explanations are quite long and detail I wonder to what extent they could reorganise things. <o:p></o:p></span></p><p style='margin-left:72.0pt'><span lang=EN-US style='color:black'>[<span style='background:yellow'>Sidley comment: We are adding “as defined in Section ___” where defined terms are used before they have been defined.</span>]<o:p></o:p></span></p><p style='margin-left:72.0pt'><span lang=EN-US style='color:black'>><br>> · Unless I missed it somewhere, as far as I can tell the ‘Decisional Participants’ are not named anywhere in the Bylaws even though they are referenced dozens of times.<br>><br>SO: That seem to be attributed(defined) in Section 6.1a<o:p></o:p></span></p><p style='margin-left:72.0pt'><span lang=EN-US style='color:black'>[<span style='background:yellow'>Sidley comment: “Decisional Participants” is defined in Article 6, Section 6.1(a).</span>]<o:p></o:p></span></p><p style='margin-left:72.0pt'><span lang=EN-US style='color:black'>> · Section 8.2 on page 54 of the redlined version (page 56 overall) says that one member of the NomCom will be selected by the NCUC.<br>><br>SO: While I think this is particularly within the scope of the CCWG, I don't think nomcom composition was even discussed in that group and I am quite surprised that there has been edits that exceeds just renumbering on that section.<o:p></o:p></span></p><p style='margin-left:72.0pt'><span lang=EN-US style='color:black'>> o I have no problem with that but I do wonder if it should say NCSG instead of NCUC.<br>><br>> o I am pretty sure that the original version of this language was before there was a NCSG and before the NPOC existed.<br>><br>SO: While my concern above still stand, the version I am looking at that compares the current bylaw with proposed version seem to indicate that it's been NCUC all along.<o:p></o:p></span></p><p style='margin-left:72.0pt'><span lang=EN-US style='color:black'>[<span style='background:yellow'>Sidley comment: Edits have not been made to the provision requiring one delegate of the NomCom to be “from consumer and civil society groups, selected by the Non-Commercial Users Constituency” other than to renumber that subsection (Section 8.2(g)(vi)); NomCom composition was not discussed in the CCWG Proposal.</span>]<o:p></o:p></span></p><p style='margin-left:72.0pt'><span lang=EN-US style='color:black'>> · Section 16.2(a) on page 86 of the redline version (page 89 overall) says: “ICANN, in its capacity as the sole Member of PTI, shall elect the directors of PTI in accordance with the articles of incorporation and bylaws of PTI and . . .”<br>><br>> o It is my understanding that ICANN shall elect three of the five directors, not all five.<br>><br>> o Shouldn’t this be corrected?<br>><br>SO: Oops that's a good catch and somehow I thought I saw where the composition was indicated early now I can't seem to find it. Thanks for noting that<o:p></o:p></span></p><p style='margin-left:72.0pt'><span lang=EN-US style='color:black'>[<span style='background:yellow'>Sidley comment: ICANN will elect <i><u>all</u></i> directors of PTI in its capacity as the sole member of PTI; ICANN will be instructed in the PTI governing documents on <i><u>how</u></i> to vote with respect to PTI director elections (i.e., the allocation of directors on the PTI Board between independent directors and employees of ICANN or employees of PTI); any amendment of the provisions in the PTI governing documents relating to PTI Board composition could be rejected by the EC pursuant to Section 16.2(c)(vii)).</span>] <o:p></o:p></span></p><p style='margin-left:72.0pt'><span lang=EN-US style='color:black'>> · Section 18.7(c) on page 97 of the redline version (page 100 overall) says that the IFRT will contain two (2) representatives from the RySG. [<span style='background:yellow'>Sidley comment: Section 18.7(c) requiring each IFRT to include two representatives appointed by the Registries Stakeholder Group is consistent with the CWG Proposal, Paragraph 283.</span>]<br>><br>> o Note that it also says that there will be three ccTLD members (two from the ccNSO and one not from the ccNSO).<br>><br>> o Note also that Section 19.5(iii) says that the SCWG will have three (3) RySG representatives, the same number as for ccTLDs, two from the ccNSO and one not from the ccNSO. [<span style='background:yellow'>Sidley comment: Section 19.5(a)(iii) requiring each SCWG to include three representatives appointed by the Registries Stakeholder Group is consistent with the CWG Proposal, Paragraph 393.</span>]<br>><br>> o Was this just an inadvertent oversight?<br>><br>> o It seems to me that the IFRT should have three (3) representatives from the RySG.<br>><br>SO: For IFRT, one could say that the Rysg having 2 is because Registrar stakeholder group has one which makes 3 in total and perhaps that of the SCWG needs to be updated to 2 RySG. <o:p></o:p></span></p><p style='margin-left:72.0pt'><span lang=EN-US style='color:black'>On a sightly related note, the more I look at the compositions on the review teams the more I wonder how this skipped us during the proposal development. There are 8/9 votes (counting the NCSG and CSG) already from the SO related groups and just 4 from the AC. It's a huge imbalance that makes me still wonder what went wrong during the discussion that made us not to pay attention to that. This is the more reason why I will always be against anything with majority in it as a way of making decisions within the groups!<o:p></o:p></span></p><p style='margin-left:72.0pt'><span lang=EN-US style='color:black'>Regards<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-US style='color:black'>> · Section 22.4(b), IANA Budget, says: “At least 45 days prior to the commencement of each fiscal year, ICANN shall prepare and submit to the Board a proposed annual budget of ICANN for direct costs for ICANN’s IANA department, all costs for PTI, direct costs for shared resources between ICANN and PTI and support functions provided by ICANN to PTI and ICANN’s IANA department for the next fiscal year (the “IANA Budget”), which shall be posted on the Website.”<br>><br>> o The recommendation of DT-O regarding the IANA Budget was that it be approved prior to approval of the ICANN Budget.<br>><br>> o DT-O’s recommendation was made prior to any knowledge that a change to the Bylaws would be proposed to require submission of an ICANN Budget to the Board 45 days prior to the start of the applicable fiscal year.<br>><br>> o I support the requirement for submission of an ICANN Budget to the Board 45 days prior to the start of the applicable fiscal year but believe that there are advantages to the IANA Budget being approved earlier than the ICANN Budget; having the IANA Budget approved prior to consideration of the final ICANN Budget will: [<span style='background:yellow'>Sidley comment: This proposed change to be discussed with ICANN once CWG signs off on the relevant provisions.</span>]<br>><br>> § Remove any dependency of IANA services funding from approval or veto of the ICANN Budget<br>><br>> § Allow more time for resolution of a veto of the IANA Budget<br>><br>> § Provide increased confidence that IANA services will continue without interruption.<br>><br>> o My personal recommendation would be that the IANA budget be submitted for Board approval with sufficient time to be approved prior to submission of the ICANN Budget for Board approval.<br>><br>> o Note that DT-O plans to discuss this issue in its meeting on 13 April 2016.<br>><br>> · Paragraph (e) in Section 3.2 (SO/AC Director removal process) on page 187 of the redline version (overall page 190) requires “a three-quarters majority of an applicable Decisional Participant as determined pursuant to the internal procedures of the Applicable Decisional Participant for the SO/AC Director Removal Petition.<br>><br>> o If the GNSO is the applicable Decisional Participant, the GNSO does not presently define what a ‘three-quarters majority’ is.<br>><br>> o Presumably, following current threshold definitions for the GNSO Council, a three-quarters majority would be defined as a three-quarters majority of each house.<br>><br>> o Is the addition of this definition considered to be an implementation action item for the GNSO?<br>><o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-US style='color:black'>[<span style='background:yellow'>Sidley comment: Our understanding is that this will form part of implementation for the GSNO, along with other procedures to be adopted by the Decisional Participants.]</span><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt'><span lang=EN-US style='color:black'><br>> · Paragraph 1.f in Annex E, The ICANN Caretaker Budget, on page 208 of the redline version (overall page 211) says: “Notwithstanding any other principle listed above, prevents ICANN from initiating activities that are subject to community consideration (or for which that community consideration has not concluded), including without limitation, preventing implementation of the expenditures or undertaking the actions that were the subject of the ICANN Budget that was rejected by the EC and that triggered the need for the Caretaker ICANN Budget.” [<span style='background:yellow'>Sidley comment: We defer to CWG on this since the caretaker budgets are not specified in detail in the proposals.</span>]<br>><br>> o This clause seems appropriate in a case where the EC rejects the budget because it does not support funding certain actions or thinks that too many funds are allocated to those actions.<br>><br>> o But what about a situation in which the EC rejects the budget because it believes that insufficient funds are budgeted for certain actions? In a case like that, it might not be necessary to prevent funding of the actions while the dispute is resolved; in other words, it might be fine if the actions proceeded at the reduced funding level until a decision is made on increased funding, especially if taking the actions at the reduced funding level would not negatively impact the actions if increased funding was provided later.<br>><br>> o I wonder whether this clause should be reworded to accommodate such situations; if so, then a change may also need to be made in section 2.b.v, Examples of expenditures that would be excluded from a Caretaker Budget: “the proposed expenditure that was the basis for the rejection by the EC that triggered the need for the Caretaker ICANN Budget.”<br>><br>> · Paragraph 1.f in Annex F, IANA Caretaker Budget Principles, on page 211 of the redline version (overall page 214) says: “Notwithstanding any other principle listed above, prevents ICANN, in its responsibility to fund the operations of the IANA functions, from initiating activities that are subject to community consideration (or for which that community consultation has not concluded), including without limitation, preventing implementation of the expenditures or undertaking the actions that were the subject of the IANA Budget that was rejected by the EC and triggered the need for the Caretaker IANA Budget.” [<span style='background:yellow'>Sidley comment: We defer to CWG on this since the caretaker budgets are not specified in detail in the proposals.</span>]<br>><br>> o This clause seems appropriate in a case where the EC rejects the budget because it does not support funding certain actions or thinks that too many funds are allocated to those actions.<br>><br>> o But what about a situation in which the EC rejects the budget because it believes that insufficient funds are budgeted for certain actions? In a case like that, it might not be necessary to prevent funding of the actions while the dispute is resolved; in other words, it might be fine if the actions proceeded at the reduced funding level until a decision is made on increased funding, especially if taking the actions at the reduced funding level would not negatively impact the actions if increased funding was provided later.<br>><br>> o I wonder whether this clause should be reworded to accommodate such situations; if so, then a change may also need to be made in section 2.b.v, Examples of expenditures that would be excluded from a Caretaker Budget: “the proposed expenditure that was the basis for the rejection by the EC that triggered the need for the Caretaker ICANN Budget.” (Note that a minor edit is needed: it should say Caretaker IANA Budget, not Caretaker ICANN Budget.)<br>><br>> o Note that DT-O plans to discuss this issue in its meeting on 13 April 2016.<br>><br>> · Note that a glossary of acronyms and key terms would be a very useful aid for community members. [<span style='background:yellow'>Sidley comment: This has been recommended to ICANN but there are concerns that there is insufficient time to develop such a list and gather feedback.</span>]<br>><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:black'> <o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'>SHARON R. FLANAGAN</span></b><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman",serif;color:black'><br></span><span lang=EN-US style='font-size:9.0pt;font-family:"Arial",sans-serif;color:black'><br><br><b>SIDLEY AUSTIN LLP</b><br>555 California Street<br>Suite 2000<br>San Francisco, CA 94104<br>+1 415 772 1271</span><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman",serif;color:black'><br></span><span lang=EN-US style='font-size:9.0pt;font-family:"Arial",sans-serif;color:black'><a href="mailto:sflanagan@sidley.com" title="Click to send email to Flanagan, Sharon">sflanagan@sidley.com</a></span><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman",serif;color:black'><br><a href="http://www.sidley.com" title=www.sidley.com><span style='font-size:9.0pt;font-family:"Arial",sans-serif'>www.sidley.com</span></a></span><span lang=EN-US style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial",sans-serif;color:black'><img border=0 width=126 height=54 id="_x0000_i1025" src="http://www2.sidley.com/files/upload/signatures/SIDLEY_150-AUTOSIG.png" alt=SIDLEY></span></b><span lang=EN-US style='color:black'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Times New Roman",serif;color:black'> </span><span lang=EN-US style='color:black'><o:p></o:p></span></p><p class=c4a0c8ff-067a-402c-bfec-95ed9cd1c28e><span lang=EN-US style='color:black'> <o:p></o:p></span></p><p><span lang=EN-US style='color:black'>****************************************************************************************************<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>****************************************************************************************************<o:p></o:p></span></p></div></div></div></div></div></body></html>