Hi, On Thu, 29 Jan 2026 at 11:56, Max Emig via db-wg <[email protected]> wrote: > > Hi all, > > considering that ASN aren't exactly sparse, I propose improving the cleanup > on the RIPE NCC side and keep them in a waiting pool as long as there are > valid Route Objects, ROA or PeeringDB accounts for it and notify the relevant > parties automatically.
PeeringDB should automatically remove network pages for ASNs that no longer have a registration in an RIR or NIR database. If there are stray cases where this doesn't happen, we'd appreciate notifications at [email protected]. > So, this would be more of an Address Policy issue. Donning my Address Policy WG co-chair hat... developing a policy is probably more expensive than just asking the RIPE NCC's people to make an improvement. On the whole they like to do the best they can for the community. Regards, Leo ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/db-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/
