This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[db-wg] Update: Bogon Route objects (part 2)

• Previous message (by thread): [db-wg] Update: Bogon Route objects (part 2)
• Next message (by thread): [db-wg] Update: Bogon Route objects (part 2)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Nick Hilliard nick at foobar.org
Thu Aug 5 15:24:55 CEST 2021

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

• Previous message (by thread): [db-wg] Update: Bogon Route objects (part 2)
• Next message (by thread): [db-wg] Update: Bogon Route objects (part 2)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]