Hi Ed, Specifically regarding the deletion of objects that are RPKI OV valid I could see this causing some issues. (Such as having some providers not implementing RPKI OV and requiring IRR objects) I would like it if the NCC could solicit feedback on this from those who would have objects deleted because of this. If the NCC doesn't get any objections within a reasonable time frame it can continue. In case there are any objections I'd like it if this feedback could be provided to the WG. -Cynthia On Fri, 8 Aug 2025, 16:43 Edward Shryane, <eshryane@ripe.net> wrote:
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/