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 ]
Ronald F. Guilmette
rfg at tristatelogic.com
Fri Aug 6 00:32:14 CEST 2021
In message <554aaaf7-f262-d97f-7c64-056c3d331c11 at foobar.org>, Nick Hilliard <nick at foobar.org> wrote: >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. Just to be clear, I am in complete agreement with Nick, and I probably should not have muddied the waters. For all the same reasons that bogus route objects which refer to bogon IP address space have been deleted, those bogus route objects that refer to bogon ASNs should also go into the ash heap of history. They are an anathema to the whole concept of the orderly assignment and usage of number resources, as promoted and supported by the several RIRs. Regards, rfg
- 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 ]