Ronald F. Guilmette via db-wg wrote on 05/08/2021 14:10:
I would like to suggest that at the very least these should be moved to NONAUTH, but preferably deleted altogether.
there's no way of updating a route(6) object with an bogus ASN, i.e. these objects cannot be corrected.
If you register an update with a different ASN, then that creates a separate db object.
This is why they need to be deleted: they're materially wrong from the point of view of routing policy and they're irrecoverable.
Nick
