- ripe-list - mailman.ripe.net

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

NRO Strategy Document 2026-2028
by Ulka Athale 11 Jun '26

11 Jun '26

This message is sent on behalf of the Number Resource Organization (NRO) ------------------- The announcement can be viewed at: https://www.nro.net/nro-strategy-document-2026-2028/ ------------------- NRO Strategy Document 2026-2028 The Number Resource Organization (NRO), the coordinating body of the Regional Internet Registries, has published its Strategy Document for 2026–2028: https://www.nro.net/wp-content/uploads/NRO-Strategy-2026-2028-Document-FINA… The strategy document sets out three areas where the RIRs will work together over the next three years — focusing on issues where collective action delivers the greatest value to the global Internet community. ------------------- Internet Number Registry Governance ------------------- The NRO will coordinate implementation of the RIR Governance Document across all regions, serving as the main point of contact with ICANN on governance matters. Outputs will be published openly to support transparency and shared understanding across the community. ------------------- Security ------------------- The strategy continues the NRO’s focus on Internet routing security. Planned RPKI work includes delivery of a Trust Anchor Constraints document, deployment of Autonomous System Provider Authorization (ASPA), and ongoing reliability improvements across RIR systems. The NRO will also strengthen how RIRs share threat intelligence, establishing coordination processes and introducing metrics to measure their effectiveness. ------------------- IPv6 ------------------- Recognizing IPv6 as critical to the Internet’s future, the strategy prioritizes coordinated efforts across the RIRs to support its deployment — addressing barriers, sharing what is working across regions, and preparing for an environment where IPv4 is no longer dominant. Supporting a stable and secure Internet Through coordinated work on Internet number registry governance, security, and IPv6, the NRO aims to support a stable, secure, and scalable Internet number registry system for the benefit of the global Internet community. NRO Executive Council -- Kind regards, Ulka Athale Community Development Manager RIPE NCC www.ripe.net

1 0

New on RIPE Labs: Discovery of IPv6 Router Addresses Using Subnet-Router Anycast
by Alun Davies 11 Jun '26

11 Jun '26

Dear colleagues, In his new article on RIPE Labs, Maynard Koch investigates the use of subnet-router anycast probing to discover IPv6 router addresses at Internet scale and looks into its potential for Internet measurement and topology discovery: https://labs.ripe.net/author/mkoch/discovery-of-ipv6-router-addresses-using… Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

RIPE 93 Registration, Call for Presentations, Accommodation and More Information
by Meeting Mailbox 11 Jun '26

11 Jun '26

Dear colleagues, In this mail, you can find information about the following RIPE 93-related topics: 1. Registration and Ticket Options 2. Call for Presentations 3. Call for Sponsors 4. Local Hubs 5. RIPE Academic Collaboration Initiative (RACI) 6. Mentoring Programme 7. Accommodation 1. Registration and Ticket Options ---------------------------------------------- You can now register for RIPE 93 at: https://ripe93.ripe.net/register/attend-onsite/ RIPE 93 will take place at the Grand Hotel Millennium Sofia, Bulgaria, from 26-30 October 2026. Week ticket: €400 (Early Bird €350) Day ticket: €130 (Early Bird €125) Student (week) ticket: € 50 Dinner ticket: € 75 The early bird rate is available until 31 July 2026. You can find more information about onsite and online ticket options at: https://ripe93.ripe.net/register/ 2. Call for Presentations -------------------------------- The Call for Presentations is now open. You can find all necessary information here: https://ripe93.ripe.net/present/call-for-presentations/ 3. Call for Sponsors --------------------------- Supporting a RIPE Meeting through sponsorship gives your organisation fantastic exposure in the global Internet community. Get in touch with the RIPE Meeting team if you are interested in sponsoring RIPE 93: https://ripe93.ripe.net/about/sponsors/ 4. Local Hubs ------------------- Not everyone can travel to Sofia to attend RIPE 93 in person. Want to help bring the RIPE community together in your area? Host a Local Hub! https://ripe93.ripe.net/attend/local-hubs/ 5. RACI ----------- The RIPE Academic Cooperation Initiative (RACI) covers the cost of the meeting ticket, travel and accommodation for successful applicants to present their research at RIPE 93. Apply before 3 August at: https://www.ripe.net/community/community-initiatives/raci/ 6. Mentoring Programme ---------------------------------- The RIPE Meeting Mentoring Programme connects newcomers with experienced members of the community. RIPE Meetings have brought people together for over 25 years to talk about Internet operations, policy, and governance. As the community grows, we want everyone to feel welcome and involved—no matter their skills or experience. Want to be a mentor or find one? For more information about how to become a mentor or to be paired with a mentor, visit: https://ripe93.ripe.net/attend/mentoring-programme/ 7. Accommodation ------------------------- Due to the limited number of rooms available, please book your accommodation soon: https://ripe93.ripe.net/on-site/accommodation/ More information about RIPE 93 can be found at: https://ripe93.ripe.net/ Track the #RIPE93 hashtag on social media for the latest updates. See you in Sofia! Kind regards, Kajal Ince (For the RIPE Meeting Organisation Team)

1 0

New on RIPE Labs: What We Learned from a Multi-Service Vulnerability Disclosure
by Eleonora Petridou 10 Jun '26

10 Jun '26

Dear colleagues, Following the conversation at RIPE 92 around Sasha Romijn's presentation on our bug bounty program, I've written a RIPE Labs article about some of the practical lessons that came out of the recent coordinated vulnerability disclosure: https://labs.ripe.net/author/eleonora-petridou/what-we-learned-from-a-multi… Kind regards, Eleonora -- [image: This is Eleonora Petridou's card. Their email is epetridou(a)ripe.net. Their phone number is +31 6 55225554. Their phone number is +31 20 535 4444.] <https://hihello.me/p/d9c852ea-239c-4453-a05a-39552bc9e194?sharer_id=UAhnsts…>

1 0

Follow-up Notice to the RIR Community: ICANN Empowered Community Rejection Action Petition
by Ulka Athale 09 Jun '26

09 Jun '26

This message is sent on behalf of the Number Resource Organization ------------------ The announcement is available at: https://www.nro.net/follow-up-notice-to-the-rir-community-icann-empowered-c… ------------------ Follow-up Notice to the RIR Community: ICANN Empowered Community Rejection Action Petition ------------------ On 12 May 2026, the ASO Secretariat published a notice to the RIR community regarding the ICANN Board’s approval of several items subject to the ICANN Empowered Community rejection process, including the Standard Bylaws Amendment to Article 27 of the ICANN Bylaws. That notice informed the RIR community that the ICANN Board had approved, on 3 May 2026, a proposed amendment to Article 27 of the ICANN Bylaws to create a temporary pause and reset mechanism for ICANN’s Specific Reviews. It also noted that, during the applicable Rejection Action Petition Period, any individual could submit a petition to any Decisional Participant seeking to reject the Board action. Following that notification, the At-Large Advisory Committee (ALAC), acting as an ICANN Empowered Community Decisional Participant, issued a Rejection Action Petition concerning the proposed Standard Bylaws Amendment to add Section 27.6, “Timing for Specific Reviews,” to the ICANN Bylaws. The ASO subsequently received a request to consider supporting the Community Rejection Petition. In response, the NRO Executive Council reached out to the RIR communities through the respective CCG mailing lists to seek input on whether the ASO should support the Community Rejection Petition. NRO Announcement: https://www.nro.net/notice-to-the-rir-community-request-for-aso-considerati… AFRINIC: https://lists.afrinic.net/pipermail/announce/2026/002566.html APNIC: https://orbit.apnic.net/hyperkitty/list/apnic-talk@lists.apnic.net/thread/B… ARIN: https://lists.arin.net/pipermail/arin-announce/2026-June/003014.html LACNIC: https://mail.lacnic.net/pipermail/anuncios/2026-June/001484.html RIPE NCC: https://mailman.ripe.net/archives/list/ripe-list@ripe.net/thread/KSR4GXIOMH… No input in support of the petition was received from the RIR communities through this process. As a result, and in accordance with the ASO’s consideration of Empowered Community matters, the ASO will not support the Community Rejection Petition. This notice is provided to inform the RIR community of the outcome of the consultation and the resulting ASO position. The ASO Secretariat -- Kind regards, Ulka Athale Community Development Manager RIPE NCC www.ripe.net

1 0