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 on RIPE NCC Network
- Previous message (by thread): [routing-wg] RPKI: how to migrate an entire industry from RSYNC to RRDP?
- Next message (by thread): [routing-wg] New on RIPE Labs: Does The Internet Route Around Damage? - Edition 2021
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nathalie Trenaman
nathalie at ripe.net
Tue Apr 13 15:28:27 CEST 2021
Dear colleagues, (My colleagues are drafting a reply on the rsync issue) Following up on my previous email and the discussion we had in this mailing last about enabling Route Origin Validation (ROV) invalid == reject on the RIPE NCC’s network, AS3333, I am happy to inform you that we will be going ahead on Monday, 19 April. I have written a RIPE Labs article with more information, which you can find at: https://labs.ripe.net/author/nathalie_nathalie/rpki-and-as3333-or-how-we-eat-our-own-dogfood/ Thank you very much for your contributions, discussion and support. Kind Regards, Nathalie Trenaman Routing Security Programme Manager RIPE NCC
- Previous message (by thread): [routing-wg] RPKI: how to migrate an entire industry from RSYNC to RRDP?
- Next message (by thread): [routing-wg] New on RIPE Labs: Does The Internet Route Around Damage? - Edition 2021
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]