Skip to content

Commit 7ffc993

Browse files
committed
add RPKI system figure
1 parent 4306da8 commit 7ffc993

File tree

4 files changed

+179
-1
lines changed

4 files changed

+179
-1
lines changed

figures/RPKI-system.png

76.6 KB
Loading

figures/SecurityFigs.odp

46.5 KB
Binary file not shown.

figures/router.svg

Lines changed: 158 additions & 0 deletions
Loading

infra.rst

Lines changed: 21 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -429,7 +429,27 @@ origin AS for a subprefix of YouTube, that could immediately be
429429
detected as false information and discarded by any router receiving
430430
such an advertisement, not just the neighbors of the offending ISP.
431431

432-
.. need a figure here
432+
433+
434+
.. _fig-rpki-sys:
435+
.. figure:: figures/RPKI-system.png
436+
:width: 600px
437+
:align: center
438+
439+
Each AS maintains a local cache of the RPKI repository, and BGP
440+
speakers query the local cache, allowing them to validate BGP
441+
advertisements.
442+
443+
Some of the practical aspects of ROV are shown in :numref:`Figure %s
444+
<fig-rpki-sys>`. An AS performing route origin validation maintains a
445+
local cache of the RPKI repository, which is fetched using rsync or
446+
the RPKI Repository Delta Protocol (RRDP). A BGP speaker in the AS
447+
retrieves the set of valid ROAs by querying the local cache, using
448+
another protocol called the RPKI-to-router (RTR) protocol. This
449+
protocol allows the router to receive periodic updates to the set of
450+
valid ROAs from the local cache. With this information in hand, the
451+
router is able to check the validity of the originating AS in BGP
452+
advertisements that it receives from other ASes.
433453

434454
While there are many forms of attack or misconfiguration that would
435455
not be caught by ROV (particularly an AS falsely advertising a path that

0 commit comments

Comments
 (0)