On Mon, Oct 12, 2026 at 04:34:50PM +0100, Kaveh Ranjbar via db-wg wrote:
Both cleanups remove objects that have a better copy elsewhere, so what disappears is a duplicate, not information. Additionally, the database stops carrying data that nobody has maintained since it was created with the shared password.
Kaveh summarizes it nicely. I support deleting the following classes of objects: * NONAUTH objects with a matching VALID ROA. * NONAUTH objects with a matching object in another RIR database. But just to be sure - can 'valid ROA' be defined as valid ROAs subordinate to the following RPKI Trust Anchors? afrinic.tal (key identifier EB680F38F5D6C71BB4B106B8BD06585012DA31B6) apnic.tal (key identifier 0B9CCA90DD0D7A8A37666B19217FE0D84037B7A2) arin.tal (key identifier 13D4F24F9A9FCD98DB36F930631808C88F3974BC) lacnic.tal (key identifier FC8A9CB3ED184E17D30EEA1E0FA7615CE4B1AF47) ripe.tal (key identifier E8552B1FD6D1A4F7E404C6D8E5680D1EBC163FC3) I believe the RIPE-NONAUTH cleanup should not use the dangerous 'AS0' TALs that APNIC & LACNIC maintain alongside their normal 'production' RPKI. Kind regards, Job ps. For a detailed write-up on why AS0 TALs are bad for business please see https://mailman.ripe.net/archives/list/routing-wg@ripe.net/message/3MPEL5Q4I...