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] Removal of bogon route objects
- Previous message (by thread): [db-wg] Removal of bogon route objects
- Next message (by thread): [db-wg] Removal of bogon route objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Fri Jun 11 10:24:35 CEST 2021
With regards to the 192.175.48.0/24 block, the route for which I had incorrectly listed as a bogon, it seems that someone @ NRO somehow managed to muck this one up. Here is the relevant line from the latest nro-extended-stats file: iana|ZZ|ipv4|192.175.48.0|256|20150501|reserved|ietf|iana In reality the block isn't reserved and it doesn't belong to IANA. It's a regular old (assigned) ARIN block. I guess that I have to start distrusting the nro-extended-stats since it apparently contains some bogus information. Regards, rfg
- Previous message (by thread): [db-wg] Removal of bogon route objects
- Next message (by thread): [db-wg] Removal of bogon route objects
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]