Hi All

Please find the rapporteurs assignments here:

https://docs.google.com/document/d/1hYrFtP3XnkWXQ1kzxnIwhf7zBuvM-Gyl0v5CiZFJoRk/edit?usp=drivesdk

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.
*******************************************

On Wed, May 28, 2025, 15:10 Joke Braeken via Ccnso-council <ccnso-council@icann.org> wrote:

NOTES | Council prep | 28 May 2025 at noon UTC



1.    Welcome 

 

By alejandra. Welcome to Nigel, who is now a member of the Council



2.            Workplan and workflow

 

Bart: I spoke with Chris, he is the new chair of the Triage committee. Next week there is a triage committee meeting, to allow the current membership to become familiar with the tools we use, and the upcoming work items. 

Under the assumption the RM will be adopted in Prague, there are several policy items coming our way, e.g. study groups, we noticed a lot of ongoing and new work. Secondly, we are at capacity from a staff perspective. May have some consequences going forward. We support about 10 WG, with the RM and study groups on top, and prep for ICANN meetings, we are over capacity. We already support 10 WG. 

Brief discussion in Prague. Prepare you for an adoption of the work plan, and to set priorities. 

Triage will meet next week.

Stephen: be careful with staff workload



3.            Next round of 360 reviews

 

Should we continue? It took a lot of effort last time. 

Jaijit: if i click on the links, i do not not see enough info

Bart: see agenda item 4

Alejandra: impression we want to continue?

Peter: thanks to those that filled out the survey. I did find it helpful. I once had such a review in the nomcom. It would be interesting to understand where/why people that make the evaluation, would, or would not be be able, to respond to certain questions. 

In favour of continuing, but perhaps we need to review the questions asked. 

Alejandra: Next week we will discuss individual evaluations. Aim is to have growth in council work



4.            Session rapporteurs 

 

See notes in https://docs.google.com/document/d/1qOTIkPqsQdlZa7S5KTTUhbnbmFfmC4BSxxCuPEKmxYM/edit?usp=sharing 

 

Alejandra: regarding RSS, Peter is requested to please coordinate with Luis Diego if Council should be made aware of anything during ICANN83, other than what is included in the regular written updates

 

Jaijit: more info on these sessions?

Alejandra: these are not ccnso sessions. The people assigned to those sessions will report back to council, if needed. In our table, we included the link to the session on the ICANN83 schedule, where you can find further info

 

Joke Read more about the ccnso schedule here: https://icann-community.atlassian.net/wiki/spaces/ccnsowkspc/pages/198410241 

Consult the ICANN83 ccNSO Session Highlights: This document outlines the ccNSO schedule for ICANN83, including session dates, times, and locations, along with agenda details. It serves as a reference for attendees to navigate the ccNSO-related meetings and discussions during the event.

https://docs.google.com/document/d/1qOTIkPqsQdlZa7S5KTTUhbnbmFfmC4BSxxCuPEKmxYM/edit?usp=sharing 



5.            AOB

 

Bart: coming soon, a follow-up with MPC Review volunteers

 

 

 

 

 

Joke Braeken

joke.braeken@icann.org

 

 

 

 

_______________________________________________
Ccnso-council mailing list -- ccnso-council@icann.org
To unsubscribe send an email to ccnso-council-leave@icann.org
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.