Dear Job,
On 17 Jul 2025, at 20:23, Job Snijders <job@sobornost.net> wrote:
Dear Ed,
On Thu, Jul 17, 2025 at 06:07:07PM +0200, Edward Shryane wrote:
The RIPE-NONAUTH database has only reduced in size by about 10% since it was created in 2018. The existing cleanup jobs and maintainers are not deleting much data.
Perhaps nitpicking - but I thought back in October 2018 [1] RIPE-NONAUTH contained ~ 69,178 'route:' objects, and nowadays 45,601, a 34% hefty decrease!
You are correct! Apologies, I mis-remembered the original size of the NONAUTH database. As you mentioned there are now 45,601 route(6) RIPE-NONAUTH objects, and in addition 2,066 aut-num and 67 as-set objects.
Sadly, shaving off only 34% is less than I was hoping for back in 2018...
Which equates to a few thousand objects deleted yearly since 2018.
Would it be feasible for you to produce a more statistics and insights on what exactly is contained in RIPE-NONAUTH?
* which of the other four RIRs is supposed to manage what % of route/route6 objects?
I searched today by route(6) *prefix* (only) compared to the latest NRO combined delegated stats to find which delegated space is supposed to manage what % of route(6) objects (out of 45,601 total) : * AFRINIC: 37,053 * APNIC: 1,512 * ARIN: 6,102 * LACNIC: 868 * No match (e.g. reserved space) : 66
* how many distinct entities does the space belong to? (perhaps hard to answer, perhaps be found via RDAP?)
I will check the IRR mirror databases and group by organisation if possible, or maintainer if not. This will take a bit more time.
* How many route/route6 objects have an exact, more-specific, or less-specific match in one of the four other RIR-managed IRR databases?
When I previously searched for a matching *route(6) object* in the other RIR's IRR mirror databases (with exact match ASN and exact or less-specific matching prefix) I found : * AFRINIC: 29,847 * APNIC: 302 * ARIN: 1,604 * LACNIC: 56 * No match : 13,824
It seems that roughly 15,619 'route:' objects are RPKI-OV VALID.
Would it make sense to extend RIPE-731 to also cleanup RPKI-OV VALID objects (because the routing intentions for those resources are also asserted in a cryptographicly validated database... ? But then what to do with the remaining 28,998 'route:' objects?
We can extend RIPE-731 to include VALID objects, if the DB-WG agrees. Can this be done as a new NWI ? Is it enough to expect RPKI adoption to increase to eventually cover all delegated space, to eventually cleanup the RIPE-NONAUTH database? Could we additionally implement a new cleanup by deleting RIPE-NONAUTH route(6) objects if matching a route(6) object in an RIR's authoritative database?
Kind regards,
Job
[1]: https://mailman.ripe.net/archives/list/routing-wg@ripe.net/message/OVLYCURRI...