- address-policy-wg - mailman.ripe.net

Making Resource Holders Easier to Identify: Introducing reg-nr: in the RIPE Database
by Marco Schmidt 30 Apr '26

30 Apr '26

Dear colleagues, We’re happy to share that, as of 30 April, the reg-nr: attribute is now available in the RIPE Database following the completion of NWI-21. https://www.ripe.net/community/wg/active-wg/db/numbered-work-items/ First proposed at RIPE 91 in the Address Policy Working Group and then discussed further in the Database Working Group, it’s now in place ahead of RIPE 92. This is a great example of how community input can quickly turn into something tangible and useful. Thank you to all who provided feedback and contributed to this outcome. The reg-nr: attribute adds the official company registration number of resource holders to organisation objects co-maintained by the RIPE NCC. This makes it easier to clearly identify organisations, especially where names are similar or the same. Please note that this does not apply to all organisation objects. For privacy reasons, a reg-nr: with value "Not applicable" will be published for natural persons and governmental organisations. If you come across information that appears incorrect or incomplete, please let us know by sending an email to ripe-dbm(a)ripe.net. Our Member Services team will follow up. More details are available in the RIPE Labs article: https://labs.ripe.net/author/marco_schmidt/making-resource-holders-easier-t… Kind regards, Marco Schmidt Manager Registration Services RIPE NCC

1 0

2024-01 New Discussion Phase (Revised IPv6 PI Assignment Policy)
by Angela Dall'Ara 24 Apr '26

24 Apr '26

Dear colleagues,   Version 2 of RIPE policy proposal 2024-01 "Revised IPv6 PI Assignment Policy" is now available for discussion again. The proposers and the APWG Chairs decided to open a new Discussion Phase because of the limited feedback received in the previous one. You can find the full proposal at: https://www.ripe.net/community/policies/proposals/2024-01 As per the RIPE Policy Development Process (PDP), the purpose of this four-week Discussion Phase is to discuss the proposal and provide feedback to the proposers. At the end of the Discussion Phase, the proposers, with the agreement of the WG Chairs, will decide how to proceed with the proposal.   The PDP document can be found at: https://www.ripe.net/publications/docs/ripe-781  We encourage you to review this proposal and send your comments to  address-policy-wg(a)ripe.net before 24 April 2026.   Kind regards,   Angela Dall'Ara Policy Officer RIPE NCC

12 13

Draft Agenda RIPE92
by Franziska Lichtblau 17 Apr '26

17 Apr '26

Hi, We have a draft agenda for the Address Policy WG's two sessions at RIPE 92. Please note, that the agenda might still change until the upcoming meeting. Session 1, Thursday 11:30 UTC A Open session B Co-chair selection C ASO AC Update, Hervé Clément, Constanze Bürger, Andrei Robachevsky D Policy Update, Angela Dall'Ara E Registration Services Update, Marco Schmidt F IP address allocations to celestial bodies (informational), Tony Li Session 2, Thursday 14:00 UTC A Recycling AS Numbers, Antonis Chariton B IPv6 PI (2024.01), Tobias Fiebig C Legacy status: pre proposal discussion, Clara Wade D Open Mic You can find the whole meeting plan here: https://ripe92.ripe.net/programme/meeting-plan/ Looking forward to seeing you there! Your co-chairs, Alex, Franziska, Leo

1 0

Re: 2024-01
by Aron Strecker 04 Apr '26

04 Apr '26

Hello everyone, I want to support this as well -> +1 from me. -- Mit freundlichen Grüßen | Yours sincerely Aron Strecker AS212691 PS: Bei der angehängten asc Datei handelt es sich um mein OpenPGP Zertifikat. Dies wird verwendet um per verschlüsselter E-Mail zu kommunizieren. Am 04.04.26 um 14:58 schrieb address-policy-wg-request(a)ripe.net: > Welcome to the "address-policy-wg" mailing list! > > To post to this list, send your message to: > > address-policy-wg(a)ripe.net > > You can unsubscribe or make adjustments to your options via email by > sending a message to: > > address-policy-wg-request(a)ripe.net > > with the word 'help' in the subject or body (don't include the > quotes), and you will get back a message with instructions. You will > need your password to change your options, but for security purposes, > this password is not included here. If you have forgotten your > password you will need to reset it via the web UI. >

1 0

Nominations Open: New Address Policy WG Co-Chair Sought
by Leo Vegoda 31 Mar '26

31 Mar '26

Dear Address Policy Working Group, You can now nominate yourself as a potential co-chair for the Address Policy WG. You do this by writing to apwg-chairs(a)ripe.net with your name and your affiliation. Please do not self-nominate on this list. I am not seeking reselection, so we need a new co-chair. Send your nomination to apwg-chairs(a)ripe.net by 15 March. We will publish the list of candidates on 23 March. The candidates may then introduce themselves to the list. The Working Group will make its selection during the Address Policy WG session at RIPE 92 in Edinburgh. If you are interested in serving as a co-chair of this Working Group, you are welcome to speak to Alex, Franziska, or me, to learn what we do off-list. Mirjam and Anna, as RIPE Chair and Vice Chair are also happy to answer any questions you have. And, you can also seek input from RIPE NCC staff and previous co-chairs. Our selection process is documented here: https://www.ripe.net/community/wg/active-wg/ap/address-policy-wg-chair-sele… You can also read the Job Description here: https://www.ripe.net/publications/docs/ripe-692/ A RIPE Working Group Chair Training course is available at the RIPE NCC Academy: https://academy.ripe.net/enrol/index.php?id=16 Kind regards, Leo Vegoda, for the co-chairs

3 3

2024.01 Revised IPv6 PI Assignment Policy - Next steps
by Franziska Lichtblau (rhalina) 25 Mar '26

25 Mar '26

Dear Address Policy WG, The Discussion Phase for Version 2 of policy proposal 2024-01 ended on 28 November 2025. The feedback received during this phase was limited. We have discussed the situation with Tobias, who has confirmed the intention to continue with the proposal. As per the RIPE Policy Development Process (PDP), at the end of the Discussion Phase the proposer, with the agreement of the WG Chairs, decides whether the proposal will move to the next phase or be withdrawn. The WG Chairs and the proposer have agreed to proceed. If you have not yet shared your view on this proposal, we encourage you to do so now. The limited feedback during the Discussion Phase on v2 of 2024.01 means that the community's feedback is particularly valuable right now. Even a brief statement of support, opposition, or neutrality helps us as WG Chairs assess the situation. You can find the proposal at: https://www.ripe.net/community/policies/proposals/2024-01/2/ Kind regards, Alex, Franziska, Leo Address Policy Working Group Chairs

5 4

Heads up: New discussion phase for 2024.01 upcoming
by Franziska Lichtblau 25 Mar '26

25 Mar '26

Dear Address Policy WG, To correctly follow the PDP and incorporate your comments we need to start a new discussion phase. There will be a formal announcement soon and we'd be grateful if you could resend comments made in the last days during that period. Apologies for the inconvenience. Kind regards, Alex, Franziska, Leo Address Policy Working Group Chairs

1 0

Verification of Legacy Resource Holders without Contract
by Marco Schmidt 20 Mar '26

20 Mar '26

Dear colleagues, At RIPE 91, I presented the idea that the RIPE NCC would contact the roughly 1,600 legacy resource holders who currently have no contractual relationship with either the RIPE NCC or a sponsoring LIR. [1] While the policy “RIPE NCC Services to Legacy Internet Resource Holders” [2] does not require a contractual relationship to be in place, this creates challenges in terms of data accuracy. For many of these resources, the holdership and contact details are outdated, unclear, or missing. This makes it difficult to contact the resource holder and process updates, and increases the risk of disputes or misuse. To address this, we will soon begin contacting legacy resource holders based on the available registration information. Once we have verified their status, we will add a co-maintained organisation object to their resources in the RIPE Database. This will clearly identify the resource holder and ensure that any future updates involve the RIPE NCC and are similarly verified. This step will improve registration accuracy, reduce the risk of misuse, and bring these resources closer in line with how other resources are maintained in the RIPE Database. We aim to complete this activity by October 2026. In cases where we are unable to verify holdership , we will add an organisation object with an anonymised name to indicate that this is currently unverified. This can be updated later at any time once verification becomes possible. Legacy resource holders without a contract who would like to prioritise verification can contact us at legacy(a)ripe.net. We will update you on the progress of this work in the coming months. Kind regards, Marco Schmidt Manager Registration Services RIPE NCC [1] https://ripe91.ripe.net/programme/meeting-plan/sessions/40/FJ7YSH/ [2] https://www.ripe.net/publications/docs/ripe-639/

2 2

Status of 2024-01 Revised IPv6 PI Assignment Policy
by Rhys Perry 12 Mar '26

12 Mar '26

Hi All, Apologies in advance if this is against the working group etiquette, as I mostly lurk here and am not too involved. Is there any update on the 2024-01 Revised IPv6 PI Assignment Policy? It was moved into its six week discussion phase on 2025-10-30, and is now apparently "Awaiting decision from proposer" according to the proposal page on ripe.net. Rhys

3 3

2024-02 Policy Proposal Withdrawn (IPv6 Initial Allocations /28 and extension to /28)
by Angela Dall'Ara 26 Feb '26

26 Feb '26

Dear colleagues,   The policy proposal 2024-02, "IPv6 Initial Allocations /28 and extension to /28” has been withdrawn.   This proposal aimed to change the initial IPv6 allocation size from up to /29 to up to /28 and allow the extension of one IPv6 allocation per LIR up to /28 without justification.   The proposal is archived and can be found at:  https://www.ripe.net/participate/policies/archived-policy-proposals/archive…   Reason for withdrawal:  The proposer did not feel that any further redrafting of the proposal would achieve consensus. Please note that as per RIPE Policy Development Process “After a withdrawal, anyone is free to re-introduce the topic on the mailing list.“ The PDP document can be found at: https://www.ripe.net/publications/docs/ripe-781 Kind regards, Angela Dall'Ara Policy Officer RIPE NCC

1 0