<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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:Verdana;
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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
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";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Well done Jonathan. I am personally comfortable with all of your response and provide input on three of them below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="color:#1F497D">Costs (5.1)</span></u><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">DT-O didn’t specifically review this clause or Sidley’s comments but I think that the General Comment included with DT-O’s comments on Schedule A may apply here: “</span>Although not necessarily required to be
in the Services Agreement, it is recommended that the PTI Operating Plan & Budget provide detailed costs for each of the Schedule A services. This will facilitate monitoring and evaluating PTI costs corresponding to Schedule A.<span style="color:#1F497D">”
I personally think that it might be helpful of invoices detailed costs by the services listed in Schedule A. That would make it easier for the community to not only monitor costs bust also to track fulfillment of the services.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="color:#1F497D">Termination by ICANN (8.2(b))</span></u><u><span style="color:#1F497D"><o:p></o:p></span></u></p>
<p class="MsoNormal"><span style="color:#1F497D">I am concerned with this wording in the clause as I think Sidley appears to be: “</span><span style="font-size:9.0pt">until PTI has obtained alternative services for the Services</span><span style="color:#1F497D">”.
It seems to me that in some circumstances it would be inappropriate for PTI to be responsible for obtaining alternative services. I agree that further discussion is needed on this.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="color:#1F497D">Schedule A Services</span></u><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I sent proposed comments from DT-O to the IOTF list today.<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">Hope this is helpful. Please let me know if you have any questions.<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">Chuck<o:p></o:p></span></p>
<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"><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""> iotf-bounces@icann.org [mailto:iotf-bounces@icann.org]
<b>On Behalf Of </b>Jonathan Robinson<br>
<b>Sent:</b> Wednesday, August 24, 2016 7:30 AM<br>
<b>To:</b> 'Yuko Green'; iotf@icann.org<br>
<b>Subject:</b> Re: [IOTF] Schedule A of the ICANN-PTI Services Agreement<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-IE" style="color:#1F497D">Yuko,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE" style="color:#1F497D">Thank-you for this. From the subsequent email chain, I see that there has been discussion of various points including possible input from DT-O.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE" style="color:#1F497D">I have been through Sidley’s issue list and inserted a series of possible CWG comments (attached). It would be helpful to understand if that issues list is still as it was on 18 August or if more
recent work has moved it on.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE" style="color:#1F497D">Assuming it is as it was on 18 August, then I propose that my list of responses be utilised as a strawman for the CWG responses. However, if it has move on and many of the issues are now resolved
and closed, it will be helpful to know that and to possibly see a revised / shorter issues list.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE" style="color:#1F497D">Jonathan<o:p></o:p></span></p>
<p class="MsoNormal"><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"><b>From:</b> Yuko Green [<a href="mailto:yuko.green@icann.org">mailto:yuko.green@icann.org</a>]
<br>
<b>Sent:</b> 18 August 2016 09:05<br>
<b>To:</b> <a href="mailto:iotf@icann.org">iotf@icann.org</a><br>
<b>Subject:</b> [IOTF] Schedule A of the ICANN-PTI Services Agreement<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-IE"><o:p> </o:p></span></p>
<p class="MsoNormal">Dear IOTF members,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">During today’s CWG meeting #88 (18 August at 06:00 UTC), it was requested by CWG and Sidley that IOTF review the Schedule A of the attached ICANN-PTI Services Agreement. As such, I am sending you the Services Agreement as well as Sidley’s
notes about the Agreement.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Today’s CWG call recording where the request was made can be found here:
<a href="https://icann.adobeconnect.com/p6fvs9tegl2/?OWASP_CSRFTOKEN=2edd84f04d82a2e5c09303a5a3afb38728cb286cf510c1fcd31bc41c7abd6969">
<b><span style="font-size:9.0pt;font-family:"Verdana","sans-serif";color:black;background:white">https://icann.adobeconnect.com/p6fvs9tegl2/</span></b></a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please also note that the intention is to re-discuss this Services Agreement during the next CWG call on 25 August at 14:00 UTC.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Yuko Green</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Strategic Programs Manager</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Global Domains Division</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Internet Corporation for Assigned Names and Numbers (ICANN)</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Direct Line: +1 310 578 8693</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Mobile: +1 310 745 1517</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">E-mail:
<a href="mailto:yuko.green@icann.org"><span style="color:blue">yuko.green@icann.org</span></a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><a href="http://www.icann.org/"><span style="color:blue">www.icann.org</span></a></span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>