Dear Max, Thank you for your email. We will contact all legacy resource holders without a contract. In most cases where a RIPE NCC member holds legacy resources, these are already under contract and managed via their LIR account. You are likely referring to a small number of cases where members have chosen not to bring their legacy resources under contract, but these still appear in their LIR portal due to the technical link via their default maintainers. We recognise that this can be confusing and are looking into ways to make the contractual status of such resources clearer in the portal. Regarding your second point, the current project focuses on verifying the status of legacy resource holders. After completion, we will report back on cases where the holder could not be verified and present potential next steps. Kind regards, Marco Schmidt Manager Registration Services RIPE NCC On 17/03/2026 15:48, Max Emig wrote:

Hi,

does this include all legacy resources with no contract or does it exclude all legacy holders without a contract, that have them in their RIPE LIR account?

If you find ones where the holding entity does not exist anymore and they are not announced, please return them to IANA, even though it's been a while since the last return the policy is still standing and I'm convinced that a least a bunch of /24 could be recovered: https://www.iana.org/assignments/ipv4-recovered-address-space/ipv4-recovered...

Thanks

Max

On 17 March, 2026 15:25 CET, Marco Schmidt <mschmidt@ripe.net> wrote:

...

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@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/

----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/address-policy-wg.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/