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] Bogon cleanup -- Current anomalies
- Previous message (by thread): [db-wg] Bogon cleanup -- Current anomalies
- Next message (by thread): [db-wg] Bogon cleanup -- Current anomalies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Fri Jul 23 17:54:32 CEST 2021
Gert Doering via db-wg wrote on 23/07/2021 14:54: > While Anycast 6to4 needs to die, it isn't fully dead yet. So routes for > these two prefixes are legitimate. the discussion is whether it's appropriate for the RIPE NCC to continue to publish route objects for this prefix, which is a different discussion to the announcements in the dfz. The route objects are documentation of policy. If the prefix isn't legitimate according to IANA or RIR allocations / assignments (and in this case, it definitely isn't), then the route object shouldn't be in the IRRDB. There's nothing stopping operators from continuing to announce the prefix. It would be better if it were left to die, but this is ultimately a choice of each individual operator. The same argument applies to the route objects for 2002::/16. Nick
- Previous message (by thread): [db-wg] Bogon cleanup -- Current anomalies
- Next message (by thread): [db-wg] Bogon cleanup -- Current anomalies
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]