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 ]
Randy Bush
randy at psg.com
Tue Mar 3 22:34:15 CET 2020
>> 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. yep but ... > 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 would this duplication of infrastructure actually be needed or useful? the american idiom is "making a mountain out of a molehill" randy -------------- next part -------------- A non-text attachment was scrubbed... Name: molehill.jpg Type: image/jpeg Size: 27330 bytes Desc: not available URL: </ripe/mail/archives/routing-wg/attachments/20200303/52cd4725/attachment-0001.jpg>
- 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 ]