Towards cleaning up RPKI INVALIDs
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
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.
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@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
HI Thiago, On Mon, Sep 17, 2018 at 3:13 PM, Thiago da Cruz <tdacruz@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@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
participants (3)
-
Melchior Aelmans -
nusenu -
Thiago da Cruz