<html 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="Title" content="">
<meta name="Keywords" content="">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:Calibri;}
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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Dear all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Per call yeserday, please find included the email sned to the SO/AC infor alert list, which includes all chairs of the ICANN SO/AC’s, stakeholder group and large group of ICANN staff.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">Bart<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt"><o:p> </o:p></span></p>
<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"><soac-infoalert-bounces@icann.org> on behalf of Bart Boswinkel <bart.boswinkel@icann.org><br>
<b>Date: </b>Thursday 1 December 2016 at 15:18<br>
<b>To: </b>"soac-infoalert@icann.org" <soac-infoalert@icann.org><br>
<b>Subject: </b>[Soac-infoalert] FW: Monthly Report of the CSC on PTI Performance - October 2016</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman""><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">Dear all,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">Please find included the first report from the CSC and PTI (Ocotber 2016) on the PTI Performance</span>
<span style="font-size:14.0pt;color:black">and an introductionary note from Byron Holland, chair of the CSC.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">Kind regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:14.0pt;color:black">Bart Boswinkel</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt">------------------------------------------------------------------------------------------------------------------------------------------------</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt">Dear Community Members,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><span lang="EN-CA" style="font-size:14.0pt;line-height:115%">As chair of the Customer Standing Committee I am pleased to provide you with our first monthly report on the performance of Public
Technical Identifiers, PTI, for October, 2016, the first period after the beginning of the IANA transition. You will see
<span style="color:#1F497D">the </span>CSC has concluded that, overall, PTI’s performance was “Satisfactory”, in that they met the service level agreement for 95.9% of the defined metrics. For those missed service level agreements, the CSC believes that these
were satisfactorily explained and has determined that these exceptions were no cause for concern. No persistent problems were identified and no further action is needed. Also attached is the report from PTI to the CSC listing the individual service level metrics
along with their actual and historical performance. As this is the first report in what we expect to be an evolving process, any comments would be welcomed.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><span lang="EN-CA" style="font-size:14.0pt;line-height:115%">Some of you may find a bit of background on the CSC and these reports to be useful. Most of you will be aware that effective October
1, 2016, PTI has entered into a contract (the <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_iana-5Fpti-5Fdocs_151-2Diana-2Dnaming-2Dfunction-2Dcontract-2Dv-2D30sep16&d=DgMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=nC4gfbyyEQpMRtwgTZRqwi_KEPkorJJN6BPIwtsjBWQ&m=Iucv7ufAjCNf-vHy0NWoUpBuyw7hic9o8YBvz5UL4eQ&s=t6WeBTjiwZhOSndhajB94XK5rYsClMIVfgbYvRI0SP4&e=">
IANA Naming Function Contract[icann.org]</a> ) with ICANN for the provision of naming related services related to management of the DNS. Annex A of the contract specifies that PTI will respect some very specific “service level expectations” which have specific
thresholds. For example, the monthly threshold of staff processing time needed to validate and review a request for the creation or transfer of a gTLD is 10 days (‘less than or equal to’). To be considered to have met this metric, PTI needs to meet the threshold
90% of the time. You will note in the CSC’s report (page 18) that there were 8 gTLD requests in October, the longest of which took 3.92 days, and the mean time was 1.06 days. So, PTI
<i>has met the SLE</i> for gTLD creation/transfer requests for the month of October.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><span lang="EN-CA" style="font-size:14.0pt;line-height:115%">Similarly, there is a SLE for supplemental technical checks related to a ccTLD creation or transfer which is 5 minutes (‘less than
or equal to’) 95% of the time (see page 12 of the PTI Report). Of the 6 requests, three took longer than 5 minutes, and the average was 7.98 minutes, so PTI
<i>did not meet</i> the SLE in this case. But, as noted above, CSC believes that this variance was satisfactorily explained and has determined the exceptions do not represent a cause for concern.</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.0pt;line-height:115%"><span lang="EN-CA" style="font-size:14.0pt;line-height:115%">The CSC was formed effective October 1, 2016. Background on the committee along with transcripts of our meetings and other useful
information can be found on <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_csc&d=DgMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=nC4gfbyyEQpMRtwgTZRqwi_KEPkorJJN6BPIwtsjBWQ&m=Iucv7ufAjCNf-vHy0NWoUpBuyw7hic9o8YBvz5UL4eQ&s=h-6bNHxTWtw8-tRi3oKZHyMifvFrks7v2rjyZZuqXJ4&e=">
our website[icann.org]</a>. </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt">Byron Holland</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt">Chair of the CSC</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><b><span lang="EN-CA" style="font-size:14.0pt;mso-fareast-language:EN-CA">Byron Holland</span></b><span lang="EN-CA" style="font-size:14.0pt;mso-fareast-language:EN-CA">, President & CEO</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt;mso-fareast-language:EN-CA">Canadian Internet Registration Authority (CIRA)</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt;mso-fareast-language:EN-CA">Twitter:
<a href="mailto:@cira001">@cira001</a></span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt;mso-fareast-language:EN-CA">Trends, Commentary, Perspective. Stay tuned to
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cirablog.ca_&d=DgMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=nC4gfbyyEQpMRtwgTZRqwi_KEPkorJJN6BPIwtsjBWQ&m=Iucv7ufAjCNf-vHy0NWoUpBuyw7hic9o8YBvz5UL4eQ&s=1vd0S-MduheixBfnvcFzdAVs50jZJD_WvU9eFtBQf_U&e=">
cirablog.ca[cirablog.ca]</a></span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt;mso-fareast-language:EN-CA"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cira.ca_&d=DgMFAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=nC4gfbyyEQpMRtwgTZRqwi_KEPkorJJN6BPIwtsjBWQ&m=Iucv7ufAjCNf-vHy0NWoUpBuyw7hic9o8YBvz5UL4eQ&s=h_UArXz2pEVO4HMQhSrCy525VCED_tvGc7IJYGTQ7OI&e=">www.cira.ca[cira.ca]</a></span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt;mso-fareast-language:EN-CA"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:14.0pt"> </span><o:p></o:p></p>
</div>
</body>
</html>