[ICANN-CSC] [Ext] VS: [GAC] Briefing - CSC work and evaluation of PTI

Wed Feb 22 01:40:56 UTC 2017

Dear Elise,

If I understand the question in the thread, Mr. Ahkuputra would like to know what is meant by “aspirational target”.  In PTI’s October 2016 Monthly report to the CSC, we noted that the primary cause for the exception to the SLA of 60 days for processing a ccTLD delegation was an “aspirational target”.  

The 60 day service level target which was established by the CWG’s Design Team A was chosen after it had reviewed data for previous ccTLD delegations. The data related to processing ccTLD delegations was in the hundreds of days for processing and the Design Team decided to set a tighter SLA acknowledging that it might not be achievable.  If the SLA proved to be too tight and unrealistic, it was acknowledged that the SLA would be revisited at some time in the future.  Since this SLA for “Staff Processing; Validation and Review; ccTLD creation/transfer” was set at a level that does not reflect the trending data for processing ccTLD delegations, we noted that the cause of missing the SLA was that the target was something to strive to attain, but might not be achievable – an aspirational target.  

I hope that answers Mr. Ahkuputra’s question.  And do enjoy your time skiing!

Kind regards,

  --Elise

Elise Gerich 

President | PTI

12025 Waterfront Drive | Suite 300

Los Angeles, CA 90094

+1-310-463-1108

From: "Lindeberg, Elise" <elise.lindeberg at Nkom.no>
Date: Tuesday, February 21, 2017 at 8:12 AM
To: Elise Gerich <elise.gerich at iana.org>, "ICANN-CSC at icann.org" <ICANN-CSC at icann.org>
Subject: [Ext] VS: [GAC] Briefing - CSC work and evaluation of PTI

Dear Elise, CSC colleagues

I am forwarding a question/response that I received from my GAC colleagues on CSC - it follows in the thread beneath.  

This is a question/response after I sent out a GAC briefing on CSC as part of the preparation for Copenhagen (We all have to do this on the various topics on the GAC agenda some weeks before the ICANN meetings). This is related to IDN ccTLD delegation request in one of the PTI reports  - and I should give some feedback/answer to this on the GAC list preferable before Copenhagen. Could you look into this Elise, - when you have time - I am on my way to the Norwegian mountains for a much longed for ski holiday, and will not be back in office before next week  - so no rush really J

Thanks,

Kind regards 

Elise 

Elise Lindeberg

Chief Legal Adviser

Norwegian GAC representative

Norwegian Communications Authority

Dir. +47 22 824607 Mob. +47 90190947

ekl at nkom.no 

Fra: Manal Ismail [mailto:manal at tra.gov.eg] 
Sendt: 9. februar 2017 06:47
Til: Wanawit Ahkuputra; Lindeberg, Elise; gac-bounces at gac.icann.org; gac at gac.icann.org
Emne: RE: [GAC] Briefing - CSC work and evaluation of PTI

Adding my thanks to Elise, and my support to Wanawit's suggestion ..

Kind Regards

--Manal

Egypt GAC Representative

From: gac-bounces at gac.icann.org [mailto:gac-bounces at gac.icann.org] On Behalf Of Wanawit Ahkuputra
Sent: Thursday, February 09, 2017 2:34 AM
To: Lindeberg, Elise; gac-bounces at gac.icann.org; gac at gac.icann.org
Subject: Re: [GAC] Briefing - CSC work and evaluation of PTI

Dear Elise,

Thanks for your update on your CSC work. Reference to the mentioned report under the section “Staff Processing

Validation and Reviews”

There were on exception report as follow:

Exception Narrative

Primary cause: Aspirational target

Analysis/Comments: This is an IDN ccTLD delegation request. The request was lodged in March 2016,

prior to the new service levels. A ccTLD delegation request requires extensive

amount of communications with the requestor. In this particular case, the staff were

extra cautious in their review because the supporting materials gave some confusion

about who is the proposed operator of the TLD. In addition, the requesting entity

also operates the ASCII ccTLD for the country and there were some issues that

existed for the ASCII ccTLD that we wanted to make sure are mitigated in the

delegation of the IDN ccTLD.

It would be benefit to us all to understand some of the specific term use for primary cause “Aspirational target” as it might not easy t understand the meaning of it. Delegation and Re-Delegation on ccTLD is very much relate to the GAC and it would be necessary for us to understand the process of how this process work. At the GAC meeting this round might be some of the issue relate to this function of PTI as well.

Thanks, you for your contribution and continuous support GAC work since the beginning of IANA transition.

Regards,

Mr. Wanawit Ahkuputra

Deputy Executive Director

ETDA - Electronic Transactions Development Agency (Public Organization)

MDES-Ministry of Digital Economy and Society

Royal Thai Government

Tel: +66 2123 1234

Fax: +66 2123 1200

Mob.: +668 9301 8818

Email: wanawit at etda.or.th

Electronic Transactions Development Agency (Public Organization)

The9th Tower Grand Rama9 Building (Tower B) Floor 21 

33/4 Rama 9 Road, Huai Khwang, Bangkok 10310

[T] 0-2123-1234 

[F] 0-2123-1200

From: <gac-bounces at gac.icann.org> on behalf of "Lindeberg, Elise" <elise.lindeberg at Nkom.no>
Date: Wednesday, February 8, 2017 at 22:56
To: "gac-bounces at gac.icann.org" <gac-bounces at gac.icann.org>, "gac at gac.icann.org" <gac at gac.icann.org>
Subject: [GAC] Briefing - CSC work and evaluation of PTI

Dear GAC colleagues, I`m sending you an update on the ongoing work of the Customer Standing Committee (CSC) before ICANN 58 in Copenhagen. 

For our new colleagues in the GAC, a brief description of the CSC and its tasks :  

Under the expired IANA functions contract, NTIA (US GOV) provided operational oversight of the IANA naming function. As part of the IANA transition the domain names community required that a Customer Standing Committee (CSC) be formed to replace this oversight and ensure the continued satisfactory performance of the IANA naming function towards the direct customers of the naming services (direct customers is defined as  a gTLD registry operator, a ccTLD manager or registry operator or other direct customer of Contractor  - e.g., a root server operator or other non-root zone function). CSC monitors PTI’s performance of the IANA naming function by analyzing performance reports on a monthly basis and publishing its findings. The reports from PTI shows performance metrics on responding, processing and completing technical or administrative changes in the root zone - this includes many different categories of change requests that are explained in the PTI reports. CSC is authorized to undertake remedial action to address poor performance, and if performance issues are not remedied, the CSC is authorized to escalate the performance issues to the ccNSO and GNSO for consideration. 

The CSC is a small committee consisting of members from the “direct customers” of the IANA naming functions, and liaisons from the rest of the community  - GAC, SSAC, ALAC, GNSO (Non-Registry) and RSSAC. Liaisons are not members of or entitled to vote on the CSC, but otherwise liaisons participate on equal footing with members of the CSC. The full list of members and liaisons is available at https://www.icann.org/en/csc/members-liaisons[icann.org]

CSC work and meetings from October 2016 to January 2017 : 

The CSC has been active since October 1st 2016. Meeting schedule has been set to a monthly conference call meeting on the 15th of each month, or the first Monday/weekday thereafter  - with the possibility to schedule additional meetings if needed.  In the startup 2016 there was some additional meetings to discuss future meeting structure, selection of chair, format of monthly reports etc.   

In total there has been 6 CSC meetings from October 2016 to January 2017 - one f2f meeting at ICANN 57 in Hyderabad, and 5 additional conference calls. Before each CSC call PTI has produced a monthly report on the deliverables towards the direct customers -  with explanation on all divergent findings measured against the SLA obligations that PTI have towards the direct customers. Based on these PTI reports, online discussions and monthly conference calls between PTI leadership and CSC,  - CSC produces a monthly evaluation and findings reports on PTI performance that are published on the ICANN/ICANN CSC websites, and also sent directly to the chairs of the chartering SO`s and AC`s.  

In short the performance from PTI has been satisfactory. PTI met the service level agreement for 95.9% - 99.0% of defined metrics in the monitored months from October 2016 - January 2017. Missed service level agreements were satisfactorily explained and the CSC has determined that these exceptions were no cause for concern. No persistent problems were identified and no further action is needed. Under the IANA Naming Function Contract, PTI is required to collaborate with the CSC on an annual customer service survey. PTI has delivered a very good “IANA Customer Service Survey” for 2016  that shows overall satisfaction among all customer groups who used the services provided by the IANA department in the past 12 months. The overall satisfaction remained high at 94 percent – 

https://www.iana.org/reports/2017/customer-survey-20170111.pdf[iana.org]. The CSC will work together with PTI and the rest of the community to further develop and improve this annual customer survey.   

For detailed information about the monthly reports from PTI and CSC, CSC charter, latest updates on meetings and work sessions, transcripts from meeting etc., go to https://www.icann.org/csc[icann.org]  

If you'd like to be directly informed of upcoming meetings, receive CSC reports, etc., subscribe at https://mm.icann.org/mailman/listinfo/csc-announce

Kind regards

Elise Lindeberg

Chief Legal Adviser

Norwegian GAC representative

Norwegian Communications Authority

Dir. +47 22 824607 Mob. +47 90190947

ekl at nkom.no 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/icann-csc/attachments/20170222/e6cab87c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4607 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/icann-csc/attachments/20170222/e6cab87c/smime-0001.p7s>