- Ccnso-leadership - lists.icann.org

9 May deadline | Draft ccNSO response to the “How We Meet” request for comments
by Joke Braeken May 8, 2025

May 8, 2025

Hello All, The council leadership team met earlier today, and discussed the “how we meet” ccNSO response. Since @Jodi Anderson<mailto:jodi@internetnz.net.nz> is currently on vacation, here is a revised timeline: * Friday, 9 May (end of day in New Zealand): deadline for comments by the drafting team * Friday, 9 May (AM European time): Secretariat sends the draft response to community and Council * Tuesday, 13 May (23:59 UTC): deadline for Council comments * Thursday, 15 May: Council Meeting 217. Council adopts the ccNSO Council response * Friday, 16 May: ccNSO response is submitted * Monday, 19 May 2025 | 23:59 UTC: public comment closes Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> From: Joke Braeken <joke.braeken(a)icann.org> Date: Monday, 5 May 2025 at 18:04 To: Jodi Anderson <jodi(a)internetnz.net.nz>, Molehe Wesi <molehe(a)zadna.org.za>, Pablo Rodriguez <pablo(a)nic.pr> Cc: Bart Boswinkel <bart.boswinkel(a)icann.org>, Claudia Ruiz <claudia.ruiz(a)icann.org>, "ccnso-leadership(a)icann.org" <ccnso-leadership(a)icann.org> Subject: REMINDER | Please review by 6 May, COB | draft ccNSO response to the “How We Meet” request for comments Hello @Jodi Anderson<mailto:jodi@internetnz.net.nz>, @Molehe Wesi<mailto:molehe@zadna.org.za>, @Pablo Rodriguez<mailto:pablo@nic.pr>, All Here is a reminder to please review the draft responses to the “How We Meet” request for comments. https://docs.google.com/document/d/141FfWTZFaPhUDSd1cAmQSN8Xt2VEtczbdH15t5U… Timeline: * Tue, 6 May, COB: Drafting team reviews and refines the draft response * Wed, 7 May: Draft response is sent to Council for review and input * Fri, 9 May: deadline Council input * Mo, 12 May: draft response shared with ccTLD community * Thu, 15 May: final opportunity to discuss during Council Meeting 217 * Fri, 16 May: ccNSO response is submitted * 19 May 2025 | 23:59 UTC: public comment closes Background: https://docs.google.com/document/d/1ALuqeeO0_5NYU3FWjfkwYsg-YVR2_CVlvfxPEX_… Thank you Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> From: Joke Braeken <joke.braeken(a)icann.org> Date: Tuesday, 29 April 2025 at 16:32 To: Jodi Anderson <jodi(a)internetnz.net.nz>, Molehe Wesi <molehe(a)zadna.org.za>, Pablo Rodriguez <pablo(a)nic.pr>, Alejandra Reynoso Barral <alejandra.reynoso(a)gmail.com> Cc: Bart Boswinkel <bart.boswinkel(a)icann.org>, Claudia Ruiz <claudia.ruiz(a)icann.org> Subject: Please review by 7 May latest | draft ccNSO response to the “How We Meet” request for comments Hello Jodi, Molehe, Pablo and Alejandra I have contacted you regarding the draft ccNSO response to the “How We Meet” request for comments. First and foremost, thank you for joining the drafting team. Here is a call to action for you. Based on the notes of the special ccNSO Council meeting (see here<https://docs.google.com/document/d/1_jEO_FJ8A2oPogd3DSX1s5ZWZ6aCjfInTcA67gt…>), I started a (very preliminary) draft of the responses, taking into account the input template, and the character limitations. Could you please have a look at the draft, adjust the proposed rationale where needed, and complete the missing answers? See here: https://docs.google.com/document/d/141FfWTZFaPhUDSd1cAmQSN8Xt2VEtczbdH15t5U… May I suggest Tuesday, 6 May 2025 (COB) as a deadline for doing so? This would allow Council to review the draft response. The idea was to also circulate the ccNSO Council response to the broader ccTLD community. Note: I did not have a chance to draft the rationale for all questions yet, and a second reading is missing too. Background materials and relevant links are here: https://docs.google.com/document/d/1ALuqeeO0_5NYU3FWjfkwYsg-YVR2_CVlvfxPEX_… Thank you. Best regards. Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 1

REMINDER | Please review by 6 May, COB | draft ccNSO response to the “How We Meet” request for comments
by Joke Braeken May 5, 2025

May 5, 2025

Hello @Jodi Anderson<mailto:jodi@internetnz.net.nz>, @Molehe Wesi<mailto:molehe@zadna.org.za>, @Pablo Rodriguez<mailto:pablo@nic.pr>, All Here is a reminder to please review the draft responses to the “How We Meet” request for comments. https://docs.google.com/document/d/141FfWTZFaPhUDSd1cAmQSN8Xt2VEtczbdH15t5U… Timeline: * Tue, 6 May, COB: Drafting team reviews and refines the draft response * Wed, 7 May: Draft response is sent to Council for review and input * Fri, 9 May: deadline Council input * Mo, 12 May: draft response shared with ccTLD community * Thu, 15 May: final opportunity to discuss during Council Meeting 217 * Fri, 16 May: ccNSO response is submitted * 19 May 2025 | 23:59 UTC: public comment closes Background: https://docs.google.com/document/d/1ALuqeeO0_5NYU3FWjfkwYsg-YVR2_CVlvfxPEX_… Thank you Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> From: Joke Braeken <joke.braeken(a)icann.org> Date: Tuesday, 29 April 2025 at 16:32 To: Jodi Anderson <jodi(a)internetnz.net.nz>, Molehe Wesi <molehe(a)zadna.org.za>, Pablo Rodriguez <pablo(a)nic.pr>, Alejandra Reynoso Barral <alejandra.reynoso(a)gmail.com> Cc: Bart Boswinkel <bart.boswinkel(a)icann.org>, Claudia Ruiz <claudia.ruiz(a)icann.org> Subject: Please review by 7 May latest | draft ccNSO response to the “How We Meet” request for comments Hello Jodi, Molehe, Pablo and Alejandra I have contacted you regarding the draft ccNSO response to the “How We Meet” request for comments. First and foremost, thank you for joining the drafting team. Here is a call to action for you. Based on the notes of the special ccNSO Council meeting (see here<https://docs.google.com/document/d/1_jEO_FJ8A2oPogd3DSX1s5ZWZ6aCjfInTcA67gt…>), I started a (very preliminary) draft of the responses, taking into account the input template, and the character limitations. Could you please have a look at the draft, adjust the proposed rationale where needed, and complete the missing answers? See here: https://docs.google.com/document/d/141FfWTZFaPhUDSd1cAmQSN8Xt2VEtczbdH15t5U… May I suggest Tuesday, 6 May 2025 (COB) as a deadline for doing so? This would allow Council to review the draft response. The idea was to also circulate the ccNSO Council response to the broader ccTLD community. Note: I did not have a chance to draft the rationale for all questions yet, and a second reading is missing too. Background materials and relevant links are here: https://docs.google.com/document/d/1ALuqeeO0_5NYU3FWjfkwYsg-YVR2_CVlvfxPEX_… Thank you. Best regards. Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

FW: [Ccnso-pgawg] [Ext] Re: [EXTERNAL] - Friendly reminder Re: Draft final report PGA WG
by Jordan Carter May 2, 2025

May 2, 2025

Hi team Does anyone think the below is unreasonable? I support us doing it as a simple administrative action.... Jordan From: Kim Davies <kim.davies(a)iana.org> Sent: Wednesday, 30 April 2025 4:29 AM To: Chris Disspain <chris.disspain(a)identity.digital>; Jordan Carter via Ccnso-pgawg <ccnso-pgawg(a)icann.org> Cc: Jordan Carter <jordan.carter(a)auda.org.au> Subject: Re: [Ccnso-pgawg] [Ext] Re: [EXTERNAL] - Friendly reminder Re: Draft final report PGA WG I hope that it can be easily done because I think it benefits all! My wishlist would be: * A clear table of adopted policies, and whether they are active, retired, amended or superseded * For each policy, publish the clearly delineated normative policy language, distinct from anything else that is informative or optional reading, like council and board transmittal artefacts * Cross-reference any normative clarifications or interpretational guidance (errata, formal communications) that must be read in conjunction with the associated policy. * Ideally in HTML for ease of citation and cutting-and-pasting * Situated at a concise long-lived URL that isn't likely to change when software gets upgraded. I note many cited documents in our work have been on the community wiki where many URLs recently broke. Another point of comparison or inspiration is the ASO policy list: https://aso.icann.org/policy/global/current-global-policies/. To look at the IPv4 allocation policy IANA must follow as an example, the policy language is clearly stated without extraneous material: https://www.icann.org/resources/pages/allocation-ipv4-post-exhaustion-2012-… kim From: Chris Disspain <chris.disspain(a)identity.digital<mailto:chris.disspain@identity.digital>> Date: Tuesday, April 29, 2025 at 11:01 To: Jordan Carter via Ccnso-pgawg <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> Cc: Kim Davies <kim.davies(a)iana.org<mailto:kim.davies@iana.org>>, Jordan Carter <jordan.carter(a)auda.org.au<mailto:jordan.carter@auda.org.au>> Subject: Re: [Ccnso-pgawg] [Ext] Re: [EXTERNAL] - Friendly reminder Re: Draft final report PGA WG I agree. My understanding is that publication should follow 'automatically' after board adoption. Cheers, CD Chris Disspain +44 7880 642456 [cid:image001.jpg@01DBB8F9.E45AB940] On 29 Apr 2025, at 18:59, Jordan Carter via Ccnso-pgawg <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> wrote: Hi Kim, all, Personally, I think it's a purely administrative action to publish the policies that have been passed by the PDPs in the way you describe. I don't think any mandate or process is required to do so. Should we test that with the council? Cheers Jordan Jordan Carter - .au Domain Administration +61-417-243-647 on Signal or iMessage ________________________________ From: Kim Davies via Ccnso-pgawg <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> Sent: Tuesday, April 29, 2025 6:43:49 PM To: Irina Danelia via Ccnso-pgawg <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> Cc: Kim Davies <kim.davies(a)iana.org<mailto:kim.davies@iana.org>> Subject: [Ccnso-pgawg] Re: [Ext] Re: [EXTERNAL] - Friendly reminder Re: Draft final report PGA WG Hi all, I've also made a significant number of changes but almost all are just grammatical fixes, consistent usage of terms etc. With that said, I suggest the document go through a thorough copy-editing pass just for consistency, formatting etc. I think the one question of substance I had was to clarify what is means for the council to "adopt" the document. Also, an observation I received from an ICANN colleague that I wanted to share, and apologies if this reiterates earlier comments I made in the ad-hoc group or this working group. The overview document doesn't fully address that the ccNSO doesn't have a definite way of describing its adopted policies, their current status, and how they fit together. They highlight the following from the GNSO as a point of comparison: We have an example on the gtld side, where we have an overarching Consensus Policy Page: https://www.icann.org/consensus-policies-en and then each policy has its own page with revisions and clarifications (see https://www.icann.org/resources/pages/igo-ingo-protection-policy-2024-02-21…) In contrast, to take the ccTLD retirement policy for example, the policy isn't posted in its final form with adoption date etc. anywhere that I am aware of. This means that to cite the policy, IANA has to cite a subset of pages within a PDF of the draft policy proposal at the end of our procedures page: https://www.iana.org/help/cctld-retirement kim From: Irina Danelia via Ccnso-pgawg <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> Date: Monday, April 28, 2025 at 08:32 To: "ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>" <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> Cc: Irina Danelia <i.danelia(a)cctld.ru<mailto:i.danelia@cctld.ru>> Subject: [Ccnso-pgawg] Re: [Ext] Re: [EXTERNAL] - Friendly reminder Re: Draft final report PGA WG Hi all! I made several comments in the document. All editorial, not on substance See you tomorrow! Irina From: Bart Boswinkel via Ccnso-pgawg <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> Sent: Monday, April 28, 2025 12:58 PM To: Jordan Carter <jordan.carter(a)auda.org.au<mailto:jordan.carter@auda.org.au>>; Bart Boswinkel via Ccnso-pgawg <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> Cc: Joke Braeken <joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>>; Bart Boswinkel <bart.boswinkel(a)icann.org<mailto:bart.boswinkel@icann.org>> Subject: [Ccnso-pgawg] Re: [Ext] Re: [EXTERNAL] - Friendly reminder Re: Draft final report PGA WG Hi Jordan Correct, tomorrow (this week) is first reading full report. Kind regards, Bart From: Jordan Carter <jordan.carter(a)auda.org.au<mailto:jordan.carter@auda.org.au>> Date: Monday, 28 April 2025 at 10:45 To: Bart Boswinkel via Ccnso-pgawg <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> Cc: Joke Braeken <joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>>, Bart Boswinkel <bart.boswinkel(a)icann.org<mailto:bart.boswinkel@icann.org>> Subject: [Ext] Re: [EXTERNAL] - [Ccnso-pgawg] Friendly reminder Re: Draft final report PGA WG Hi all I'm back from my holiday, speak with you tomorrow! Report looks good broadly speaking. Only wonder if we should do any more specification of the proposed terms for the study groups? I have some non substantive editorial changes to suggest that I hope to tack into the Google doc this afternoon European time. I presume that our meeting this week will be a first reading? Cheers Jordan Jordan Carter - .au Domain Administration +61-417-243-647 on Signal or iMessage ________________________________ From: Bart Boswinkel via Ccnso-pgawg <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> Sent: Friday, April 25, 2025 6:26:42 PM To: ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org> <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> Cc: Joke Braeken <joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>>; Bart Boswinkel <bart.boswinkel(a)icann.org<mailto:bart.boswinkel@icann.org>> Subject: [EXTERNAL] - [Ccnso-pgawg] Friendly reminder Re: Draft final report PGA WG Dear all As a friendly reminder Please review the draft report: https://docs.google.com/document/d/1ouZnDqzikDxnuhlz5VPw0uWvqdCxX2Giy5mEGN4… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ouZnDqzikDxn…> Any comments or suggested edits, please include in suggestion mode in the doc or in response the this email. The next Policy Gap Analysis Working Group teleconference is scheduled for 29 April 2025 at 17:00 UTC. Main topic is review of the report Kind regards, Bart From: Joke Braeken via Ccnso-pgawg <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> Date: Wednesday, 16 April 2025 at 06:08 To: "ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>" <ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org>> Cc: Joke Braeken <joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>> Subject: [Ccnso-pgawg] Draft final report PGA WG Dear All, Please find here the draft final report by the PGA working group, as introduced yesterday by Bart to the group. Please review the document, and suggest any edits or comments you may have either directly in the document, or on the PGA mailing list. Thank you. https://docs.google.com/document/d/1ouZnDqzikDxnuhlz5VPw0uWvqdCxX2Giy5mEGN4… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ouZnDqzikDxn…> Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> _______________________________________________ Ccnso-pgawg mailing list -- ccnso-pgawg(a)icann.org<mailto:ccnso-pgawg@icann.org> To unsubscribe send an email to ccnso-pgawg-leave(a)icann.org<mailto:ccnso-pgawg-leave@icann.org>

2 1

Fwd: [ICANN Community Leaders] Request for Applicant Guidebook related sessions at ICANN83
by Alejandra Reynoso Barral April 24, 2025

April 24, 2025

Hi! Not sure if we are interested in this particular topic, but forwarding to check. 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: Elisa Busetto via SO-AC-SG-CLeaders <so-ac-sg-cleaders(a)icann.org> Date: Tue, Apr 1, 2025 at 2:17 PM Subject: [ICANN Community Leaders] Request for Applicant Guidebook related sessions at ICANN83 To: so-ac-sg-cleaders(a)icann.org <so-ac-sg-cleaders(a)icann.org> Cc: Marika Konings <marika.konings(a)icann.org>, Lars Hoffmann < lars.hoffmann(a)icann.org> Dear All, We hope this email finds you well. We are reaching out about our planned ‘Next Round Applicant Guidebook roadshow’ during ICANN83. As you may know already, we are working towards launching the Public Comment on the whole draft Applicant Guidebook on 30 May at the latest for a period of 50 days. We will have a number of SMEs on the ground for ICANN83 and plan to hold at least one IRT session on the AGB. As noted above, we would also like to offer to present on specific topics to your respective community groups. E.g., this could be in the form of providing details on specific topics or just sitting in on your discussions and clarification or background information, e.g. in case your community group hold a working session on the public comment. We kindly ask that you confer with your community groups if you’d like someone from our team to attend any of your meetings during ICANN83 and if so let us know, off-list, by 30 April 2025. If you have any questions, please reach out at any time. Thank you! Best regards, Elisa P.S.: We have sent a similar message to IRT members and will include a short note in an upcoming Community Digest <https://icann-community.atlassian.net/wiki/x/qAL2Bg>, too. _______________________________________________ SO-AC-SG-CLeaders mailing list -- so-ac-sg-cleaders(a)icann.org To unsubscribe send an email to so-ac-sg-cleaders-leave(a)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.

3 4

Additional Considerations for the selection of future appointees to the ccNSO Council
by Alejandra Reynoso Barral April 3, 2025

April 3, 2025

Dear Amir Thank you for the opportunity to join you for an informal conversation on 8 March 2025 during ICANN 82. As requested, please find attached a letter that outlines some key considerations the NomCom may wish to take into account as it considers and selects future appointees to the ccNSO Council. It should be read in conjunction with the position description <https://ccnso.icann.org/sites/default/files/field-attached/nomcom-appointee…> for the role. 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. *******************************************

2 1

How We Meet: ccnso discussion and next steps
by Joke Braeken April 2, 2025

April 2, 2025

Hello, Here are the notes and recording for today’s How We Meet discussion. Notes Wednesday, 2 April 2025 (06:00 UTC)<https://docs.google.com/document/d/1cvip93fAxZEkEIWFCdooNE8wp-t6zn8GQh6zp7t…> and Zoom recording<https://icann.zoom.us/rec/share/cpsQ7JFt-rTqhmPTYULjcVVT78U62sQ2kMZsUqS55aF…> The draft initial report has been added to the Library. ccNSO Library “How We Meet: https://docs.google.com/document/d/1ALuqeeO0_5NYU3FWjfkwYsg-YVR2_CVlvfxPEX_… Action item #1 Secretariat to schedule a special council meeting on Wednesday, 9 April 2025 at 19:00 UTC on how we meet Action item #2 * Jodi to start a draft note to the community, on behalf of Alejandra, Molehe, Jodi. * Deadline for the draft to be ready: Friday, end of day. * Content: alert to the public comment, provide a heads up about the upcoming Council statement. * Alejandra to send out once public comment opens (7 or 8 April). Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

How we meet - Season 2
by Alejandra Reynoso Barral March 27, 2025

March 27, 2025

Dear Jodi and Molehe Hope you are well and recovered from ICANN82 😉 Shall we have a call next Wednesday 2.April at 06:00 UTC to catch up, review the feedback gathered at the ccNSO session (see attachment) and perhaps think of next steps? 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. *******************************************

3 3

Fwd: [soac-chairs] Request for Early Input | GNSO Latin Script Diacritics Policy Development Process Working Group
by Alejandra Reynoso Barral March 25, 2025

March 25, 2025

FYI ******************************************* 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: Terri Agnew via soac-chairs <soac-chairs(a)icann.org> Date: Thu, Mar 20, 2025 at 8:45 PM Subject: [soac-chairs] Request for Early Input | GNSO Latin Script Diacritics Policy Development Process Working Group To: soac-chairs(a)icann.org <soac-chairs(a)icann.org> Cc: Michael Bauland <Michael.Bauland(a)knipp.de>, Prudence Malinki < prudence.malinki(a)markmonitor.com>, mark(a)governanceprimer.com < mark(a)governanceprimer.com>, Saewon Lee <saewon.lee(a)icann.org>, John Emery < john.emery(a)icann.org>, Steve Chan <steve.chan(a)icann.org>, GNSO-Secs < gnso-secs(a)icann.org> Dear SO/AC Chairs, We are writing to you on behalf of the GNSO Latin Script Diacritics (LD) Policy Development Process (PDP) Working Group (WG). This WG is tasked with providing the GNSO Council policy recommendations on: The limited circumstances in which a base ASCII gTLD and the Latin script diacritic version of the gTLD can be simultaneously delegated. The WG held its first meeting <https://icann82.sched.com/event/1vpYP/gnso-latin-script-diacritics-pdp-work…> on 08 March, 2025. In accordance with GNSO’s PDP requirements, we are seeking early written input on the topic from each Supporting Organization, Advisory Committee, and GNSO’s Stakeholder Group / Constituency. Each group has been invited to participate in the PDP. Kindly note that the written input is completely voluntary. In order to ensure that the WG receives your input in a timely manner and that your input is incorporated into a summary document for the WG’s consideration, we are requesting a response *no later than 24 April 2025**.* Input received after this date may be introduced into the discussion separately by your representatives, by ICANN support staff, or by me as the relevant topic is discussed. The WG’s scope of work is defined through a series of questions presented in the WG’s Charter. The list of questions and key issues to consider soliciting community input are attached for your convenience. To the extent possible, you are requested to write your responses to the individual questions in the attached document and return via email to the GNSO Secretariat *gnso-secs(a)icann.org <gnso-secs(a)icann.org>*. It is not necessary to answer every question, and you are also welcome to provide any other input and/or background information that you deem helpful to the deliberations. As with all GNSO PDPs, there will be additional opportunities for community input as the work progresses. Thank you very much and we look forward to receiving your input. On behalf of the LD PDP WG, Michael Bauland (LD PDP WG Chair) _______________________________________________ soac-chairs mailing list -- soac-chairs(a)icann.org To unsubscribe send an email to soac-chairs-leave(a)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.

1 0

Fwd: Pilot Holistic Review
by Alejandra Reynoso Barral March 25, 2025

March 25, 2025

FYI ******************************************* 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: Sophie Hey <sophie.hey(a)comlaude.com> Date: Mon, Mar 24, 2025 at 5:59 AM Subject: Pilot Holistic Review To: tripti.sinha(a)board.icann.org <tripti.sinha(a)board.icann.org>, Alan Barrett <alan.barrett(a)board.icann.org>, becky.burr(a)board.icann.org < becky.burr(a)board.icann.org>, Kane, Pat <pkane(a)verisign.com>, Cheryl Langdon-Orr <langdonorr(a)gmail.com>, Alejandra Reynoso Barral < alejandra.reynoso(a)gmail.com>, DiBiase, Gregory <dibiase(a)amazon.com>, Ram Mohan <rmohan(a)identity.digital>, tjwhalen(a)gmail.com <tjwhalen(a)gmail.com>, Jonathan Zuck <JZuck(a)innovatorsnetwork.org>, Nicolas Caballero < nicustkd(a)gmail.com>, Nigel Hickson <nigel.hickson(a)dcms.gov.uk>, Jeff Osborn <jeff(a)isc.org>, chair(a)nro.net <chair(a)nro.net>, hholen(a)ripe.net < hholen(a)ripe.net> Cc: Chris Disspain <chris.disspain(a)identity.digital>, Jason Kean < jason.kean(a)icann.org>, Mary Wong <mary.wong(a)icann.org>, Karen Lentz < karen.lentz(a)icann.org>, Jessica Villaseñor <jessica.villasenor(a)icann.org>, Theresa Swinehart <theresa.swinehart(a)icann.org>, Jessica Puccio < jessica.puccio(a)icann.org> TO Chair of Board Chair of Board Organisational Effectiveness Committee Chair of Board Governance Committee ATRT3 Co-Chairs SO/AC Chairs Dear all, We are writing to close the loop on the discussions held during ICANN 82 on reviews, to the extent that these discussions impact the work of the Pilot Holistic Review (PHR). During ICANN 82 the Board held discussions with each SO/AC at which the subject of reviews generally and the PHR specifically were raised. By way of background, we attach our letter to the OEC chair dated 13 February which explains the lead up to the various discussions that took place at ICANN 82. What we heard during ICANN 82: 1. The possibility of suspending all reviews whilst the community worked on a new approach, assessing why we review, what we should review and how best to review. 2. The possibility of using ATRT4 to do the above or to replace the PHR and work on the design of the 'Structural Review' part of the ATRT3 recommendations. 3. A number of proposals on how to proceed with the PHR. Having listened to a number of the exchanges we convened a meeting of the SO/AC/NC Chairs, the ATRT 3 Chairs and ourselves. At that meeting a number of matters were clarified: 1. ATRT3 intended the Holistic Review to be an ICANN Specific Review.1 This means that an eventual Holistic Review would be conducted in accordance with Section 4.6(a) of ICANN's Bylaws and pursuant to the Operating Standards for Specific Reviews. We note that the current Operating Standards are under review2 so the PHR is designing an Holistic Review with, at this stage, an unclear set of operating standards. By way of examples of issues arising, under the current Bylaws and Operating Standards, such matters as the structure of the review team3 and the use or non-use of independent experts4 are matters for the Holistic Review team itself, not for the PHR. Further, under the Bylaws, specific review recommendations are made to the Board5 not to the individual SO/AC or NC that may be the subject of the recommendation. This is inconsistent with deliverable 8 of the PHR Terms of Reference. 2. To the extent the PHR has been given deliverables on issues covered by Section 4.6(a) of the ICANN Bylaws, these deliverables become redundant. 3. Whilst the result of a Review of the Continuous Improvement efforts of the SO/AC/NCs would feed into a Structural Review, the two reviews are based on two contradictory assumptions: that the SO/AC/NCs are fit for purpose as set out in the Bylaws, and that the SO/AC/NCs are not fit for purpose as set out in the Bylaws. Therefore, the two reviews are really separate pieces of work with separate skill sets and deliverables. 4. The PHR is misnamed. It is, in essence, The Holistic Review Drafting Team. 5. There may not be consensus amongst the SO/AC/NC chairs that a specific review is the right mechanism for conducting a Structural Review of ICANN and/or for reviewing the continuous improvement efforts of SO/AC/NC. This is consistent with the feedback and discussions from the Board and SO/AC interactions at ICANN 82. Clearly the ICANN Board is currently considering the ICANN reviews as a whole. In the event that a decision is made to launch a process to review ICANN reviews then the below is redundant. However, should the Board decide to continue with the PHR process we recommend the following steps – 1. Bifurcate the work to develop a Continuous Improvement Program (CIP) Review and a Structural Review. 2. Empower a CIP Review drafting team to work closely with the SO/AC/NC to ascertain their CIP methodologies and design a streamlined review of the CIP work. 3. Confirm that there is SO/AC/NC consensus in favour of creating a Specific Review on ICANN's structure. 4. Empower a Structural Review drafting team to design a Specific Review of the Structure of ICANN based upon Bylaws s4.6(a) and the Operating Standards. Note that in the above, steps 1 and 2 could proceed immediately should the Board wish. Should be Board decide to proceed in this manner both of us stand ready to continue our work as Chairs. Chris Disspain & Sophie Hey Co-Chairs Pilot Holistic Review ------------------------------ 1 See ATRT3 recommendation 8, p71-2 2 https://www.icann.org/en/public-comment/proceeding/proposed-updates-to-the-… 3 Bylaws s 4.6(a)(i) 4 Bylaws, s 4.6(a)(iv) 5 Bylaws, s 4.6(a)(viii)(C) Sophie Hey she/her Policy Advisor <https://comlaude.com/> 28 Little Russell Street, London WC1A 2HN, UK *T* +44 (0) 20 7421 8250 *Ext* 252 *comlaude.com <http://comlaude.com>* *Follow us on LinkedIn <https://t-uk.xink.io/Tracking/Index/pRkAAFJfAADl_RQA0> and YouTube <https://t-uk.xink.io/Tracking/Index/bhkAAFJfAADl_RQA0>* <https://www.linkedin.com/company/com-laude> <https://twitter.com/comlaude?lang=en> <https://www.facebook.com/ComLaude/> <https://www.youtube.com/@comlaude> ------------------------------ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com <https://comlaude.com>

1 0

Supplementary email address
by Jordan Carter March 13, 2025

March 13, 2025

Hi team I am going to be on holiday all of April, in Europe. Can you please add my personal address (jordan(a)jordancarter.au) to a number of email lists, from whenever you can after this meeting? CcNSO-members CcNSO-council CcNSO-leadership CcNSO-pgawg I think those are all - you can add any others you want to, I don't mind. Thanks in advance! Jordan _______ Jordan Carter Internet Governance and Policy Director jordan.carter(a)auda.org.au<mailto:jordan.carter@auda.org.au> +61 417 243 647 [https://files.auda.org.au/images/AUDA_Fullrz1.jpg] .au Domain Administration www.auda.org.au<http://www.auda.org.au/> [cid:image001.png@01DB94B8.E33646C0]<https://www.auda.org.au/join-auda/apply-now> ________________________________ Important Notice This email may contain information which is confidential and/or subject to legal privilege, and is intended for the use of the named addressee only. If you are not the intended recipient, you must not use, disclose or copy any part of this email. If you have received this email by mistake, please notify the sender and delete this message immediately.

1 1