aboutsummaryrefslogtreecommitdiff
path: root/doc/wiki-dump/doc%2FRPKI%2FListOfPrograms
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2016-08-03 18:27:49 +0000
committerRob Austein <sra@hactrn.net>2016-08-03 18:27:49 +0000
commit14a9628f0552d3818cd58fb085e7544cdbb3b5eb (patch)
tree2c6d9665ea9743e0a25d7726fb72fd54b2aa9323 /doc/wiki-dump/doc%2FRPKI%2FListOfPrograms
parentb322ea212b6b4c53af7cb4f24faac4302b181c9c (diff)
Dump of rpki.net Wiki, to capture content not linked into the manual.
Diffstat (limited to 'doc/wiki-dump/doc%2FRPKI%2FListOfPrograms')
-rw-r--r--doc/wiki-dump/doc%2FRPKI%2FListOfPrograms52
1 files changed, 52 insertions, 0 deletions
diff --git a/doc/wiki-dump/doc%2FRPKI%2FListOfPrograms b/doc/wiki-dump/doc%2FRPKI%2FListOfPrograms
new file mode 100644
index 00000000..dc672e51
--- /dev/null
+++ b/doc/wiki-dump/doc%2FRPKI%2FListOfPrograms
@@ -0,0 +1,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.