4 v1.0
4
What makes a prefix RPKI Invalid
• Digitally signed object
q Binds list of prefixes and the nominated ASN
q can be verified cryptographically
• ** Multiple ROAs can exist for the same prefix
Prefix 203.176.32.0/19
Max-length /24
Origin ASN AS17821
5 v1.0
5
RPKI Components
• Issuing Party – Internet Registries (*IRs)
q Certificate Authority (CA) that issues resource certificates to end-holders
q Publishes the objects (ROAs) signed by the resource certificate holders
APNIC
RPKI
Engine
publication
MyAPNIC GUI
rpki.apnic.net
Repository
6 v1.0
6
RPKI Components
• Relying Party (RP)
q RPKI Validator that gathers data (ROA) from the distributed RPKI repositories
q Validates each entry’s signature against the TA to build a “Validated cache”
rpki.apnic.net
IANA Repo
APNIC
Repo
RIPE Repo
LIR Repo LIR Repo
RP
(RPKI
Validator)
Validated
Cache
rsync/RRDP
rsync/RRDP
rsync/RRDP
rsync/RRDP
14 v1.0
14
Bangladesh – RPKI ROV
Big operators are not doing ROV
https://stats.labs.apnic.net/rpki/BD
https://bgp.he.net/country/BD
Last updated: 30 Nov 2022
15 v1.0
15
Bangladesh – Routing Incidents
https://observatory.manrs.org/
Last updated: 30 Nov 2022
17 v1.0
17
Example: RPKI INVALIDs
https://stats.labs.apnic.net/roa/BD
https://bgp.he.net/
Last updated: 30 Nov 2022
18 v1.0
18
What Happens to Your INVALIDs
• Many big providers blocking it already
q Traffic may choose suboptimal path
• You may not realize if your INVALIDs are dropped
q Local providers might not drop it yet
• Your aggregated prefix might be VALID
q Hence no impact realized
q But TE might not work as expected