April 2024 - Ccnso-council - lists.icann.org

The ccNSO membership supports the ccNSO Council's recommendation to adopt the proposed ccPDP4-IDN ccTLD policy
by Joke Braeken April 19, 2024

April 19, 2024

Dear All, The ccPDP4-IDN vote is now closed: voting closed 17 April 23:59 UTC. The quorum was met, and the vote is valid. This is to inform you about the results and to thank those who voted. Vote Results At the closure of the vote, 56% of the Emissaries (97 out of 174 Emissaries) cast their vote. 97% of the votes cast were in support of the ccNSO Council recommendation to adopt the proposed ccPDP4-IDN policy. At the closure of the vote, 97 Emissaries out of 174 (56%) cast their votes: Total Ballots Cast (including duplicates): 99 Ballots Counted (excluding duplicates): 97 Voters Who Haven't Voted: 77 94 votes were in support of the ccNSO Council's recommendation to adopt the proposed policy, 3 voters did not support the recommendation. About the vote This vote was to determine whether the ccNSO membership supports the ccNSO Council's recommendation to adopt the proposed policy (part A of the Members Report) which aims to provide a framework to ICANN and the broader community for (i) the selection of IDN country code Top-Level Domain (ccTLD) strings and variants thereof, (ii) the delegation, transfer, revocation, and retirement of the selected IDN ccTLD string and its variants, (iii) the use of the review mechanism pertaining to decisions concerning the delegation, transfer, revocation, and retirement of IDN ccTLDs. Next Steps A report on the voting will be sent to the Issue Manager. The report will be included in the Draft Board Report, which - after approval by the ccNSO Council - will be submitted to the ICANN Board of Directors, as per Annex B, section 14 of the ICANN Bylaws<https://www.icann.org/resources/pages/governance/bylaws-en/#annexB>. Read more * Vote Notice<https://ccnso.icann.org/en/announcements/announcement-22mar24-en.htm> * Read the ccPDP4 frequently asked questions and answers (FAQ<https://docs.google.com/document/d/17fOE5lts0x2ILFT520i3Q_TQ1XsSyv1FggQY4eq…>). * Listen to the recording<https://community.icann.org/display/ccnsowkspc/ccNSO+Webinars> of the informative webinar held in March 2024 * Listen to the recording<https://sched.co/1a1Dg> of the ICANN79 ccPDP4 Update Session * Read the proposed policy (Members Report - Part A) here<https://ccnso.icann.org/sites/default/files/field-attached/ccpdp4-members-r…>. * Check out the ccPDP4-IDN materials<https://ccnso.icann.org/en/workinggroups/idn-cctld-strings.htm> on the ccNSO website * Go to Annex B of the ICANN Bylaws<https://www.icann.org/resources/pages/governance/bylaws-en/#annexB>, which describes the ccNSO policy development process. Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

NOTES | ccNSO Council 204 | 18 April 2024, noon UTC
by Joke Braeken April 18, 2024

April 18, 2024

NOTES | ccNSO Council 204 | 18 April 2024, noon UTC 1. Welcome and roll call Wiki: https://community.icann.org/pages/viewpage.action?pageId=320405661 a. Establish whether meeting is Quorate Yes. Bart: formal apologies fromJordan Carter, Tatiana Tropina, Sean Copeland, Wafa Dahmani b. Update Statement of Interest Peter: I now completed mine. Administrative matters 2. Relevant Correspondence<https://ccnso.icann.org/en/about/statements.htm> a. Letter from Tripti Sinha to consider input Recommendation 7 CCWG- Auction Proceeds report (Letter dated 2 March 2024) to be discussed under item 16. 3. Minutes & Action Items a. Minutes Meeting 202: Taken from transcript b. Action items Long list. Going through those that are ongoing * Council meeting 198. Establishing liaisons with GAC. For discussion during last agenda item today * Ad hoc succession planning, external roles. It is almost done. Roles and Responsibilies were adopted. What is still pending is the external appointments. Challenging in a volunteer environment. The chair and vice-chairs will review the current appointments and make suggestions to complete the roster by the May meeting. * IGLC messaging to ccTLDs regarding WSIS+20: they are working on this. Was deferred, pending ICANN action. Considered completed. Can be closed * Exclusion IRP: see item 17 on agenda. Consider this closed * GRC to review processes: board nomination process, voting process. GRC is aware. Suggestion to remove this from action list, and add as agenda items once they report back. * Future elections: 2 separate resolutions for chair and vice chair. Secretariat to add to “to do” list, for next election * World cafe: see item 19 today. * Publication notes OST session on wiki. Completed, confirms Kim Olga: regarding WSIS+20. What is happening in the ccTLD-world? Perhaps some of us are on site? Alejandra: IGLC is dealing with IG-related matters. We do not expect a report, but they gather info on what ccTLDs are doing. They are organising a session, or maybe webinars. But we do not expect a report. 4. Intermeeting decisions Triage Committee New: now they are numbered. In light of the website re-design. We will number them with the previous meeting number, followed by letters. a. 203-A Decision confirming not to participate in PIC’s/RVCs Consultation b. 203-B Actions in response to letter from Katrina Sataki and Patricio Poblete on events ICANN79. 5. Intermeeting decisions Triage Committee None Updates 6. Update ECA, IFRT & CSC (see written updates) heads-up regarding the CSC: We will be asked shortly to start the election process of a new member and alternate. Brett Carr’s 3rd and final term will end in October and we will need to select a new member. The term of the alternate is one year. Secondly, we will also need to discuss with the RySG how we want to handle the 3rd CSC review, which is supposed to start in October. Shall we put this on the agenda for our May meeting to have enough time for discussion (to prepare)? Council is in support. 7. Update WGs (written updates) a. IGLC b. GRC c. SOPC d. OISC (no meetings pending Review) e. TLD-OPS f. DASC g. Technical WG h. MPC i. UAC j. Registrant capacity ad-hoc group k. IRP Panel selection l. CCG WS 2 Implementation m. New: CIP-CCG n. Prioritization Framework group April edition of the written updates: https://docs.google.com/document/d/16HdxKIHd6H76ATQxq38KjUjrxo5c-BeTTZrG55p… 8. Update liaisons (written updates) a. Update ALAC Liaison b. Update GNSO Liaison c. Update UASG Liaison 9. Update ccNSO Website redesign High meeting frequency. Final requirement session foreseen for 8 May. As a next step, th team will prepare the wireframes based on our requirements. Stephen and Nick: good hopes. There is progress 10. Update Triage Committee a. Re-Confirmation ccNSO Purpose and Goal Statement The Triage committee requests review of the 2023 Purpose and Goal statement of the ccNSO. This statement defines the scope of the activities the ccNSO considers within its remit. The Triage Committee suggests no changes. Move? Olga Second? Chris Questions? None Adopted b. Updates portfolio of Activities 2025-2026: what to expect Nick: We were pleased with the prioritisation and activities that stood the test of time. No changes. The prioritisation is no surprise. Same priorities: the normal machinery of the ccNSO. Those activities fall into the main areas of activities by ccNSO Bart: portfolio needs to be adopted on a yearly basis. This was the first year we work with a project management tool. Deep dive is not needed, but nonetheless useful for council to have a better understanding. Suggestion is to have a working session with the council, prior to ICANN80. Present this to the membership in Kigali, and adopt the full plan at the Kigali Council meeting. Forward-looking part of the portfolio of activities itself. In time, the triage started discussing resourcing in a broad sense. That requires more prep time. That requires a deep dive into resourcing, facilitated by the Triage Committee. Needs to be in person, at its earliest in Istanbul. Nick: the 1 pager with the high level activities. Would be good to socialise that more widely. Everything we do is derived from that. Alejandra: are you considering inviting the chairs of the working groups and committees to the session where the portfolio is being developed? Nick: good point. For consideration. Alejandra: resources, some people overlap etc. there is enough time to plan, as we are doing this earliest at ICANN 81 Bart: there is the resourcing and capacity. But also, Council needs to adopt the portfolio. Suggestion to have a first run-through whats is happening in the next 2-3 years, to check if the activities are captured. The resourcing is a different type of discussion. First have the workshop prior to ICANN80, and run through what Triage is expecting in terms of activities next year. Sanity check. The next step would be the discussion regarding resourcing and capacity. 11. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat a. 1-on-1 ICANN CEO and ccNSO leadership Topics we discussed: · WSIS+20 Plenary · IDN ccPDP + UA Day + Grant Program · Policy Gap session: content + logistics Alejandra: i gave an update together with Bart to LACTLD, regarding ccPDP4. Was a good opportunity. Kim: after 9 years, I am leaving the ccNSO and the policy team, starting 1 July. Slow transition, I am moving to the meetings team. Design and production. Ensuring zero service disruption for the ccNSO. I am working with Bart and others in the policy team on the transition. Appreciate working with you. Not leaving ICANN. Alejandra: we will miss you and appreciate what you did. Chris: How dare you, after all these years ;-) Stephen: you are welcome at our ccNSO events Kim: this is recorded! Chris: depending on the number of tickets 12. Progress GAP Analysis: Preparing for Kigali Chris: Kim D started preparing a topic area list. We spent a lot of time discussing. We also looked at an experimental overview that Jordan prepared. We will be working on that in the next few weeks. Regarding the session in Kigali, over to Bart Bart: work in depth, follow-up from San Juan. What are the gaps? What is policy? Interpretation? Guidance? Incidental? And related: what are the messages to address it. Thirdly, introduce the general overview. Where to find the relevant docs and implementation info. Also, next steps. The small team runs into the limits of what can be explored without a formal mandate. Kim: That session is scheduled for Weds | 12 June 10:45-12:15 local (block 2) 13. Update and Closure 2nd Councillor 360 feed-back process Alejandra: thanks to all who completed the survey. I was one of the councillors being reviewed. I found it very useful to know how you see me. Only 12 responses. That is not much. This is a very useful tool, especially if many of us use it Olga: very useful for NomCom appointees. This completes a cycle. It is useful for Council, for the appointee and for NomCom. Chris: agree. Seems like a big task, but it does not take that long. Encourage all to participate Alejandra: soon we will have another evaluation round. Starting in July. to be reviewed: Biyi, Jordan, Nick, Demi and Pablo Ai-Chin: After I got 360 survey result, Chair and I had a half-hour talk, it was helpful to me and I now know where I can focus on improving. Administrative Matters & Decisions 14. Results Members Vote ccPDP4 The ccPDP4 vote is now closed, voting closed 17 April 23:59 UTC. The quorum was met, and the vote is valid. 56 % of the Emissaries voted. 97% of the votes cast were in support of the ccNSO Council recommendation to adopt the proposed ccPDP4-IDN policy There are no issues to report. A vote report with all observations is currently being drafted. You may expect that by end next week Alejandra: good that long processes come to a happy end. Thanks for voting Next steps * Election report coming soon * Will be included in the Board Report * Board consideration will include a public comment period, and Board will also seek GAC advice 15. Appointment Members to Committees and Working Groups, if any a. Federica Tortorella (LACTLD): observer IGLC, observer DASC. For decision Move? Olga Second? Stephen Questions regarding the resolution? None Green-red marks in Zoom Adopted 16. ccNSO Membership application Internet Society Lebanon (ISOC.LB) (.lb) We have received a ccNSO membership application from the Internet Society Lebanon (ISOC.LB) to become a member of the ccNSO. The application was reviewed, including the usual IANA review and no issues were identified with the application. Move? Demi Second? Olga Questions regarding the resolution? None Green-red marks in Zoom Adopted Substantive Matters & Decisions 17. Response to letter Tripti Sinha on amendment recommendation 7 ccWG-Auction Proceeds Alejandra: We received a letter from Tripti early March, we deferred discussion to today and we have until mid-May to respond. I propose we discuss the letter today, to set the direction of travel of our response. And we use the results of our discussion to draft a letter next week. The final letter will be signed off by the Council as always. My understanding: First part * The CCWG-AP’s Recommendation 7 sets out limitations on the use of ICANN accountability mechanisms (namely, the Independent Review Process, IRP, and Reconsideration process) to challenge decisions made on individual applications within the Grant Program. The CCWG-AP offered this recommendation to minimize use of the proceeds for purposes other than grants, such as administrative costs or legal fees. Existing ICANN accountability mechanisms such as IRP or other appeal mechanisms cannot be used to challenge a decision from the Independent Project Applications Evaluation Panel to approve or not approve an application. Applicants not selected should receive further details about where information can be found about the next round of applications as well as any educational materials that may be available to assist applicants. The CCWG recognizes that there will need to be an amendment to the Fundamental Bylaws to eliminate the opportunity to use the Request for Reconsideration and Independent Review Panel to challenge grant decisions. Chris: 2 things are related. What the Auction Process WG intended was that no-one should be able to use ICANN’s accountability mechanism, to question a decision regarding grant allocation. The issue on the current drafting of the recommendation is that the board will not only be involved in giving grants, but also overseeing the process. Changes, to ensure there is clarity on that. Alejandra: do we agree to remove that sentence? Chris: our response needs to be as a whole. The second part is to me more troubling. What the oard chose as a way forward is not something i feel comfortable with. But i agree with changing the principle of the first part (removing it) Alejandra: no harm in removing it, the first part. Second part * Full implementation also requires the ICANN Empowered Community to approve the Fundamental Bylaws Amendments to Article 4, Section 4.1 of the ICANN Bylaws. That proposed amendment, initiated by the Board: https://www.icann.org/en/public-comment/proceeding/proposed-bylaws-updates-… (27.Feb - 15.Apr) https://itp.cdn.icann.org/en/files/governance/proposed-updates-to-article-4… The amendment creates a procedure for the ICANN community to limit or make unavailable the Reconsideration Request process or the Independent Review Process (IRP) set forth at Article 4, Sections 4.2 and 4.3 of the ICANN Bylaws. If a community recommendation is made through the proposed process, and the Board approves that recommendation, the implementation of any limitation can then occur without requiring a specific Fundamental Bylaws Amendment process to embed that change within the ICANN Bylaws. The proposed threshold for establishing broad community support is that all three of the following conditions be met: The recommendation for use of the amendment stems from a Cross-Community Working Group chartered by at least five of the seven Supporting Organizations and Advisory Committees (SO/ACs). At least four of the CCWG’s chartering SO/ACs are Decisional Participants within the Empowered Community. Each of the chartering SO/ACs approves the CCWG’s recommendation to limit or restrict access to one or more of the Accountability Mechanisms. Alejandra: I have my concerns. But first i want to hear your input Chris: it is clear that the recommendation from the CCWG AP involved a bylaw change. Was suggested. Could be dealt with in T&C. But that meant that only applicants would be blocked from using the accountability mechanisms. Not other community members. Hence the bylaw change. Difficult process for changing the bylaws. But this would mean that in future you could change the bylaws, if a CCWG recommended it, without needing to go through with the restructng of ICANN with the empowered community. The only way the change should be possible: if there is a consensus reached by a cross-community group. A bylaw change group. Fundamentally flawed as a process, whilst it makes sense. Follow the existing process, to make that change. We agree the bylaw should be changed, but we do not agree to introduce a new process to make those changes. Alejandra: Not sure I understood it that way. Public comment as a test regarding what the community wants? We want to do this, and we want to know whether you like us to do this Chris: agree. There needs to be a more enrolled and developed process before it goes to a vote by the ECA. ccNSO is talking about it, but in silos. Change of a fundamental bylaw. Should be taken in a process with consultation with all parts of the community Alejandra: the discussion would happen when the bylaw process starts. There can be a community forum, as part of the process of the approval action Bart: are you suggesting that the initial steps through this letter by the board lack process? This was discussed by ccnso and board: what are the triggers for changing fundamental bylaws? Chris: i think the change for the AP should be done. Do not deal with that at a meta-level. Also, the actual concept is flawed: it should not be possible for a PDP or a CCWG to come up with a recommendation to have a bylaw change, without going through the appropriate process. Removing the checks and balances is a bad idea. Summary: yes to the AP, no to the bylaw change Bart: what is the alternative? Chris: the removal of the thing the board asked us, is right. We need to get a doc up and start drafting a possible response. That will make it easier for all to understand. Alejandra: will do. We are discussing 2 things * Process that led the board to suggest the bylaw change. Was discussed previously with board. No process. How does a fundamental bylaw change start? Related strictly to the process * The proposed bylaw change. If any other CCWG wants to restrict these accountability mechanisms, the bylaw would already address that. But there is terminology that is not defined in the bylaws. Peter: The letter seems not to be available on the ‘statements’ wiki page as linked from the PDF agenda? Chris: If anyone can put forward a by-law change suggestion and that then triggers the empowered community process that is not a good thing…. our job is not to make things easy but rather to have a predictable defined process even if it is not easy Alejandra: there are 3 parts * Request in the letter: remove text from recommendation. Yes to that * They proposed a bylaw amendment * The process on how the bylaw amendments are being done Bart: let’s have a small team that prepares a draft, which will be circulated to council afterwards Volunteers? Olga, Chris, Alejandra Peter: https://www.icann.org/en/system/files/correspondence/sinha-to-clemente-et-a… 18. Results OISC review The OISC review team has concluded its review and suggested, based on its findings, to change and limit the mandate of the OISC focusing on organising mentoring and on-boarding. I note that mentoring and on-boarding were also topics which emerged as priorities from the two world cafe session on making the ccNSO future proof. Move? Jenifer Second? Ali Questions or comments regarding the resolution? None Green-red marks in Zoom Adopted 19. Discussion and decision on next steps outcome world cafés on keeping the ccNSO relevant next 7 years In March we adopted the following process review and act upon the outcomes of the world cafes on keeping the ccNSO relevant: * Step 1 - Some suggestions and topics are already within the remit of the working groups and committees, whether explicitly or emerging as a topic. Therefore it is suggested that first the Council assesses whether each and any of the suggestions is within the remit of the ccNSO and its strategic purpose. * Step 2 - If a suggestion is within the remit of the ccNSO, the Council needs to determine whether the suggestion is within scope of the ccNSO Council or one of the existing ccNSO committees or working groups. If so, the group will need to be informed and should be asked to consider if and how it intends to include it as a work item, and report back to the community through the Council. * Step 3 - If a suggestion is not within the scope of the Council, a committee or working group, the Council is expected to consider whether it needs to be further explored and included in the portfolio of the ccNSO. * Step 4 - The Council is advised to report back to the community if and how the various suggestions have been incorporated in the portfolio of activities of the ccNSO. In preparation for this meeting staff have compiled an overview of all actions and a suggestion for assessment. Bart briefly explains the document. Alejandra: do you like the proposal Only green ticks in Zoom Alejandra: let’s have a small team that completes the assessment and presents the results at the next Council meeting. Do you like the idea? Green ticks Volunteers? None Alejandra: Let's take that offline. Bart: I will circulate an email to the council, asking for volunteers. Alejandra: will not be too time-consuming to complete. 20. ccNSO relevant meetings ICANN80 (10-13 June 2024) Alejandra talks to the proposed block schedule The joint meeting with GAC might be deferred to ICANN 81. The policy forum schedule is full, and it is a short meeting. Also, the GAC will have the HLGM. good idea nonetheless to bring GAC up to speed - perhaps at ICANN 81- , also seen by the new GAC members, what the ccNSO is doing. Chairs of the various WG /Committee provide an overview of the work of the ccNSO in other areas that might be of interest to the GAC and GAC members, and identify areas for future bilateral meetings and/or capacity building. To be confirmed. No ccNSO Cocktail at ICANN80. There will be an alternative program. Currently still work in progress, and more clarity to follow. Alejandra further speaks to the proposed sessions at ICANN80. a. Prep week ICANN80: 28-30 May 2024 b. Prep Council meetings i.Working session (conference call)? Topic: July 2025-June 2027 portfolio of activities and combine with prep session Invite the chairs and vice-chairs ii. Prep session Possible dates 23 or 30 May (any preference), note regular council meeting 16.May c. Joint Meetings i.Meeting with GAC: need for topics Suggestion to date: awaiting response from GAC ii. Virtual meeting GNSO Council - 11 July 2024 13:00 UTC d. Special Event: Tuesday 11 June 2024- block 5 e. Tentative Block Schedule Alejandra: we need to meet prior to Kigali. Topics: prep for the council meeting and other sessions at ICANN80, and discuss the ccNSO Council portfolio. We will email possible suggested dates, and you can express your preference. 23 or 30 May 21. AOB Alejandra: Katrina's heads up on the analysis of sections 2-6 of the ccPDP Review Mechanism Board Report. As we heard at the Q&A in San Juan and from the update, we will receive two set of questions: * Questions for clarification: what was meant * Request to confirm the interpretation of a recommendations It is my understanding that we can expect the questions next week. A few observations: * It is a new procedure for all of us (ccNSO, ICANN org, Board) * We are talking about ccNSO recommendations: recommendations approved initially by the working group, then the Council and finally by the membership * Currently the Council is looking at related matters through the policy gap ad-hoc group * We need careful consideration how we want to handle it We can discuss how to handle the questions at our next meeting (16 May) or have an extraordinary call before (for example in two weeks - 2 May) However, we don’t have the question yet. This was not an item on today’s agenda, since there was no time to prepare Alejandra: I will follow up via email. This meeting is over time. 22. Next Council Meetings · May 16 – 21:00 UTC (205) · June 13 @ICANN80 (206) – time TBD · July 18 – 12:00 UTC (207) · August 22 (208) – 18.00 UTC (208), may be deferred · September 19 – 12:00 UTC (209) · October 17 – 21:00 UTC (210) · November 14 @ICANN80 – (211) – time TBD · December 12 – 12:00 UTC (212) · January 16, '25 - 18:00 UTC (213) · February 13, '25 - 12:00 UTC (214 23. Adjourn Thank you all, bye. Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Agenda and Draft Resolution
by Bart Boswinkel April 18, 2024

April 18, 2024

Dear all, Please find included the agenda and draft resolutions for the upcoming Council meeting #204, Please note that the link to the background material for item 10 a (Purpose and Goal Statement ccNSO) is included in the agenda overview. The other background material was already circulated. Kind regards, Bart ------ Draft Agenda ccNSO Council Meeting 204 18 April 2024, noon UTC 1. Welcome and roll call * Establish whether meeting is Quorate * 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 1. Relevant Correspondence<https://ccnso.icann.org/en/about/statements.htm> * Letter from Tripti Sinha to consider input Recommendation 7 CCWG- Auction Proceeds report (Letter dated 2 March 2024) to be discussed under item 16. 1. Minutes & Action Items * Minutes Meeting 202: Taken from transcript * Action items ● 198-08: Liaison to GAC to follow up regarding virtual joint meeting (Ongoing, pending appointment liaison from GAC) ● 199-07: Council ad-hoc to report on succession planning external roles and responsibilities by ICANN79 (Ongoing, not completed) ● 200-03: IGLC is requested to gather information on what cc’s are doing in respect to WSIS and provide simpler/more targeting messaging to the ccTLDs. (Deferred post ICANN79, after presentation ICANN communication plan WSIS+20) ● 201-03: Staff to monitor how discussion re exclusion of IRP through contractual arrangement or Bylaw change evolves. (Ongoing, staff update) ● 201-05: GRC to review recommendations Board Nomination Process manager as included in Board Seat 12 election report. (Ongoing) ● 202-05: GRC to add anonymity voting and voting process as item to harmonisation of Guidelines (Ongoing) * 203-01: Create ccNSO-RySG mailing list, continue bilateral discussions. (Completed, ccNSO Leadership and Nick, Chris, David M and Fernando España) * 203-02: Assign and unofficial liaison ccNSO-RrSG (Completed, ccNSO Leadership and Chris, Sean & Wafa) * 203-03: Regarding Council chair election, the Secretariat is requested to inform the ICANN secretary accordingly and post an announcement on the ccNSO Website. (Completed) * 203-04: Regarding Council vice chair election, the Secretariat is requested to inform the ICANN secretary accordingly and post an announcement on the ccNSO Website. (Completed) * 203-05: For future elections, ccNSO Council consider two separate resolutions for vice-chair appointments (To be revisited by February 2025). * 203-06: Secretariat to publish the roles and responsibilities overview on the website as soon as possible. (Completed) * 203-07: The secretariat to Inform the WG members and broader community of adoption of both the ccPDP4 proposed policy and advice to ccTLD Managers (Completed) * 203-08: The voting process manager to initiate the members vote on the recommended ccPDP4 policy by 17 April 2024. (Completed) * 203-09: The ccPDP4 issue manager is requested to compile the Members Report and circulate it to the members prior to the start of the members vote. (Completed) * 203-010: ccNSO Council to implement suggestions from the world café sessions (To start, with mapping, see agenda item 19) * 203-011: GRC to experiment and test proposed continuous improvement methods (Completed, GRC informed, included in work plan) * 203-12: Publish rough notes from OST sessions on ccNSO wiki (Pending) * 203-13: GAP analysis group to continue its work and report to Council regularly (Completed, Ad-hoc group informed, topic on agenda, item 12) * 203-14: ccNSO Council to draft letter regarding deferral of ATRT4 (Completed) 1. Intermeeting Decisions (since meeting 203, March 2024) * 203-A Decision confirming not to participate in PIC’s/RVCs Consultation * 203-B Actions in response to letter from Katrina Sataki and Patricio Poblete on events ICANN79. 1. Intermeeting decisions Triage Committee The Triage Committee has made no decisions since meeting 202. Updates 1. Update ECA, IFRT & CSC (see written updates) 1. Update WGs (written updates) * IGLC * GRC * SOPC * OISC (no meetings pending Review) * TLD-OPS * DASC * Technical WG * MPC * UAC * Registrant capacity ad-hoc group * IRP Panel selection * CCG WS 2 Implementation * New: CIP-CCG * Prioritization Framework group 1. Update liaisons (written updates) * Update ALAC Liaison * Update GNSO Liaison * Update UASG Liaison 1. Update ccNSO Website redesign Informational 1. Update Triage Committee For Information & Decision * Re-Confirmation ccNSO Purpose and Goal Statement For decision The Triage committee requests review of the 2023 Purpose and Goal statement of the ccNSO. This statement defines the scope of the activities the ccNSO considers within its remit. The Triage Committee suggests no changes. Draft Resolution Decision The ccNSO Council adopts and reconfirms the 2023 ccNSO Purpose and Goals statement (https://ccnso.icann.org/sites/default/files/field-attached/purpose-goals-31…) , and request the secretariat to adjust the approval date to April 2024. This decision becomes effective seven (7) days after publication. * Updates portfolio of Activities 2025-2026: what to expect 1. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat * 1-on-1 ICANN CEO and ccNSO leadership 1. Progress GAP Analysis: Preparing for Kigali 1. Update and Closure 2nd Councillor 360 feed-back process Administrative Matters & Decisions 1. Results Members Vote ccPDP4 Informational & Next steps 1. Appointment Members to Committees and Working Groups, if any * Federica Tortorella (LACTLD): observer IGLC, observer DASC. For decision Draft Resolution Decision The ccNSO Council appoints Federica Tortorella (LACTLD) as observer to the IGLC, and observer to the DASC. The secretariat is requesed to inform the leadership of both groups and Federica. This decision becomes effective upon its publication. 1. ccNSO Membership application Internet Society Lebanon (ISOC.LB) (.lb) For Approval Draft Resolution Decision The ccNSO Council approves the ccNSO membership application of the Internet Society Lebanon (ISOC.LB) to become member of the ccNSO and welcomes ISOC.LB as member 177 of the ccNSO. The chair is requested to inform ISOC.LB and ccNSO membership. This decision becomes effective upon publication. Substantive Matters & Decisions 1. Response to letter Tripti Sinha on amendment recommendation 7 ccWG-Auction Proceeds For discussion. 1. Results OISC review For discussion and decision The OISC review team has completed its report, and suggest based on its findings to maintain the OISC, however with a clear and far more limited mandate of activities. As a result the Travel Funding Committee will stay independent from OISC, as well as fellowship selection. Draft Resolution Background The ccNSO OISC review team completed its work and has submitted its final report to Council. The review team suggests that the mandate of the OISC as currently stated in its Terms of Reference will be limited and the group focuses on mentoring and on-boarding. Decision The ccNSO Council adopts the final report of the review team, and thanks the team wholeheartedly for its work. The ccNSO Council supports the recommendation to limit the remit and scope of activities of the OISC and request the secretariat to suggest new Terms of Reference by meeting 205 of the ccNSO Council (May 2024). This decision becomes effective seven (7) days after publication. 1. Discussion and decision on next steps outcome world cafés on keeping the ccNSO relevant next 7 years For Information & discussion 1. ccNSO relevant meetings ICANN80 ( 10 – 13 June 2024) * Prep week ICANN80: 28 -30 May 2024 * Prep Council meetings * Working session (conference call)? * Prep session: * Joint Meetings * Meeting with GAC: need for topics Suggestion to date: awaiting response from GAC * Virtual meeting GNSO Council - 11 July 2024 13:00 UTC * Special Event: Tuesday 11 June 2024- block 5 * Tentative Block Schedule 1. AOB 1. Next Council Meetings * May 16 – 21:00 UTC (205) * June 13 @ICANN80 (206) – time TBD * July 18 – 12:00 UTC (207) * August 22 (208) – 18.00 UTC (208), may be deferred * September 19 – 12:00 UTC (209) * October 17 – 21:00 UTC (210) * November 14 @ICANN80 – (211) – time TBD * December 12 – 12:00 UTC (212) * January 16, '25 - 18:00 UTC (213) * February 13, '25 - 12:00 UTC (214 1. Adjourn

4 3

Re: [ccnso-council] April ccNSO Council Teleconference (204) | 18 April at 12:00 UTC
by Kimberly Carlson April 18, 2024

April 18, 2024

***STARTING IN ONE HOUR*** From: claudia.ruiz(a)icann.org When: 6:00 AM - 7:30 AM April 18, 2024 Subject: [ccnso-council] April ccNSO Council Teleconference (204) | 18 April at 12:00 UTC Location: https://icann.zoom.us/j/98347940551?pwd=R1ZLSzZ1cDZxdmRnWTF0d0RyeHV4QT09 Dear Council, The April ccNSO Council Teleconference (204) is scheduled for 18 April at 12:00 UTC. The agenda will be circulated prior to the call. Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/98347940551?pwd=R1ZLSzZ1cDZxdmRnWTF0d0RyeHV4QT09 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/98347940551?pwd=R1ZLSzZ1…> Meeting ID: 923 4208 4426 Passcode: ccNSO-0204 Wiki page: https://community.icann.org/x/nQAZEw

1 0

Call for Presentation Proposals: ICANN80 ccTLD News Session
by Joke Braeken April 18, 2024

April 18, 2024

Dear ccTLD Community Members, We are pleased to announce the call for presentation proposals for the upcoming ccTLD News Session, scheduled to take place during the ICANN80 Policy Forum, held 10-13 June in Kigali, Ruanda. This session aims to provide updates, share insights, and facilitate discussions on topics relevant to country code top-level domains (ccTLDs) and their operations. The ccTLD News Sessions have been a part of the ccNSO Members Meetings for several years and have provided a global platform for both experienced and new people to meet, share experiences and discuss ccTLD-related aspects. PRESENTATION TOPICS | This is a session for and by ccTLDs. We invite proposals for presentations on the following topics (but not limited to): * Case studies showcasing ccTLD initiatives * ccTLD collaboration and partnerships * Recent developments and updates within the ccTLD community * Policy or legislative initiatives impacting ccTLD operations * Practices in registry management, marketing, and community engagement The session will allow for both in-person and virtual participation. Simultaneous interpretation will be available for selected ccNSO sessions during the upcoming ICANN Public Meeting, including the ccTLD News Session. Participants will be able to select the language they wish to speak or listen to in Zoom. Languages available will be Arabic, English, French or Spanish. SUBMISSION GUIDELINES | Presentation proposals should include a title, abstract (few sentences), and the name, ccTLD affiliation and contact details of the presenter. SUBMISSION DEADLINE | Please submit your presentation proposals no later than 8 May 2024 (23:59 UTC) via https://forms.gle/TNefyANLGJq19wm17 SELECTION PROCESS | Proposals will be reviewed by the ccNSO Meetings Programme Committee (MPC) based on overall contribution to the objectives of the ccTLD News Session, taking into consideration the limited number of speaking slots. The MPC embraces diversity, including among others in terms of experiences and regional affiliation. Following conclusion of the MPC deliberations, all applicants will be notified by 17 May 2024, COB. All presenters will receive a briefing paper outlining role, scope, etc. All session presenters will be invited to attend an informational pre-session meeting and a rehearsal session closer to the meeting. BENEFITS OF PRESENTING | * Showcase your expertise and thought leadership within the ccTLD community * Engage with fellow ccTLD operators, industry experts, and stakeholders * Contribute to the advancement of best practices and knowledge sharing for and by ccTLDs * Gain visibility and recognition for your ccTLD or initiative CONTACT INFORMATION | For inquiries, please contact joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> The MPC looks forward to receiving your proposals and hosting an informative ccTLD News Session! Sincerely, Everton T. Rodrigues (MPC Chair) Gudrun Poulsen (MPC Vice Chair) Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Join IGLC on 8 May, noon UTC: African Union (AU) Data Policy Framework
by Joke Braeken April 17, 2024

April 17, 2024

Dear All, You are cordially invited to attend the next meeting of the ccNSO Internet Governance Liaison Committee (IGLC), held on Wednesday, 8 May 2024 at 12:00 UTC. This session aims to inform ccTLDs globally and other interested stakeholders about the African Union Data Policy Framework. Please feel free to extend this invitation to others who may be interested. IGLC is proud to welcome Ms Sadia Rizvi<https://www.ppmattorneys.co.za/team-members/sadia-rizvi/> as guest speaker, to speak about the African Union Data Policy Framework. Ms Rizvi is an Associate at PPM Attorneys, specialised in information and communications technology law, intellectual property law, media law, data privacy, and compliance. PPM Attorneys – based in Johannesburg, South Africa – is a boutique commercial law firm that provides a wide range of legal services focusing on information and communications technology (ICT), marketing and advertising and infrastructure related to these sectors. The second half of this one-hour session will focus on IGLC actions in relation to the World Summit on the Information Society 20 Year Review (WSIS+20) and IGLC session planning for ICANN80. JOIN ZOOM MEETING https://icann.zoom.us/j/98310419302?pwd=QVlBOGtuSGtyeThINzJkWm0vT3pLUT09 Meeting ID: 983 1041 9302 | Passcode: UFY1J@4Fs$ Passcode: 6785791650 (phone only) Find your local number: https://icann.zoom.us/u/acHMZnwCUS A calendar invite is enclosed. Recordings will be posted on the IGLC workspace: https://community.icann.org/x/iIHcEQ On behalf of IGLC Chair Annaliese Williams (.au), and Vice Chair Marta Dias (.pt), we look forward to welcoming you to the session. Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> ABOUT IGLC | The IGLC has been established to coordinate, facilitate, and increase the participation of ccTLD managers in discussions and processes pertaining to Internet Governance. Membership of the Committee is open to all ccTLD managers (whether members of the ccNSO or not). Currently, the committee counts approximately 30 members from ccTLDs all over the world. Read more: https://ccnso.icann.org/en/workinggroups/iglc.htm ABOUT IGLC’S FOCUS ON AFRICA SESSIONS | The 8 May 2024 IGLC meeting will be the second opportunity for the IGLC to focus on Africa and explore issues of relevance to ccTLDs from the region and potentially ccTLDs globally. During the 3 April 2024 meeting, IGLC welcomed Khodani Sengwane (Faculty of Law, Pretoria University) as a guest speaker on the topic of “Digital Tax from the perspective of Africa”. The recording of the 3 April session is available here: https://community.icann.org/x/goHcEQ Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Final reminder | ccPDP4-IDN: have you voted?
by Joke Braeken April 16, 2024

April 16, 2024

Dear ccNSO Emissaries, dear All, This is a final reminder to cast your ballots in the ongoing ccPDP4 vote. Voting closes tomorrow, on Wednesday, 17 April 2024 (23:59 UTC). Read more: https://ccnso.icann.org/en/announcements/announcement-22mar24-en.htm Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> From: Ccnso-members <ccnso-members-bounces(a)icann.org> on behalf of "ccnso-members(a)icann.org" <ccnso-members(a)icann.org> Reply to: Joke Braeken <joke.braeken(a)icann.org> Date: Friday, 12 April 2024 at 11:38 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org> Cc: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-members] ccPDP4-IDN: have you voted? Dear All, With just a few days left until the vote deadline, we need at least 5 additional votes to ensure the passing of the ccPDP4-IDN vote [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/announcements/announc…>. Your individual vote holds significance in determining the outcome. Voting closes next week, on Wednesday, 17 April 2024 (23:59 UTC). Status on Friday, 12 April 2024, 09:00 UTC * Total Ballots Cast (including duplicates): 83 * Ballots Counted (excluding duplicates): 82 * Voters Who Haven't Voted: 92 * Per region, percentage of Emissaries who have cast their vote: Africa: 37% Asia/Australia/Pacific: 44% Europe: 55% Latin America/Caribbean: 48% North America: 67% Thank you for your attention to this matter. Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> From: Ccnso-members <ccnso-members-bounces(a)icann.org> on behalf of "ccnso-members(a)icann.org" <ccnso-members(a)icann.org> Reply to: Joke Braeken <joke.braeken(a)icann.org> Date: Tuesday, 9 April 2024 at 14:46 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org> Cc: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-members] ccPDP4-IDN: have you voted? Dear All, This is another reminder to please vote: at least 13 additional votes are needed for this vote to pass. The deadline for voting is next week, on Wednesday, 17 April 2024 (23:59 UTC). Status on 9 April 2024, 12:30 UTC = = = Total Ballots Cast (including duplicates): 74 Ballots Counted (excluding duplicates): 74 Voters Who Haven't Voted: 100 = = = The vote determines whether the ccNSO membership supports the ccNSO Council recommendation to adopt the proposed ccPDP4-IDN ccTLD policy. Read the vote notice [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/announcements/announc…> and the ccPDP4 frequently asked questions and answers [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/17fOE5lts0x2I…> to learn more. For approval by the ccNSO membership, at least 50% of the ccNSO Emissaries must vote and at least 66% of those votes must be in favour of the ccNSO Council recommendation. The ccNSO counts 174 Emissaries. Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of ccnso-council <ccnso-council(a)icann.org> Reply to: Joke Braeken <joke.braeken(a)icann.org> Date: Thursday, 4 April 2024 at 14:24 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org> Cc: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] Reminder to please vote (ccPDP4-IDN) Dear All, This is a reminder about the current ccPDP4 Members vote, and an invitation to please cast your vote. The vote determines whether the ccNSO membership supports the ccNSO Council recommendation to adopt the proposed ccPDP4-IDN ccTLD policy. VOTE START | Wednesday, 27 March 2024 (00:01 UTC) VOTE DEADLINE | Wednesday, 17 April 2024 (23:59 UTC) = = = Total Ballots Cast (including duplicates): 58 Ballots Counted (excluding duplicates): 58 Voters Who Haven't Voted: 116 Your participation in this vote holds significant weight! While the policy may not immediately impact your ccTLD, it paves the way for non-Latin script country code Top Level Domains and their variants to be accessible for domain name registration. Approval of the recommended IDN ccTLD Policy by the ccNSO membership is pivotal, as it will then be presented to the ICANN Board of Directors for their deliberation. For approval by the ccNSO membership, at least 50% of the ccNSO Emissaries must vote and at least 66% of those votes must be in favour of the ccNSO Council recommendation. Your thoughtful deliberation on these matters is deeply appreciated. LEARN MORE * Vote notice: https://ccnso.icann.org/en/announcements/announcement-22mar24-en.htm [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/announcements/announc…> * Read the ccPDP4 frequently asked questions and answers (FAQ [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/17fOE5lts0x2I…>). * Join the informative webinars on Tuesday, 26 March 2024 [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/announcements/announc…>, or consult the recordings<https://community.icann.org/x/HBwFBQ> * Listen to the recording [sched.co]<https://urldefense.com/v3/__https:/sched.co/1a1Dg__;!!PtGJab4!-JmLqoHFjngNz…> of the ICANN79 ccPDP4 Update Session * Read the proposed policy (Members Report - Part A) here [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/fiel…>. * Keep an eye out for the announcements on the ccNSO members mailing list and website * Check out the ccPDP4-IDN materials [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/workinggroups/idn-cct…> on the ccNSO website * Go to Annex B of the ICANN Bylaws<https://www.icann.org/resources/pages/governance/bylaws-en/#annexB>, which describes the ccNSO policy development process. Thank you. Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Background materials council meeting 204 on 18 April 2024 (items 6, 7, 10)
by Joke Braeken April 16, 2024

April 16, 2024

Dear Councillors. Item 6, 7 and 10 on the upcoming Council meeting agenda (Meeting 204 on 18 April 2024) relates to updates by the ccnso working groups, committees and groups with ccNSO relevance. Please find the draft written updates here: https://docs.google.com/document/d/16HdxKIHd6H76ATQxq38KjUjrxo5c-BeTTZrG55p… Note that the document is still in draft, and might be subject to changes between now and the Council meeting itself. If you note your name associated with any of the sections, please review the proposed content and include edits or confirm whether you are fine with the suggestions. Thank you very much! Best regards. Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

2 2

Fwd: Heads-up
by Alejandra Reynoso Barral April 15, 2024

April 15, 2024

Dear Councillors Please find below Katrina's update on the analysis of sections 2-6 of the ccPDP Review Mechanism Board Report. Best regards, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* ---------- Forwarded message --------- From: Katrina Sataki <katrina(a)nic.lv> Date: Fri, Apr 12, 2024 at 5:48 PM Subject: Heads-up To: Alejandra Reynoso Barral <alejandra.reynoso(a)gmail.com>, Patricio Poblete <ppoblete(a)nic.cl> Dear Alejandra, As we reported to you earlier, after closure of the Bylaw required Public Comment and requesting GAC advice - the Caucus support staff started an in-depth analysis of Sections 2-6 of the Board report as part of the assessment of the feasibility of implementation of the ccPDP Review Mechanism. The objective of the analysis is to ensure that the understanding and interpretation of the proposed policy is unambiguous and aligns with the intentions of the ccNSO. This analysis is nearly completed and we expect to send you the request for additional information in the week of 22-26 April 2024. The additional information is sought using two types of questions: • Requests for confirmation: The purpose of these requests is to seek confirmation from the ccNSO that ICANN’s understanding and/or interpretation of a specific text is correct and aligns with what the ccNSO intended. • Requests for clarification: The purpose of these requests is to seek further information or clarification from the ccNSO on a specific topic that is not clear from the language of the CCRM Policy. The additional information is needed to assess whether implementation of the proposed review mechanism is feasible and/or what modifications may be needed in order for it to be feasible. In the meantime, if you have any questions on this topic, please do not hesitate to reach out to any of us! Kind regards ]{atrina

1 0

Item 18 Council meeting 204
by Bart Boswinkel April 15, 2024

April 15, 2024

Dear all, Please find included background material agenda item 18 of the agenda for the upcoming Council meeting 204. Topic: review of the OISC. The recommendation of the Review Team is to “disbanden the OISC in its current format be disbanded, but we are very concerned to ensure that the mentoring of new and prospective community members is not lost as a valuable activity. Either ccNSO community leaders (including all council members) should all collectively take up the slack with a mentoring programme, or perhaps a specific mentoring initiative to build up a pipeline of future ccNSO participants should be curated, with the objective of ensuring the passing over of ccNSO know-how and history to those who will hold leadership roles in the future.” Kind regards, Bart

1 0