[council] FW: [Soac-infoalert] CSC Report performance PTI January 2017

[James M. Bladel]

Colleagues –

Here’s some additional context from James Gannon.

Thanks—

J.


Hi James,
Would you be able to forward this to council for me?

Thanks for brining attention to the CSC report, as you can see we have now settled into a monthly reporting schedule where the CSC report of PTI performance is documented. As one of the 3 GNSO involved stakeholders, myself representing non-Registries in a liaison role and Kal Feher and Elaine Pruis as the RySG voting members, I am involved in the monthly review and assessment of all of the metrics in the report.

Unfortunately I will not be arriving in Copenhagen until after the session the CSC is holding to brief Council  on the progress, function and role of the committee but going forward I will hope to be able to participate in these face to face briefings that we will likely hold at each ICANN meeting. Of course I am always available over email for all councilors and their constituencies.

We on the CSC have settled into a good rhythm in the last 2 calls and are fleshing out our working style and operating procedures and I hope that once we are in ‘business as usual’ operation I can start to actively work with our non-RySG community on how we wish to manage our communications and reporting going forward.

I look forward to hearing any feedback from Council on this topic and look forward to seeing everyone on my arrival in Copenhagen on the 15th (Just coming in for the end and for the SSR2 RT meeting which I also thank Council for appointing me to and am very excited to begin work on)

-James Gannon




From: <council-bounces at gnso.icann.org> on behalf of "James M. Bladel" <jbladel at godaddy.com>
Date: Tuesday, February 21, 2017 at 13:46
To: GNSO Council List <council at gnso.icann.org>
Subject: [council] FW: [Soac-infoalert] CSC Report performance PTI January 2017

Councilors –

See message below and attached documents, which comprise the January 2017 report & update from the PTI/CSC.

If you have any questions for the CSC or the PTI, I recommend referring these to James Gannon (GNSO Liaison to the CSC).   Also, Marika:  Perhaps James would like to deliver these reports going forward?  He may be able to provide additional context or respond to questions from the Council or GNSO SGs and Cs.

Thank you,

J.


From: <soac-infoalert-bounces at icann.org> on behalf of Bart Boswinkel <bart.boswinkel at icann.org>
Date: Tuesday, February 21, 2017 at 12:03
Subject: [Soac-infoalert] CSC Report performance PTI January 2017

Dear all,
On behalf of the chair of the CSC (Byron Holland), please find included following message, CSC report and underlying PTI January report to the CSC,
Kind regards,
Bart Boswinkel

--------------------------
21 February 2017

Dear Community Members,
As chair of the Customer Standing Committee I am pleased to provide you with our monthly report on the performance of Public Technical Identifiers (PTI), for January 2017.  You will see the CSC has concluded that, overall, PTI’s performance in January 2017 was “Satisfactory”, in that they met the service level agreement. The CSC is aware of some minor issues that were previously identified and we are in an ongoing dialogue with PTI to mediate them for the future, noting there is no trend. In summary: No persistent problems were identified and no further action is needed, nor was the CSC informed about any complaint.

Attached is the report from PTI to the CSC listing the individual service level metrics along with their actual and historical performance.  Any comments on our reporting to you would be welcomed.

I also use this opportunity to draw your attention to our meetings with the different stakeholders and the ICANN Board of Directors at during ICANN 58 in Copenhagen. The schedule of the meetings can be found on our website.

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 https://mm.icann.org/mailman/listinfo/csc-announce


The CSC was formed effective October 1, 2016. Background information on the committee along with transcripts of our meetings and other useful information can be found athttps://www.icann.org/csc[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_csc&d=DgMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=nC4gfbyyEQpMRtwgTZRqwi_KEPkorJJN6BPIwtsjBWQ&m=VZQPuV5dbiIC99ZtBIQGg5_YI5jr7ULTG7KNY2BIoX8&s=rxAQ54V1tRLjtdb8J5WVGdOA66R0al6v7UrxxdqzJc8&e=> .

Kind regards,
Byron Holland
Chair CSC


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/council/attachments/20170222/05eba18e/attachment.html>