OSNTC.051: How RPKI Protects BGP Route Origins

Network engineer at a laptop among racks of data center networking equipment, with one BitcoinVersus.tech neon-green watermark at bottom left.

The Border Gateway Protocol (BGP) carries announcements telling networks which autonomous system, or AS, originates an IP prefix. Because ordinary BGP does not independently prove that claim, an incorrect or malicious announcement can divert traffic. Resource Public Key Infrastructure (RPKI) adds a cryptographically verifiable way to authorize route origins. In OSNTC.051, the objective is to classify routes, explain the operational limits and avoid a misconfigured policy that drops legitimate traffic.

Video: Internet2 presents practical route-origin authorization and RPKI operations with ARIN, published in 2026.

The three components of origin validation

First, an IP address resource holder creates a Route Origin Authorization (ROA), identifying an authorized origin AS, a prefix and an optional maximum prefix length. Second, an RPKI relying-party validator verifies signed repository objects and produces Validated ROA Payloads (VRPs). Third, a router uses these VRPs to evaluate incoming BGP routes through Route Origin Validation (ROV). The ARIN ROA documentation and RFC 6811 define the relevant terms.

A router does not usually fetch and cryptographically validate every ROA itself. A validator maintains the trusted data and supplies a cache of verified origin information to routers. Routing policy decides how to act on validation results; cryptographic validation alone does not automatically discard routes.

Valid, invalid and not found

RFC 6811 specifies three states. Valid means at least one VRP covers the announcement and matches its origin AS and maximum length. Invalid means a VRP covers the announced prefix but none authorizes the exact origin-and-length combination. NotFound means no VRP covers the announced prefix. NotFound is not equivalent to an attacker, and an invalid state can arise from a legitimate operator’s inaccurate ROA.

Consider a fictitious, documentation-only ROA authorizing 203.0.113.0/24 from AS64500 with maximum length /24. Advertising the same /24 from AS64500 is Valid. Advertising it from AS64501 is Invalid. Advertising 203.0.113.128/25 from the authorized AS is also Invalid because the route is more specific than the permitted /24. Assuming no other covering ROAs, an announcement of 198.51.100.0/24 is NotFound. The addresses and private ASNs are training examples, not public observations.

Video: ARIN’s tutorial covers resource certification and creating RPKI authorization data. Interface details may have changed since the recording.

Field checklist before enforcement

Audit every intentional BGP origin, including backup providers and planned more-specific routes. Validate prefix lengths, verify the complete set of legitimate origin ASNs, synchronize the validator, and test route classifications before enabling rejection of Invalid announcements. Most networks retain NotFound routes during incremental deployment. Protect validator availability, monitor cache freshness and keep a recovery procedure; incorrect authorizations can cause an outage even when every certificate is valid.

RPKI origin validation is not full AS-path authentication. A forged path that preserves a valid origin can evade the origin-only check. ROV complements peer filtering, monitoring and other controls rather than replacing them. Compare the separate roles of BGP fundamentals, BFD failure detection, EVPN route types and data-center fabrics. Each addresses a different routing or availability problem.

Knowledge check

Question 1: A prefix has no covering VRP. What state is returned? Answer: NotFound. Question 2: A matching origin AS advertises a prefix longer than the ROA’s maximum length. Answer: Invalid. Question 3: Does a Valid RPKI state prove the AS path is legitimate? Answer: No; origin validation checks the authorized origin, not the complete path.

Primary references: IETF RFC 6811; RIPE NCC origin-validation guidance; ARIN Route Origin Authorization guide; RIPE NCC ROA management.

We volunteer daily to ensure the credibility of the information on our platform is Verifiably True. If you would like to support our research initiative and help secure its integrity, please scan the QR code below.

BitcoinVersus.Tech donation QR code

Leave a Reply