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] Towards cleaning up RPKI INVALIDs
- Previous message (by thread): [routing-wg] Towards cleaning up RPKI INVALIDs
- Next message (by thread): [routing-wg] Multi home BGP reestablishment.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Melchior Aelmans
melchior at aelmans.eu
Mon Sep 17 18:25:38 CEST 2018
HI Thiago, On Mon, Sep 17, 2018 at 3:13 PM, Thiago da Cruz <tdacruz at ripe.net> wrote: > Hi Nusenu, > > You're right, we could improve the quality (valids/total announcements for > the region) with a few emails. > And we had it in mind when we introduced “Alert configuration” to the RPKI > dashboard. See img below. > > Now I’m thinking if this feature has already provided what it was able to > and if we should take a more proactive approach. > I definitely see 'need' for a more proactive approach. Offering this notification service is great for people already aware but as far as I'm concerned we should take this even a step further and start actively notifying instead of reactional. Cheers, Melchior > Would you be open to reach out to your affected members to inform them > about > their affected IP prefixes? > > > I cannot answer it now. I want to hear more from the WG. > But, without a doubt, your article provides food for thought. > > Cheers, > Thiago da Cruz > > > > > > On 15 Sep 2018, at 15:17, nusenu <nusenu-lists at riseup.net> wrote: > > Hi, > > we made an analysis of the RPKI INVALIDs and broke them down by > * RIR > * INVALID reason > * causing ROA > * number of members each RIR would have to contact to fix them > after filtering them to those prefixes that actually would become > unreachable in > an ROV environment. > > https://medium.com/@nusenu/towards-cleaning-up-rpki-invalids-d69b03ab8a8c > > Looking forward to comments from the WG and RIPE NCC. > > The central question in the direction of RIPE NCC is: > > Would you be open to reach out to your affected members to inform them > about > their affected IP prefixes? (as has been suggested by Job Snijders before) > > > kind regards, > nusenu > > -- > https://twitter.com/nusenu_ > https://mastodon.social/@nusenu > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20180917/59abfc5e/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: alerts.png Type: image/png Size: 78000 bytes Desc: not available URL: </ripe/mail/archives/routing-wg/attachments/20180917/59abfc5e/attachment.png>
- Previous message (by thread): [routing-wg] Towards cleaning up RPKI INVALIDs
- Next message (by thread): [routing-wg] Multi home BGP reestablishment.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]