August 2024 - Ccnso-council

Heads-up 360 Review Councillors
by Bart Boswinkel Aug. 22, 2024

Aug. 22, 2024

Dear Councillors As you recall you adopted the update of the Councillor 360 review procedure at our meeting on 21 December 2023. The updated version has been posted and is available at:https://ccnso.icann.org/sites/default/files/field-attached/ccnso-council… [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/fiel…> You also agreed to the following scheme for the frequency of the reviews: https://docs.google.com/spreadsheets/d/1gUaUDBeROr7nNphJJbGaxvSqI1WvvJ0emID… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1gUaUDBeR…>. According to the review procedure all Councillors are expected to receive two 360 feedback reports during their term. The first one will be received 1 year after they take their seat on the Council. The second round of feedback should be concluded 6 months before the end of the term. The following Councillors who took their seat approximately one year ago will be subject to the review: Biyi, Jordan, Nick, Demi, and Pablo. Recently -17 July - you agreed on-line with the timeline for the 360 reviThis Review has been scheduled for February 2024 (duration 3 weeks), and feed-back to the individual Councillors subject to the review will be provided during or around ICANN79 (see proposed timeline below). The evaluator for this round is Alejandra. As Alejandra will be subject to the review herself, the proposed Designee(s) for her feed-back are Biyi and Jordan. The proposed Feedback Process Manager is Bart Boswinkel. Timeline * Start of Survey: Thursday, 25 July 2024 – Links to Surveymonkey Surveys will be sent to all Councillors who are not subject to survey and to staff. Each of you will receive a links in one email. * Closure of Survey: Thursday 22 February 2024 * Compilation of individual Reports: 23 - 26 August * Share results with individual Councillors and Evaluator: 27 August 2024 * Conversations Chair or Designee and individual Councillor: 1 – 28 September 2024 Kind regards, Bart

1 1

Background material Council meeting 208: written updates
by Joke Braeken Aug. 21, 2024

Aug. 21, 2024

Hello All. Please find here the draft written updates for the upcoming Council meeting https://docs.google.com/document/d/1po8Zrb34uu3pGQUUBAhdYFdqcKVtaks9dN57xnU… if you see your name in the list below, could you please review the proposed draft written update by the end of this week? Many thanks. = = = Updates: ccNSO Working Groups or Committees = = = ccPDP3-Review Mechanism: Stephen Deerhake ccPDP4-IDN: Ai-Chin Lu, Jiankang Yao DASC: Nick Wenban-Smith GRC: Sean Copeland IGLC: TBC MPC: Alejandra Reynoso OMC: TBC SOPC: Biyi Oladipo Registrant Capacity ad hoc group: Biyi Oladipo Tech WG: Stephen Deerhake TLD-OPS SC: Ali Hadji Mmadi UASC: Ai-Chin Lu, Jiankang Yao Triage Committee: Nick Wenban-Smith = = = Updates: other = = = ECA: Alejandra Reynoso CCG WS2 Implementation: David McAuley CIP-CCG: Sean Copeland CSC: Bart Boswinkel IFR2: Peter Koch Community Representatives Group to nominate members to the IRP Standing Panel: David McAuley Planning Prioritization Process: Chris Disspain RZERC: Peter Koch RSS GWG: Peter Koch Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> From: ccnso-council <ccnso-council(a)icann.org> Reply to: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Tuesday, 20 August 2024 at 16:58 To: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] Agenda and draft Resolution Meeting 208 Dera all, Please find included the agenda and draft resolution for the upcoming meeting. The draft resolution is on item 13 Also included is the letter to ICANN Board on the Deferral 3rd CSC effectiveness review, which you reviewed earlier. This letter was also reviewed by GNSO and no comments were made. On item 16 ( Caucus questions): Hopefully the team drafting the responses will be done today, in which I’ll circulate the draft responses to you tomorrow. Kind regards, Bart Agenda and draft resolution ccNSO Council Meeting 208 22 August 2024, 18.00 UTC 1. Welcome and roll call * Is meeting Quorate? 2. Update Statement of Interest For information [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/about/ccnso-internal-…>Guideline [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/about/ccnso-internal-…> & [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLSfRpehi…>Template [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/forms/d/e/1FAIpQLSfRpehi…> Administrative matters 3. Relevant Correspondence [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/about/statements.htm_…> * Letter from ICANN re WSIS+20 (Item 17) * Letter to ICANN and response from ICANN re “How we meet” (item 18) 4. Minutes & Action Items * Minutes Meeting 207: Circulated 29 July 2024 * Action items * Action item 207-01: Peter Koch will provide a written report to Council regarding RSS GWG developments. If actions are needed, the Secretariat is requested to reflect this in the agenda for the next Council meeting. (Pending) * Action item 207-02: The secretariat is requested to ensure the RSS GWG updates are included in the monthly written updates. (Completed) * Action item 207-03: Jordan Carter will prepare a draft plenary session proposal for ICANN 81 on the WSIS+20 strategy. (Completed) * Action item 207-04: Alejandra Reynoso will inform the ICANN planning team that a plenary session proposal for ICANN 81 on the WSIS+20 strategy is forthcoming. (Completed) * Action item 207-05: The Secretariat shall inform all volunteers of the outcome of the Council's decision to appoint the volunteers and the initial Chair of the PGA WG and shall publish the decision as soon as possible. (Completed) * Action item 207-06: The Secretariat shall send a draft resolution for online decision to Council, regarding the appointment of Chris Disspain (Council), Nick Wenban-Smith (.uk) as members of the ccNSO PGA WG, and Peter Van Roste (CENTR) as Liaison. (Completed) * Action item 207-07: The Secretariat shall inform all volunteers about the outcome of the Council's decision to appoint the Tech WG Vice Chairs and shall publish the decision as soon as possible. (Completed) * Action item 207-08: The Secretariat shall publish the Council decision to adopt the Council election timeline and the appointment of the Election Process Manager as soon as possible. (Completed) * Action item 207-09: Secretariat and Councillors to draft letter on deferral 3rd CSC Effectiveness Review and to revisit decision in 1 year. To be shared with the Council in 2 weeks, in time for the next Council meeting. (Completed) * Action Item 207-10: The Travel Funding Committee, with assistance from the secretariat, should propose updates to the ccNSO travel funding process, using the ccNSO Continuous Improvement Framework. The committee should provide an update on progress by the next Council meeting, and with aspiration to conclude the update by the next round of travel funding requests (for ICANN82 or ICANN83). (Completed, See item 13 on the agenda) * Action Item 207-11: A Council drafting team will prepare a draft response to the request for input on the “how we meet” paper. The proposed draft will be circulated by 26 July 2024 to Council for review and adoption. (Completed) * Action Item 207-12: Sean Copeland is requested to circulate background materials and questions to Council. Councillors are requested to respond in a timely manner. (Completed) * Action Item 207-13: Alejandra Reynoso will circulate the initial draft of the ICANN81 ccNSO block schedule to the Council mailing list. (Completed) 5. Intermeeting Decisions (since meeting 207, July 2024) * 207-A: Appointment members PGA WG & IGLC * 207-B: Support letter to ICANN Interim CEO and President re: “How we meet” * 207-C: Approval membership National Communication Authority (NCA) of South Sudan (.ss) as member 178 of the ccNSO * 207-D: Approval full slate CSC membership (by Council selection committee) 6. Intermeeting decisions Triage Committee The Triage Committee has made no decisions since the last meeting. Updates 7. Update ECA, IFR2 & CSC (written updates<https://community.icann.org/x/4QciCw>) Note: Proposed change to Article 4, which is Fundamental Bylaw. Requires ccNSO approval. Tentatively scheduled community forum@iCANN81 8. Update WGs (written updates) * ccPDP3-Review Mechanism - Dormant * ccPDP4-IDN - Dormant * DASC * GRC * IGLC * MPC * OMC - To be established * PGA WG - First meeting is scheduled for 27 August 2024 * SOPC * Tech WG - Had no meeting since Council meeting 207 * TLD-OPS SC - Had no meeting since Council meeting 207 * UAC * Triage Committee - Had no meeting since Council meeting 207 * CCG WS2 Implementation- Had no meeting since Council meeting 207 * IRP Panel Selection - Had no meeting since Council meeting 207 * Planning Prioritization Process group - Had no meeting since Council meeting 207 * RZERC * RSS GWG * CIP-CCG 9. Update liaisons (written updates) * Update ALAC Liaison * Update GNSO Liaison * Update UASG Liaison 10. Update ccNSO Website redesign Informational 11. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat * ICANN81 Planning call (Block schedule, Plenary topics), see item 17 & 19 c * SO/AC Roundtable meeting, see item 17 * Meeting on “How we meet”, see item 18 Administrative Matters & Decisions 12. Appointment Members to Committees and Working Groups, if any 13. Deferral 3rd CSC Effectiveness Review Draft Resolution Background According to the ICANN Bylaws and CSC Charter, the 3rd CSC Effectiveness Review is expected to start by 1 October 2024, and the ccNSO and GNSO Councils have to determine the review method. The Council notes that the 2nd CSC Effectiveness Review was launched in August 2021 by adoption of the Terms of Reference and appointment of the members of the Review Team. The Final Report was adopted by both Councils on 20 April 2023. In May 2023, the ccNSO and GNSO Councils jointly informed the ICANN Board of Directors of the outcome of the review and requested initiation of the process of Bylaw changes to adjust the frequency of Bylaw changes as suggested. The Review Team recommended, among other recommendations, to reduce the frequency to once every five years after the previous review was concluded, or at the request of the PTI Board, the CSC, the ccNSO or RySG if any of them deem a CSC effectiveness review to be necessary. Current status of the implementation of this recommendation is unknown. To inform the ICANN Board of Directors the ccNSO and GNSO Council drafted a joint letter. Decision Assuming the GNSO council will decide in a similar manner, the ccNSO Council decides to defer the 3rd CSC Effectiveness Review, and to revisit this decision in August 2025. The Council requests its chair jointly with the chair of the GNSO Council to inform the chair of the ICANN Board of Directors, by sending the letter that was drafted for that purpose, after this resolution becomes effective. The secretariat is requested to publish the resolution as soon as possible, and this resolution becomes effective seven (7) days after its publication. 14. Update & introduction changes to ccNSO Travel Support Guideline 15. Generic “letter” to invite ccTLDs to join the ccNSO? Substantive Matters & Decisions 16. Update and next steps re requests for clarification and confirmation Board Caucus ccPDP review mechanism 1. Review and support response by Council 2. Topics to include in Cover Note 17. WSIS+20 exchange of letters: what’s next? 18. Follow-up Discussion on ICANN’s “How we meet” initiative 19. Tentative ccNSO Block Schedule ICANN81 * Council (prep) meetings/workshop * Joint meetings: Meeting with the Board and GAC Tentative topics GAC meeting: i. introducing the Policy Gap Analysis ii. Supporting the MSM in context of WSIS+20 iii. Relevant takeaways 2nd DNS Abuse survey 1. Plenary session: 2. Working groups/Committees meetings 3. Tech Day 4. Members sessions 20. AOB 21. Next Council Meetings * 19 September 2024 | 12:00 UTC, Meeting 209 * 17 October 2024 | 21:00 UTC, Meeting 210 * 14 November 2024 | time TBD, Meeting 211 (at ICANN81) * 12 December 2024 | 12:00 UTC, Meeting 212 * 16 January 2025 | 18:00 UTC, Meeting 213 * 13 February 2025 | 12:00 UTC, Meeting 214 22. Adjourn

1 0

Appointment Tsholofelo Mokone (.za) to IGLC
by Joke Braeken Aug. 21, 2024

Aug. 21, 2024

Dear Councilors, Please find below a draft resolution, presented to you for an online decision. Kindly provide me with your input by the end of Wednesday, 21 August 2024, 23:59 UTC, in case you do not agree with the proposed resolution. In case there are no comments, the decision is carried. Appointment member For decision formal appointment additional member to the Internet Governance Liaison Committee (IGLC) Draft Resolution Tsholofelo Mokone (.za) expressed an interest to be member of the IGLC. The ccNSO Council approves Tsholofelo’s membership to the IGLC. The secretariat is requested to take all necessary steps to include her as member of the IGLC, including informing the respective committee Chair and Vice Chair. This decision becomes effective upon publication. Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

6 5

Draft responses Board Caucus question re ccPDP RM ( item 17 a meeting 208)
by Bart Boswinkel Aug. 20, 2024

Aug. 20, 2024

Dear all, Please find included the (tentative) final draft response to questions from the Board caucus RM. Today the members of the small group attending the call supported the responses. However, the document is tentative to allow the group to go over the final version for a final check, and to allow those of group who were not able to attend this last session to review the proposed responses. On the call the document will be introduced by the co-chairs of the small group (either Stephen or Jordan), Kind regards, Bart

1 0

Agenda and draft Resolution Meeting 208
by Bart Boswinkel Aug. 20, 2024

Aug. 20, 2024

Dera all, Please find included the agenda and draft resolution for the upcoming meeting. The draft resolution is on item 13 Also included is the letter to ICANN Board on the Deferral 3rd CSC effectiveness review, which you reviewed earlier. This letter was also reviewed by GNSO and no comments were made. On item 16 ( Caucus questions): Hopefully the team drafting the responses will be done today, in which I’ll circulate the draft responses to you tomorrow. Kind regards, Bart Agenda and draft resolution ccNSO Council Meeting 208 22 August 2024, 18.00 UTC 1. Welcome and roll call * Is meeting Quorate? 2. Update Statement of Interest For information <https://ccnso.icann.org/en/about/ccnso-internal-procedure-general-soi-coi-2…> Guideline<https://ccnso.icann.org/en/about/ccnso-internal-procedure-general-soi-coi-2…> & <https://docs.google.com/forms/d/e/1FAIpQLSfRpehiCw2ty2PYRiaPG0K3lZSKk9LrLPQ…> Template<https://docs.google.com/forms/d/e/1FAIpQLSfRpehiCw2ty2PYRiaPG0K3lZSKk9LrLPQ…> Administrative matters 3. Relevant Correspondence<https://ccnso.icann.org/en/about/statements.htm> * Letter from ICANN re WSIS+20 (Item 17) * Letter to ICANN and response from ICANN re “How we meet” (item 18) 4. Minutes & Action Items * Minutes Meeting 207: Circulated 29 July 2024 * Action items * Action item 207-01: Peter Koch will provide a written report to Council regarding RSS GWG developments. If actions are needed, the Secretariat is requested to reflect this in the agenda for the next Council meeting. (Pending) * Action item 207-02: The secretariat is requested to ensure the RSS GWG updates are included in the monthly written updates. (Completed) * Action item 207-03: Jordan Carter will prepare a draft plenary session proposal for ICANN 81 on the WSIS+20 strategy. (Completed) * Action item 207-04: Alejandra Reynoso will inform the ICANN planning team that a plenary session proposal for ICANN 81 on the WSIS+20 strategy is forthcoming. (Completed) * Action item 207-05: The Secretariat shall inform all volunteers of the outcome of the Council's decision to appoint the volunteers and the initial Chair of the PGA WG and shall publish the decision as soon as possible. (Completed) * Action item 207-06: The Secretariat shall send a draft resolution for online decision to Council, regarding the appointment of Chris Disspain (Council), Nick Wenban-Smith (.uk) as members of the ccNSO PGA WG, and Peter Van Roste (CENTR) as Liaison. (Completed) * Action item 207-07: The Secretariat shall inform all volunteers about the outcome of the Council's decision to appoint the Tech WG Vice Chairs and shall publish the decision as soon as possible. (Completed) * Action item 207-08: The Secretariat shall publish the Council decision to adopt the Council election timeline and the appointment of the Election Process Manager as soon as possible. (Completed) * Action item 207-09: Secretariat and Councillors to draft letter on deferral 3rd CSC Effectiveness Review and to revisit decision in 1 year. To be shared with the Council in 2 weeks, in time for the next Council meeting. (Completed) * Action Item 207-10: The Travel Funding Committee, with assistance from the secretariat, should propose updates to the ccNSO travel funding process, using the ccNSO Continuous Improvement Framework. The committee should provide an update on progress by the next Council meeting, and with aspiration to conclude the update by the next round of travel funding requests (for ICANN82 or ICANN83). (Completed, See item 13 on the agenda) * Action Item 207-11: A Council drafting team will prepare a draft response to the request for input on the “how we meet” paper. The proposed draft will be circulated by 26 July 2024 to Council for review and adoption. (Completed) * Action Item 207-12: Sean Copeland is requested to circulate background materials and questions to Council. Councillors are requested to respond in a timely manner. (Completed) * Action Item 207-13: Alejandra Reynoso will circulate the initial draft of the ICANN81 ccNSO block schedule to the Council mailing list. (Completed) 5. Intermeeting Decisions (since meeting 207, July 2024) * 207-A: Appointment members PGA WG & IGLC * 207-B: Support letter to ICANN Interim CEO and President re: “How we meet” * 207-C: Approval membership National Communication Authority (NCA) of South Sudan (.ss) as member 178 of the ccNSO * 207-D: Approval full slate CSC membership (by Council selection committee) 6. Intermeeting decisions Triage Committee The Triage Committee has made no decisions since the last meeting. Updates 7. Update ECA, IFR2 & CSC (written updates<https://community.icann.org/x/4QciCw>) Note: Proposed change to Article 4, which is Fundamental Bylaw. Requires ccNSO approval. Tentatively scheduled community forum@iCANN81 8. Update WGs (written updates) * ccPDP3-Review Mechanism - Dormant * ccPDP4-IDN - Dormant * DASC * GRC * IGLC * MPC * OMC - To be established * PGA WG - First meeting is scheduled for 27 August 2024 * SOPC * Tech WG - Had no meeting since Council meeting 207 * TLD-OPS SC - Had no meeting since Council meeting 207 * UAC * Triage Committee - Had no meeting since Council meeting 207 * CCG WS2 Implementation- Had no meeting since Council meeting 207 * IRP Panel Selection - Had no meeting since Council meeting 207 * Planning Prioritization Process group - Had no meeting since Council meeting 207 * RZERC * RSS GWG * CIP-CCG 9. Update liaisons (written updates) * Update ALAC Liaison * Update GNSO Liaison * Update UASG Liaison 10. Update ccNSO Website redesign Informational 11. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat * ICANN81 Planning call (Block schedule, Plenary topics), see item 17 & 19 c * SO/AC Roundtable meeting, see item 17 * Meeting on “How we meet”, see item 18 Administrative Matters & Decisions 12. Appointment Members to Committees and Working Groups, if any 13. Deferral 3rd CSC Effectiveness Review Draft Resolution Background According to the ICANN Bylaws and CSC Charter, the 3rd CSC Effectiveness Review is expected to start by 1 October 2024, and the ccNSO and GNSO Councils have to determine the review method. The Council notes that the 2nd CSC Effectiveness Review was launched in August 2021 by adoption of the Terms of Reference and appointment of the members of the Review Team. The Final Report was adopted by both Councils on 20 April 2023. In May 2023, the ccNSO and GNSO Councils jointly informed the ICANN Board of Directors of the outcome of the review and requested initiation of the process of Bylaw changes to adjust the frequency of Bylaw changes as suggested. The Review Team recommended, among other recommendations, to reduce the frequency to once every five years after the previous review was concluded, or at the request of the PTI Board, the CSC, the ccNSO or RySG if any of them deem a CSC effectiveness review to be necessary. Current status of the implementation of this recommendation is unknown. To inform the ICANN Board of Directors the ccNSO and GNSO Council drafted a joint letter. Decision Assuming the GNSO council will decide in a similar manner, the ccNSO Council decides to defer the 3rd CSC Effectiveness Review, and to revisit this decision in August 2025. The Council requests its chair jointly with the chair of the GNSO Council to inform the chair of the ICANN Board of Directors, by sending the letter that was drafted for that purpose, after this resolution becomes effective. The secretariat is requested to publish the resolution as soon as possible, and this resolution becomes effective seven (7) days after its publication. 14. Update & introduction changes to ccNSO Travel Support Guideline 15. Generic “letter” to invite ccTLDs to join the ccNSO? Substantive Matters & Decisions 16. Update and next steps re requests for clarification and confirmation Board Caucus ccPDP review mechanism 1. Review and support response by Council 2. Topics to include in Cover Note 17. WSIS+20 exchange of letters: what’s next? 18. Follow-up Discussion on ICANN’s “How we meet” initiative 19. Tentative ccNSO Block Schedule ICANN81 * Council (prep) meetings/workshop * Joint meetings: Meeting with the Board and GAC Tentative topics GAC meeting: i. introducing the Policy Gap Analysis ii. Supporting the MSM in context of WSIS+20 iii. Relevant takeaways 2nd DNS Abuse survey 1. Plenary session: 2. Working groups/Committees meetings 3. Tech Day 4. Members sessions 20. AOB 21. Next Council Meetings * 19 September 2024 | 12:00 UTC, Meeting 209 * 17 October 2024 | 21:00 UTC, Meeting 210 * 14 November 2024 | time TBD, Meeting 211 (at ICANN81) * 12 December 2024 | 12:00 UTC, Meeting 212 * 16 January 2025 | 18:00 UTC, Meeting 213 * 13 February 2025 | 12:00 UTC, Meeting 214 22. Adjourn

1 0

Re: Appointment Tsholofelo Mokone (.za) to IGLC
by Stephen Deerhake ＠ ASNIC Aug. 19, 2024

Aug. 19, 2024

I am in favour. Best, //Stephen From: Joke Braeken via Ccnso-council <ccnso-council(a)icann.org> Reply-To: Joke Braeken <joke.braeken(a)icann.org> Date: Monday, August 19, 2024 at 14:57 To: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] Appointment Tsholofelo Mokone (.za) to IGLC Dear Councilors, Please find below a draft resolution, presented to you for an online decision. Kindly provide me with your input by the end of Wednesday, 21 August 2024, 23:59 UTC, in case you do not agree with the proposed resolution. In case there are no comments, the decision is carried. Appointment member For decision formal appointment additional member to the Internet Governance Liaison Committee (IGLC) Draft Resolution Tsholofelo Mokone (.za) expressed an interest to be member of the IGLC. The ccNSO Council approves Tsholofelo’s membership to the IGLC. The secretariat is requested to take all necessary steps to include her as member of the IGLC, including informing the respective committee Chair and Vice Chair. This decision becomes effective upon publication. Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

REMINDER | Call For Volunteers: ccNSO Appointed Delegate to the 2025 ICANN NomCom
by Joke Braeken Aug. 19, 2024

Aug. 19, 2024

Dear All, This is a reminder regarding the call for volunteers for one delegate to the 2025 ICANN NomCom. Read more below, or here: https://ccnso.icann.org/en/announcements/announcement-13aug24-en.htm Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> From: ccnso-council <ccnso-council(a)icann.org> Reply to: Joke Braeken <joke.braeken(a)icann.org> Date: Monday, 12 August 2024 at 18:27 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org>, ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] Call For Volunteers: ccNSO Appointed Delegate to the 2025 ICANN NomCom Dear All, In accordance with the Guideline: ccNSO Appointment Procedures [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/fiel…>, the ccNSO Council is now looking for one (1) volunteer to serve on the 2025 ICANN Nominating Committee (NomCom) on behalf of the ccNSO. The 2025 NomCom meets for the first time during ICANN81, and participation is mandatory for all delegates, including the ccNSO appointed delegate. This call for volunteers opens Monday, 12 August 2024 and closes Tuesday, 27 August 2024 (23:59 UTC). Sophie Mitchell (.au) has served two 1-year terms on the NomCom. As per the ICANN Bylaws, section 8.3<https://www.icann.org/resources/pages/governance/bylaws-en/#article8>, she is no longer eligible to serve another term. How to apply? You are required to be associated with a ccTLD manager. ccNSO Councilors are not eligible. If you are interested in serving in this position, send an email to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> . Please include a motivation letter explaining why you wish to serve on the NomCom and how you meet the candidate requirements below. By submitting your personal data, you acknowledge that your personal data will be processed in accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy<https://urldefense.com/v3/__https:/www.icann.org/privacy/policy__;!!PtGJab4…>) and you agree to abide by the electronic Terms of Service (https://www.icann.org/privacy/tos<https://urldefense.com/v3/__https:/www.icann.org/privacy/tos__;!!PtGJab4!vp…>) This call for volunteers opens Monday, 12 August 2024 and closes Tuesday, 27 August 2024 (23:59 UTC). Key Responsibilities and Duties * Act independently and in the larger public interest and not act as representatives of, nor lobby or advance the interest of any particular Organization, Group or Committee, in particular with respect to the assessment and selection of candidates * Engage in outreach, recruitment, and information gathering * Read the submitted and gathered information about each candidate under consideration; to participate in both deliberations about individual candidates and construction of slates of candidates that will fulfill the requirements for each of the leadership bodies for which the NomCom selects delegates * Participate in NomCom teleconferences * Work diligently with NomCom colleagues toward an overall consensus on the best possible group of candidates to be selected * Adhere to the ICANN Code of Conduct * Provide brief reports to its respective SO/AC on relevant issues considered by the Nominating Committee, as Nominating Committee confidentiality permits. * Adhere to the ICANN Nominating Committee Participation Agreement<https://www.icann.org/resources/pages/nomcom2021-participation-agreement-20…>. Time Commitment The member should be able to join monthly teleconferences (typically 15:00 or 16:00 UTC). Note that the committee's workload usually increases significantly during Apr/May/June when the candidate assessment process will be at its busiest. Conference calls are held more frequently (typically weekly and the duration of the calls may last up to 3 hours) during this time as well. All NomCom delegates should be able to attend all ICANN meetings and all officially scheduled NomCom committee meetings When attending ICANN Meetings, attendance at scheduled NomCom meetings is mandatory. In the event of schedule conflicts with other volunteer activities, priority should be given to the NomCom meetings. Candidate requirements: Required Knowledge, Skills and Abilities (KSAs) ccNSO appointed NomCom delegates are required to be associated with a ccTLD manager. ccNSO Councilors are not eligible. As outlined in the ICANN Bylaws article 8.4<https://www.icann.org/resources/pages/governance/bylaws-en/#article8>, delegates to the ICANN Nominating Committee shall be: * Accomplished persons of integrity, objectivity, and intelligence, with reputations for sound judgment and open minds, and with experience and competence with collegial large group decision-making * Persons with a high-level network contacts essential to candidate recruitment, broad experience in the Internet community, and a commitment to the success of ICANN * Persons whom the selecting body is confident will consult widely and accept input in carrying out their responsibilities * Persons who are neutral and objective, without any fixed personal commitments to particular individuals, organizations, or commercial objectives in carrying out their Nominating Committee responsibilities * Persons with an understanding of ICANN's mission and the potential impact of ICANN's activities on the broader Internet community * Familiarity with the ICANN groups to which the NomCom appoints (Board, ALAC, GNSO, ccNSO) * An understanding of Non-profit Board Governance * Are willing to serve as volunteers, without compensation other than the reimbursement of certain expenses; and * Persons who are able to work and communicate in written and spoken English * Prior experience in executive recruiting and Human Resources is a plus. Eligibility Exception No person who is an employee of or paid consultant to ICANN (including the Ombudsman) shall simultaneously serve on the Nominating Committee. ccNSO Councilors are not eligible. Term of Eligibility * Per the ICANN Bylaws Article 8, Section 8.3<https://www.icann.org/resources/pages/governance/bylaws-en/#article8>, NomCom voting delegates shall serve one-year terms and may serve at most two successive one-year terms, after which at least two years must elapse before the individual is eligible to serve another term. * Per the ICANN Bylaws Article 8, Section 8.3<https://www.icann.org/resources/pages/governance/bylaws-en/#article8>, Non-voting liaisons shall serve during the term designated by the entity that appoints them. The Chair, the Chair-Elect, and any Associate Chair shall serve as such until the conclusion of the next ICANN annual meeting. Diversity The ICANN community is diverse and the composition of NomCom should reflect this in order to fulfill its mission. NomCom believes that all persons are entitled to equal employment opportunity and does not discriminate against qualified applicants because of race, color, religion, sex, pregnancy, childbirth or related medical conditions, family care status, national origin, ancestry, citizenship, age, marital status, physical disability, mental disability, medical condition, sexual orientation, or any other characteristic protected by applicable local law. NomCom will make reasonable accommodations for the known physical or mental limitations of an otherwise qualified individual with a disability who is a NomCom member unless undue hardship would result. Next steps Once the call for volunteers closes, the list of candidates will be presented to all ccNSO Councillors eligible to vote, who will then make a decision regarding the appointment of the ccNSO delegate to the NomCom by email vote. Further details on the selection procedure by the ccNSO Councillors can be found here [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/fiel…>. In case you are being selected, you will be required to consent to ICANN processing your personal data for the purpose of serving on the NomCom under ICANN's data protection policy. About the ICANN NomCom Per the ICANN Bylaws article 8.1<https://www.icann.org/resources/pages/governance/bylaws-en#article8.1>, there shall be a Nominating Committee of ICANN ("Nominating Committee"), responsible for nominating all Directors except the President and those Directors nominated by Decisional Participants; for nominating two directors of PTI (in accordance with the articles of incorporation and bylaws of the Public Technical Identifiers body); and for such other selections as are set forth in these Bylaws. Notification of the Nominating Committee's Director nominations shall be given by the Nominating Committee Chair in writing to the EC (Empowered Community) Administration, with a copy to the Secretary, and the EC shall promptly act on it as provided in Section 7.25. Notification of the Nominating Committee's PTI director nomination shall be given to the Secretary. Specific criteria and requirements regarding the Nominating Committee ("NomCom") composition and NomCom delegates are outlined in the ICANN Bylaws in Article 8, Sections 8.2 and 8.4<https://www.icann.org/resources/pages/governance/bylaws-en/#article8> , which are incorporated in the job description. The NomCom also has a procedure<https://www.icann.org/resources/pages/nomcom2021-operating-procedures-2021-…> document for reference that provides additional information about the work of the NomCom. The 2025 NomCom will be selecting people to fill the following positions: * Three members of the ICANN Board of Directors * Two regional representatives to the At-Large Advisory Committee (ALAC) * One member of the Generic Names Supporting Organization (GNSO) Council * One member of the Country Code Names Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Announcement of early resignation from the ccNSO Council
by Tatiana Tropina Aug. 16, 2024

Aug. 16, 2024

Dear ccNSO councillors, I hope this message finds you well. I am writing to formally announce my early resignation from the Council, effective tomorrow, 17 August 2024. I already contacted you through informal channels, but I wanted to ensure that you are properly informed through this official communication on the mailing list. I am stepping down due to a new job opportunity that I’ve recently accepted. While I am eager to start this next chapter in my career, it is bittersweet to be leaving this incredible group. It has been a privilege and a pleasure to serve on the Council with you. I learnt so much from you all. Thank you so much for your professionalism, your passion, and dedication. The experience has been truly rewarding, and I am forever grateful for the time spent as part of this community. Unfortunately, I have not got an opportunity to thank you all in person, but I am hopeful that I see you all some time in the future and say many thanks personally. Warm regards, Tatiana

1 0

Draft Agenda meeting 208 | 22 August 2024 18.00 UTC
by Bart Boswinkel Aug. 15, 2024

Aug. 15, 2024

Dear all, Please find included the draft agenda for the upcoming Council meeting 208, 22 August 2024- 18.00 UTC Background material will follow closer to the meeting, Kind regards, Bart Draft Agenda ccNSO Council Meeting 208 22 August 2024, 18.00 UTC 1. Welcome and roll call * Is meeting Quorate? 2. Update Statement of Interest For information <https://ccnso.icann.org/en/about/ccnso-internal-procedure-general-soi-coi-2…> Guideline<https://ccnso.icann.org/en/about/ccnso-internal-procedure-general-soi-coi-2…> & <https://docs.google.com/forms/d/e/1FAIpQLSfRpehiCw2ty2PYRiaPG0K3lZSKk9LrLPQ…> Template<https://docs.google.com/forms/d/e/1FAIpQLSfRpehiCw2ty2PYRiaPG0K3lZSKk9LrLPQ…> Administrative matters 3. Relevant Correspondence<https://ccnso.icann.org/en/about/statements.htm> * Letter from ICANN re WSIS+20 () * Letter to ICANN and response from ICANN re “How we meet” (item bb) 4. Minutes & Action Items * Minutes Meeting 207: Circulated 29 July 2024 * Action items * Action item 207-01: Peter Koch will provide a written report to Council regarding RSS GWG developments. If actions are needed, the Secretariat is requested to reflect this in the agenda for the next Council meeting. (Pending) * Action item 207-02: The secretariat is requested to ensure the RSS GWG updates are included in the monthly written updates. (Completed) * Action item 207-03: Jordan Carter will prepare a draft plenary session proposal for ICANN 81 on the WSIS+20 strategy. (Completed) * Action item 207-04: Alejandra Reynoso will inform the ICANN planning team that a plenary session proposal for ICANN 81 on the WSIS+20 strategy is forthcoming. (Completed) * Action item 207-05: The Secretariat shall inform all volunteers of the outcome of the Council's decision to appoint the volunteers and the initial Chair of the PGA WG and shall publish the decision as soon as possible. (Completed) * Action item 207-06: The Secretariat shall send a draft resolution for online decision to Council, regarding the appointment of Chris Disspain (Council), Nick Wenban-Smith (.uk) as members of the ccNSO PGA WG, and Peter Van Roste (CENTR) as Liaison. (Completed) * Action item 207-07: The Secretariat shall inform all volunteers about the outcome of the Council's decision to appoint the Tech WG Vice Chairs and shall publish the decision as soon as possible. (Completed) * Action item 207-08: The Secretariat shall publish the Council decision to adopt the Council election timeline and the appointment of the Election Process Manager as soon as possible. (Completed) * Action item 207-09: Secretariat and Councillors to draft letter on deferral 3rd CSC Effectiveness Review and to revisit decision in 1 year. To be shared with the Council in 2 weeks, in time for the next Council meeting. (Completed) * Action Item 207-10: The Travel Funding Committee, with assistance from the secretariat, should propose updates to the ccNSO travel funding process, using the ccNSO Continuous Improvement Framework. The committee should provide an update on progress by the next Council meeting, and with aspiration to conclude the update by the next round of travel funding requests (for ICANN82 or ICANN83). (Completed, See item 13 on the agenda) * Action Item 207-11: A Council drafting team will prepare a draft response to the request for input on the “how we meet” paper. The proposed draft will be circulated by 26 July 2024 to Council for review and adoption. (Completed) * Action Item 207-12: Sean Copeland is requested to circulate background materials and questions to Council. Councillors are requested to respond in a timely manner. (Completed) * Action Item 207-13: Alejandra Reynoso will circulate the initial draft of the ICANN81 ccNSO block schedule to the Council mailing list. (Completed) 5. Intermeeting Decisions (since meeting 207, July 2024) * 207-A: Appointment members PGA WG & IGLC * 207-B: Support letter to ICANN Interim CEO and President re: “How we meet” * 207-C: Approval membership National Communication Authority (NCA) of South Sudan (.ss) as member 178 of the ccNSO * 207-D: Approval full slate CSC membership ( by Council selection committee) 6. Intermeeting decisions Triage Committee The Triage Committee has made no decisions since the last meeting. Updates 7. Update ECA, IFR2 & CSC (written updates<https://community.icann.org/x/4QciCw>) Note: Proposed change to Article 4, which is Fundamental Bylaw. Requires ccNSO approval. Tentatively scheduled community forum@iCANN81 8. Update WGs (written updates) * ccPDP3-Review Mechanism - Dormant * ccPDP4-IDN - Dormant * DASC * GRC * IGLC * MPC * OMC - To be established * PGA WG - First meeting is scheduled for 27 August 2024 * SOPC * Tech WG - Had no meeting since Council meeting 207 * TLD-OPS SC - Had no meeting since Council meeting 207 * UAC * Triage Committee - Had no meeting since Council meeting 207 * CCG WS2 Implementation- Had no meeting since Council meeting 207 * IRP Panel Selection - Had no meeting since Council meeting 207 * Planning Prioritization Process group - Had no meeting since Council meeting 207 * RZERC * RSS GWG * CIP-CCG 9. Update liaisons (written updates) * Update ALAC Liaison * Update GNSO Liaison * Update UASG Liaison 10. Update ccNSO Website redesign Informational 11. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat * ICANN81 Planning call (Block schedule, Plenary topics), see item 17 & 19 c * SO/AC Roundtable meeting, see item 17 * Meeting on “How we meet”, see item 18 Administrative Matters & Decisions 1. Appointment Members to Committees and Working Groups, if any 13. Adoption letter on deferral 3rd CSC Effectiveness Review 14. Update & introduction changes to ccNSO Travel Support Guideline 15. Need for a Generic “letter” to invite ccTLDs to join the ccNSO? Substantive Matters & Decisions 16. Update and next steps re requests for clarification and confirmation Board Caucus ccPDP review mechanism * Review and support response by Council * Topics to include in Cover Note 17. WSIS+20 exchange of letters: what’s next? 18. Follow-up Discussion on ICANN’s “How we meet” initiative 19. Tentative ccNSO Block Schedule ICANN81 * Council (prep) meetings/workshop * Joint meetings: Meeting with the Board and GAC Tentative topics GAC meeting: i. introducing the Policy Gap Analysis ii. Supporting the MSM in context of WSIS+20 iii. Relevant takeaways 2nd DNS Abuse survey 1. Plenary session 2. Working groups/Committees meetings 3. Tech Day 4. Members sessions 20. AOB 21. Next Council Meetings * 19 September 2024 | 12:00 UTC, Meeting 209 * 17 October 2024 | 21:00 UTC, Meeting 210 * 14 November 2024 | time TBD, Meeting 211 (at ICANN81) * 12 December 2024 | 12:00 UTC, Meeting 212 * 16 January 2025 | 18:00 UTC, Meeting 213 * 13 February 2025 | 12:00 UTC, Meeting 214 22. Adjourn

1 0

Call For Volunteers: ccNSO Appointed Delegate to the 2025 ICANN NomCom
by Joke Braeken Aug. 12, 2024

Aug. 12, 2024

Dear All, In accordance with the Guideline: ccNSO Appointment Procedures<https://ccnso.icann.org/sites/default/files/field-attached/guidelines-ccnso…>, the ccNSO Council is now looking for one (1) volunteer to serve on the 2025 ICANN Nominating Committee (NomCom) on behalf of the ccNSO. The 2025 NomCom meets for the first time during ICANN81, and participation is mandatory for all delegates, including the ccNSO appointed delegate. This call for volunteers opens Monday, 12 August 2024 and closes Tuesday, 27 August 2024 (23:59 UTC). Sophie Mitchell (.au) has served two 1-year terms on the NomCom. As per the ICANN Bylaws, section 8.3<https://www.icann.org/resources/pages/governance/bylaws-en/#article8>, she is no longer eligible to serve another term. How to apply? You are required to be associated with a ccTLD manager. ccNSO Councilors are not eligible. If you are interested in serving in this position, send an email to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> . Please include a motivation letter explaining why you wish to serve on the NomCom and how you meet the candidate requirements below. By submitting your personal data, you acknowledge that your personal data will be processed in accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy<https://urldefense.com/v3/__https:/www.icann.org/privacy/policy__;!!PtGJab4…>) and you agree to abide by the electronic Terms of Service (https://www.icann.org/privacy/tos<https://urldefense.com/v3/__https:/www.icann.org/privacy/tos__;!!PtGJab4!vp…>) This call for volunteers opens Monday, 12 August 2024 and closes Tuesday, 27 August 2024 (23:59 UTC). Key Responsibilities and Duties * Act independently and in the larger public interest and not act as representatives of, nor lobby or advance the interest of any particular Organization, Group or Committee, in particular with respect to the assessment and selection of candidates * Engage in outreach, recruitment, and information gathering * Read the submitted and gathered information about each candidate under consideration; to participate in both deliberations about individual candidates and construction of slates of candidates that will fulfill the requirements for each of the leadership bodies for which the NomCom selects delegates * Participate in NomCom teleconferences * Work diligently with NomCom colleagues toward an overall consensus on the best possible group of candidates to be selected * Adhere to the ICANN Code of Conduct * Provide brief reports to its respective SO/AC on relevant issues considered by the Nominating Committee, as Nominating Committee confidentiality permits. * Adhere to the ICANN Nominating Committee Participation Agreement<https://www.icann.org/resources/pages/nomcom2021-participation-agreement-20…>. Time Commitment The member should be able to join monthly teleconferences (typically 15:00 or 16:00 UTC). Note that the committee's workload usually increases significantly during Apr/May/June when the candidate assessment process will be at its busiest. Conference calls are held more frequently (typically weekly and the duration of the calls may last up to 3 hours) during this time as well. All NomCom delegates should be able to attend all ICANN meetings and all officially scheduled NomCom committee meetings When attending ICANN Meetings, attendance at scheduled NomCom meetings is mandatory. In the event of schedule conflicts with other volunteer activities, priority should be given to the NomCom meetings. Candidate requirements: Required Knowledge, Skills and Abilities (KSAs) ccNSO appointed NomCom delegates are required to be associated with a ccTLD manager. ccNSO Councilors are not eligible. As outlined in the ICANN Bylaws article 8.4<https://www.icann.org/resources/pages/governance/bylaws-en/#article8>, delegates to the ICANN Nominating Committee shall be: * Accomplished persons of integrity, objectivity, and intelligence, with reputations for sound judgment and open minds, and with experience and competence with collegial large group decision-making * Persons with a high-level network contacts essential to candidate recruitment, broad experience in the Internet community, and a commitment to the success of ICANN * Persons whom the selecting body is confident will consult widely and accept input in carrying out their responsibilities * Persons who are neutral and objective, without any fixed personal commitments to particular individuals, organizations, or commercial objectives in carrying out their Nominating Committee responsibilities * Persons with an understanding of ICANN's mission and the potential impact of ICANN's activities on the broader Internet community * Familiarity with the ICANN groups to which the NomCom appoints (Board, ALAC, GNSO, ccNSO) * An understanding of Non-profit Board Governance * Are willing to serve as volunteers, without compensation other than the reimbursement of certain expenses; and * Persons who are able to work and communicate in written and spoken English * Prior experience in executive recruiting and Human Resources is a plus. Eligibility Exception No person who is an employee of or paid consultant to ICANN (including the Ombudsman) shall simultaneously serve on the Nominating Committee. ccNSO Councilors are not eligible. Term of Eligibility * Per the ICANN Bylaws Article 8, Section 8.3<https://www.icann.org/resources/pages/governance/bylaws-en/#article8>, NomCom voting delegates shall serve one-year terms and may serve at most two successive one-year terms, after which at least two years must elapse before the individual is eligible to serve another term. * Per the ICANN Bylaws Article 8, Section 8.3<https://www.icann.org/resources/pages/governance/bylaws-en/#article8>, Non-voting liaisons shall serve during the term designated by the entity that appoints them. The Chair, the Chair-Elect, and any Associate Chair shall serve as such until the conclusion of the next ICANN annual meeting. Diversity The ICANN community is diverse and the composition of NomCom should reflect this in order to fulfill its mission. NomCom believes that all persons are entitled to equal employment opportunity and does not discriminate against qualified applicants because of race, color, religion, sex, pregnancy, childbirth or related medical conditions, family care status, national origin, ancestry, citizenship, age, marital status, physical disability, mental disability, medical condition, sexual orientation, or any other characteristic protected by applicable local law. NomCom will make reasonable accommodations for the known physical or mental limitations of an otherwise qualified individual with a disability who is a NomCom member unless undue hardship would result. Next steps Once the call for volunteers closes, the list of candidates will be presented to all ccNSO Councillors eligible to vote, who will then make a decision regarding the appointment of the ccNSO delegate to the NomCom by email vote. Further details on the selection procedure by the ccNSO Councillors can be found here<https://ccnso.icann.org/sites/default/files/field-attached/guidelines-ccnso…>. In case you are being selected, you will be required to consent to ICANN processing your personal data for the purpose of serving on the NomCom under ICANN's data protection policy. About the ICANN NomCom Per the ICANN Bylaws article 8.1<https://www.icann.org/resources/pages/governance/bylaws-en#article8.1>, there shall be a Nominating Committee of ICANN ("Nominating Committee"), responsible for nominating all Directors except the President and those Directors nominated by Decisional Participants; for nominating two directors of PTI (in accordance with the articles of incorporation and bylaws of the Public Technical Identifiers body); and for such other selections as are set forth in these Bylaws. Notification of the Nominating Committee's Director nominations shall be given by the Nominating Committee Chair in writing to the EC (Empowered Community) Administration, with a copy to the Secretary, and the EC shall promptly act on it as provided in Section 7.25. Notification of the Nominating Committee's PTI director nomination shall be given to the Secretary. Specific criteria and requirements regarding the Nominating Committee ("NomCom") composition and NomCom delegates are outlined in the ICANN Bylaws in Article 8, Sections 8.2 and 8.4<https://www.icann.org/resources/pages/governance/bylaws-en/#article8> , which are incorporated in the job description. The NomCom also has a procedure<https://www.icann.org/resources/pages/nomcom2021-operating-procedures-2021-…> document for reference that provides additional information about the work of the NomCom. The 2025 NomCom will be selecting people to fill the following positions: * Three members of the ICANN Board of Directors * Two regional representatives to the At-Large Advisory Committee (ALAC) * One member of the Generic Names Supporting Organization (GNSO) Council * One member of the Country Code Names Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0