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/routing-wg@ripe.net/
[routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
- Previous message (by thread): [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
- Next message (by thread): [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jared Mauch
jared at puck.nether.net
Sun Feb 23 15:17:07 CET 2020
> On Feb 23, 2020, at 8:45 AM, Nick Hilliard <nick at foobar.org> wrote: > > JORDI PALET MARTINEZ via routing-wg wrote on 23/02/2020 13:06: >> I don't think is objective to say that the proposal as asking the NCC >> to "inject" invalids. >> The proposal is providing the information of the invalids (in this >> case unallocated/unassigned) by means of RPKI. > > Jordi, > > You're splitting hairs here. The end result is the same. I’m cornered about something like this as we’ve been down this road before with bogon lists, etc and even though it’s well intentioned by smart people(tm), the distributed legacy and cleanup has often taken years to recover. - Jared
- Previous message (by thread): [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
- Next message (by thread): [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]