Your comments indicate to me that you don't really understand RPKI beyond a marketing value because if you did you wouldn't be throwing it around as some silver

Your comments indicate to me that you don't really understand RPKI beyond a marketing value because if you did you wouldn't be throwing it around as some silver bullet. RPKI although a step in the right direction is also susceptible to misconfiguration and attack by hostile entities[1]. Additionally outages as bad as any BGP misconfiguration are also possible if an RIR's RPKI repo becomes unavailable. This has already happened. See: https://www.arin.net/vault/announcements/2018/20181024_update.html https://www.arin.net/vault/announcements/2018/20181024_updat... and https://www.ripe.net/support/service-announcements/service-announcements/ripe-ncc-rpki-repository-outage https://www.ripe.net/support/service-announcements/service-a... There are also issues such a broken legacy ROAS: https://blog.apnic.net/2018/10/16/cleaning-up-roas-inconsistent-with-the-bgp-state/ https://blog.apnic.net/2018/10/16/cleaning-up-roas-inconsist... And the list goes on. Please stop with the hype and hand waving. [1] https://www.cs.bu.edu/~goldbe/papers/sigRPKI_full.pdf https://www.cs.bu.edu/~goldbe/papers/sigRPKI_full.pdf