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 ]
Leo Vegoda
leo at vegoda.org
Thu Mar 18 17:01:36 CET 2021
Hi, On Thu, Mar 18, 2021 at 8:03 AM Nathalie Trenaman <nathalie at ripe.net> wrote: [...] > What is the Problem? > 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. [...] > From an analysis we made on 10 February, there were 511 of such announcements from our members and End Users. If the goal is to do this in a customer friendly way, perhaps consider creating a website at something like: https://brokenrpki.ripe.net, on a network that does not validate RPKI, so that users can be provided with any analytical tools or step-by-step guides thought necessary. Kind regards, Leo
- 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 ]