<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)"><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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0cm;
        margin-right:0cm;
        margin-bottom:0cm;
        margin-left:36.0pt;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma",sans-serif;}
p.9e7b50e6-8ae3-4c49-a6d0-8087ee035f4a, li.9e7b50e6-8ae3-4c49-a6d0-8087ee035f4a, div.9e7b50e6-8ae3-4c49-a6d0-8087ee035f4a
        {mso-style-name:9e7b50e6-8ae3-4c49-a6d0-8087ee035f4a;
        mso-style-priority:99;
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
span.EmailStyle22
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle23
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
span.EmailStyle24
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
span.EmailStyle25
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
span.EmailStyle26
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle27
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:#1F497D;}
span.EmailStyle28
        {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'>All,<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'>Please see below and attached for review and comments from Sidley on the Naming Function Agreement.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:EN-US'><br>Thank-you,<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> Hofheimer, Joshua T. [mailto:jhofheimer@sidley.com] <br><b>Sent:</b> 28 July 2016 05:11<br><b>To:</b> 'Client Committee' <cwg-client@icann.org><br><b>Cc:</b> jrobinson@afilias.info; Resnick, Yael <yresnick@sidley.com>; Grapsas, Rebecca <rebecca.grapsas@sidley.com>; Flanagan, Sharon <sflanagan@sidley.com>; Gregory, Holly <holly.gregory@sidley.com>; Greeley, Amy E. <AGreeley@Sidley.com><br><b>Subject:</b> RE: [client com] ICANN-PTI Naming Functions Agreement & Services Agreement Headers<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Client Committee – Attached is a further revised draft of the Naming Functions Agreement. For convenience, we have included a clean version and two redlines – an incremental draft marked against the Sidley draft circulated per the email below, and a cumulative redline against the original ICANN-legal draft proposal. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Regarding Annex C, on our review many of the concepts do appear to have been incorporated either into the Naming Functions Agreement or into the governance documents. We have added only a few suggested, additional clauses related to Annex C in the attached draft, along with mapping to the particular provision in the Annex. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Thank you and speak to you tomorrow.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Josh<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><i><span lang=EN-US style='font-size:9.0pt;color:#1F497D'>Joshua Hofheimer<o:p></o:p></span></i></p><p class=MsoNormal><i><span lang=EN-US style='font-size:9.0pt;color:#1F497D'>Sidley Austin LLP<o:p></o:p></span></i></p><p class=MsoNormal><i><span lang=EN-US style='font-size:9.0pt;color:#1F497D'><a href="mailto:jhofheimer@sidley.com">jhofheimer@sidley.com</a><o:p></o:p></span></i></p><p class=MsoNormal><i><span lang=EN-US style='font-size:9.0pt;color:#1F497D'>(213) 896-6061 (LA direct)<o:p></o:p></span></i></p><p class=MsoNormal><i><span lang=EN-US style='font-size:9.0pt;color:#1F497D'>(650) 565-7561 (Palo Alto direct)<o:p></o:p></span></i></p><p class=MsoNormal><i><span lang=EN-US style='font-size:9.0pt;color:#1F497D'>(323) 708-2405 (cell)<o:p></o:p></span></i></p></div><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><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 style='margin-left:36.0pt'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma",sans-serif'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma",sans-serif'> Jonathan Robinson [<a href="mailto:jrobinson@afilias.info">mailto:jrobinson@afilias.info</a>] <br><b>Sent:</b> Wednesday, July 27, 2016 3:02 AM<br><b>To:</b> Hofheimer, Joshua T.; 'Client Committee'<br><b>Cc:</b> Greeley, Amy E.<br><b>Subject:</b> RE: [client com] ICANN-PTI Naming Functions Agreement & Services Agreement Headers<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'>Dear Josh,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'>My understanding is as follows:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt'><span style='color:#1F497D'>1.</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F497D'> </span><span style='color:#1F497D'>That the CWG is agreed that the provisions of Annex C must be appropriately documented into the Naming Functions Agreement, PTI Bylaws or both.<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt'><span style='color:#1F497D'>2.</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F497D'> </span><span style='color:#1F497D'>Sidley have indicated that it will be satisfactory (in terms of the implementation of the CWG proposal) to have the provisions of Annex C appropriately documented into the Naming Functions Agreement or PTI Bylaws or both.<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt'><span style='color:#1F497D'>3.</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F497D'> </span><span style='color:#1F497D'>ICANN Legal have argued that they do not believe it is appropriate to have the provisions of Annex C documented in the PTI Bylaws.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'>Therefore,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt'><span style='color:#1F497D'>A.</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F497D'> </span><span style='color:#1F497D'>It will be helpful to have you confirm that the above is consistent with your understanding and <o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt'><span style='color:#1F497D'>B.</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif;color:#1F497D'> </span><span style='color:#1F497D'>It seems to me to be certain that the </span><span lang=EN-US style='color:#1F497D'>provisions (that the CWG drafted to implement Annex C) must be incorporated into the </span><span style='color:#1F497D'>Naming Functions Agreement<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'>Accordingly, it will be helpful to receive your </span><span lang=EN-US style='color:#1F497D'>review of the Naming Functions Agreement against Annex C </span><span style='color:#1F497D'>as soon as possible and/or proposed revision of the Naming Functions Agreement in order to achieve the appropriate documentation of Annex C .<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'>Thank-you.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'>Jonathan<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span style='color:#1F497D'><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 style='margin-left:36.0pt'><b><span lang=EN-US>From:</span></b><span lang=EN-US> Hofheimer, Joshua T. [<a href="mailto:jhofheimer@sidley.com">mailto:jhofheimer@sidley.com</a>] <br><b>Sent:</b> 26 July 2016 02:20<br><b>To:</b> Client Committee <<a href="mailto:cwg-client@icann.org">cwg-client@icann.org</a>><br><b>Cc:</b> Greeley, Amy E. <<a href="mailto:AGreeley@sidley.com">AGreeley@sidley.com</a>><br><b>Subject:</b> Re: [client com] ICANN-PTI Naming Functions Agreement & Services Agreement Headers<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'>Client Committee -- Attached is a further revised draft of Sidley’s comments to the Naming Functions Agreement. For convenience, we have included a clean Word version, a cumulative PDF redline against the ICANN draft, and an internal redline against the version we sent yesterday. <o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'>Please note, we have not undertaken a formal review of the Naming Functions Agreement against Annex C. We are looking for guidance from the CWG as to whether the provisions that the CWG drafted to implement Annex C (as described in the Implementation Proposal dated June 9, 2016) will be incorporated in the bylaws or the naming function agreement. Once this determination is made, we can ensure that the provisions are appropriately documented, if requested.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'>Cheers,<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'>Josh<o:p></o:p></span></p><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal style='margin-left:36.0pt'><i><span lang=EN-US style='font-size:9.0pt;color:#1F497D'>Joshua Hofheimer<o:p></o:p></span></i></p><p class=MsoNormal style='margin-left:36.0pt'><i><span lang=EN-US style='font-size:9.0pt;color:#1F497D'>Sidley Austin LLP<o:p></o:p></span></i></p><p class=MsoNormal style='margin-left:36.0pt'><a href="mailto:jhofheimer@sidley.com"><i><span lang=EN-US style='font-size:9.0pt'>jhofheimer@sidley.com</span></i></a><i><span lang=EN-US style='font-size:9.0pt;color:#1F497D'><o:p></o:p></span></i></p><p class=MsoNormal style='margin-left:36.0pt'><i><span lang=EN-US style='font-size:9.0pt;color:#1F497D'>(213) 896-6061 (LA direct)<o:p></o:p></span></i></p><p class=MsoNormal style='margin-left:36.0pt'><i><span lang=EN-US style='font-size:9.0pt;color:#1F497D'>(650) 565-7561 (Palo Alto direct)<o:p></o:p></span></i></p><p class=MsoNormal style='margin-left:36.0pt'><i><span lang=EN-US style='font-size:9.0pt;color:#1F497D'>(323) 708-2405 (cell)<o:p></o:p></span></i></p></div><p class=MsoNormal style='margin-left:36.0pt'><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p></div></body></html>