blob: dc672e51f0b065cff51a3e8b2d92dcf95f60169a (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
[[TracNav(doc/RPKI/TOC)]]
[[PageOutline]]
= List of RPKI programs =
This is the beginning of a list of all the programs included in the
RPKI toolkit. It's not complete yet. At the moment, its primary
purpose is just to move fragments of such a list out of other
documentation pages where they just clutter things up and make the
text unreadable.
== RP tools ==
Relying party ("RP") tools.
=== rcynic ===
rcynic is the primary validation tool.
See the [[wiki:doc/RPKI/RP/rcynic|rcynic documentation]] for details.
=== rcynic-html ===
rcynic-html is a post-processor which converts rcyic's XML status
output into a set of HTML pages displaying status and history.
=== rcynic-cron ===
rcynic-cron is a small script to run the most common set of relying
party tools under cron.
=== rtr-origin ===
rtr-origin is an implementation of the rpki-rtr protocol, using
[[#rcynic|rcynic's]] output as its data source.
See the [[wiki:doc/RPKI/RP/rpki-rtr|rtr-origin documentation]] for details.
=== roa-to-irr ===
roa-to-irr is an experimental program for converting RPKI ROA data
into IRR data. Some operators have established procedures that depend
heavily on IRR, so being able to distribute validated RPKI data via
IRR is somewhat useful to these operators.
roa-to-irr expects its output to be piped to the `irr_rpsl_submit`
program.
Opinions vary regarding exactly what the RPSL corresponding to a
particular set of ROAs should look like, so roa-to-irr is currently
experimental code at best. Operators who really care about this may
well end up writing their own ROA to IRR conversion tools.
|
