February 2022 - CSC-EffectivenessRT

Notes joint meeting CSC and Review team (14 February 2022)
by Bart Boswinkel Feb. 25, 2022

Feb. 25, 2022

Dear all, Please find included the notes from your meeting with the CSC (16 February 2022), Kind regards, Bart 1. Welcome From RT: Donna Austin, Jonathan Robinson (RySG), Sean Copeland (ccNSO), apology Maarten Simon (ccNSO Discussion helpful for the group General observation: CSC is in good shape as anticipated 2. Discussion CSC-Effectiveness RT Brett spokesperson CSC. Topics: * Chair of the CSC: Should Chair be a member of the CSC or is it just “preferred”? Does language in Charter need to be updated ? Background: Developed charter, preference member of Recognize. Lars- Liman is liaison Brett: limited number of members may at times require flexibility. Discussion that members need to be present. Issue that because limited number of member both be a new member and churn does not leave the CSC in comfortable place. Fall back to liaison. Good flexibility ensure to have same kind of approach. Liman concurs with Brett, Observation Jonathan: current experience, useful language: language feels about right. Formulation quite to the point. No further comment * Frequency of meetings In developing the charter, and importance of the role, especially taking into. Account possibility of escalation, monthly meeting was needed, welcomed, foundation document Most of business in 20-30 minutes: is frequency needed? Also in relation with scope. If CSC would like to take on larger role? Brett: on monthly basis limited time If that would be the case. If report does not need any discussion. If scope needs to be expended, more work to be done No need to become more agile, about fallback. Liman: current balance is good in light of scope.There was time low work load. Keeping current cadence Meeting rotate through time zones. Number of meetings: if fewer meetings with same issue. Monthly update that does not require discussion. If not meeting in zoom. People need to confirm Absolute minimum to maintain relations at least every two-months Is work affected by pandemic? Need for cohesion, some of the members never met in person. Pandemic has not affected direct work: it naturally affects relationship, not just CSC but all groups. Attending from Sydney is a long haul. Meet during ICANN meeting good thing do, does not preclude participating in zoom. * Will the CSC be able to keep attracting qualified members and liaisons? Need to line up people. Thankful everyone has expressed willingness to continue. Have all appointing organizations assigned people to the CSC? How interesting is the work: Is there a need to market what the CSC is doing and its value Anybody? Responses: Not all organizations have assigned people. SSAC declined structurally after first term. Lesser priority cannot find commitment. Low level of nominations Observation Sean: look at how I came to be here, I found the work interesting, but I found the description of qualifications were excluding, so I would not have normally applied even though I had interest. * Scope of CSC activities Result of initial conversation with CSC. From RT perspective: During the Stewardship transition process there was a point in creation of CSC it was discussed whether the CSC should take on broader role. In the end the CSC was tasked with a limited role: monitor PTI performance. What would happen if role of CSC would be broadened? Brett: suggest to this question in context of next question. * Regular Review of adequacy of SLAs and related thresholds? Liman: Compared of the work of the CSC with maintenance program for car. Certification gap IDN. Focus should remain limited. Issues emerge over long-term. Review may help for long-term and to be approved Nuanced distinction: existing accountability mechanism. What value would broader scope CSC add in wider context? Example: CSC identified gap in IDN related process and discussion around monitoring DNSsec key roll-over (discussed by the CSC in 2019). In latter case already extensive accountability mechanism in place, additional role add hardly any value, if at all. Appropriate to check accountability. Structure may need to be reviewed. Brett: defer until future. The CSC is not seeking additional work i.e looking for things to do. However a regular review (whatever regular means) might be appropriate. Kim Davies: Adequacy of current SLAs. CSC is well placed to be familiar with current are constructed set. However, CSC is small, broader input needed given number of direct customers. Note: At the same time there is a process in place for consultation related to Amendment 1 IANA Naming Function Contract. 3. Next Steps RT * Conversation with PTI Board * Draft report * Webinar to speak customers and alert to report 4. Closure

1 0

CSC Effectiveness Review Team meeting with the PTI Board
by Claudia Ruiz Feb. 17, 2022

Feb. 17, 2022

Topic: CSC Effectiveness Review Team meeting with the PTI Board Time: Wednesday, 02 March 2022 at 21:00 UTC Join Zoom Meeting: https://icann.zoom.us/j/96293911941?pwd=emxPZklwOE9aY3JBU0krSEpsVCt1UT09 For other times: https://tinyurl.com/2p9bxrn5 CSC Effectiveness Review Team Wiki space: https://community.icann.org/x/OwGlCg Agenda (To be updated): https://community.icann.org/x/jw8iCw Meeting ID: 962 9391 1941 Passcode: CSC&PTI#01 Dial in Passcode: 4067613498 Find your local number: https://icann.zoom.us/u/aeG0UQCma9

1 0

CSC Meeting 58 | 16 February at 18:00 UTC
by Claudia Ruiz Feb. 16, 2022

Feb. 16, 2022

***STARTING IN 10 MINS*** Topic: CSC March Meeting 58 Time: 16 February 2022 at 18:00 UTC Agenda: https://community.icann.org/x/CAciCw For other times: https://tinyurl.com/2p8bkche Join Zoom Meeting https://icann.zoom.us/j/98047078693?pwd=azlPL2d2WTd6SW9JVDRkV3MwSG9OQT09 Meeting ID: 980 4707 8693 Passcode: #CSCmtg58! Dial in Passcode: 8787425513 Find your local number: https://icann.zoom.us/u/ac3fd9aen2 Thank you. Kind regards, Claudia Ruiz

1 0

CSC Effectiveness Review Team meeting witjh. CSC 16 February 2022 18.00 UTC
by Bart Boswinkel Feb. 16, 2022

Feb. 16, 2022

Dear all, Please find included the updated Metrics overview. Action items from yesterday’s meeting: * Next meeting: week 28 February – 3 March, to be scheduled after the meeting with PTI Board * At next meeting determine outcome of item 1- 15, start discussion on possible areas for improvement/recommendations * Discuss outcome new metrics/questions (item 16-21) at following meeting with CSC on 16 February 2022 Kind regards, Bart

1 0

Updated Doodle: CSC Effectiveness Review Team meeting with the PTI Board - Week of Feb 28
by Claudia Ruiz Feb. 15, 2022

Feb. 15, 2022

Dear all, The previous doodle did not work for all, please complete the updated doodle poll below as soon as possible to schedule our call with the PTI Board for the week of the 28th of February. Doodle: https://doodle.com/poll/d5t5stg8ndsrhas4?utm_source=poll&utm_medium=link Thank you. Kind regards, Claudia Ruiz

1 0

Re: [CSC-EffectivenessRT] CSC Effectiveness Review Team Call 15 February 2022
by Bart Boswinkel Feb. 15, 2022

Feb. 15, 2022

Dear all, Please find included the 0202 -2022 version of the metrics doc. Also included for your reference the agenda of the CSC meeting tomorrow 16 February Proposed agenda for today: 1. Welcome and roll call, agenda bashing 2. Assess the 2nd Review Outcome -The metrics are * Achieved * Not Achieved * Not Applicable (N/A) 3. Prepare for meeting with CSC on 16 February: topics the new Metrics 4. Meeting with PTI Board: scheduled date & topics for discussion 5. Identify preliminary areas improvement: how do does RT want to approach this? 6. Next meetings 7. AOB 8. Closure From: claudia.ruiz(a)icann.org When: 20:00 - 21:00 15 February 2022 Subject: CSC Effectiveness Review Team Call Location: 19:00 UTC | Zoom: https://icann.zoom.us/j/91619166269?pwd=QVRMWnlidFBMeFBtOXN6eEhzV3hjZz09 Topic: CSC Effectiveness Review Team Call Time: Tuesday, 15 February 2022 at 19:00 UTC CSC Effectiveness Review Team Wiki space: https://community.icann.org/x/OwGlCg Agenda (To be updated): https://community.icann.org/x/zQciCw Join Zoom Meeting: https://icann.zoom.us/j/91619166269?pwd=QVRMWnlidFBMeFBtOXN6eEhzV3hjZz09 Meeting ID: 916 1916 6269 Passcode: CSC-ERT#01 Dial in Passcode: 6746343461 Find your local number: https://icann.zoom.us/u/ac0gLFMNvp

1 0

Doodle: CSC meeting with PTI Board - Week of Feb 21
by Claudia Ruiz Feb. 11, 2022

Feb. 11, 2022

Dear all, Please complete the Doodle poll below as soon as possible. Thank you. Kind regards, Claudia Ruiz From: Aaron Jimenez <aaron.jimenez(a)icann.org> Date: Friday, February 11, 2022 at 10:00 AM To: "pti-board(a)icann.org" <pti-board(a)icann.org> Cc: "Board-Ops-Team(a)icann.org" <board-ops-team(a)icann.org>, Claudia Ruiz <claudia.ruiz(a)icann.org> Subject: Doodle: CSC meeting with PTI Board - Week of Feb 21 Hello PTI Board, Please complete the following Doodle for the CSC meeting with PTI Board the week of February 21, 2022. Doodle: https://doodle.com/poll/p76cevus6yuaaubg?utm_source=poll&utm_medium=link Best, Aaron Jimenez 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 Email: aaron.jimenez(a)icann.org<mailto:aaron.jimenez@icann.org> Mobile: 1-310-913-4129

1 0

CSC Effectiveness Review Team Call
by Claudia Ruiz Feb. 10, 2022

Feb. 10, 2022

Topic: CSC Effectiveness Review Team Call Time: Tuesday, 15 February 2022 at 19:00 UTC CSC Effectiveness Review Team Wiki space: https://community.icann.org/x/OwGlCg Agenda (To be updated): https://community.icann.org/x/zQciCw Join Zoom Meeting: https://icann.zoom.us/j/91619166269?pwd=QVRMWnlidFBMeFBtOXN6eEhzV3hjZz09 Meeting ID: 916 1916 6269 Passcode: CSC-ERT#01 Dial in Passcode: 6746343461 Find your local number: https://icann.zoom.us/u/ac0gLFMNvp

1 0

CSC January Meeting 58 | 16 February at 18:00 UTC
by Claudia Ruiz Feb. 3, 2022

Feb. 3, 2022

Topic: CSC March Meeting 58 Time: 16 February 2022 at 18:00 UTC Agenda: https://community.icann.org/x/CAciCw For other times: https://tinyurl.com/2p8bkche Join Zoom Meeting https://icann.zoom.us/j/98047078693?pwd=azlPL2d2WTd6SW9JVDRkV3MwSG9OQT09 Meeting ID: 980 4707 8693 Passcode: #CSCmtg58! Dial in Passcode: 8787425513 Find your local number: https://icann.zoom.us/u/ac3fd9aen2 Thank you. Kind regards, Claudia Ruiz

1 0

CSC Effectiveness RT meeting 1 February 2022
by Bart Boswinkel Feb. 2, 2022

Feb. 2, 2022

Dear all, Please find included the updated overview of the metrics table. For ease of reading I have deleted two columns (findings and outcome first Review). In addition the overview includes major points from yesterday’s discussion @ Jonathan: 1. Sean Copeland is the newly ccNSO appointed member replacing Jens Petur. 2. Could you be so kind to share the results of your second pass of the document Maarten shared? I’ll include then include them in the updated doc ( included) @ All: May I suggest that you start completing the Outcome column before the next scheduled call (15 February 2022 19.00 UTC) May I also suggest that the next meeting will be used to prepare for the meeting with the CSC the next day (16 February 2022, 18.00-19.00 UTC) Kind regards, Bart From: Maarten Simon <maarten.simon(a)sidn.nl> Date: Tuesday, 1 February 2022 at 15:23 To: Bart Boswinkel <bart.boswinkel(a)icann.org>, "csc-effectivenessrt(a)icann.org" <csc-effectivenessrt(a)icann.org>, Sean Copeland <sean.a.copeland(a)icloud.com> Cc: NIC VI <sean.copeland(a)nic.vi> Subject: [Ext] Re: [CSC-EffectivenessRT] Draft agenda CSC Effectiveness RT meeting 1 February 2022 Hi all, Please find my findings of the review of the Metric document attached. I have added a column to the document in order to give where necessary a comment per item. Bart has already reviewed my findings and added some comments and included a suggestion for a recommendation. We will discuss the findings under agenda item 3. Best, Maarten Van: CSC-EffectivenessRT <csc-effectivenessrt-bounces(a)icann.org> namens Bart Boswinkel via CSC-EffectivenessRT <csc-effectivenessrt(a)icann.org> Beantwoorden - Aan: Bart Boswinkel <bart.boswinkel(a)icann.org> Datum: dinsdag 1 februari 2022 om 15:13 Aan: "csc-effectivenessrt(a)icann.org" <csc-effectivenessrt(a)icann.org>, Sean Copeland <sean.a.copeland(a)icloud.com> CC: NIC VI <sean.copeland(a)nic.vi> Onderwerp: [CSC-EffectivenessRT] Draft agenda CSC Effectiveness RT meeting 1 February 2022 Dear all, As you will have noted Jens Petur has stepped down from the RT. Last Thursday the ccNSO Council discussed the matter and Sean Copeland (.vi) kindly agreed to step in and replace Jens Petur at short notice to ensure continuity. Included are the notes from previous meeting ( circulated 19 January 2022), For later today please find included the draft agenda. 1. Welcome, roll call and agenda bashing 1. Administrative matters * Appointment of Sean Copeland to replace Jens Petur * Question re Charter change process, (see notes 18 January, section 4.b) 1. Review of Metric document ( Maarten) 1. Assessment of findings to date From 18 January 2022 notes: Outcome -The metric is: · Achieved · Not Achieved · Not Applicable (N/A) After Maarten has provided his findings (25 January) RT membership is expected to complete the 2nd review Outcome column individually in preparation of the upcoming meeting on 1 February, using categories: Achieved, Not Achieved, Not Applicable. Meeting will be used to discuss preliminary outcomes and check where divergence and agreement. 1. New item: Full SLAs review (Brett) From Brett: In the CSC’s most recent meeting (19th Jan) one of the liaisons raised the following question: “At the last meeting there was a pressntation on IANA Naming Function SLAs & Threshold. As part of a recent discussion it was raised that there might expectation that the SLAs would be reviewed periodically and and asked whether they have been reviewed. Question for discussion: should the CSC and PTI review the set of SLAs & Thresholds.” The CSC thought that this might be something the review team might want to consider and report back on. 1. Next meetings * RT Meetins: i. 15 February 19.00 UTC ii. 1 March 19.00 UTC * Meeting with PTI Board i. Date see Doodle * Second meeting with CSC 1. AOB 1. Closure Notes 18 January 2022 1. Welcome & Roll Call/Approval of topics No comments Members present: Donna & Maarten 1. Report Maarten on whether the provided information is accurate (see below notes from last meeting). Maarten would check the links etc included in the overview (see document, included again for reference). Action Maarten: complete review by 25 January 2022. Circulate findings to RT email list. If any issues, to be included in overview (see also item 4 b) 1. Preparing meeting with the PTI Board and PTI staff (if necessary) Claudia is in process to schedule a meeting with the PTI Board. Claudia to circulate Doodle: meeting with PTI Board considered necessary. 1. Scheduling next steps/work items: * Meeting with others groups? Discussion on need to meet with groups other then PTI Board and CSC. Agreed that not necessary at this stage: PTI staff shared their views on earlier meeting (Kim Davies). In addition Amy shared her view: CSC is very on top of issues, if any. When necessary, CSC will ask and try to understand the underlying issue for missing a SLA or threshold: latest example manual transactions. Scrutiny is not just to uunderstand whether there is a systemic issue as is mandate of the CSC, but also to understand whether need to review and adjust the SLA ( example the frist SLA that was changed after procedures for change became effective) CSC has build a strong relation with PTI, respectful, and each aware of their own responsibilities, CSC is very aware of it is acting on behalf of the direct customers. Meeting with direct customers to be organized through a webinar that will introduce the initial Report for Public Consultation: webinar anticipated by the end of March, after RT has agreed on Initial Report. Feed-back and response from attendees on webinar to be used as feed-back Report. This is also proposed approach for item b third bullet point below. * Scheduling Initial Assessment of metrics i.e Outcome Outcome -The metric is: · Achieved · Not Achieved · Not Applicable (N/A) After Maarten has provided his findings (25 January) RT membership is expected to complete the 2nd review Outcome column individually in preparation of the upcoming meeting on 1 February, using categories: Achieved, Not Achieved, Not Applicable. Meeting will be used to discuss preliminary outcomes and check where divergence and agreement. Outcome will be bases for further queries, and conversations * Reporting: how do you want to organize the reporting? Once assessment has been completed, group will start drafting. Use reports first review as starting point (template) Question: May RT suggest change of charter, and ho would this work? From the CSC charter: Review The Charter may be reviewed at the request of the CSC, ccNSO Council, RySG or GNSO Council or in connection with an IANA Function Review. The review will be conducted by a committee of representatives from the ccNSO and the RySG in accordance with a method determined by the ccNSO Council and RySG. Each review is to include the opportunity for input from other ICANN stakeholders, via a Public Comment process. Any recommended changes are to be ratified by the ccNSO and the GNSO Councils. The effectiveness of the CSC will initially 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. From the ICANN Bylaws ( section 17.3) Thereafter (BB: CSC Charter review), the CSC Charter shall be reviewed by such committee of representatives from the ccNSO and the Registries Stakeholder Group selected by such organizations 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. (d) Amendments to the CSC Charter shall not be effective unless ratified by the vote of a simple majority of each of the ccNSO and GNSO Councils pursuant to each such organizations' procedures. Prior to any action by the ccNSO and GNSO, any recommended changes to the CSC Charter shall be subject to a public comment period that complies with the designated practice for public comment periods within ICANN. Notwithstanding the foregoing, to the extent any provision of an amendment to the CSC Charter conflicts with the terms of the Bylaws, the terms of the Bylaws shall control. For discussion on potential CSC Charter change (if recommended): Option 1. The charter may be reviewed at the request of the CSC, ccNSO or GNSO Council, or RySG. This review will then be conducted by reps. from ccNSO and RySG. The CSC RT could therefore recommend a review to the ccNSO and GNSO Council, who after adoption of the recommendation wil have to set up a review. In making the recommendations the suggestions for amendments of the Charter could be included of course. However that process will startafter the RT has concluded its tasks. Options 2: Alternatively, the CSC itself or the Review Team could request/suggest the Councils a review may be appropriate. Such an issue is out of scope of the RT mandate and hence the RT may want to inform the respective Councils. The Council could mandate the RT to do conduct such a (limited) review. the ToR for the RT will need to be updated/amendment added. * Public consultation: Include a public session? Limit to Public consultation of Initial Report? See above item a. 1. Additional points for questions/discussion with CSC, if any Tomorrow 19 January there is a CSC meeting at 10.00 UTC. Their agenda includes the item “Progress Review”. This could be an opportunity to raise additional questions/discussion. In February 2022 the CSC will meet again on the 16th from 18.00 to 19.00 UTC. Observation from today’s CSC meeting: CSC was informed about planning. 1. AOB 1. Next meeting(s) Proposed dates and time Review Team meetings 1 February 2022, 19.00 UTC 15 February 2022, 19.00 UTC 1 March 2022, 19.00 UTC Additional meetings ( PTI Board, others) TBD’ed

1 0