<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="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:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Sent on behalf of the Chair of the CSC, Lars-Johan Liman.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">------------------------------</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">27 February 2020<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear Community Members,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">It’s my pleasure as chair of the Customer Standing Committee (CSC), to provide you our latest monthly findings on the performance of Public Technical Identifiers (PTI) over January 2020. I am pleased to inform
you that the CSC has concluded that PTI’s overall performance over January 2020 was “Satisfactory” - PTI met the service level agreement at 98.5% for the month of January 2020. The missed Service Level was satisfactory explained and is subject to a CSC recommendation
to introduce new measurements to create a more meaningful performance measurement for this process. The related PTI report to the CSC, listing the individual service level metrics along with their actual and historical performance, can be found at: <a href="https://www.iana.org/performance/csc-reports" title="https://www.iana.org/performance/csc-reports">https://www.iana.org/performance/csc-reports</a>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I’m also very pleased to provide you an update on the one outstanding SLA change – the ccTLD Creation/Transfer – Validation and Reviews: SLA amendments. In accordance with the SLA change process (<a href="https://www.icann.org/en/system/files/files/iana-naming-function-sla-amendment-process-28mar19-en.pdf">https://www.icann.org/en/system/files/files/iana-naming-function-sla-amendment-process-28mar19-en.pdf</a> ) the
CSC has formally asked the ccNSO and GNSO Councils to agree to the amendment of the SLA. After both Councils support the change implementation work will start. The SLA changes are explained in more detail in the CSC Findings report.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I am also pleased to inform you that the CSC and PTI have initiated a discussion on the possible scope of the role the CSC in the context of the IANA Naming Function Contract. This discussion will be continued.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">As you may be aware the CSC was supposed to conduct an in person meeting during ICANN67 in Cancun and had scheduled meetings with the Board Technical Committee and IANA Function Review Team and would provide
updates to the ccTLD Managers present and Registry Stakeholder Group. However, with the change of ICANN67 to a virtual meeting the CSC has cancelled its meeting during ICANN67. The next meeting will be at or around the regular meeting time.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The CSC regular meetings are scheduled on or around the 15th every month. The schedule can be found on the CSC website (<a href="https://www.icann.org/csc">https://www.icann.org/csc</a>). The CSC Findings
report on the PTI performance is sent out shortly after that. CSC meetings are open to attend. If you would like to be informed of upcoming meetings or receive CSC reports directly, you may want to subscribe to our announce list at <a href="https://mm.icann.org/mailman/listinfo/csc-announce">https://mm.icann.org/mailman/listinfo/csc-announce</a> .
Any comments on our reporting to you is welcome.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The CSC became effective October 1, 2016. Background information on the committee along with transcripts of our meetings and other useful information can be found at<a href="https://www.icann.org/csc" title="https://www.icann.org/csc">https://www.icann.org/csc</a> .<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Lars-Johan Liman <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Chair CSC<o:p></o:p></span></p>
</div>
</body>
</html>