Page History
THE CSC'S SCOPE
The Customer Standing Committee is defined in Bylaws Article 17
The CSC ensures the satisfactory performance of the Internet Assigned Numbers Authority (IANA) naming function.
The CSC is responsible for monitoring Public Technical Identifier’s (PTI) performance of the IANA naming function against the service level expectations in the IANA Naming Function Contract.
The CSC analyzes performance reports provided by PTI and publishes its findings.
The CSC is authorized to undertake remedial action to address poor performance of the IANA naming function, and if performance issues are not remedied, may escalate the issues to the ccNSO and GNSO.
- The CSC was established in accordance with Article 17.3 (b) of the ICANN Bylaws and conducted its first meeting on 6 October 2016.
- CSC wiki
- Guidelines for CSC Practices
- The CSC sends a monthly report to its customers that includes a review of the latest PTI Naming Performance Report, as well a cover letter to convey any additional messages.
- Adopted Remedial Action Procedures were developed to address a PTI Performance Issue, which is defined in the ICANN Bylaws as “any deficiency, problem or other issue that has adversely affected PTI's performance under the IANA Naming Function Contract. To date, the RAPs have not be needed to be used.
- Service Level Agreement Change Procedures: The SLAs are enforceable by ICANN through the IANA Naming Functions Contract it holds with PTI. This process was developed to enable timely amendments to service levels that fall into a number of defined categories. This same document also holds the Procedure for Modifying the Process for Amending the IANA Naming SLAs, should the change process itself need modification.
To date, three sets of SLA changes have been or in the process of being changed:
-Technical Checks: SLA changes were approved (based on SLA Change Type, no Public Comment was required) and went live on 01 July 2019
-IDN Tables was approved by the ccNSO and GNSO Councils during ICANN66 and will go live 01 December 2019.
-ccTLD Transfer and Changes: currently in Public Comment
Description of Proposed ccTLD Creation and Transfer SLAs
- CSC Charter Review: Bylaws 17.3.c calls for a “Review of the CSC’s Charter on year after the first meeting of the CSC, and thereafter only at the request of the CSC, ccNSO, GNSO, the Board and/or the PTI Board and/or by an IFRT in connection with an IFR.“ The Charter Review Team convened in November 2017 and published their final report on 26 June 2018.
-CSC Charter Review Final Report
-Original CSC Charter
- CSC Effectiveness Review: Bylaws 17.3.b calls for “the effectiveness of the CSC shall be reviewed two years after the first meeting of the CSC; and then every three years thereafter. The method of review will be determined by the ccNSO and GNSO and the findings of the review will be published on the Website.” CSC Effectiveness Review convened in October 2018 and published their Final Report in April 2019.
-CSC Effectiveness Review Wiki
-CSC Effectiveness Review Final Report
...
2022 - 2023 CSC EFFECTIVENESS REVIEW
In accordance with Section 17 of the ICANN Bylaws and the CSC Charter, the effectiveness of the CSC is to be reviewed two years after its first meeting, and then every three years, using a method determined by the ccNSO and GNSO. In September 2018, the ccNSO and GNSO Councils adopted a Template to conduct the first Effectiveness Review. In August 2021, the ccNSO and GNSO Councils adopted the Terms of Reference for the second CSC Effectiveness Review, using the same template as the first review supplemented with a question on whether the recommendations of the first review had been implemented and were effective.
March 2023 CSC Effectiveness Review Final Report: https://gnso.icann.org/sites/default/files/policy/2023/correspondence/csc-to-gnso-council-et-al-17mar23-en.pdf
...
