- OFB-WG - lists.iana.org

[Final Reminder] ICANN81 Session Report
by ICANN At-Large Staff Nov. 13, 2024

Nov. 13, 2024

Hi all, This is a friendly reminder to populate the ICANN81 Session Report. Please use the following templated reporting format. The Session Reports will be highlighted during the ICANN81 At-Large Leadership Wrap Up session taking place tomorrow, 14 November 2024 at 15:00 local time during. ICANN81 Session Report link: https://community.icann.org/x/ToDlF Template format: What happened? Example: This session discussed.... What are the At-Large specific takeaways from this session? Example: At-Large is interested in... What are the At-Large specific action items (next steps)? Example: At-Large needs to... Please let us know if you have any questions. Kind Regards, ICANN Policy Staff in support of the At-Large Community

1 0

[Input Requested] ICANN81 Session Report
by ICANN At-Large Staff Nov. 11, 2024

Nov. 11, 2024

Dear At-Large Community Members, We hope ICANN81has been going well for you all. This is a friendly reminder to please sign up to provide your session reports for ICANN81. Please use the following templated reporting format and the following link to record your session reports. Please let us know if you have any issues recording your name or posting your report on the wiki page. Please also let us know if a session you are reporting on is missing and we will add the session to the wiki page. ICANN81 Session Report link: https://community.icann.org/x/ToDlF Template format: What happened? Example: This session discussed.... What are the At-Large specific takeaways from this session? Example: At-Large is interested in... What are the At-Large specific action items (next steps)? Example: At-Large needs to... Please let us know if you have any questions. Kind Regards, ICANN Policy Staff in support of the At-Large Community

1 0

[At-Large Community] ICANN81 Talking Points Document
by Andrew Chen Nov. 4, 2024

Nov. 4, 2024

Dear At-Large Community Members, Thank you to all of those who contributed to the ICANN81 Talking Points Document. As we prepare for ICANN81, we kindly request your attention to review the ALAC ICANN81 Talking Points linked below. These points are essential to ensure alignment on the ALAC’s messaging regarding ongoing topics of importance. ICANN81 Talking Points: https://docs.google.com/document/d/19HXdKJfjiV9xyrvcm2J-W_c8Uit9Hb1OsIer-20… Safe travels to those traveling to Istanbul, Türkiye. See you all soon. Sincerely, Andrew -- Andrew Chen Policy Development Support Sr. Specialist, Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org/ Skype: atchen122

1 0

Fwd: RIPE on ICP-2
by avri＠doria.org Oct. 31, 2024

Oct. 31, 2024

Hi, shared with CPWG and was reminded I should share here too. avri -------- Original Message -------- SUBJECT: RIPE on ICP-2 DATE: 2024-10-31 16:00 FROM: avri(a)doria.org TO: Cpwg <cpwg(a)icann.org> Hi, I have been online attending RIPE89 this week. As part of the RIPE Community Plenary 4. Report from the ASO AC and ICP-2 Community Consultation Hervé Clement, ASO AC https://ripe89.ripe.net/archives/video/1533 For anyone following the topic, it may be interesting hearing it from that side of the perspective. avri

1 0

ACTION: Volunteers for ALAC statement: Proposed Internet Coordination Policy 2 (ICP-2) Version 2 Principles
by ICANN At-Large Staff Oct. 30, 2024

Oct. 30, 2024

Dear OFB WG members, Message sent on behalf OFB co-chairs, Claire Craig and Jonathan Zuck, The OFB WG will draft an ALAC statement on the At-Large Workspace: Proposed Internet Coordination Policy 2 (ICP-2) Version 2 Principles<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Pro…>, Please kindly send your name to staff if you wish to volunteer to be a penholder. Thank you! 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_3195945787]

4 4

REQUEST FOR COMMENTS: ICANN81 Board Questions to the ALAC
by ICANN At-Large Staff Oct. 30, 2024

Oct. 30, 2024

Dear All, On behalf of Jonathan Zuck, ALAC Chair, you are requested to add your comments to two of the questions that the ICANN Board has asked the ALAC for discussion during the ICANN81 Board meeting with the ALAC. The two questions are below: 1. In addition to the resources that Org has provided, is there anything else that ALAC/At-Large needs to bring applicants into the Next Round from underserved communities? At-Large Shepherds: Hadia Elminiawi 1. ICANN's new CEO will come on board in December. What do you think his top three priorities should be, and why? Please be as concrete as possible. At-Large Shepherd: Justine Chew Please add your comments by Thursday, 7 November at 23:59 UTC using the comments function here: https://docs.google.com/document/d/1qTpHWuYlIvWDHIHcc166r85mK4hf2lVUSrsXMpW…. 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_215869771]

1 0

Fwd: [cip-ccg] Reminder by 31 October: Action requested: Finalization of Continuous Improvement Program Principles
by Sebicann Bachollet Oct. 30, 2024

Oct. 30, 2024

Dear colleagues, Please find the exchange of mails including the ones send by ICANN Org regarding Principal 4 and 5. Principal 4 I am for keeping « accountable » version Principal 5 Let’s confirm that At-Large (ALAC and the 5 Ralos) agrees with the following version > Confirmed change to Principle 5: “The SO, AC, or NomCom collaborates to further the mission of ICANN and the effectiveness of the ICANN bottom-up multistakeholder model.” Thanks All the best SeB Sébastien Bachollet +33 6 07 66 89 33 sebicann(a)bachollet.fr @SebBach EURALO Chair > Début du message réexpédié : > > De: Evin Erdogdu via cip-ccg <cip-ccg(a)icann.org> > Objet: [cip-ccg] Reminder by 31 October: Action requested: Finalization of Continuous Improvement Program Principles > Date: 28 octobre 2024 à 19:25:24 UTC+1 > À: "cip-ccg(a)icann.org" <cip-ccg(a)icann.org> > Répondre à: Evin Erdogdu <evin.erdogdu(a)icann.org> > > Dear CIP-CCG Volunteers, > > A kind reminder for your feedback by Thursday, 31 October in advance of ICANN81. Regarding Principle 4, seems the focus of CIP-CCG discussion is primarily centered on whether to include reference to "accountability”. > > 22 October version: > The SO, AC, or NomCom is accountable internally to its stakeholders and substructures (where applicable), and externally to the wider ICANN community in benefit of the global Internet population. > > 23 October version (suggested by GNSO representatives to the CIP-CCG): > The SO, AC, or NomCom adheres to ICANN’s mission and Bylaws with respect to its stakeholders and substructures (where applicable), and to the wider ICANN community in benefit of the global Internet population. > > Please view the redline of proposed changes here <https://docs.google.com/document/d/1jAisJH-FCvblCA0C0SSexmMI-Jl-ucU1ygNG1Pl…>. > > For context, ICANN Organizational Reviews as described in the ICANN Bylaws have asked whether the Supporting Organizations (SOs), Advisory Committees (ACs), and the Nominating Committee (NomCom) have a continuing purpose within the ICANN community. Rather than articulating this as a single principle, it an overarching consideration that is addressed through five separate principles that would guide the successful execution of the Continuous Improvement Program (CIP). The related criteria and indicators for each principle are intended to provide an opportunity for each structure to demonstrate how they comply with said principle (or whether improvement is needed to that end). > > The current ICANN Organizational Review objectives in the Bylaws state: > Organizational Reviews specifically assess: (i) whether that organization, council or committee has a continuing purpose in the ICANN structure; (ii) if so, whether any change in structure or operations is desirable to improve its effectiveness; (iii) whether that organization, council or committee isaccountable to its constituencies, stakeholder groups, organizations and other stakeholders. > > Please share your views regarding the inclusion of "accountability" in Principle 4 on the CIP-CCG list in advance of ICANN81 (31 October). If needed, a discussion and poll of the group could take place during ICANN81 (13 November), to finalize. > > Thank you all for your thorough engagement and attention, as always! > > Cheers, > Evin > > From: Tijani <tijani.benjemaa(a)topnet.tn <mailto:tijani.benjemaa@topnet.tn>> > Sent: Friday, October 25, 2024 3:02 AM > To: Evin Erdogdu; cip-ccg(a)icann.org <mailto:cip-ccg@icann.org> > Cc: Tijani > Subject: [Ext] Re: [cip-ccg] Action requested: Finalization of Continuous Improvement Program Principles > > Good morning Evin and all, > > For Principle 4, I see that the notion of accountability is contested and removed from the original text. > For the record, the accountability was a condition for the transition to happen: the accountability of ICANN to its community. If you contest the accountability, you should also contest the transition > There was in parallel with the cross community IANA transition WG a cross community WG on accountability and the result is that 9 powers are given to the community that must be considered by all including the ICANN Board of directors. And today, we are still speaking about a vagueness of the accountability. > > Again, this CIP is to replace the organizational reviews of the SOs, ACs and NomCom that are all ICANN community structures. It can’t be done out of the ICANN mission, governance model and accountability. > > I believe that the original text of Principle 4 is the more adequate for the CIP: > Principle 4: The SO, AC, or NomCom is accountable internally to its stakeholders and substructures (where applicable), and externally to the wider ICANN community in benefit of the global Internet population community. > For the record, we spent several months working on criteria and indicators based of the 5 already agreed on principles, and in the few past weeks, we receive new concerns about the principles and requests for removing the multistakeholder model and the accountability from these principles…. > > Tijani > > De : Evin Erdogdu via cip-ccg <cip-ccg(a)icann.org <mailto:cip-ccg@icann.org>> > Répondre à : Evin Erdogdu <evin.erdogdu(a)icann.org <mailto:evin.erdogdu@icann.org>> > Date : jeudi 24 octobre 2024 à 19:16 > À : "cip-ccg(a)icann.org <mailto:cip-ccg@icann.org>" <cip-ccg(a)icann.org <mailto:cip-ccg@icann.org>> > Objet : [cip-ccg] Action requested: Finalization of Continuous Improvement Program Principles > > Dear CIP-CCG volunteers, > > Further to the group’s meeting held yesterday, please find confirmed and proposed changes to Principles 4 & 5 for CIP-CCG feedback by Thursday, 31 October, in advance of ICANN81: > > Confirmed change to Principle 5: “The SO, AC, or NomCom collaborates to further the mission of ICANN and the effectiveness of the ICANN bottom-up multistakeholder model.” > > Per 23 October CIP-CCG meeting discussion, when polled the majority of CIP-CCG members expressed support for the inclusion of the ICANN multistakeholder model language in Principle 5. Only one CIP-CCG volunteer from the IPC did not support the change. > > Proposed change to Principle 4 (for CIP-CCG feedback): “The SO, AC, or NomCom adheres to ICANN’s mission and Bylaws with respect is accountable internally to its stakeholders and substructures (where applicable), and externally to the wider ICANN community in benefit of the global Internet community population.” > > Per 10/23 GNSO CIP group discussion, the proposed revisions for CIP-CCG to Principle 4 "address the vagueness argument related to 'accountability' and include the global Internet population that the (GNSO volunteers to the CIP-CCG) think is appropriate". > > You may also reference a new redline of these changes in the collaborative CIP-CCG Google Drive here [docs.google.com] <https://urldefense.com/v3/__https://docs.google.com/document/d/1jAisJH-FCvb…>. > > Thank you for your diligence and engagement, > >  > Evin Ashley Erdoğdu > Review Support & Accountability Project Manager > Internet Corporation for Assigned Names and Numbers (ICANN) > > _______________________________________________ cip-ccg mailing list -- cip-ccg(a)icann.org <mailto:cip-ccg@icann.org> To unsubscribe send an email to cip-ccg-leave(a)icann.org <mailto:cip-ccg-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. > _______________________________________________ > cip-ccg mailing list -- cip-ccg(a)icann.org <mailto:cip-ccg@icann.org> > To unsubscribe send an email to cip-ccg-leave(a)icann.org <mailto:cip-ccg-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.

4 4

At-Large Operations, Finance and Budget Working Group (OFB-WG)
by ICANN Policy Calendar Oct. 28, 2024

Oct. 28, 2024

EN - IMPORTANT INFORMATION FOR FRENCH AND SPANISH INTERPRETATION FR - INFORMATIONS IMPORTANTES POUR LES PARTICIPANTS EN FRANCAIS ET ESPAGNOL ES - INFORMACIÓN IMPORTANTE PARA LOS PARTICIPANTES FRANCESES Y ESPAÑOLES Dear All, EN - IMPORTANT INFORMATION FOR FRENCH AND SPANISH INTERPRETATION The Meetings Technical Services (MTS) and Languages Services (LS) Teams are running a preliminary test of the Zoom interpretation feature on community calls. * To listen to interpretation for this meeting, please join Zoom using Computer Audio. * Choose the language you will listen to from the Language Interpretation menu in the Zoom toolbar. * Before speaking, ensure you have selected the language you will speak from in the interpretation menu. If for any reason, the audio you are listening to is silent, please select “unmute original audio”. FR - INFORMATIONS IMPORTANTES POUR LES PARTICIPANTS EN FRANCAIS ET ESPAGNOL Les équipes des services techniques des reunions (MTS) et des services linquistiques (LS) effectuent un test préliminaire de la function di’interpretation Zoom sur les appels communautaires. * Pour écouter l’interprétation de cette reunion, veuillez rejoindre Zoom en utilisant l’audio ordinateur/tablette/telephone portable. Choisissez la langue que vous écouterez dans le menu “Interprétation” linquistique de la barre d’outils Zoom. * Avant de parler, assurez-vous d'avoir sélectionné la langue dans laquelle vous parlerez dans le menu d'interprétation. Si, pour une raison quelconque, l'audio que vous écoutez est silencieux, veuillez sélectionner « réactiver l'audio original ». ES - INFORMACIÓN IMPORTANTE PARA LOS PARTICIPANTES FRANCESES Y ESPAÑOLES Los equipos de Servicios Técnicos de Reuniones (MTS) y Servicios de Idiomas (LS) estám realizando una prueba preliminar de la función de interpretatción de Zoom en llamadas comunitarias. * Para escuchar la interpretación para esta reunión, únase a Zoom mediante Computer Audio * Elija el idioma que escucharà en el menu Interpretación de idiomas en la barra de herramientas de Zoom * Antes de hablar, asegúrese de haber seleccionado el idioma que hablará en el menú de interpretación. Si por algún motivo el audio que está escuchando está en silencio, seleccione "activar audio original". * Dear All, The next At-Large Operations, Finance and Budget Working Group (OFB-WG) Call is scheduled for Thursday, 05 December 2024 at 14:00 UTC for 60 mins. For other times: https://tinyurl.com/pj73pbym<https://tinyurl.com/yc6ypf3m> The agenda (to be updated) and call details can be found at: https://community.icann.org/x/NIATFw Zoom Room: https://icann.zoom.us/j/92139943237?pwd=RR7XGoRSXgUGFm2K4QKyAFEp54AzQb.1 / Password: OFBC#12345 Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN Wiki Workspace: https://community.icann.org/x/koTsBw Other toll-free numbers: https://www.adigo.com/icann [adigo.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.adigo.com_icann&d=…> If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, 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>

1 0

[At-Large Community] ICANN81 Board Engagement Session Talking Points
by ICANN At-Large Staff Oct. 25, 2024

Oct. 25, 2024

Dear At-Large Community Members, As we prepare for ICANN81 Prep Week, we kindly request your attention to review the ALAC/At-Large ICANN81 Board Engagement Session Talking Points<https://docs.google.com/document/d/16k6mnbxmXaVVEnT84TYsMpd-KowPuTxn227GjE9…> in preparation for the 28 October Board Engagement Session<https://sched.co/1nJjv>. These points are essential to ensure alignment on the ALAC/At-Large messaging regarding the Registration Data Request Service (RDRS) and New gTLD Program Applications in rounds or continuously accepting applications (first come, first serve). ICANN81 Board Engagement Session Talking Points: https://docs.google.com/document/d/16k6mnbxmXaVVEnT84TYsMpd-KowPuTxn227GjE9… Thank you to those who have contributed to the development of these talking points. Please let us know if you have any questions. 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>

1 0

Meeting invitation: At-Large Operations, Finance and Budget Working Group (OFB-WG) Call on Thursday, 24 October 2024 at 18:00 UTC
by ICANN At-Large Staff Oct. 24, 2024

Oct. 24, 2024

***If you require a dial out or need to state an apology, please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number*** Dear All, The next At-Large Operations, Finance and Budget Working Group (OFB-WG) Call is scheduled for Thursday, 24 October 2024 at 18:00 UTC for 60 mins. For other times: https://tinyurl.com/yc6ypf3m The agenda (to be updated) and call details can be found at: https://community.icann.org/x/qoDvFg Zoom Room: https://icann.zoom.us/j/92139943237?pwd=RR7XGoRSXgUGFm2K4QKyAFEp54AzQb.1 / Password: OFBC#12345 Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN Wiki Workspace: https://community.icann.org/x/koTsBw ADIGO Conference Bridge: EN, ES & FR: 1638 (subject to availability) Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann [adigo.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.adigo.com_icann&d=…> If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, 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>

1 4