<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 12 (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:0in;
        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:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        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:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        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:0in;
        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-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
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-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Jonathan – We share your understanding on points 1-3 below, though we note that some still had been advocating for inclusion of certain Annex C concepts in the PTI Bylaws.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">In the meantime, however, we are preparing a revised draft of the agreement incorporating these provisions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Josh<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><i><span style="font-size:9.0pt;color:#1F497D">Joshua Hofheimer<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:9.0pt;color:#1F497D">Sidley Austin LLP<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:9.0pt;color:#1F497D">jhofheimer@sidley.com<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span style="font-size:9.0pt;color:#1F497D">(213) 896-6061 (LA direct)<o:p></o:p></span></i></p>
<p class="MsoNormal"><i><span 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 style="font-size:9.0pt;color:#1F497D">(323) 708-2405 (cell)<o:p></o:p></span></i></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><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""> Jonathan Robinson [mailto:jrobinson@afilias.info]
<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:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D">Dear Josh,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D">My understanding is as follows:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in"><span lang="EN-IE" style="color:#1F497D">1.</span><span lang="EN-IE" style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span lang="EN-IE" 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:1.0in;text-indent:-.25in"><span lang="EN-IE" style="color:#1F497D">2.</span><span lang="EN-IE" style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span lang="EN-IE" 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:1.0in;text-indent:-.25in"><span lang="EN-IE" style="color:#1F497D">3.</span><span lang="EN-IE" style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span lang="EN-IE" 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:.5in"><span lang="EN-IE" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D">Therefore,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in"><span lang="EN-IE" style="color:#1F497D">A.</span><span lang="EN-IE" style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span lang="EN-IE" 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:1.0in;text-indent:-.25in"><span lang="EN-IE" style="color:#1F497D">B.</span><span lang="EN-IE" style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#1F497D">
</span><span lang="EN-IE" style="color:#1F497D">It seems to me to be certain that the
</span><span style="color:#1F497D">provisions (that the CWG drafted to implement Annex C) must be incorporated into the
</span><span lang="EN-IE" style="color:#1F497D">Naming Functions Agreement<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D">Accordingly, it will be helpful to receive your
</span><span style="color:#1F497D">review of the Naming Functions Agreement against Annex C
</span><span lang="EN-IE" 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:.5in"><span lang="EN-IE" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D">Thank-you.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D">Jonathan<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b>From:</b> 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></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span 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:.5in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span 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:.5in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D">Josh<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><i><span style="font-size:9.0pt;color:#1F497D">Joshua Hofheimer<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i><span style="font-size:9.0pt;color:#1F497D">Sidley Austin LLP<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-left:.5in"><span lang="EN-IE"><a href="mailto:jhofheimer@sidley.com"><i><span lang="EN-US" style="font-size:9.0pt">jhofheimer@sidley.com</span></i></a></span><i><span style="font-size:9.0pt;color:#1F497D"><o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-left:.5in"><i><span 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:.5in"><i><span 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:.5in"><i><span 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:.5in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.0in"><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""> Hofheimer, Joshua T.
<br>
<b>Sent:</b> Monday, July 25, 2016 12:50 PM<br>
<b>To:</b> 'Client Committee'<br>
<b>Cc:</b> Resnick, Yael; Flanagan, Sharon; Gregory, Holly; Grapsas, Rebecca; Greeley, Amy E.<br>
<b>Subject:</b> RE: ICANN-PTI Naming Functions Agreement & Services Agreement Headers<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:1.0in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#1F497D">Dear Client Committee – If you have not already started reviewing the attached, please hold for a few hours. We will have a revised draft to you shortly with further observations on
the connections to the ICANN Bylaws, and some additional revisions.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#1F497D">Josh<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="margin-left:1.0in"><i><span style="font-size:9.0pt;color:#1F497D">Joshua Hofheimer<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-left:1.0in"><i><span style="font-size:9.0pt;color:#1F497D">Sidley Austin LLP<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-left:1.0in"><span lang="EN-IE"><a href="mailto:jhofheimer@sidley.com"><i><span lang="EN-US" style="font-size:9.0pt">jhofheimer@sidley.com</span></i></a></span><i><span style="font-size:9.0pt;color:#1F497D"><o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-left:1.0in"><i><span 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:1.0in"><i><span 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:1.0in"><i><span 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:1.0in"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:1.5in"><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""> Hofheimer, Joshua T.
<br>
<b>Sent:</b> Sunday, July 24, 2016 4:02 PM<br>
<b>To:</b> Client Committee<br>
<b>Cc:</b> Resnick, Yael; Flanagan, Sharon; Gregory, Holly; Grapsas, Rebecca; Greeley, Amy E.<br>
<b>Subject:</b> ICANN-PTI Naming Functions Agreement & Services Agreement Headers<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:1.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">Dear Client Committee,<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">Attached please find proposed comments to the Naming Functions Agreement and the Services Agreement Headers, both clean and marked against the versions sent by ICANN. Because the Services Agreement Headers received
from ICANN was in PDF only, we converted to Word and added formatting. However, this has made the redline look more atrocious than it actually is. We are going to try to clean this up a little in the versions to go to ICANN, but did not want to delay getting
feedback or comments from the community. <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">On the Naming Functions Agreement, we focused primarily on verifying the mapping exercise undertaken by ICANN to ensure the CWG’s views and conditions have been incorporated. Where the proposed draft appears to
be lacking or inconsistent, we have noted with questions, comments, and in some instances direct revisions.
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">Cheers,<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in">Josh<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.5in">
<b><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">JOSHUA T. HOFHEIMER</span></b><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Partner<br>
<br>
<b>SIDLEY AUSTIN LLP</b><br>
+1 650 565 7561 (PA direct)<br>
+1 213 896 6061 (LA direct)<br>
+1 323 708 2405 (Cell)</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
</span><span lang="EN-IE"><a href="mailto:jhofheimer@sidley.com" title="Click to send email to Hofheimer, Joshua T."><span lang="EN-US" style="font-size:9.0pt;font-family:"Arial","sans-serif"">jhofheimer@sidley.com</span></a></span><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
</span><span lang="EN-IE"><a href="http://www.sidley.com" title="www.sidley.com"><span lang="EN-US" style="font-size:9.0pt;font-family:"Arial","sans-serif"">www.sidley.com</span></a></span><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:1.5in">
<b><span lang="EN-IE" style="font-size:10.0pt;font-family:"Arial","sans-serif""><img border="0" width="158" height="68" id="_x0000_i1025" src="http://www2.sidley.com/files/upload/signatures/SIDLEY_150-AUTOSIG.png" alt="SIDLEY"></span></b><span style="font-size:10.0pt;font-family:"Times New Roman","serif""><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.5in"><span style="font-size:10.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.5in"><o:p> </o:p></p>
<p class="9e7b50e6-8ae3-4c49-a6d0-8087ee035f4a" style="margin-left:.5in"> <o:p></o:p></p>
<p style="margin-left:.5in">****************************************************************************************************<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></p>
</div>
</body>
</html>