March 2018 - CSC-Review - lists.icann.org

Review of the Report
by Martin Boyle April 6, 2018

April 6, 2018

Hi All, On the call on Monday, I promised to provide some tidying up on the draft report (and Keith would then use this document as he reviewed the Charter amendments section). I have tried to eliminate inconsistencies (I think there are still some in the use of PTI and IFO), simplify the language and break the text into shorter, more manageable paragraphs. I've also tried to cut out some of the repetition (I hope that I haven't over-cut) and remove redundant words. The result is attached: it is based on the v7 amended by Donna in her e-mail last Friday with her comments all accepted. I'm not precious about the exact wording, but I hope that I have made the text a little more readable! Best Martin

4 14

Update on SLA changes
by Elaine Pruis April 3, 2018

April 3, 2018

Dear all, Following are notes and proposed text that Bart put together, and I've reviewed, to provide some context and background on the need to change the language in the charter with respect to amending Service Levels; The starting point is in the current charter in the Review section: “The CSC or the IANA Functions Operator can request a review or change to service level targets. Any proposed changes to service level targets as a result of the review must be agreed to by the ccNSO and GNSO.” Note 1. This section in the current charter is under the heading of Reviews, which may not be the most adequate location in the text. Changes result from monitoring the performance of PTI, and needs from the community ( for example adding SLAs for the IDN tables). Note 2. The section in the charter referenced above is first and foremost related to the service levels as defined in the IANA Naming Function Contract. There may be potential overlap with the section under the Scope of Responsibilities Donna mentioned in her email yesterday. However the CSC used the language in the Review section as a starting point for discussing and suggesting changes to the Service Levels As the Service Level targets are defined in the* IANA Naming Function Contract,* amending the service levels at first reading implies a change of the contract, which could be very heavy handed for most of the changes needed ( see Elaine’s email). Here is the relevant section in the IANA Naming Functions Contract: Section 2.c of Annex A of the Naming Function Agreement, where the SLAs are housed, states: (italics EP) “Either Party (BB Comment: ICANN or PTI) may initiate a change to the *services* performed by Contractor hereunder by delivering to the other a change request, in a form mutually acceptable to the Parties. Thereafter, the Parties will discuss the requested change in good faith and upon the Parties’ *mutual written agreement* that a change to the services performed by Contractor hereunder should be made, such change shall be evidenced in writing and* deemed to be incorporated into this Contract, without any need to amend the terms of this Contract*.” (See: https://www.icann.org/iana_pti_docs/151-iana-naming-function-contract-v-30s… ) Now quoting Sam Eisner: “With that, we see the work here is essentially to develop a subprocess for the CSC, ICANN and PTI to demonstrate that a proposed SLA change is supported by the customers and PTI, and that ICANN and PTI can then agree to modify the SLAs. The full contract modification process is not required in this instance. Some highlights for that subprocess could include (including areas already considered by the CSC to be part of it): - CSC and PTI agree that there is a need for a modification to the SLA (can be reflected in minutes, etc.) - CSC helps consult among/socialize with naming functions customers (Note: this is reflected as a possible public comment period in the process, but ICANN org would not require a comment period for this type of operational change; the consultation process could be designed in another way to reach the appropriate/impacted customers). - Once agreement is reached on the appropriate SLA, identify the proper threshold for documenting the customer support of change. (Note: because this is not a full contract amendment, the CSC could consider if the threshold counts based on the ccSNO and GNSO Council are still appropriate or if it should be tailored more to the customers) - PTI and ICANN Board approval would typically not be required for a change to the SLA, unless it imposed material financial impact to implement, or possibly if modifications to other contracts were needed to accommodate the SLA modification.” With the highlights Sam mentioned in mind, a CSC sub-group started to develop a set of procedures for the different types of changes, the Variable SLA Change Procedures, which were shared with the CSC RT and illustrated by Elaine. As each of the procedures headings states, the starting point is a change to the documented Service Levels. In terms of the CSC, they developed change processes that adequately address the need to remain transparent in all its dealings with PTI-IANA, while not exhausting the respective communities with the necessity to examine and affirmatively acknowledge trivial SLA changes. As the CSC members act as representatives of and remain accountable to their communities they feel that working with PTI-IANA to introduce SLA changes should be a core function of that representation. (EP Note: the ccNSO and RYSG can at anytime recall their appointees; if there is concern that a member is acting out of the interest of the direct customers, they can be replaced). The CSC also expressed that an addition / clarification is required to the current CSC charter. The required change should be made in the “Scope of Responsibilities” section. To avoid any confusion or conflation with responsibilities related to changes to the IFO services we recommend that this new responsibility appear amongst the earlier paragraphs of that section (and hence *replaces* the current language in the Review section) and include in the Scope of Responsibilities an additional subsection directly following the section on monitoring the performance of the IFO. Proposed language to include in the CSC Charter as part of the review team work: *The CSC will develop appropriate processes for engagement with registry operators and the community consultation by which Service Level changes can occur. These processes are commensurate with the nature of the Service Level change being proposed. Informing the registry operators shall always be required. Where the proposed changes are minor, for example a minor change to a target/threshold, a full community consultation would not be required. The processes for amendments of the service level 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 ccNSO Council and RySG, the direct customers.* Please let me know if you have any questions. Elaine

3 2

Amended Charter
by Austin, Donna March 27, 2018

March 27, 2018

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 donna.austin(a)team.neustar<mailto:donna.austin@team.neustar> / Website: home.neustar<http://www.home.neustar/> Follow Neustar: LinkedIn<http://www.linkedin.com/company/5349> / Twitter<http://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.

3 3

Re: [CSC-Review] [Ext] RE: CSC Charter Review Team Call
by Maria Otanes March 26, 2018

March 26, 2018

Hi Keith, I’ve added you to the group and tried dialing out to you. Have you received it? From: "Drazek, Keith" <kdrazek(a)verisign.com> Date: Monday, March 26, 2018 at 1:02 PM To: Maria Otanes <maria.otanes(a)icann.org>, "CSC-review(a)icann.org" <CSC-review(a)icann.org> Cc: Bart Boswinkel <bart.boswinkel(a)icann.org>, "martin.boyle.hertford(a)ntlworld.com" <martin.boyle.hertford(a)ntlworld.com> Subject: [Ext] RE: CSC Charter Review Team Call Hi all, my Skype address is keithdrazek -----Original Appointment----- From: Maria Otanes [mailto:maria.otanes@icann.org] Sent: Monday, March 26, 2018 11:33 AM To: CSC-review(a)icann.org Cc: Bart Boswinkel; Martin Boyle Subject: [EXTERNAL] [CSC-Review] CSC Charter Review Team Call When: Monday, March 26, 2018 5:00 PM-6:00 PM (UTC) Coordinated Universal Time. Where: Skype We will use Skype, but if for some reason that doesn’t work, we will use Adigo (details below). While Adobe Connect is down, please use the dial in numbers below for next week’s CSC Review Team call. US/Canada: 1 800 550 6865 Dial in numbers: http://www.adigo.com/icann/[adigo.com] Conference ID: 6294 << File: ATT00001.txt >>

1 0

CSC Charter Review Team Call
by Maria Otanes March 26, 2018

March 26, 2018

We will use Skype, but if for some reason that doesn't work, we will use Adigo (details below). While Adobe Connect is down, please use the dial in numbers below for next week's CSC Review Team call. US/Canada: 1 800 550 6865 Dial in numbers: http://www.adigo.com/icann/ Conference ID: 6294

2 1

CSC Review Team call on Monday, 26 March
by Maria Otanes March 26, 2018

March 26, 2018

Hello all, Hope your travels back from Puerto Rico was uneventful. With Adobe Connect down, would you be able to join a Skype call on Monday? If so, please send me your Skype ID. Otherwise, we will use Adigo: Dial in numbers: http://www.adigo.com/icann/ Conference ID: 6294 Please let me know by EOD Friday, 23 March what works best for you. Thanks! Ria _______________________________________________________________________________________________ Ria Otanes | Secretariat Operations Coordinator Email maria.otanes(a)icann.org | Cell +1 202 679 5185 Internet Corporation for Assigned Names and Numbers Washington, DC Office | EDT / UTC-4

4 5

Updated report
by Bart Boswinkel March 23, 2018

March 23, 2018

Dear all, Please find included the updated version of the Initial report (06 redline and clean). I started with the latest version Elaine send to the list. As discussed: Checked and included references to ICANN Bylaws. Added subsection numbering Included references in amended charter text + slight adjustments Finally version 7 does NOT include the table anymore. Suggest once the RT reaches agreement on changes to the charter to include a compare/redline of the proposed charter with current charter (Annex A). Kind regards, Bart

2 1

CSC Charter Review Team Call
by Maria Otanes March 22, 2018

March 22, 2018

While Adobe Connect is down, please use the dial in numbers below for next week's CSC Review Team call. US/Canada: 1 800 550 6865 Dial in numbers: http://www.adigo.com/icann/ Conference ID: 6294

3 2

CSC Charter Review Team Call
by Maria Otanes March 14, 2018

March 14, 2018

Link to Adobe Connect: https://participate.icann.org/csc/ US/Canada: 1 800 550 6865 Dial in numbers: http://www.adigo.com/icann/ Conference ID: 6294

1 0

Next steps charter review process
by Bart Boswinkel March 13, 2018

March 13, 2018

Dear all, This morning Donna, Elaine and Martin met to talk through the final steps to finalize the Initial report for publication. Goal is to publish the Report by 29 March or 3 April. To meet this goal the following steps have been agreed: Bart to check latest version against the ICANN Bylaw (Article 17) and ensure reference to relevant section in Bylaws, including reference to GNSO (Council), ccNSO (Council), and RySG. Include section numbering of the main text and reference in the amended charter. Verified version to be send to RT by 20 March. All to check text version 20 March- 23 March and send updates comments and suggestions. Bart to consolidate comments by 26 March. Finalize and conclude open issues conference call 26 March 17.00 UTC. Maria to send out calendar invite. In addition it was discussed to exclude the table with the proposed changes from the final text. Bart

2 1