[db-wg] Removal of bogon route objects

Edward Shryane via db-wg wrote on 14/06/2021 15:16:
> Thanks, that was my question, should we validate that*either*  the IP
> or AS is unregistered, or*both*  IP and AS are unregistered (and you
> indicated*either*).
definitely if the prefix is unregistered.

If there's a nonauth route object registered with a valid address range, 
but invalid AS, is it currently possible to update the route object to 
reference a correctly registered ASN? If the answer is that it's not 
possible (i.e. because the db primary key is a concatenation of the 
prefix + as), then the route object should be deleted because it's 
basically unfixable.

If there are no immediate plans to investigate recently reregistered 
space, would it be worth running the invalid prefix analysis for all of 
the extended delegation files every month since 2018-09-04?  The 
unallocated / reserved address pools change, and it should be easy 
enough to script this up.

Nick