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 ]
Nick Hilliard
nick at foobar.org
Tue Mar 3 20:03:38 CET 2020
Job Snijders wrote on 03/03/2020 18:41: > Let me rephrase: what is the cost to the community of no > implementation of 2019-08 at all? > > [...] but if it > boils down either using the RPKI for this or nothing, the latter > option is what I support. Pretty much that. They've made it clear that the costs will be substantial, including: - duplication of the entire RPKI infrastructure - 6m wall clock time for some of the software team - additional internal / external processes + documentation This isn't a small undertaking - it's substantial. Set against that, the benefit to the proposal is marginal at best, and harmful in some important respects. On top of that, it isn't reasonable for people to hit the RIPE NCC with requests to do more and more ground work on an impact analysis for proposals where it's far from clear that's any consensus to start with. 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 ]