- ICANN-CSC - lists.icann.org

CSC Findings Report January 2026
by Jennifer Bryce Feb. 16, 2026

Feb. 16, 2026

Dear CSC, Attached please find the draft CSC findings report for January 2026 for review and approval at your next meeting. Best, Jennifer Jennifer Bryce Senior Project Manager, Office of the Chief Technology Officer (OCTO) Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org<http://www.icann.org>

1 0

Draft Agenda CSC meeting 100 Wednesday 18 February | 02.00-03.00 UTC
by Bart Boswinkel Feb. 11, 2026

Feb. 11, 2026

Dear all, Please find included the draft agenda for the upcoming CSC meeting, Kind regards, Bart ------ Draft Agenda Customer Standing Committee (CSC) Meeting 100 Wednesday 18 February | 02.00-03.00 UTC 1. Welcome & Roll call 1. Action Items Action Items Action item 01-99 2025 IANA to tie incidents to missed SLA in reporting going forwards Action item 02-99 2025 Staff to circulate findings December 2025 Completed Action item 03-99 2025 PTI/ ICANN to identify representative ICANN (if anyone) in the SLA review process. Action item 04-99-26 Chair CSC to Build spreadsheet to capture assessment process Completed Action item 05-99 -26 PTI to identify interesting cases to familiarize PTI and CSC membership on how to assess SLA. Action item 06-99-26 Staff to schedule continuation discussion SLA agenda February meeting Completed 3. Performance IANA Naming Function January 2026 a) PTI report to CSC January 2026 Circulated by Selina on 11 February. Performance over January was 100%. b) CSC Findings PTI Performance January 2026 1. Administrative updates * Board adoption Bylaw changes to section 17 * Chair and Vice chair selection March 2026 See: https://www.icann.org/en/system/files/files/csc-appointment-procedure-04nov… 1. SLA review - Review of grid and testing The grid may be updated closer to meeting The grid: https://docs.google.com/spreadsheets/d/1RF9gWrgaTG_mJEJLO1sMTaHzSWzflmu7XJC… 1. Next Meetings * Meeting 101 – ICANN85, Mumbai, Monday 9 March 2026, Block 1 * Meeting 102 – 15 April 2026 | 10.00 – 11.00UTC * Meeting 103 – 20 May 2026 | 18.00 – 19.00 UTC * Meeting 104 – 24 June 2026 | 02.00 – 03.00 UTC (no meeting during iCANN86, Policy Forum | 8-11 June 2026) 1. AOB 1. Adjourn

1 0

January 2026 IANA Naming Function Performance Report
by Selina Harrington Feb. 11, 2026

Feb. 11, 2026

Dear CSC, Please find attached the IANA Naming Function Performance Report for January 2026. During the month of January, we met 100% of the SLA thresholds. We look forward to answering any questions you may have. Kind regards, Selina Harrington IANA Operations Manager

1 0

Notes and Agenda meeting 99 (21 January 2026)
by Bart Boswinkel Feb. 9, 2026

Feb. 9, 2026

Dear all, Please find included the notes and action items latest CSC meeting ( 21 January 2026) Kind regards, Bart ---------- Agenda and Notes Customer Standing Committee (CSC) Meeting 99 Wednesday 21 January 2026 | 18.00 – 19.00 UTC Action items meeting 99 * Action Item 01-99-26: IANA (Selina) to tie incident(s) to missed SLA in reporting * Action item 02-99-26 staff to circulate findings * Action 03-99- 26 – PTI/ ICANN to identify representative ICANN (if anyone) in the SLA review process. * Action item 04-99-26: Chair CSC to Build spreadsheet to capture assessment process * Action item 05-99 -26: PTI to identify interesting cases to familiarize PTI and CSC membership on how to assess SLA. * Action item 06-99-26: staff to schedule continuation discussion SLA agenda February meeting 1. Welcome & Roll call Meeting quorate No questions re agenda 1. Action Items Action Items Action item 01-98 2025 Staff to circulate findings PTI performance October and November 2025 Completed Action item 02-98 2025 Staff to schedule review of SLA process agenda meeting 99 Completed, see item 4 Action item 03-98 2025 CSC membership close read SLA change procedure ( change procedure is published here<https://www.icann.org/en/system/files/files/iana-naming-sla-amendment-proce…> ) and get familiar with SLAs ( current list of SLAs can be found here<https://pti.icann.org/iana-naming-function-services-service-level-agreements> ) To be discussed item 4 Action items completed 3. Performance IANA Naming Function December 2025 a) PTI report to CSC December 2025 Circulated by Selina on 13 January 2026– PTI performance was 93.8 %. From the email: The following SLAs were not met: - Email Dispatch Routine (Technical) - Email Dispatch Other Changes - Notification of Completion Routine (Non-Technical) - Time to Acknowledge Manual Enquiries PTI: PTI met 60 of 64 SLA. Email issues affected 4 SLAs. Request stopped due a bug Initially resolved by manually sending. Triggered by hardly used service Technical staff PTI present to provide in-depth explanation. Question: report October and November 100 %. Heard before bug, resolved. Now similar problem. Some bugs, some logic, and logic was corrected. What triggers the bug? PTI: First SLA based on volume, the more events come outliers pushed. Email got blogged: affected the SLA. Duration will trigger failure SLA. Issues in December are independent of previous issues Infrequently used item. In this case staff taking an action, no system, issue. Combination of data and interaction with customer. Staff took manual action caused incident. Testing suite: this situation causing issues is not included in test suite and is unforeseen CSC: Comment on how incident matches up it with SLA. Help to understand which SLA was triggered. After reading SLA. What is logic of implementation. Is published, if not should it be? Dispatch of routine notification, does not prevent action from happening Request were moving forward. Customers were not notified. Technical issues Manual sending emails, until fix was implemented Observation on SLA and how to meet them: IANA does not publish how systems meet SLA. SLA around a black box. Not very much control around sending email. SLA more about what is controlled. Form the chat: Wondering how long did it take to realize the SLA was not met. Is it at the time the SLAs were collected (sort of end of the month) or is it a few seconds after delay for notification had passed ? When did you realize SLA was not met? Reply: Not immediately noticed, but after a few business days. CSC observation: It sounds like that problem was agitated by customer. Last used long time ago, as a result bad data in system? It was logic looking at wrong field. Specific condition caused by confluence of two hardly used instances. Very small issue, staff worked around it. Macro issue difficulty connecting the email issue with SLA. Future version, hard connecting the dots. Interested in better description of incident. Question is whether we are not measuring correctly or did we miss anything in missing the SLA. Trust you measure the right thing. Report on missing. Did incident change how SLAs are captured? IANA: SLA tied back to customer impact. Not try to optimize away. SLA did show incident. Outbound stalled for 48 hours. Big impact so should have big impact on SLAs Action Item 01-99-26 IANA (Selina): Tie incident to missed SLA in reporting b) CSC Findings PTI Performance December 2025 Jennifer circulated CSC Findings 15 January. No need to adjust language (standard) Approved by Members Action item 02-99-26 staff to circulate findings 1. General SLA review process (Note Kim Davies is not available due to travel) The current list of SLAs can be found here<https://pti.icann.org/iana-naming-function-services-service-level-agreements> The 2025 change procedure is published here<https://www.icann.org/en/system/files/files/iana-naming-sla-amendment-proce…> CSC leadership and IANA to propose process to conduct the review. As discussed in Dublin, ICANN84, the actual review is expected to start in January 2026. Per discussion in December 2025 core part of procedure is section 2.2 Each change request needs to meet a series of criteria: 1. for the benefit to the customer as determined by PTI and CSC. Could also mean for the benefit of PTI, for example a simplification of process 2. Feasibility as determined by PTI. Cost and Time 3. Trade-off: benefit and costs, short and longer term and impact. Keep section 2.2 SLA change document in mind. Core principles Working method. Build spreadsheet to analyse SLA based on criteria section 2.2 * Number of SLA * Identifying kind of change: * What is benefit, cost and impact * All parties need to agree, if not no change Unclear who is going to represent ICANN in process. Action 03-99- 26 – PTI/ ICANN to identify representative ICANN (if anyone) in the SLA review process. Concept what change could mean * Eliminating * Changing thresholds * Combining * Adding new one All need to realize that all SLA change will take time and money to implement It takes every SLA to operate, use discussion on SLA of the meeting to look at it in the context of this month Action item 04-99-26: Chair CSC to Build spreadsheet to capture assessment process Action item 05-99 -26: PTI to identify interesting cases to familiarize PTI and CSC membership on how to assess SLA. When suggesting SLA change, keep implementation in mind. Note SLAs are based on percentages. Useful to understand how many actions are captured Looking at SLA report, note the count Action item 06-99-26: staff to schedule continuation discussion SLA agenda February meeting 1. Next Meetings * Meeting 100 – 11 February 2026 | 02.00 – 03.00 UTC (note is deferred one week to 18 February) * Meeting 101 – 7- 12 March 2026 (ICANN85, Mumbai) Scheduled Monday Block 1 Explanation why reschedule. No concerns. Action item staff : circulate placeholder calendar * Meeting 102 – 15 April 2026 | 10.00 – 11.00UTC * Meeting 103 – 20 May 2026 | 18.00 – 19.00 UTC * Meeting 104 – 24 June 2026 | 02.00 – 03.00 UTC (no meeting during iCANN86, Policy Forum | 8-11 June 2026) 1. AOB No AOB 1. Adjourn

1 0

CSC Meeting #100 | 18 February 2026 at 02:00 UTC
by ccNSO Calendar Feb. 7, 2026

Feb. 7, 2026

***Please note this meeting has been changed to 18TH of February*** Dear all, The next CSC meeting is scheduled for Wednesday, 11 February 2026 at 02:00 UTC Join Zoom Meeting https://icann.zoom.us/j/98949851121?pwd=ozbxT2VbDG41a0ro8ZIOgjwkJzaaKx.1 Meeting ID: 989 4985 1121 Passcode: 9p.ma0=hyZ Thank you!

2 1

Notice of CSC Meeting Postponement
by Claudia Ruiz Feb. 4, 2026

Feb. 4, 2026

Dear all, I am writing to inform you all that our schedule meeting will be postponed by one week due to an unforeseen scheduling matter. The meeting will now take place on The changes have been made to the calendar invite, please accept the changes. I have also attached the ICAL for the meeting with the new date. The agenda will be circulated a few days prior to the meeting. Thank you all for your understanding. Kind regards, Claudia

1 0

CSC Meeting #100 | 18 February 2026 at 02:00 UTC
by ccNSO Calendar Feb. 4, 2026

Feb. 4, 2026

***Please note this meeting has been changed to 18TH of February*** Dear all, The next CSC meeting is scheduled for Wednesday, 11 February 2026 at 02:00 UTC Join Zoom Meeting https://icann.zoom.us/j/98949851121?pwd=ozbxT2VbDG41a0ro8ZIOgjwkJzaaKx.1 Meeting ID: 989 4985 1121 Passcode: 9p.ma0=hyZ Thank you!

1 0

CSC Meeting #100 | 11 February 2026 at 02:00 UTC
by ccNSO Calendar Feb. 3, 2026

Feb. 3, 2026

Dear all, The next CSC meeting is scheduled for Wednesday, 11 February 2026 at 02:00 UTC Join Zoom Meeting https://icann.zoom.us/j/98949851121?pwd=ozbxT2VbDG41a0ro8ZIOgjwkJzaaKx.1 Meeting ID: 989 4985 1121 Passcode: 9p.ma0=hyZ Thank you!

1 0

PLACEHOLDER - CSC #101 | Mumbai ICANN85 | 09 March 2026 at 03:30 UTC | 09:00 Local Time
by ccNSO Calendar Jan. 23, 2026

Jan. 23, 2026

DETAILS TO FOLLOW…

1 0

PLACEHOLDER - CSC #101 | Mumbai ICANN85 | 09 March 2026 at 03:30 UTC | 09:00 Local Time
by ccNSO Calendar Jan. 23, 2026

Jan. 23, 2026

DETAILS TO FOLLOW…

1 0