[db-wg] RIPE NONAUTH route(6) objects using unregistered space cleanup - deployment *today*

Cynthia Revström via db-wg wrote on 29/06/2021 14:00:
> I might have a different opinion if it is a huge amount of objects that 
> could be cleaned up or if it is such a tiny amount that maybe just 
> contacting the maintainers manually would be enough.
> Summary: I don't think it is a good idea unless it is either a very 
> large amount of objects, a very trivial task, or there is another good 
> reason to do so.

If the information is incorrect and can't be corrected, then the outcome 
of removing those objects will be an improvement in the quality of the 
data in the db, with no downsides.

So, can a route/route6 object with valid prefix but invalid origin asn 
be updated to correct the asn?  My understanding is not, and that an 
attempt to update the object with a different origin will create a new 
DB object.

I.e. route/route6 objects with invalid origin ASN should be deleted, as 
they're both incorrect and unfixable.

Nick