- ALAC - lists.icann.org

Re: SSAC Workshop: Open Sessions
by Matthias M. Hudobnik Sept. 20, 2024

Sept. 20, 2024

1 0

Re: SSAC Workshop: Open Sessions
by Matthias M. Hudobnik Sept. 20, 2024

Sept. 20, 2024

1 0

SSAC Workshop: Open Sessions
by Matthias M. Hudobnik Sept. 19, 2024

Sept. 19, 2024

Dear colleagues, as promised, I am happy to share with you below the remote participation details for the open sessions as follows: >> Please click the link below to join the webinar: >> >> https://icann.zoom.us/j/95868189441?pwd=4LQp8z1rvaqkIS027d1aZgpVXb5Xfb.1 >> >> >> >> Passcode: %ZV*1YN6GJ >> >> >> >> Webinar ID: 958 6818 9441 >> >> >> >> Passcode: 9408318027 >> >> >> >> International numbers available: https://icann.zoom.us/u/a0FzHsONG >> Have a nice day, and we are very much looking forward to seeing you remotely at the sessions! Best, Matthias __________________________ Ing. Mag. Matthias M. Hudobnik FIP, CIPP/E, CIPT, DPO, CIS LA matthias(a)hudobnik.at http://www.hudobnik.at @mhudobnik

3 2

ccNSO #210 meeting Draft Agenda September 19th. 2024 12:00 UTC
by Laura Margolis Sept. 16, 2024

Sept. 16, 2024

Dear All: The next ccNSO meeting will take place next *Thursday September 19th., at 12:00 UTC* Here is the *DRAFT AGENDA* <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…> *BACKGROUND MATERIALS and Council Workspace* <https://community.icann.org/x/HQEZEw> and *STATEMENTS and RESPONSES* <https://ccnso.icann.org/en/about/statements.htm> ***If you would like to join as an observer, you are welcome, please, send an email to Claudia Ruiz claudia.ruiz(a)icann.org <claudia.ruiz(a)icann.org> and she will send you the zoom link.* ccNSO Council Meeting 209 (draft agenda, including one draft resolution) Thursday, 19 September 2024 at 12:00 UTC AGENDA 1. Welcome *a) **Establish Whether Meeting Is Quorate* 2. Updates Statements of Interest Fill out the ccNSO Statement of Interest form: https://forms.gle/79Jw4wSnNhn5W4Z46 Check your SOI here: https://community.icann.org/x/doAFEg Consult the ccNSO SOI Guideline: https://ccnso.icann.org/sites/default/files/field-attached/ccnso-internal-p… ADMINISTRATIVE MATTERS 3. Relevant Correspondence *a) **Notice of Resignation of Board Member Katrina Sataki to ccNSO Council Chair and Secretariat | 23 August 2024* *b) **Secretary's Notice of Resignation of Board Member Katrina Sataki to ECA and ccNSO Council Chair | 24 August 2024* 4. Minutes & Action Items *a) **Minutes Meeting 208: Circulated 10 September 2024* 2. *Action Items* ● *Action item 208-01: Completed* Following the departure of Tatiana Tropina from Council, the Secretariat is requested to add the topic to the agenda of Council meeting 209, regarding filling the vacancies for one (1) member to the Triage Committee, and one (1) Council liaison to IGLC. ● *Action item 208-02: Completed* The secretariat is requested to publish the resolution regarding the CSC effectiveness review deferral ● *Action item 208-03: Completed* The ccNSO Chair to send letter to ICANN Board Chair, regarding the CSC effectiveness review deferral ● *Action item 208-04: Completed (see agenda item 14, Council meeting 209)* Once the Travel Fund Committee finalises the proposed revised Travel Fund Guideline, the secretariat is requested to send it to Council for review, and then to the community, unless Council raises any concerns. ● *Action item 208-05: Completed (see agenda item 15, Council meeting 209)* The Secretariat is requested to prepare a boilerplate text for the invite to ccTLD managers to join the ccNSO, and send to the draft to Council for discussion ● *Action item 208-06: Completed (see agenda item 17, Council meeting 209)* The volunteers that stepped forward during Council meeting 207 are requested to draft a cover note regarding the ccNSO response to the Board Caucus regarding the questions about the proposed ccPDP3-RM policy. ● *Action item 208-07: Completed (see agenda item 11, Council meeting 209)* The ccNSO Chair is requested to keep Council informed about developments in the ICANN “how we meet” initiative. ● *Action item 208-08: Ongoing (see agenda item 18, Council meeting 209)* The ccNSO Council members are requested to suggest topics for the joint session between the ccNSO and the ICANN Board at ICANN 81. ● *Action item 208-09: Completed* The ccNSO Council members interested in joining the planning committee for the ICANN 81 Plenary session on the ALAC topic proposal are invited to inform the Council chair. ● *Action item 208-10: Completed (see agenda item 16, Council meeting 209)* The Secretariat is requested to propose to Council a template for the DASC review. ● *Action item 208-11: Completed* Council members are invited to participate in the DASC survey 5. Intermeeting Decisions (Since Meeting 208, August 2024) *208-A: *Appointment of Jordan Carter and Peter Koch as members to the informal WSIS+20 Discussion Group, and Biyi Oladipo as alternate. *208-B:* Adoption Board Seat 12 Nomination Process timeline and appointment Joke Braeken as Nomination Process Manager *208-C: *Selection Eyitayo Iortim as ccNSO Delegate to the 2025 NomCom 6. Intermeeting Decisions Triage Committee The Triage Committee has made no decisions since the last meeting. UPDATES 7. Update ECA, IFRT & CSC (Written Updates) Informational 8. Update Working Groups (Written Updates) Informational *a) **ccPDP3-Review Mechanism - Dormant* *b) **ccPDP4-IDN - Dormant* *c) **DASC* *d) **GRC* *e) **IGLC* *f) **MPC* *g) **OMC - First meeting prior to ICANN81* *h) **PGA WG * *i) **SOPC* *j) **Tech WG - Had no meeting since Council meeting 208* *k) **TLD-OPS SC - Had no meeting since Council meeting 208* *l) **UAC* *m) **Triage Committee - Had no meeting since Council meeting 208* *n) **CCG WS2 Implementation- Had no meeting since Council meeting 208* *o) **IRP Panel Selection - Had no meeting since Council meeting 208* *p) **Planning Prioritization Process group - Had no meeting since Council meeting 208* *q) **RZERC* *r) **RSS GWG* *s) **CIP-CCG * 9. Update Liaisons (Written Updates) Informational *a) **Update ALAC Liaison * *b) **Update GNSO Liaison * *c) **Update UASG Liaison* 10. Update ccNSO Website Redesign Informational 11. Update Chair, Vice-Chairs, Councillors, Regional Organisations and Secretariat Informational *a) **Update on “How we meet”-initiative by ICANN org* *b) **Heads up: Council leadership meeting with ICANN President and CEO on 2 October* *c) **Update on progress by WSIS+20 discussion group* 12. Update Board Seat 12 Nomination Process by the Nomination Process Manager Informational 13. Update Council Election Process by the Election Process Manager Informational ADMINISTRATIVE MATTERS & DECISIONS 14. Appointment Members to Committees and Working Groups, if any For decision *Background* Following a call for volunteers, two persons applied to join the ccNSO Universal Acceptance Standing Committee (UAC). One volunteer spontaneously stepped forward to join the ccNSO Meetings Programme Committee (MPC). Following a call for volunteers, several persons applied to become a member of the ccNSO Onboarding and Mentoring Committee (OMC). As per the respective charters, members to the Committee need to be appointed by Council. Secondly, following a call for nominations, the UAC reconfirmed Qing Cai (.cn) for another term as ccNSO liaison to UASG. Furthermore, Councillors volunteered to replace Tatiana Tropina on the ccNSO Council Triage Committee, and as Council liaison to the ccNSO Internet Governance Liaison Committee (IGLC). Finally, following a call for nominations for one (1) ccNSO Policy Gap Analysis Working Group (PGA WG) Chair and one (1) PGA WG Vice Chair, the working group selected Jordan Carter (.au) as its Chair, and Maria Camila Rojas (.co) as its Vice Chair. *Decision* (placeholder) 15. Adoption proposed ccNSO Travel Support Guideline For decision *Background* The ccNSO Travel Support Committee, consisting of a subset of Councillors, proposed changes to the ccNSO Travel Support Guideline. The Travel Support Committee used the Continuous Improvement Model as previously adopted by Council to guide its review. The Committee seeks to achieve two things: Firstly, a fair and equitable distribution of the ccNSO travel funding slots, with a better balance between enabling the participation of individuals who can contribute significantly to the work of the ccNSO and encouraging broader participation. Secondly, the ccNSO Travel Fund guideline, including the selection criteria, should be clear and easily accessible to all. The draft guideline was shared with Council for review and comments. Following minor adjustments to the proposed phrasing, the draft guideline was sent to the community for review and comments. *Decision* (placeholder) 16. Discussion boilerplate text: letter inviting ccTLD managers to become ccNSO members For discussion *Background* Council was requested to send a letter to an individual ccTLD, inviting them to join the ccNSO as a member. Council noted that such letter, if any, needs to be addressed to the current ccTLD Manager as listed in the Root Zone delegation record. Therefore, the proposal is to not publish a generic letter on the ccNSO website, but rather to encourage ccTLDs to reach out to the Secretariat, should they require such a letter. The Secretariat was requested to draft a boilerplate text and send it to Council for review. 17. Discussion template ccNSO DNS Abuse Standing Committee (DASC) review For discussion *Background* DASC met for the first time in May 2022. As per the Terms of Reference of the DASC, a review of its Terms of Reference and the activities of the Committee will take place every two years, or earlier when considered necessary. An update to the Terms of Reference will not become effective until it has been approved by both the Committee and the ccNSO Council and published on the ccNSO website. SUBSTANTIVE MATTERS & DECISIONS 18. Board Caucus request for clarification on the proposed ccPDP3-Review Mechanism Policy *a) **Adoption proposed response to the Board Caucus on ccPDP3-RM questions* For decision *Background* The fourth ccNSO Policy Development Process (ccPDP4) will 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. The proposed policy does not amend or change the current policies on delegation, transfer, revocation, and retirement of ccTLDs, but rather builds upon them. Council adopted the recommended policy at its ICANN79 meeting. The ccNSO membership supports the ccNSO Council's recommendation to adopt the proposed policy. A report on the voting was sent to the Issue Manager. The report has been included in the Draft Board Report, which - following approval by the ccNSO Council at ICANN80 - has been submitted to the ICANN Board of Directors, as per Annex B, section 14 of the ICANN Bylaws. The proposed policy is currently under Board consideration. The Board Caucus on ccPDP3-Review Mechanism, overseeing the policy implementation feasibility, shared some questions for clarification. A group of members of the ccPDP3-RM Working Group and Councillors prepared a draft response, and a cover letter. *Decision* THE CCNSO COUNCIL RESOLVES TO adopt the response to the questions for clarification by the Board Caucus on ccPDP3-Review Mechanism. The Council requests its chair to inform the Board Caucus, by sending the response that was drafted for that purpose, after this resolution becomes effective. The ccNSO Council wholeheartedly thanks the response team. The Council requests the secretariat to publish the response on the ccNSO website correspondence page. This resolution becomes effective seven (7) days after publication. *b) **Adoption proposed cover letter for the response to the Board Caucus on ccPDP3-RM* *Background* The Board Caucus on ccPDP3-Review Mechanism, overseeing the policy implementation feasibility, shared some questions for clarification. A group of members of the ccPDP3-RM Working Group and Councillors prepared a draft response, and a cover letter. The cover note addresses the following: ● Information on how the responses were structured ● An invite to the Caucus and relevant support staff to meet to discuss the requests and responses. This is suggested to avoid losing time by sending further written communication back and forth. ● A response on the foundational assumption made in the cover note which (paraphrased) asks to confirm that the ccPDP3-RM Policy is limited to a procedural review. The substantive material review of an IFO Decision is not subject to a CCRM review. ● A request for clarity of the scope of Annex B section 15(a) of the ICANN Bylaws. What can the ccNSO expect to be included in “Procedures for Board Consideration”? ● An alert to the Board and ICANN org that last year the ccNSO has adopted an Outline <https://ccnso.icann.org/en/about/outline-ccnso-policy-implementation-assist…> on how it intends to organize its work during the implementation phase of a Board adopted ccNSO policy. *Decision* THE CCNSO COUNCIL RESOLVES TO adopt the cover letter to the response to the questions for clarification by the Board Caucus on ccPDP3-Review Mechanism. The Council requests its chair to inform the Board Caucus, by sending the cover letter together with the response that was drafted for that purpose, after this resolution becomes effective. The ccNSO Council thanks the drafting team. The Council requests the secretariat to publish the response on the ccNSO website correspondence page. This resolution becomes effective seven (7) days after publication. 19. Tentative ccNSO Block Schedule ICANN81 *a) **Council preparatory meeting* *b) **Council workshop* *c) **Council meeting* *d) **Joint meeting: ccNSO and ICANN Board* * i. **Topics for discussion* *e) **Joint meeting: ccNSO and GAC* * i. **Topics for discussion* *f) **Working Group and Committee meetings* *g) **Tech Day* *h) **ccNSO Members Meeting sessions* *i) **Plenary Session* 20. AOB 21. Next Council Meetings 17 October 2024 | 21:00 UTC, Meeting 210 14 November 2024 | 10:15-11:30 UTC, Meeting 211 (at ICANN81) 12 December 2024 | 12:00 UTC, Meeting 212 16 January 2025 | 18:00 UTC, Meeting 213 13 February 2025 | 12:00 UTC, Meeting 214 22. Adjourn I will send the report after the meeting. Thank you! Kindest Regards, -- *Laura Margolis* ALAC Liaison to ccNSO margolisl(a)gmail.com +59899690992 skype: lauri.margolis ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>

1 0

ALAC Chair Nomination
by Eduardo Diaz Sept. 13, 2024

Sept. 13, 2024

I nominate Jonathan Zuck for the position of ALAC Chair for the term from AGM 2024 to AGM 2025. -ed

7 6

At-Large Participants in the WSIS+20 Discussion Group
by ICANN At-Large Staff Sept. 12, 2024

Sept. 12, 2024

Dear All, On behalf of Jonathan Zuck, ALAC Chair, please note that ICANN org will shortly be convening a WSIS+20 Discussion Group. This group will be informal (i.e., no charter) and lightweight (i.e., limited membership) to foster trusted collaboration and efficient coordination. Each SOAC was asked to identify two participants from their community. Given the expertise on WSIS+20 issues, Jonathan has asked Amrita Choudhury and Marita Moll to serve as the ALAC participants in the WSIS+20 Discussion Groups. Amrita and Marita will provide regular updates during the At-Large Operations, Finance, and Budget Working Group (OFB-WG) meetings. Please let Jonathan and staff know privately by Friday, 13 September should you have any concerns regarding the ALAC-selected participants. See full details of the group below. ** WSIS+20 Discussion Group Purpose The WSIS+20 Discussion Group will serve as a conduit for the ICANN organization and the ICANN community to discuss and coordinate approaches to explain, promote, and defend the multistakeholder model of Internet governance in the context of the WSIS+20 review process. The discussion group will provide a platform for information exchange and shared understanding between the ICANN organization and ICANN community on matters related to the WSIS+20 review process. This may include the development of consistent messaging for use with stakeholders of the WSIS+20 review process to bolster the credibility of the technical community and ensure its successful, continued engagement in the evolving global Internet governance landscape. Scope The discussion group is not a policy development or advisory group within the ICANN community or a chartered cross-community working group. The discussion group will not define the strategy of the ICANN Board or ICANN organization. The discussion group will not develop deliverables such as recommendations, though its members are encouraged to share suggestions, best practices, and other informational resources to their appointing ICANN community groups. The discussion group is separate from the WSIS+20 Outreach Network, which is a broader effort (as outlined in its goals<https://www.icann.org/en/government-engagement/wsis20-outreach-network>) beyond the ICANN community that the ICANN organization currently facilitates. Membership ICANN community participation in the discussion group is optional. Each Supporting Organization and Advisory Committee may designate up to two participants. Discussion group participants should be willing to participate and contribute their knowledge about the WSIS+20 review process. Discussion group participants will be members in their individual capacity and not representatives of their appointing ICANN community group. ICANN’s Role The ICANN organization will convene the discussion group and will invite participation from the ICANN community. In addition to facilitating the discussion group, the ICANN organization will have a distinct role in that it will share its thinking and analysis to inform the approaches that the ICANN community and the technical community may consider in the context of the WSIS+20 review process. Support In addition to its distinct role as a participant, the ICANN organization will provide subject matter experts and operational support to the discussion group. Operational support may include a mailing list, virtual meetings, and a workspace (e.g., GoogleDrive or Atlassian Confluence wiki), as determined by the participants. There are no budgetary resources or travel support for the discussion group, which will cease to exist at the conclusion of the WSIS+20 Review process. ** Kind regards, At-Large Staff At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [signature_1936264891]

3 2

CORRECTION: ALAC Chair Call for Nomintions
by Heidi Ullrich Sept. 12, 2024

Sept. 12, 2024

Dear All, Please note the corrected list of next year’s ALAC members below. Apologies for the oversight. Kind regards, Heidi From: ICANN Staff <staff(a)atlarge.icann.org> Date: Tuesday, September 10, 2024 at 11:59 AM To: "alac(a)atlarge-lists.icann.org" <alac(a)atlarge-lists.icann.org> Cc: Jonathan Zuck <JZuck(a)innovatorsnetwork.org>, ICANN Staff <staff(a)atlarge.icann.org> Subject: ALAC Chair Call for Nomintions Dear All, On behalf of Jonathan Zuck, we would like to announce the timetable for the ALAC Chair selection process. The roster of 2024-2025 ALAC Members is now complete (see: the 2024 ALAC and RALO Elections, Selections, and Appointments workspace<https://community.icann.org/display/atlarge/2024+ALAC+and+RALO+Elections%2C…>). The ALAC Rules of Procedure<https://community.icann.org/display/atlarge/Rules+of+Procedure?preview=/226…> (RoP) Article 5.2 states "A person nominated to be Chair does not need to be an ALAC Member at the time of nomination but must have an expectation of being an ALAC Member after the next ALAC Annual General Meeting...". The 15 known Members on next year's ALAC are (in alphabetical order of region and family name): AF: Raihanath Gbadamassi, Aziz Hilali, Bukola Oronti AP: Satish Babu, Justine Chew, Shah Zahidur Rahman EU: Pari Esfandiari, Natálie Terčová, Emilia Zalewska-Czajczyńska LAC: Claire Craig, Lilian Ivette de Luque Bruges, Eunice Alejandra Pérez Coello NA: Eduardo Diaz, Judith Hellerstein, Kathleen Scoggin Nominations, including self-nominations, are now being accepted. In accordance with the ALAC RoPs, this Call for Nominations will remain open for no less than 14 days and will end at 23:59 UTC on 22 September. ONLY CURRENT ALAC MEMBERS MAY MAKE NOMINATIONS. Nominations must be sent to the ALAC list. Messages accepting {or declining nominations] must be sent to the ALAC list no later than 7 days after the close of nominations by 23:59 UTC on 27 September. If there is more than one candidate, there will be an opportunity to talk to the candidates during a special ALAC Meeting and an election will be held starting 7 October 2024. The winner must receive votes from the majority of sitting ALAC Members. The ALAC RoPs Section 17.2 details the election procedure and how to proceed in the case of a variety of unusual conditions. The full selection schedule for the ALAC Chair is outlined below: Selection Schedule for ALAC Chair: · 9 September 2024 - Announcement of call for nominations and Nominee's Statement. (Only current ALAC Members may make nominations. Nominations must be sent to the ALAC list.) · 9 September 2024 - 22 September 2024 (23:59 UTC) - Nomination period (nominations accepted for 14 calendar days). · 27 September 2024 (23:59 UTC) - Nomination acceptance deadline. Messages accepting or declining nominations must be sent to the ALAC list no later than 7 days after the close of nominations. · 7 October 2024- 11 October 2024- Elections (If required, elections will begin no later than one week after the deadline for nomination acceptances and end no later than two weeks after that deadline). The winner must receive votes from the majority of sitting ALAC Members. The ALAC RoP Section 17.2<https://community.icann.org/display/atlarge/Rules+of+Procedure> details the election procedure and how to proceed in the case of a variety of unusual conditions. · 2024 AGM [ ICANN81 ] - The newly elected ALAC Chair shall be seated at the 2024 AGM following the close of the Board Meeting on 14 November 2024. Kind regards, At-Large Staff At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [signature_279756756]

6 7

RECORDED / ALAC Chair Nomination
by Yesim Saglam Sept. 11, 2024

Sept. 11, 2024

Dear Eduaro, Your nomination is recorded. Thank you. Kind Regards, Yeşim Sağlam From: Eduardo Diaz via ALAC <alac(a)icann.org> Reply-To: Eduardo Diaz <eduardodiazrivera(a)gmail.com> Date: 11 September 2024 Wednesday at 00:25 To: ALAC Working List <alac(a)atlarge-lists.icann.org> Subject: [ALAC] ALAC Chair Nomination I nominate Jonathan Zuck for the position of ALAC Chair for the term from AGM 2024 to AGM 2025. -ed

1 0

ALAC Chair Call for Nomintions
by ICANN At-Large Staff Sept. 10, 2024

Sept. 10, 2024

Dear All, On behalf of Jonathan Zuck, we would like to announce the timetable for the ALAC Chair selection process. The roster of 2024-2025 ALAC Members is now complete (see: the 2024 ALAC and RALO Elections, Selections, and Appointments workspace<https://community.icann.org/display/atlarge/2024+ALAC+and+RALO+Elections%2C…>). The ALAC Rules of Procedure<https://community.icann.org/display/atlarge/Rules+of+Procedure?preview=/226…> (RoP) Article 5.2 states "A person nominated to be Chair does not need to be an ALAC Member at the time of nomination but must have an expectation of being an ALAC Member after the next ALAC Annual General Meeting...". The 15 known Members on next year's ALAC are (in alphabetical order of region and family name): AF: Raihanath Gbadamassi, Aziz Hilali, Bukola Oronti AP: Satish Babu, Justine Chew, Shah Zahidur Rahman EU: Pari Esfandiari, Natálie Terčová, Emilia Zalewska-Czajczyńska LAC: Claire Craig, Lilian Ivette de Luque Bruges, Eunice Alejandra Pérez Coello NA: Eduardo Diaz, Bill Jouris, Jonathan Zuck Nominations, including self-nominations, are now being accepted. In accordance with the ALAC RoPs, this Call for Nominations will remain open for no less than 14 days and will end at 23:59 UTC on 22 September. ONLY CURRENT ALAC MEMBERS MAY MAKE NOMINATIONS. Nominations must be sent to the ALAC list. Messages accepting {or declining nominations] must be sent to the ALAC list no later than 7 days after the close of nominations by 23:59 UTC on 27 September. If there is more than one candidate, there will be an opportunity to talk to the candidates during a special ALAC Meeting and an election will be held starting 7 October 2024. The winner must receive votes from the majority of sitting ALAC Members. The ALAC RoPs Section 17.2 details the election procedure and how to proceed in the case of a variety of unusual conditions. The full selection schedule for the ALAC Chair is outlined below: Selection Schedule for ALAC Chair: · 9 September 2024 - Announcement of call for nominations and Nominee's Statement. (Only current ALAC Members may make nominations. Nominations must be sent to the ALAC list.) · 9 September 2024 - 22 September 2024 (23:59 UTC) - Nomination period (nominations accepted for 14 calendar days). · 27 September 2024 (23:59 UTC) - Nomination acceptance deadline. Messages accepting or declining nominations must be sent to the ALAC list no later than 7 days after the close of nominations. · 7 October 2024- 11 October 2024- Elections (If required, elections will begin no later than one week after the deadline for nomination acceptances and end no later than two weeks after that deadline). The winner must receive votes from the majority of sitting ALAC Members. The ALAC RoP Section 17.2<https://community.icann.org/display/atlarge/Rules+of+Procedure> details the election procedure and how to proceed in the case of a variety of unusual conditions. · 2024 AGM [ ICANN81 ] - The newly elected ALAC Chair shall be seated at the 2024 AGM following the close of the Board Meeting on 14 November 2024. Kind regards, At-Large Staff At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [signature_279756756]

1 0

CALL FOR COMMENTS Monday 2-6 September - ALAC statement on the IRP-IOT – Proposed updates to the IRP Supplementary Procedures-
by ICANN At-Large Staff Sept. 2, 2024

Sept. 2, 2024

Dear OFB-WG and ALAC members, On July 03, the Public Comment proceeding opened for the IRP-IOT-Proposed updates to the IRP Supplementary Procedures. Pari Esfandiari and Bukola Oronti volunteered to draft the ALAC statement in response to the Public Comment for the IRO-IOT- Proposed updates to the IRP Supplemental Procedures. On 29 August 2024, the final draft was presented to the OFB-WG membership by the 2 penholders. This is a call for comments to all OFB-WG and ALAC members, open from Monday 02 September until Friday 06 September at 23:59 UTC. Please kindly review the draft statement and insert any comments using the comment function. See the Draft ALAC Public Comment Statement: https://docs.google.com/document/d/14Fp9GY1HCGejvW_ElJk1xwicHgeFUuF0SHUpb_d… For background information see wiki: At-Large Workspace: IRP-IOT – Proposed updates to the IRP Supplementary Procedures<https://community.icann.org/pages/viewpage.action?pageId=354353169> Thank you very much! At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://facebook.com/icannatlarge> Twitter: @ICANNAtLarge<https://twitter.com/ICANNAtLarge> [signature_2879150646]

1 0