<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
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","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{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-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">CSC Members and Liaisons,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Below is the introductory email I intend to accompany our first report to the community as well as the revised PTI report. As indicated on our last call I would like to ensure Elaine had the time to review it as well as ensure all CSC
members are in agreement. I believe the text below and the attached docs satisfy our objectives. Unless I hear otherwise I intend for this package to be out by end of day today, November 30<sup>th</sup>.<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">Byron<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">------------------------------------------------------------------------------------------------------------------------------------------------<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear Community Members,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:10.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.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.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://www.icann.org/iana_pti_docs/151-iana-naming-function-contract-v-30sep16">
IANA Naming Function Contract</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.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.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.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:10.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://www.icann.org/csc">our website</a>. <o:p></o:p></p>
<p class="MsoNormal">Byron Holland<o:p></o:p></p>
<p class="MsoNormal">Chair of the CSC<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;mso-fareast-language:EN-CA">Byron Holland</span></b><span style="font-size:9.0pt;mso-fareast-language:EN-CA">, President & CEO<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;mso-fareast-language:EN-CA">Canadian Internet Registration Authority (CIRA)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;mso-fareast-language:EN-CA">Twitter:
<a href="mailto:@cira001">@cira001</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;mso-fareast-language:EN-CA">Trends, Commentary, Perspective. Stay tuned to
<a href="http://www.cirablog.ca/">cirablog.ca</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;mso-fareast-language:EN-CA"><a href="http://www.cira.ca/">www.cira.ca</a></span><o:p></o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>