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/[email protected]/
[routing-wg] new tool: rpki-ov-checker
- Previous message (by thread): [routing-wg] new tool: rpki-ov-checker
- Next message (by thread): [routing-wg] Weekly Routing Table Report
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at ntt.net
Thu Feb 6 13:53:02 CET 2020
On Thu, Feb 06, 2020 at 12:47:48PM +0000, Mick O'Donovan wrote: > VERY cool job I like it a lot! > > This might help me make the case to push the button on dropping RPKI > invalids internally even more. What might also help is to analyse how much traffic is actually flowing towards those 'invalid_unreachable' destinations. Pmacct and kentik are tools that can help you understand this easily (they both support separately showing problematic invalids and invalids which are covered). https://mailman.nanog.org/pipermail/nanog/2019-February/099522.html https://www.kentik.com/blog/technical-guide-using-rpki-resource-public-key-infrastructure-in-kentik/ Kind regards, Job
- Previous message (by thread): [routing-wg] new tool: rpki-ov-checker
- Next message (by thread): [routing-wg] Weekly Routing Table Report
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]