I spent some time with Bart this morning going over the SLA change procedures, the history of the conversations with ICANN legal, PTI, and CSC, and the documents.

Bart is going to put together a summary email and send that out tomorrow.

In the meantime I thought it would be helpful to provide some context to the SLA change procedures. Please see attached document that includes comments illustrating each proposed change type. I hope that sheds some light on each type of SLA change, and why each type of change could be non material or material, depending on the service being reviewed.

********
Below is all of the language on SLA changes from the current Draft. The language in the "review" section conflicts with the language in the "scope of responsibilities"

Scope of responsibilities:

The CSC will develop with the IANA Function Operator and ICANN a process for timely

amendments to service levels where such changes are minor and are unlikely to impose

additional resource requirements on the IANA Naming Function Operator (15) (Section 4.3.10).

This process for timely amendments of the service levels may be updated from time to time and will only become effective after publication of the process on the CSC webpage and after informing the direct customers.

 

Scope of responsibilities:

In the event it is agreed that a material change in IANA naming services or operations would be beneficial, the CSC reserves the right to call for a community consultation and independent validation, to be convened by the IANA Functions Operator, on the proposed change. Any recommended change must be approved by the ccNSO Council and RySG. In the event that the proposed changes require an amendment to the IANA Naming Function Contract this will be done in accordance with (is there a section of the contract we can site?)and RySG.

 

Review:

The CSC or the IANA Functions Operator can request a review or change to service levels targets. Any proposed changes to service llevel targets as a result of the review must be agreed to by the ccNSO and GNSO.