Hi Kaveh, On 6 Jul 2026, at 11:12, Kaveh Ranjbar via db-wg <db-wg@ripe.net> wrote: […]
The real prize, I think, is registration data hygiene. A holder with a lot of assignment activity has two poor options today. Register nothing below the allocation, which leaves coarse, unhelpful data for abuse handling, research and routing. Or bulk-load large numbers of assignment objects that start drifting out of date the day they land, which means stale data and central database bloat. An optional referral to the place where the data is actually maintained gives the community accurate, current, granular registration data served from the source, keeps the central database lean, and preserves an unbroken, machine-walkable chain from the bootstrap to the exact object. It rewards holders for publishing good, live data rather than penalising them for it.
It sounds like a great idea but I don’t understand this part. Why would a resource holder not prefer to have their IPAM synchronise what it knows to be true with the RIPE Database instead of spending money on building and maintaining some infrastructure? Yes, I’m assuming that anyone who wants to run their own RDAP server has an IPAM of some kind. Thanks, Leo