- ripe-list - mailman.ripe.net

The RIPE Chair Team Reports - July 2026
by Mirjam Kuehne 08 Jul '26

08 Jul '26

Dear colleagues, In this new update on RIPE Labs, we talk about the latest developments across the community, from RIPE 93 preparations and policy work to governance updates and community activities: https://labs.ripe.net/author/mirjam_kuhne/the-ripe-chair-team-reports-july-… Kind regards, Mirjam Kühne and Anna Wilson RIPE Chair Team

2 2

New on RIPE Labs: Birds of a Feather at IETF 126 Vienna
by Alun Davies 08 Jul '26

08 Jul '26

Dear colleagues, Greg Wood looks ahead to the Birds-of-a-Feather (BoF) sessions coming up at IETF 126 in Vienna to give us a run down on where Internet standards work may be heading next, from HTTP and transport security to AI agent communication: https://labs.ripe.net/author/greg-wood/birds-of-a-feather-at-ietf-126-vienn… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

ASO Decision on ICANN Fundamental Bylaws Amendments to Articles 17 and 18
by Ulka Athale 07 Jul '26

07 Jul '26

This message is sent on behalf of the Number Resource Organization (NRO) ----------------- The announcement is available at: https://www.nro.net/aso-decision-on-icann-fundamental-bylaws-amendments-to-… ----------------- Summary The Number Resource Organization (NRO) serves as the Address Supporting Organization (ASO) within the ICANN framework. The ICANN Board approved amendments to Articles 17 and 18 of the ICANN Fundamental Bylaws. Upon review of the amendments and in the absence of substantive feedback from the RIR communities, the Number Resource Organization Executive Council (NRO EC) has determined that the ASO will support the Approval Action concerning the Fundamental Bylaws Amendments to Articles 17 and 18 of the ICANN Bylaws. ----------------- ASO Decision on ICANN Fundamental Bylaws Amendments to Articles 17 and 18 ----------------- The Number Resource Organization Executive Council (NRO EC), acting in relation to the Address Supporting Organization’s role as a Decisional Participant in the ICANN Empowered Community, has considered the ICANN Board-approved Fundamental Bylaws Amendments to Articles 17 and 18 of the ICANN Bylaws. This decision follows the previous notices published on the NRO website regarding this Approval Action process: - Notice to the ASO Community on the Approval Action Community Forum on Board Approval of Fundamental Bylaws Amendments to Articles 17 and 18 of the ICANN Bylaws: https://www.nro.net/notice-to-the-aso-community-on-approval-action-communit… - Follow-up Notice to the ASO Community on the Approval Action Decision Period for Fundamental Bylaws Amendments to Articles 17 and 18 of the ICANN Bylaws: https://www.nro.net/follow-up-notice-to-the-aso-community-on-the-approval-a… The Approval Action Community Forum was held during ICANN 86. Following the Community Forum, the Approval Action Decision Period began and concluded at 23:59 PST on Thursday, 2 July 2026. The amendments were approved by the ICANN Board on 3 May 2026. They relate to the governance and review mechanisms associated with the IANA naming function, specifically the Customer Standing Committee (CSC) under Article 17 and the IANA Naming Function Reviews (IFRs) under Article 18. The Article 17 amendments update the governance and operating rules of the CSC, including the introduction of alternate CSC members and alternate liaisons, the movement of certain operational details from the ICANN Bylaws to the CSC Charter, and the extension of the regular CSC effectiveness review cycle from three years to five years. Article 17 continues to provide that the ASO/NRO may appoint a liaison to the CSC; however, the CSC’s role remains focused on the IANA naming function and outside the scope of Internet number resources. The Article 18 amendment adjusts how the five-year cycle for future IANA Naming Function Reviews is calculated. Under the approved amendment, the cycle will begin when the previous IFR team submits its final report to the ICANN Board, rather than when the previous review team was first convened. The amendment does not change the purpose, scope, composition, or powers of the IFR. The RIR community was informed of the Approval Action Community Forum through the first notice and was subsequently invited to provide comments during the Approval Action Decision Period through the follow-up notice. After reviewing the amendments and considering the absence of any substantive concerns from the RIR community, the NRO EC determined that the amendments do not create any new obligation or operational impact for the ASO, the NRO, the Regional Internet Registries, or the Internet number resources community. Accordingly, in accordance with the ASO Procedure for Empowered Community Approval Actions, the NRO EC has determined that the ASO will support the Approval Action concerning the Fundamental Bylaws Amendments to Articles 17 and 18 of the ICANN Bylaws. The ASO EC Administration Representative notified the ICANN Empowered Community Administration of the ASO’s decision. Relevant documents: ICANN Board resolutions, 3 May 2026 https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… Proposed updates to Article 17 — Customer Standing Committee https://itp.cdn.icann.org/en/files/governance/proposed-updates-to-article-1… Proposed updates to Article 18 — IANA Naming Function Reviews https://itp.cdn.icann.org/en/files/governance/proposed-updates-to-article-1… ASO Procedure for Empowered Community Approval Actions https://www.nro.net/accountability/aso-and-icann-accountability/icann-empow… Regards, The ASO Secretariat -- Kind regards, Ulka Athale Community Development Manager RIPE NCC www.ripe.net

1 0

RIPE 93 Call for Local Hubs
by Gergana Petrova 07 Jul '26

07 Jul '26

Dear colleagues, We want to help people who can’t physically join a RIPE Meeting to participate remotely and in a more engaging way. Do you want to facilitate a space for them to meet in your city? If yes, organise a Local Hub! Local Hubs are in-person gatherings that run alongside the RIPE Meeting. They give registered participants the chance to: - Watch the webcast of the RIPE Meeting - Follow discussions and take part remotely via chat, audio, or video - Connect face-to-face with other community members locally - Share perspectives, ideas, and discussions rooted in their local context As a host, you can also tailor the experience by adding local discussions or debates around RIPE Meeting topics that matter most to your community. Interested? You can find all the details at: https://ripe93.ripe.net/attend/local-hubs/ Local Hubs can be organised at any time, but if you let us know by Monday, 14 September 2026, we’ll be able to feature your Local Hub on the RIPE 93 website and provide additional technical information, promotion, and support. We are looking forward to hearing from you. Best regards, Gergana --- Gergana Petrova Community Development RIPE NCC

1 0

New on RIPE Labs: When Internet Traffic Becomes a Physical Event
by Alun Davies 06 Jul '26

06 Jul '26

Dear colleagues, Drawing on observations from Namex, Flavio Luciani explores how synchronised digital events reveal the physical nature of Internet traffic, and why collective user behaviour can place concentrated pressure on network infrastructure: https://labs.ripe.net/author/flavio_luciani_1/when-internet-traffic-becomes… Comments and discussion welcome as always! Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Draft RIPE 92 Community Plenary Minutes
by Mirjam Kuehne 01 Jul '26

01 Jul '26

Dear colleagues, The minutes of the RIPE 92 community plenary are ready for review: https://www.ripe.net/community/ripe-governance/ripe-community-plenary/minut… Please let me know if you have any comments. Kind regards, Mirjam Kühne RIPE Chair

1 0

New on RIPE Labs: ASPA Is Live. Can You See It Working?
by Alun Davies 29 Jun '26

29 Jun '26

Dear colleagues, In this new article, Ritesh Mukherjee talks about a current observability gap around ASPA and introduces RAVEN, an open-source tool that combines BMP and RTR data to show ROV and ASPA validation in real time, including route leaks that ROV alone cannot detect: https://labs.ripe.net/author/ritesh-mukherjee/aspa-is-live-can-you-see-it-w… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

New on RIPE Labs: IPv6-Only vs IPv6-Mostly - Appropriate Use Cases
by Alun Davies 24 Jun '26

24 Jun '26

Dear colleagues, In this new article on RIPE Labs, Jordi Palet Martínez looks at the distinction between IPv6-Only and IPv6-Mostly, outlines their respective use cases, and argues that matching the right model to the right environment is key to success: https://labs.ripe.net/author/jordipaletm/ipv6-only-vs-ipv6-mostly-appropria… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Follow-up Notice to the ASO Community on the Approval Action Decision Period for Fundamental Bylaws Amendments to Articles 17 and 18 of the ICANN Bylaws
by Ulka Athale 15 Jun '26

15 Jun '26

This message is sent on behalf of the Number Resource Organization (NRO) --------- The original announcements are available on the NRO website: https://www.nro.net/follow-up-notice-to-the-aso-community-on-the-approval-a… --------- Summary This notice announces the 21-day Approval Action Decision Period that was started following the conclusion of the Approval Action Community Forum held during ICANN 86 to allow the ICANN community to discuss the recently approved ICANN Fundamental Bylaws Amendments. The ICANN Board recently approved amendments to Article 17 Customer Standing Committee and Article 18 IANA Naming Function Reviews. The deadline to send comments to the ASO Secretariat at secretariat at aso.icann.org is 23:59 PST on Thursday, 2 July 2026 (3 July at 6:59 UTC). --------- Follow-up Notice to the ASO Community on the Approval Action Decision Period for Fundamental Bylaws Amendments to Articles 17 and 18 of the ICANN Bylaws Dear RIR Community, This announcement is a follow-up to the notice published on 29 May 2026 regarding the Approval Action Community Forum on the ICANN Board’s approval of Fundamental Bylaws Amendments to Articles 17 and 18 of the ICANN Bylaws: https://www.nro.net/notice-to-the-aso-community-on-approval-action-communit… As a Decisional Participant in the ICANN Empowered Community, the Address Supporting Organization previously received a notification from the ICANN Secretary concerning the ICANN Board’s approval of these Fundamental Bylaws Amendments. On 3 May 2026, the ICANN Board approved the proposed Fundamental Bylaws Amendments to Article 18, Section 18.2(b), through Resolution 2026.05.03.11, and the proposed Fundamental Bylaws Amendments to Article 17, through Resolution 2026.05.03.12. The ICANN Board also approved related updates to the Customer Standing Committee (CSC) Charter through Resolution 2026.05.03.13. The ICANN Board resolutions are available at: https://www.icann.org/en/board-activities-and-meetings/materials/approved-r… The documents reviewed in relation to these amendments are available at: Proposed updates to Article 17 — Customer Standing Committee: https://itp.cdn.icann.org/en/files/governance/proposed-updates-to-article-1… The proposed amendments to Article 17 relate to the governance and operating rules of the Customer Standing Committee (CSC), which monitors the performance of the IANA naming function. The proposed changes would introduce alternate CSC members and alternate liaisons, simplify outdated language related to the initial establishment of the CSC, and move certain operational details, such as attendance requirements and vacancy-filling procedures, from the Bylaws to the CSC Charter. The amendments would also extend the regular CSC effectiveness review cycle from three years to five years, while preserving the possibility of earlier reviews if requested by relevant bodies. Proposed updates to Article 18 — IANA Naming Function Reviews: https://itp.cdn.icann.org/en/files/governance/proposed-updates-to-article-1… The proposed amendment to Article 18 relates to the timing of future IANA Naming Function Reviews (IFRs). The change would adjust the way the five-year review cycle is calculated, so that the period begins when the previous IFR team submits its final report to the ICANN Board, rather than when the previous review team was first convened. This would help ensure that the timing of future reviews is based on the completion of the prior review process. The proposed amendment does not change the purpose, scope, composition, or powers of the IFR, and it remains focused on the IANA naming function. In accordance with the ICANN Bylaws, an Approval Action Community Forum was convened during ICANN 86 to allow the ICANN community to discuss the approved Fundamental Bylaws Amendments. Record of the Approval Action Community Forum can be found here: https://icann86.sched.com/event/2NQQy/icann-empowered-community-community-f… Following the conclusion of the Approval Action Community Forum, a new 21-day period, known as the Approval Action Decision Period, has now begun. During this period, each Decisional Participant must decide whether to support, object to, or abstain from the Approval Action. The Approval Action Decision Period will expire at 23:59 PST on Thursday, 2 July 2026 (3 July at 6:59 UTC). Any comments from the RIR community on these ICANN Bylaws changes should be sent to the ASO Secretariat at secretariat at aso.icann.org no later than the above-mentioned deadline. The NRO Executive Council will consider any input received from the RIR community before taking a decision on the matter. Regards, ASO Secretariat ----------------- Background Information The NRO serves as the Address Supporting Organization (ASO) which is a Supporting Organization under ICANN's structure. The Empowered Community is the mechanism through which ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) can organize under California law to legally enforce community powers. The Community has nine powers to ensure the ICANN Board and Organization are accountable: - Reject ICANN and IANA budgets, and ICANN operating and strategic plans - Reject standard Bylaw amendments - Reject PTI governance actions - Approve fundamental Bylaw and Articles amendments, and asset sales - Recall the entire ICANN Board - Appoint and remove individual ICANN Board directors (other than the President) - Require the ICANN Board to review its rejection of IANA Function Review (IFR),special IFR, Separation Cross-Community Working Group (SCWG) creation,and SCWG recommendation decisions - Initiate community reconsideration request, mediation, or Independent Review Process (IRP) - The rights of inspection and investigation Read more about the Empowered Community here: https://www.icann.org/ec -- Kind regards, Ulka Athale Community Development Manager RIPE NCC www.ripe.net

1 0

RIPE Working Group Chair Job Description and Procedures published as ripe-861
by Mirjam Kuehne 15 Jun '26

15 Jun '26

Dear colleagues, The updated RIPE Working Group Chair Job Description and Procedures have now been published as ripe-861: https://www.ripe.net/publications/docs/ripe-861/ Kind regards, Mirjam Kühne RIPE Chair

1 0