[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 ]
Robert Kisteleki
robert at ripe.net
Wed Mar 4 10:57:40 CET 2020
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 ]