[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 11:22:22 CET 2020
Hi Robert, All, My main issue was about every netadmin (i.e. each ASN) having to do something alongside RPKI. If the info about unallocated/unassigned can be kicked-in at the RPKI software level, that will make life easier for each ASN-admin -- i.e. only need to worry about running RPKI and fine tune it... Thanks for raising my optimism! Cheers, Carlos On Wed, 4 Mar 2020, Robert Kisteleki wrote: > > > On 2020-03-04 08:23, Carlos Friaças via routing-wg wrote: > >> Maybe the SLURM file trade-off is a good one (and it's availability >> seems inevitably positive), but if RPKI's takeup is slow, the SLURM file >> usage will be even slower... :-( > > I'm more optimistic. If SLURM is the chosen path, then support for it > only need to materialise in RPKI software -- which I'm pretty sure it > will, since maintainers of said software know what they are doing and > they are generally responsive to user needs. > > Robert >
- 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 ]