March 2025 - Ccnso-council - lists.icann.org

May ccNSO Council Teleconference (217) | 15 May at 12:00 UTC
by ccNSO Calendar March 25, 2025

March 25, 2025

Dear Council, The May ccNSO Council Teleconference (217) is scheduled for 15 May 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/94742071601?pwd=5bYDGW1ZUJNMdeLPbeOeoHmANjhWYl.1 Meeting ID: 947 4207 1601 Passcode: ccNSO-0217 Wiki page: https://icann-community.atlassian.net/wiki/x/D4wlBg

1 0

April ccNSO Council Teleconference (216) | 17 April at 21:00 UTC
by ccNSO Calendar March 25, 2025

March 25, 2025

Dear Council, The April ccNSO Council Teleconference (216) is scheduled for 17 April at 21: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/93623172289?pwd=V5uUIve1jBRLTAPjRMGdqcONKHko7V.1 Meeting ID: 936 2317 2289 Passcode: ccNSO-0216 Wiki page: https://icann-community.atlassian.net/wiki/x/C4wlBg

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 1:59 PM 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

Re: [ECAdmin] Appointment Alejandra Reynoso ccNSO representative ECA March 2025-end of ICANN85
by Ozan Sahin March 25, 2025

March 25, 2025

Dear Bart, Thank you for this letter. I would like to confirm that the letter has been published on the Empowered Community correspondence page: https://www.icann.org/en/ec/correspondence Best regards, Ozan Sahin (on behalf of staff supporting the Empowered Community Administration) From: Bart Boswinkel via ECAdmin <ecadmin(a)icann.org> Reply-To: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: 24 March 2025 Monday at 17:39 To: John Jeffrey <john.jeffrey(a)icann.org> Cc: "ecadmin(a)icann.org" <ecadmin(a)icann.org>, "ccNSO-Council(a)icann.org" <ccNSO-Council(a)icann.org>, "ccnso-tracker(a)icann.org" <ccnso-tracker(a)icann.org> Subject: [ECAdmin] Appointment Alejandra Reynoso ccNSO representative ECA March 2025-end of ICANN85 Dear John, Please find attached the letter informing you of the appointment of Alejandra Reynoso as the ccNSO representative to the Empowered Community Administration. On behalf of the ccNSO Council Bart Boswinkel ccNSO Secretariat

1 0

Call for nominations: one (1) ccNSO Councillor from the European Region
by Joke Braeken March 25, 2025

March 25, 2025

Dear ccNSO members from the European region, To fill the vacancy on the ccNSO Council for the European region, the ccNSO will open a call for nominations on Wednesday, 26 March 2025, at 00:01 UTC. The nomination and secondment period will close on Tuesday, 15 April 2025, at 23:59 UTC. This new nomination process is initiated because the Councillor-elect from the European region, chosen during the 2025 ccNSO Council nomination process, resigned in February 2025. Note: As per the ccNSO Guideline, only the Representative from a ccNSO member from the European region will be able to nominate and second candidates to serve as a ccNSO Councillor for the European region. Further instructions are included below. The ICANN Bylaws, Article 10 – Section 10.4 (g)<https://www.icann.org/resources/pages/governance/bylaws-en/#article10> state: "(g) The ccNSO Council members selected by the ccNSO members from each Geographic Region (see Section 10.3(a)(i)) shall be selected through nomination, and if necessary, election, by the ccNSO members within that Geographic Region. At least 90 days before the end of the regular term of any ccNSO-member-selected member of the ccNSO Council, or upon the occurrence of a vacancy in the seat of such a ccNSO Council member, the ccNSO Council shall establish a nomination and election schedule, which shall be sent to all ccNSO members within the Geographic Region and posted on the Website." TIMELINE | The nomination and secondment procedure starts Wednesday, 26 March 2025 (00:01 UTC) and closes Tuesday, 15 April 2025 (23:59 UTC). WHO CAN NOMINATE OR SECOND? | The ICANN Bylaws, Article 10 – Section 10.4 (h)<https://www.icann.org/resources/pages/governance/bylaws-en/#article10> state: Representatives from ccNSO members from the European region. "(h) Any ccNSO member may nominate an individual to serve as a ccNSO Council member representing the ccNSO member's Geographic Region. Nominations must be seconded by another ccNSO member from a different Territory, from the same Geographic Region. By accepting their nomination, individuals nominated to the ccNSO Council agree to support the policies committed to by ccNSO members." The ccNSO Council election guideline, section 3.2<https://ccnso.icann.org/sites/default/files/field-attached/guideline-ccnso-…>, states: "Only the Representative from a ccNSO member will be able to nominate and second candidates to serve as a ccNSO Councillor. New ccNSO members can participate in the nomination process if their ccNSO membership application has been approved by the ccNSO Council one day prior to the day the nomination process starts. A Representative from a ccNSO member may self-nominate, but is then not allowed to second their self-nomination. Self-nominations must be seconded by two Representatives from two other Territories in the Region." The Glossary of the Internal ccNSO Rules, states:<https://ccnso.icann.org/sites/default/files/field-attached/internal-members…> "Representative - Each ccTLD manager may designate in writing a person, organization, or entity to represent the ccTLD manager in matters relating to the ccNSO ("Representative"). In the absence of such a designation, the person, organization, or entity listed as the administrative contact in the IANA database shall be deemed to be the designate of the ccTLD manager by whom the ccNSO member shall be represented." Contact joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>, in case you have questions regarding who is listed as the Representative for your ccTLD. NEW ccNSO MEMBERS | Note that new ccNSO members can participate in the nomination process if the ccNSO membership application has been approved by the ccNSO Council one day prior to the nomination process start, i.e., latest on 25 March 2025. SELF-NOMINATIONS | As per the relevant ccNSO guideline<https://ccnso.icann.org/sites/default/files/field-attached/guideline-ccnso-…>, ccNSO members may self-nominate themselves, but are not allowed to second their nomination. Self-nominations must be seconded by two ccNSO members from the region. INSTRUCTIONS | Nominations and secondments should be sent by e-mail to the Election Manager at the following e-mail address: ccnso-nominations(a)icann.org<mailto:ccnso-nominations@icann.org>. Templates for nominating and seconding nominations are provided below. You are kindly invited to follow these instructions closely, and not to use alternative templates. Consult the archive for nominations and secondments here: https://lists.icann.org/hyperkitty/list/ccnso-nominations@icann.org/ = = = please send to ccnso-nominations(a)icann.org<mailto:ccnso-nominations@icann.org> TEMPLATE | NOMINATION TO THE ccNSO COUNCIL Your full name: Your ccTLD: Your geographic region: Full name of the person you nominate to the ccNSO council: = = = send to ccnso-nominations(a)icann.org<mailto:ccnso-nominations@icann.org> TEMPLATE | SECONDING A NOMINATION TO THE CCNSO COUNCIL Your full name Your ccTLD: Your geographic region: Full name of the nominee you would like to second: ELIGIBILITY REQUIREMENTS TO BE ELECTED TO CCNSO COUNCIL | A Councillor can be any individual nominated, seconded, and elected as described in the ccNSO Council Election Guideline. Individuals are elected in their personal capacity and serve the ccTLD community. Councillors do not represent the views and interests of their employers. Candidates need to be neither resident in the region, nor a citizen of a country, within the region in which they stand for election. The ccNSO Council consists of 18 Councillors, representing 5 ICANN geographical regions. Each region has 3 Councillors, with 15 elected by ccNSO members within their respective regions and 3 appointed by the ICANN Nominating Committee. VALID CANDIDATES | A valid candidate is one that has been nominated and seconded according to the ccNSO council Election Guideline, and that has accepted the nomination. If there is more than one valid candidate in a Geographical Region, an election shall be conducted in that region. Voting will be by secret ballot. ACCEPTING NOMINATIONS | After closure of the nomination period, the Election Manager will ask the candidates that are nominated to accept their nomination. The Election Manager will provide a list with the name(s) of the candidate(s) who have accepted their nomination. A record of who has nominated and seconded the candidate(s) is publicly available: https://lists.icann.org/hyperkitty/list/ccnso-nominations@icann.org/ NEXT STEPS | The Election Manager will ask the candidate(s) to provide a written candidate statement. A Question and Answer session with the candidate(s) will be held on 29 April 2025 (time TBC). In preparation of the Q&A session, the written candidate statement(s) will be posted on the ccNSO website. The Q&A session gives the ccNSO members and broader ccTLD community an opportunity to interact with the candidate(s). If at the close of nominations there are no more valid candidates in a particular geographic region than there are seats on the ccNSO Council available for that geographic region, then the nominated candidates shall be selected to serve on the ccNSO Council. Otherwise, an election shall be held for that geographic region, to select the ccNSO Councillors from among the valid candidates. The first election round (if any), will start 21 May 2025 (00:01 UTC) and will close 11 June 2025 (23:59 UTC), as per the timeline adopted by the Council. LINKS * ICANN bylaws, Article 10<https://www.icann.org/resources/pages/governance/bylaws-en/#article10> * ccNSO Internal Membership Rules<https://ccnso.icann.org/en/about/internal-membership-rules-26oct22-en.pdf> * Archive for nominations and secondments<https://lists.icann.org/hyperkitty/list/ccnso-nominations@icann.org/> * Relevant ccNSO guideline<https://ccnso.icann.org/sites/default/files/field-attached/guideline-ccnso-…> * Timeline<https://icann-community.atlassian.net/wiki/spaces/ccNSOCWS/pages/103123967/…> * Announcements related to Council elections<https://ccnso.icann.org/en/about/elections/council.htm> Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 0

Appointment Alejandra Reynoso ccNSO representative ECA March 2025-end of ICANN85
by Bart Boswinkel March 24, 2025

March 24, 2025

Dear John, Please find attached the letter informing you of the appointment of Alejandra Reynoso as the ccNSO representative to the Empowered Community Administration. On behalf of the ccNSO Council Bart Boswinkel ccNSO Secretariat

1 0

Second IANA Naming Function Review Team (IFR2) Initial Report out for public comments
by Joke Braeken March 24, 2025

March 24, 2025

Dear all, The Second IANA Naming Function Review Team (IFR2) seeks community input on its Initial Report. The report contains findings and Recommendations in three key areas: * Presence of specific Domain Name System Security Extensions (DNSSEC) policy details in the IANA Naming Function Contract * Transparency and availability of Contract amendments * Frequency of reviews It also presents several findings deemed ‘Incidental.’ Timeline (UTC) Open for Submissions: 20 March 2025 Closed for Submissions: 28 April 2025 | 23:59 Report Due: 12 May 2025 | 23:59 Read more https://www.icann.org/en/public-comment/proceeding/second-iana-naming-funct… Best regards, Joke Braeken joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Read more about the ccNSO at ICANN82: https://bit.ly/4h4E8Ot

1 0

November ccNSO Council Teleconference (223) | 20 November at 12:00 UTC
by ccNSO Calendar March 24, 2025

March 24, 2025

Dear Council, The November ccNSO Council Teleconference (223) is scheduled for 20 November 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/96095269567?pwd=aV3V56a07eWL5h3BHyvQRkALD7s7Ci.1 Meeting ID: 960 9526 9567 Passcode: ccNSO-0223 Wiki page: https://icann-community.atlassian.net/wiki/x/J4wlBg Thank you!

1 0

December ccNSO Council Teleconference (224) | 18 December at 18:00 UTC
by ccNSO Calendar March 24, 2025

March 24, 2025

Dear Council, The December ccNSO Council Teleconference (224) is scheduled for 18 December at 18: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/93706364777?pwd=LDSnMfa0IrTFJ2TfNmWUagfQsxaXRG.1 Meeting ID: 937 0636 4777 Passcode: ccNSO-0224 Wiki page: https://icann-community.atlassian.net/wiki/x/K4wlBg Thank you!

1 0

November ccNSO Council Teleconference (223) | 20 November at 12:00 UTC
by ccNSO Calendar March 24, 2025

March 24, 2025

Dear Council, The November ccNSO Council Teleconference (223) is scheduled for 20 November 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/96095269567?pwd=aV3V56a07eWL5h3BHyvQRkALD7s7Ci.1 Meeting ID: 960 9526 9567 Passcode: ccNSO-1123 Wiki page: https://icann-community.atlassian.net/wiki/x/J4wlBg Thank you!

1 0