- Ccnso-council - lists.icann.org

NOTES | ccNSO Council Meeting 208 | 22 August 2024 (18:00 UTC)
by Joke Braeken Aug. 22, 2024

Aug. 22, 2024

NOTES | ccNSO Council Meeting 208 | 22 August 2024 (18:00 UTC) 1. Welcome and roll call Welcome by Alejandra. Extensive thank you to Tatiana, recognising her for her valuable contributions to Council and ccNSO. Alejandra mentioned that at the next meeting council will need to discuss the replacement of Tatiana in Triage Committee, IGLC etc. a. Is meeting Quorate? yes. apologies by Jenifer and Olga 3 items for AOB * Bart: 360 review * Chris: voluntary fraud grace period * Nick: DASC survey and charter review Alejandra: can we skip items 3-10? Nick: yes, in favour of efficiency. can we scroll through the items? 2. Update Statement of Interest For information Guideline<https://ccnso.icann.org/en/about/ccnso-internal-procedure-general-soi-coi-2…> & Template<https://docs.google.com/forms/d/e/1FAIpQLSfRpehiCw2ty2PYRiaPG0K3lZSKk9LrLPQ…> Administrative matters 3. Relevant Correspondence<https://ccnso.icann.org/en/about/statements.htm> a. Letter from ICANN re WSIS+20 (item 17) 1. Letter to ICANN and response from ICANN re “How we meet” (item 18) 4. Minutes & Action Items a. Minutes Meeting 207: Circulated 29 July 2024 1. Action items 5. Intermeeting Decisions (since meeting 207, July 2024) 6. Intermeeting decisions Triage Committee 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) a. ccPDP3-Review Mechanism - Dormant b. ccPDP4-IDN - Dormant c. DASC d. GRC e. IGLC f. MPC g. OMC - To be established h. PGA WG - First meeting is scheduled for 27 August 2024 i. SOPC j. Tech WG - Had no meeting since Council meeting 207 k. TLD-OPS SC - Had no meeting since Council meeting 207 l. UAC m. Triage Committee - Had no meeting since Council meeting 207 n. CCG WS2 Implementation- Had no meeting since Council meeting 207 o. IRP Panel Selection - Had no meeting since Council meeting 207 p. Planning Prioritization Process group - Had no meeting since Council meeting 207 q. RZERC r. RSS GWG s. CIP-CCG 9. Update liaisons (written updates) a. Update ALAC Liaison b. Update GNSO Liaison c. Update UASG Liaison 10. Update ccNSO Website redesign 11. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat a. ICANN81 Planning call (Block schedule, Plenary topics), see item 17 & 19c b. SO/AC Roundtable meeting, see item 17 c. Meeting on “How we meet”, see item 18 pilot holistic review call by chairs yesterday. * 12 primary candidates + 3 incoming fro SSAC + 1 incoming from the Board = 16 * +1 secondary candidate to balance region on gender diversity * Total of 17 members. * 4 potential co-chairs, in order of preference will be contacted to check whether they are willing to do the job. * GAC couldn’t attend the call. Their approval will be requested. Stephen: call for presentation proposals to Tech Day is out now Administrative Matters & Decisions 12. Appointment Members to Committees and Working Groups, if any none today 13. Adoption letter on deferral 3rd CSC Effectiveness Review Letter to send to Tripti and Sally on the deferral of the 3rd CSC effectiveness review For the record the arguments to defer the review are: The 2nd review closed in March 2023 (a little over a year ago) and the ccNSO and GNSO Councils adopted the final report in April 23. The Board was first informed about the outcome, including the recommended change to Bylaws to extend the period between reviews from every 3 years, starting in October, to 5 years after conclusion of the previous review. As result of this short time between reviews, the recommendations from previous review will most likely not be implemented, and finally, thai review is again overlapping with the IAAN Function review, which is for a small part also looking at the CSC/PTI relation, and also overlaps in resources. We drafted the letter jointly. See background materials. Any questions? none. Alejandra will send the letter on behalf of both Councils Move? Stephen Second? Sean Any questions regarding resolution? none All in favour 14. Update & introduction changes to ccNSO Travel Support Guideline Peter: the committee met twice and had email exchange. guideline was streamlined. details removed, and having a fresh read and editorial changes. We met earlier today. Guideline is not yet fully finalised. Purposes is to finalise in time for the ICANN82 round. hope we can approve the guideline via an intermediary decision. idea is to give the committee a bit more leeway in evaluating the criteria. start measuring the success. assisting active participants to join the meeting physically, and also help new people to network and become active in the ccNSO community. the intention is to evaluate this new approach in a year or two. wafa agrees. Alejandra: what is the next step? proposal first to Council ? then also to community? Peter: understood it will be subject to community review. trust the secretariat with the formalities Joke: icann82 application round starts prior to ICANN 81. Bart: Council has a week for comments, then circulate to community for one week. then it is ready for adoption. can do that online, but there is also enough time to do that at the next Council meeting. 15. Generic “letter” to invite ccTLDs to join the ccNSO? received the request to send an invite letter to an individual ccTLD. proposal to make a generic letter instead. Sean: Is that enough? Alejandra: We do not know. but ccNSO is a voluntary organisation. Ali: How many ccTLDs are not yet members? Alejandra: we have the list Bart: Not that easy. Some ccTLD managers run several ccTLDs. they are only member for one. And there are IDN ccTLDs. original thinking at the time: ccNSO not to actively seek membership. this is a voluntary organisation. Peter: let’s first check with the ccTLD whether it is enough. We can trust the secretariat to send the letter without formalities from our side Alejandra: reminds me about the funded traveller process. if you need a letter to apply for a visa, there is a generic one, but can be personalised post a generic one on the website Stephen: rather post “contact secretariat” if you need an invitation letter have boiler plate ready. Chris: agree Biyi: precedence. up to date we never had to invite someone Peter: The “invitation” should not be a vehicle in an ion-country dispute about the ccTLD(s) Chris: not setting a precedent. if we are going to send it, it needs to go to the manager in the IANA DB. Alejandra: we will prepare a boiler plate text, and send to the council. We will discuss the content on the mailing list. Substantive Matters & Decisions 16. Update and next steps re requests for clarification and confirmation Board Caucus ccPDP review mechanism a. Review and support response by Council As you know the Board Caucus that oversees the assessment of the feasibility of implementation of the Review Mechanism policy asked us in April 2024 (4 months ago) to provide clarifications and/or confirmation about the policy. At the time we decided that a group of Councillors and members of the ccPDP3 WG would prepare our response to the questions, without changing the recommended policy and the Council would need to sign off on the responses. At the time we appointed Jordan and Stephen as co-chairs. As you recall it was raised more than once whether the process the Board is using, is within the boundaries of section 15 a of the Annex B of the Bylaws: a. The Board shall meet to discuss the ccNSO Recommendation as soon as feasible after receipt of the Board Report from the Issue Manager, taking into account procedures for Board consideration Stephen: text is done, but formatting issues to be resolved. 43 questions. Some questions contained several parts. 27 questions required detailed responses. complete consensus on all matters. thanks to secretariat and Bernard Turcotte and all WG members. please read the responses. Council needs to make a decision. Jordan: as you review the text, please check. are there fatal flaws? the work product is good enough to send to start the conversation with the board. we try to finish the PDP and not extend the process further. we should do a retrospective on what happened here and how to avoid it in future. let’s avoid it next time. good for all. substantive review and procedural review. sometimes the answer was vague, but on purpose. not an argument we should get into. Nick: support Jordan’s comments. Chris: implementation review team. we would be involved there? Alejandra: implementation guideline. but process? Bart: in principle yes. include in cover note. alert the caucus. Nick: not yet received for the retirement Bart: was still being developed at the time we invited Marika K. and Karen L. to share their experiences. structuring the ccnso side. Chris: implementation review team. we should say in the cover note if we did not provide much detail. we dealt with policy now. now it is a matter for implementation Alejandra: good enough is good enough. one week for review. if there are issues or edits needed, we have some time. Jordan and Stephen will make a final editorial pass. Do you agree? green ticks. 1. Topics to include in Cover Note Now we have closed the discussion on the responses, we need to discuss what we want to include in a cover letter, if anything. It is my understanding that earlier the group suggested 3 points: * Invite the Caucus and staff to discuss the requests and responses. This was suggested to avoid losing time sending letters back and forth. * A response on the foundational assumption made in the cover note from Katrina which paraphrased asks to confirm that the CCRM Policy is limited to a procedural review. So, the substantive material review of an IFO Decision is not subject to a CCRM review. * A formal clarification of scope of section 15 a of Annex B, what can the ccNSO expect to be included in Procedures for Board consideration. * Alert - Companionship of the implementation process - Link Guideline. Jordan: council members of the group to do that drafting. Jordan, Stephen, Peter, Chris, Sean volunteered. 17. WSIS+20 exchange of letters: what’s next? Activities to date: 11. Jul Call drafting team to prep for the informal call with Sally. 15. Jul letter sent 16. Jul informal call with Sally + drafting team. 09. Aug - Call with Elena + drafting team. 14. Aug - heads up to SO/AC chairs on monthly call 15. Aug - Roundtable - no time to present it properly 19. Aug - Our plenary topic didn’t get selected. (Toss of a coin with ALAC’s proposal) Alejandra: Any further action needed? Chris: no Jordan: What do you think? Alejandra: It is hard. Some are very willing to act. but if we do not have the substantive matter. the only thing we can do is to ask for a status update. unless the informal group is presented to all, we have something not intangible. Jordan; wait until the end of next week. leave it at that. Chris: we talk about the at large proposal Alejandra: no, the informal group that Elena is going to organise. Chris: i am speaking to Elena tomorrow on a different matter. can check. Alejandra: our plenary proposal was rejected Chris: encouraging message from Becky MGilley. Peter: icann submitted GDC statement earlier today. 18. Follow-up Discussion on ICANN’s “How we meet” initiative 19.Aug - Informal call * Clarification that the informal call did not intend any major decisions. Brainstorm. * How to make work more efficient: * Less redundant/repetitive. People feeling not heard vs. Not getting what they want. * Use project management techniques (time bound) * Best is enemy of the very good (good enough) * Do we need the space of ICANN offices? (something for the new CEO to finish) * Regarding meetings: * Improve travel flight costs (new partner ongoing). Timing (faster = cheaper) * Some suggestions on how to improve meetings costs: * Fixed locations * SO/AC Chairs & vice-chairs got a high level summary of ICANN meeting costs. I requested more data to be able to provide personal insights. * Costs as detailed as possible * Include inter ICANN meeting in-person activities Chris: previous surveys at icann said. “complete lack of trust”. but when you explore further, you see that it is made by those who are not being heard. sections of the community refused to accept the fixed hubs. push the concept of hubs. cost-saving. Alejandra; unsure when the follow-up conversation is, but will let you know. seems it is going that way 19. Tentative ccNSO Block Schedule ICANN 81 draft schedule being shared. a. Council (prep) meetings/workshop on Sunday. 1. Joint meetings: Meeting with the Board and GAC wednesday, block 1 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 Any tentative topics for the Board? Tue 12.Nov - Block 5 (share them on the mailing list) 1. Plenary session: confirmed for Wednesday, block 2 (ALAC’s proposal) Working Title: Shifting Paradigms: Multistakeholderism, Geopolitics, International Law, and New Internet Infrastructures. Anyone would like to join the prep calls? 1. Working groups/Committees meetings 1. Tech Day 1. Members sessions Interest from the RySG on WSIS+20 - Invite them to IGLC session? Stephen: Having the Approval Action Forum on the morning of the last day is frankly an insult to the ECA. Nick: on saturday afternoon block 4 we have a DASC working session. one of the things that comes up is a review of the DASC. i was leading the review of the OISC. was to good to meet with them in person. council to set up a review team. have the interviews in Istanbul? Bart: secretariat to propose a template for review. similar to OISC. action item: add to agenda for September meeting Chris: regarding the ECA, it is right before the public forum. excellent time and location Stephen: agree. 20. AOB Bart: 360 council review. you have until today. We received 11,5 responses, out of 18. please complete asap. secondly, regarding the DASC survey https://ccnso.icann.org/en/announcements/announcement-09aug24-en.htm 4 completed responses to date useful for the role of DASC in future, and inform the broader community with respect to what ccTLDs are doing to dns abuse expects councilors to respond, at least Chris: email from owen. voluntary fraud grace period Nick and I will deal with it. DASC is the natural place. alejandra: no objections. no definition of dns abuse. Chris: just a conversation currently happening. 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 thank you all. Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Tech WG Update
by Stephen Deerhake ＠ ASNIC Aug. 22, 2024

Aug. 22, 2024

The call for presentations for IST has gone out. Best regards, //Stephen

1 0

REMINDER : August ccNSO Council Teleconference (208) | 22 August at 18:00 UTC
by Claudia Ruiz Aug. 22, 2024

Aug. 22, 2024

Dear Council, As a reminder, the August ccNSO Council teleconference (208) is scheduled for 22 August at 18:00 UTC. Draft Agenda is attached. Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/94061694297?pwd=TkF0dTMrUW1UeTRvWTBOSnRKcXVKdz09 Meeting ID: 923 4208 4426 Passcode: ccNSO-0208 Wiki page: https://community.icann.org/x/BQEZEw If you are unable to attend, please let staff know. Thank you. Kind regards, Claudia Ruiz

2 2

Fwd: Outreach re: voluntary fraud grace period (FGP)
by Chris Disspain Aug. 22, 2024

Aug. 22, 2024

Alejandra, All, Please see the email below from Owen Smigelski at Name Cheap. It is, I think, self explanatory. Could we please pop this on the agenda under AOB for our call today for a very brief chat about it? Cheers, CD Chris Disspain +44 7880 642456 Donuts and Afilias have rebranded to Identity Digital. identity.digital ---------- Forwarded message ---------- From: Owen Smigelski <owen.smigelski(a)namecheap.com> Date: 21 Aug 2024 at 21:21 +0100 To: Chris Disspain <chris.disspain(a)identity.digital> Subject: Outreach re: voluntary fraud grace period (FGP) > Hi Chris, > > Thanks for helping with the efforts of the voluntary fraud grace period (FGP) framework team. This was an effort within the RrSG and RySG that is now outside of ICANN. The goal is to combat domain names registered via payment fraud, which are always used for malicious purposes. > > The effort arose due to registrars exceeding AGP limits when deleting domain names used for payment fraud. Although we are still working on the details, under this framework, registrars can identify domains registered via payment fraud during a certain period (e.g. 30 days). They will return the stolen funds and receive most of the wholesale registry cost. Domains will be suspended for a period of time before being deleted, intended to reduce recidivism (as domains deleted during AGP are immediately available for re-registration). Domains flagged through the FPG will be placed on a “payment reputation list” that any participating registrar or registry can query for free as part of anti-fraud processes. > > Current participants include over a dozen registrars (including Namecheap, GoDaddy, Tucows, and Realtime Registrar) and nine registry operators (including Identity Digital, PIR, and Verisign). Nominet just joined, and we are looking to expand to other ccTLD operators. If anyone is would like more information or is interested in participating, please email me (owen.smigelski(a)namecheap.com) We are still identifying a regular meeting time, but hope to have a first draft to discuss at ICANN81. > > Thanks again! > > Regards, > > Owen

2 1

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