[routing-wg] Towards cleaning up RPKI INVALIDs
- Previous message (by thread): [routing-wg] RIPE NCC RPKI Validator 3 API spec?
- Next message (by thread): [routing-wg] Towards cleaning up RPKI INVALIDs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
nusenu
nusenu-lists at riseup.net
Sat Sep 15 15:17:00 CEST 2018
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 -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <https://lists.ripe.net/ripe/mail/archives/routing-wg/attachments/20180915/6684ec14/attachment.sig>
- Previous message (by thread): [routing-wg] RIPE NCC RPKI Validator 3 API spec?
- Next message (by thread): [routing-wg] Towards cleaning up RPKI INVALIDs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]