[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 ]
Carlos Friaças
cfriacas at fccn.pt
Wed Mar 4 21:28:29 CET 2020
On Wed, 4 Mar 2020, Nick Hilliard wrote: > Carlos Friaças via routing-wg wrote on 04/03/2020 07:23: >> Unfortunately, you will only "run AS0" over non-distributed APNIC space. >> >> If you were able to do it for the full problem space, those who will >> continue to explore this weakness in the global routing system would not >> have an excellent alternative by simply choosing to abuse non-distributed >> space by the other RIRs... > > Carlos, > > are you seriously suggesting that APNIC or any other RIR should use a TAL for > 0/0 to claim authority over unallocated space from other RIRs? Nick, All, What did cross my mind was that if *one* RIR was going to double the not-so-cheap infrastructure, maybe, with enough levels of coordination with other RIRs (and a cost-sharing model), the cost could be (globally) smaller. i.e. ((1+1) x 5 RIRs) vs. ((1 x 5 RIRs) + 1 by APNIC). > This would be an extraordinary breach of trust in the RIR community. Between RIR communities? I wonder what would happen if *one* community at some point decides to ask their RIR to "please throw in also the unallocated/unassigned blocks (junk) from other RIRs, while you are at it" :-) Carlos > Nick >
- 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 ]