Thanks Elaine, I look forward to the additional information from Bart. One important note--in my mind, this is not about SLAs: 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. and must be read in conjunction with the preceding text: The CSC, in consultation with registry operators, is authorized to discuss with the IANA Functions Operator ways to enhance the provision of IANA’s operational services for any of the following reasons: · to meet changing technological environments; · as a means to address performance issues; or · other unforeseen circumstances. 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. From memory, when we drafted this language, it was not intended to be about SLAs but was intended to provide some flexibility to suggest improvements to systems or technology that would improve IANA’s responsiveness or performance. For example, with the introduction of new gTLDs perhaps IANA’s systems were not adequate to do what they could adequately do for 200 TLDs. I’d welcome input from others. From: Elaine Pruis [mailto:elainepruis@gmail.com] Sent: Tuesday, March 27, 2018 9:54 AM To: Martin Boyle <martin.boyle.hertford@ntlworld.com>; Bart Boswinkel <bart.boswinkel@icann.org> Cc: Austin, Donna <Donna.Austin@team.neustar>; CSC-review@icann.org Subject: [EXTERNAL] Re: [CSC-Review] Amended Charter Thanks Martin 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. On Tue, Mar 27, 2018 at 12:22 PM, Martin Boyle via CSC-Review <csc-review@icann.org<mailto:csc-review@icann.org>> wrote: As promised, I have made some minor edits to the amended charter for consideration. I’ve also made a few comments on areas of the text! From: CSC-Review <csc-review-bounces@icann.org<mailto:csc-review-bounces@icann.org>> On Behalf Of Austin, Donna via CSC-Review Sent: 26 March 2018 22:03 To: CSC-review@icann.org<mailto:CSC-review@icann.org> Subject: [CSC-Review] Amended Charter Keith, all Attached for your review is the Amended Charter as discussed earlier today. To the extent that its helpful I’ve also provided a compare of the Amended and Original Charters; and a copy of the Original Charter. Thanks Donna Donna Austin Neustar, Inc. / Senior Policy Manager, Registry Solutions Mobile: +1 310 890 9655<tel:(310)%20890-9655> donna.austin@team.neustar<mailto:donna.austin@team.neustar> / Website: home.neustar<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.home.neustar_&d=DwMF...> Follow Neustar: LinkedIn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company...> / Twitter<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_neustar&...> Reduce your environmental footprint. Print only if necessary. ________________________________ The information contained in this email message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this email message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message. _______________________________________________ CSC-Review mailing list CSC-Review@icann.org<mailto:CSC-Review@icann.org> https://mm.icann.org/mailman/listinfo/csc-review<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_csc-2Dreview&d=DwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=fz80z-mqrRzCYNtAfq2MIOy4ya0PtrBkm7N83Oyg8VM&s=CWVy-d1feNTP9EnriAd8ow9WEd-IsAJV8UpRoUWiHBQ&e=>