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] RPKI Route Origin Validation and AS3333
- Previous message (by thread): [routing-wg] RPKI Route Origin Validation and AS3333
- Next message (by thread): [routing-wg] RPKI Route Origin Validation and AS3333
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mikael Abrahamsson
swmike at swm.pp.se
Fri Mar 19 08:42:35 CET 2021
On Thu, 18 Mar 2021, Nathalie Trenaman wrote: > Currently, some of our upstream providers already perform ROV. This > means that some of our members that potentially misconfigured their ROA > or members who have lost control of creation and modification of their > ROAs cannot reach our services via those peers. Thanks for the outreach to the community. Indeed, as stated above, the more providers are enabling RPKI, the less consequential it is whether RIPE NCC is performing ROV or not. This, as the scales tip to "if you made a ROA mistake you can't talk to the Internet", it instead becomes important that RIPE NCC staff has deep knowledge in how the RPKI ecosystem works, including monitoring etc. That would be an upside to performing ROV and implementing all monitoring that should come with it. Then RIPE NCC will have staff with operational knowledge of all aspects of routing, ROV and RPKI. I believe this would be beneficial to RIPE NCC and the Internet as a whole. Thanks. -- Mikael Abrahamsson email: swmike at swm.pp.se
- Previous message (by thread): [routing-wg] RPKI Route Origin Validation and AS3333
- Next message (by thread): [routing-wg] RPKI Route Origin Validation and AS3333
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]