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
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@icann.org> namens Bart Boswinkel via CSC-EffectivenessRT <csc-effectivenessrt@icann.org> Beantwoorden - Aan: Bart Boswinkel <bart.boswinkel@icann.org> Datum: dinsdag 1 februari 2022 om 15:13 Aan: "csc-effectivenessrt@icann.org" <csc-effectivenessrt@icann.org>, Sean Copeland <sean.a.copeland@icloud.com> CC: NIC VI <sean.copeland@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
All unfortunately due to a personal commitment I won’t be able to join todays call however I can update you on my comments on item 5: 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.
WE believe a review of the SLAs is in the CSC mandate looking at the IANA Naming Function contract and its amendment in 2019. https://www.icann.org/en/system/files/files/iana-naming-function-sla-amendment-process-28mar19-en.pdf<https://www.icann.org/en/system/files/files/iana-naming-function-sla-amendment-process-28mar19-en.pdf)> We also note that the IFRT is also mandated to conduct a review and suggest changes but we don’t see why both can’t happen. I will discuss this with Liman and if he agrees we will suggest at the next CSC meeting we (the CSC) schedule a review of the SLAs. Apologies again for missing the meeting but I will listen to the recording afterwards to see what you thought about the above. Brett -- Brett Carr Manager DNS Engineering Nominet UK From: CSC-EffectivenessRT <csc-effectivenessrt-bounces@icann.org> on behalf of Bart Boswinkel via CSC-EffectivenessRT <csc-effectivenessrt@icann.org> Date: Tuesday, 1 February 2022 at 14:13 To: csc-effectivenessrt@icann.org <csc-effectivenessrt@icann.org>, Sean Copeland <sean.a.copeland@icloud.com> Cc: NIC VI <sean.copeland@nic.vi> Subject: [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 2. Administrative matters a. Appointment of Sean Copeland to replace Jens Petur b. Question re Charter change process, (see notes 18 January, section 4.b) 3. Review of Metric document ( Maarten) 4. 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.
5. 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.
6. Next meetings a. RT Meetins: i. 15 February 19.00 UTC ii. 1 March 19.00 UTC b. Meeting with PTI Board i. Date see Doodle c. Second meeting with CSC 7. AOB 8. Closure Notes 18 January 2022 1. Welcome & Roll Call/Approval of topics No comments Members present: Donna & Maarten 2. 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) 3. 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. 4. Scheduling next steps/work items: a. 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. b. 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 o 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. o Public consultation: Include a public session? Limit to Public consultation of Initial Report? See above item a. 5. 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. 6. AOB 7. 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
participants (3)
-
Bart Boswinkel -
Brett Carr -
Maarten Simon