September 2026 - ripe-list - mailman.ripe.net

Updated RIPE Code of Conduct Team: Appointment and Responsibilities (for your review)
by Mirjam Kuehne 11 Sep '26

11 Sep '26

Dear colleagues, The original document that describes the appointment and responsibilities of the RIPE Code of Conduct Team was published as ripe-793 in 2023. [1] With the experience gained by the Code of Conduct Team, the RIPE Chair Team and the community at large, it is time to update this document. You can find the new draft version (including a document showing the changes made) on the website: https://www.ripe.net/publications/docs/ripe-documents/other-documents/draft… The main changes are made in the section describing terms and term limits. Term limits were originally introduced to avoid long-term emotional burden on the team members and to avoid complacency. However, it was recognised that especially related to a code of conduct team, building trust and providing continuity carry more weight than regular rotation of team members. Having said that, it is important to make sure team members are not overloaded and don't feel obliged to continue. Therefore we introduce a scheduled conversation with the RIPE Chair after each term ends. In addition to that, the team is always open for volunteers which ensures new members can be added at any time. I would like to thank the members of the RIPE Code of Conduct Team for their constructive and valuable contributions that led to this draft document. Please review the document and send any questions or comments to the RIPE List or directly to me at chair at ripe dot net before 24 October 2026. Kind regards, Mirjam Kühne RIPE Chair [1] RIPE Code of Conduct Team: Appointment and Responsibilities https://www.ripe.net/publications/docs/ripe-793/

1 0

Transfer of internet resource policy, change of business structure
by Lucas Rolff 10 Sep '26

10 Sep '26

Hello, I'm currently in the process of converting from a sole proprietorship to a BV (Limited company for those outside NL). As a part of this process, there's obviously a bunch of work that has to be done with various vendors, including RIPE NCC in terms of the LIR membership and the resources I currently have under my LIR account. While I was reading through the RIPE-831 policy (Transfer of Internet Number Resources and Change of a Member’s Official Legal Name). I kind of got the impression based on section 3.6 Transfers of Internet Number Resources under Policy Restrictions Due to a Change in the Member's Business Structure, that change of structure, obviously has to be communicated to RIPE NCC, but that it explicitly mentions that resources can remain within the original LIR account as a part of changing the business structure (The tax office in Netherlands consider it a business structure change, if you convert the sole proprietorship to a limited company, because there's the assumption that the limited company will fully absorb the sole proprietorship and it's assets) I however, had a few other questions for RIPE as a part of this process, but I was at the same time told that apparently? RIPE does not consider it a change of business structure, and thus requires a new LIR account for the internet resources. Is it me that fully misunderstood the policy and specifically section 3.6? - Lucas R

2 1

New on RIPE Labs: The /3 Body Problem
by Alun Davies 10 Sep '26

10 Sep '26

Dear colleagues, In this new article, Remco van Mook looks at what happens when IPv6 addressing leaves Earth, and what the RIR communities might need to decide as space networking moves from theory towwards deployment: https://labs.ripe.net/author/remco-van-mook/the-3-body-problem/ Comments and feedback very welcome as always! Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

RIPE93 Second Call for Presentations
by Massimiliano Stucchi 08 Sep '26

08 Sep '26

Dear colleagues, The RIPE Programme Committee (PC) has opened the second call for presentations seeking for content proposals from the RIPE community for the plenary sessions, lightning talks and BoFs. RIPE93 will be a hybrid meeting so both in-person and virtual presentations would be accepted and encouraged. The deadline to submit a presentation proposal is Monday 14 of September 2026. Proposals submitted after this date will only be considered if there are still time slots available. Already submitted presentations which have not received an acceptance or rejection notification yet are still under consideration. You can read more about the CfP and submit your proposal at: https://pretalx.ripe.net/ripe-93/cfp More about the RIPE93 Meeting: https://ripe93.ripe.net/ Regards, Massimiliano Stucchi (On Behalf of the RIPE Programme Committee)

1 0

New on RIPE Labs: When Traceroutes Lie - How TTL Jumps Can Give Us a False Impression of the Internet’s Topology
by Alun Davies 03 Sep '26

03 Sep '26

Dear colleagues, Sebastian Kappes and colleagues look at how routers that rewrite TTL values can cause traceroute to miss parts of a path and give a misleading picture of how networks are interconnected: https://labs.ripe.net/author/shk/when-traceroutes-lie-how-ttl-jumps-can-giv… Comments and feedback very welcome as always! Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

New on RIPE Labs: The IRR Landscape - What RPKI Can Replace
by Alun Davies 01 Sep '26

01 Sep '26

Dear colleagues, In the third part of their series on the IRR landscape, Matthias Wichtlhuber and colleagues use routing and traffic data from AMS-IX and DE-CIX to ask which parts of the IRR ecosystem can safely be replaced by RPKI today: https://labs.ripe.net/author/mw/the-irr-landscape-what-rpki-can-replace/ Comments and feedback are very welcome as always! Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Reminder: Nominations to Fill One Seat on the NRO NC
by Hans Petter Holen 01 Sep '26

01 Sep '26

Dear colleagues, This is a reminder that nominations are open to fill one seat on the Number Resource Organization Number Council (NRO NC). The seat will be filled by appointment by the RIPE NCC Executive Board for a three-year term, from 1 January 2027 to 31 December 2029. The NRO NC performs the role of the Address Supporting Organization Address Council (ASO AC), including overseeing the Global Policy Development Process, advising the ICANN Board on Internet number resource policy, and nominating individuals to serve in key ICANN roles. Any individual residing within the RIPE NCC service region, who has participated in at least three RIPE Meetings, is eligible for nomination, except Regional Internet Registry (RIR) staff members. Self-nominations are permitted. Nominations should include the nominee’s name, country of residence, organisation or employer, email address and motivation for nomination, as well as the name and organisation of the person making the nomination. Please send nominations to nominations(a)ripe.net no later than 23:59 UTC on Wednesday, 30 September 2026. Nominees will need to accept the nomination, provide identification for verification and agree to adhere to the RIPE Code of Conduct by 14 October 2026. The list of confirmed nominees will be published by 15 October 2026. More details are available at: https://www.ripe.net/community/nro-nc/nro-nc-nominations-october-2026/ Kind regards, Hans Petter Holen Chief Executive Officer RIPE NCC --------------------- Important Dates ---------------------- 30 September 2026: Deadline for NRO NC nominations 14 October 2026: Deadline for nominees to complete the confirmation requirements 15 October 2026: Final date for publication of the list of confirmed nominees 30 October 2026: Final date for announcement of the Board appointment 26-30 October 2026: RIPE 93 Meeting

1 0

Recommended Draft RIR Governance Document, Rationale Report, and next steps
by Ulka Athale 01 Sep '26

01 Sep '26

This message is sent on behalf of the Number Resource Organization ----------------------- Recommended Draft RIR Governance Document, Rationale Report, and next steps ----------------------- The Number Resource Organization Executive Council (NRO EC) had announced that the Number Council (NC) concluded its work to review and update Internet Coordination Policy-2 (ICP-2): Criteria for Establishment of New Regional Internet Registries following its delivery of the ‘ASO AC Recommended Draft RIR Governance Document‘. The NRO NC is now sharing that document, including a redline version for comparison to the second draft, and a rationale document that details the changes between version two and version three of the document. ASO AC Recommended Draft RIR Governance Document: https://www.nro.net/policy/internet-coordination-policy-2/rir-governance-do… Redline version: https://www.nro.net/wp-content/uploads/RIR-Gov-Doc.-v3.-redline.pdf Rationale document: https://www.nro.net/wp-content/uploads/Draft-v3-Changes-and-Rationale-24082… The key changes in version three include: - Clearer definitions and decision-making provisions, including new or amended definitions for Audit, Compliance Review, Rehabilitation Plan, Temporary Emergency Continuity Arrangement, Temporary Emergency Operator, and Transition Plan. - A restructured Recognition process, with more detailed proposal and review requirements, a two-thirds Regional Internet Registry (RIR) support threshold, conflict-of-interest disclosure, clearer ICANN responsibilities, and greater transparency through the publication of assessments and rationales. - Clarifications to Service Region, Coordination Limitation, and Community Consultation provisions to improve readability and explain how consultation may occur during Recognition or Derecognition processes. - A revised audit and compliance framework, including a five-year regular audit cycle, a distinct Compliance Review process with safeguards against misuse, and clearer outcomes and follow-up through Rehabilitation Plans where needed. - Updated emergency continuity provisions, including terminology changes, the ability for an affected RIR to initiate a Temporary Emergency Continuity Arrangement for its own services, a lowered initiation threshold involving ICANN and two-thirds of the RIRs, a retained 90-day limit, and additional transparency safeguards. - A more detailed Derecognition process that emphasizes rehabilitation as the preferred path, aligns key steps with the Recognition process, clarifies ICANN’s review and decision-making role, requires publication of decisions and supporting documents, and applies a two-thirds RIR support threshold excluding the subject RIR. - New amendment safeguards that prevent the document from being amended during a Temporary Emergency Continuity Arrangement or while a proposal for Derecognition is pending. By setting out these changes and the accompanying reasons, the NRO NC hopes to help readers understand the major considerations weighed in developing version three and how the draft seeks to address the main community concerns during the feedback process. We sincerely thank everyone who has shared their insights, and we appreciate the time, thought and effort put in by our respondents. On behalf of the NRO NC * The NRO NC is also known as the Address Supporting Organization Address Council (ASO AC) within ICANN, where it serves as the body responsible for overseeing global policy development related to Internet number resources. -- Kind regards, Ulka Athale Community Development Manager RIPE NCC www.ripe.net

1 0