Dear colleagues,

Thanks for your feedback, there appears to be support to extend the existing NONAUTH cleanup job as follows:

* Continue to delete RPKI-OV INVALID objects (the RIPE-731 mandate)
* Delete RIPE-NONAUTH route(6) objects when they become RPKI-OV VALID
* Delete RIPE-NONAUTH route(6) objects when they become *covered* by a route(6) object in another RIR's auth database.

We will only perform an exact-match (and not less-specific) lookup to match a route(6) in another RIRs database.

We will document the cleanup on the DB documentation website: https://docs.db.ripe.net/

We will not cleanup NONAUTH aut-nums or as-sets for now.

We will contact maintainers of NONAUTH objects before we delete them.

We will later reassess what to do with the remaining NONAUTH objects.

DB-WG Co-chairs, please let me know if we can proceed and whether an NWI is needed.

Regards
Ed Shryane
RIPE NCC


> On 17 Jul 2025, at 18:07, Edward Shryane <eshryane@ripe.net> wrote:
>
> Dear colleagues,
> ...

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