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]/
[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] RPKI Outage Post-Mortem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Mon Mar 2 20:15:18 CET 2020
Dear Massimiliano, Thank you for the overview and proposing possible paths forward. On Tue, Feb 25, 2020 at 08:30:21PM +0100, Massimiliano Stucchi wrote: > C) We can change the proposal to a different ask for RIPE NCC. The idea > could be to ask RIPE NCC to provide a SLURM file (similar to what APNIC > does), so that single users can decide if they want to feed it to their > validators. I would be in favor of option C - generation of a SLURM file. It appears cheap to implement and efficient in its purpose, it is opt-in. A good balance. Kind regards, Job
- 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] RPKI Outage Post-Mortem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]