<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.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;
        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.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle21
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle22
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle24
        {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-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><a name="_MailEndCompose"><span style="color:#1F497D;mso-fareast-language:EN-US">Dear All,<o:p></o:p></span></a></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 the attached Naming Functions Agreement which the comments from Sidley. We have a CWG call on Thursday where we can discuss the issues raised by Sidley.<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">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Lise<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"> cwg-client-bounces@icann.org [mailto:cwg-client-bounces@icann.org]
<b>On Behalf Of </b>Hofheimer, Joshua T.<br>
<b>Sent:</b> 26 July 2016 03:20<br>
<b>To:</b> 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"><o:p> </o:p></p>
<p class="MsoNormal"><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"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><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"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Cheers,<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">jhofheimer@sidley.com<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""> 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:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" 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: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">Thanks,<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"><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" 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>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:72.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""> 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:72.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US">Dear Client Committee,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US">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></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US">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></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US">Josh<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:72.0pt">
<b><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif"">JOSHUA T. HOFHEIMER</span></b><span lang="EN-US" style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
</span><span lang="EN-US" 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 lang="EN-US" style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
</span><span lang="EN-US" style="font-size:9.0pt;font-family:"Arial","sans-serif""><a href="mailto:jhofheimer@sidley.com" title="Click to send email to Hofheimer, Joshua T.">jhofheimer@sidley.com</a></span><span lang="EN-US" style="font-size:12.0pt;font-family:"Times New Roman","serif""><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="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:72.0pt">
<b><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";border:solid windowtext 1.0pt;padding:0cm"><img border="0" width="126" height="54" id="_x0000_i1025" src="cid:image001.jpg@01D1E736.9AF51BE0" alt="Image removed by sender. SIDLEY"></span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Times New Roman","serif""><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US" style="font-size:10.0pt"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="9e7b50e6-8ae3-4c49-a6d0-8087ee035f4a"><span lang="EN-US"> <o:p></o:p></span></p>
<p><span lang="EN-US">****************************************************************************************************<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>
</body>
</html>