aboutsummaryrefslogtreecommitdiff
path: root/doc/09.RPKI.RP.HierarchicalRsync.md
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2016-08-03 23:46:44 -0400
committerRob Austein <sra@hactrn.net>2016-08-03 23:46:44 -0400
commit949e9c8358b5259656c02e4a1ada7912d943afd2 (patch)
tree4d04acc169abb7d7f7e08790a98736ba8214f97d /doc/09.RPKI.RP.HierarchicalRsync.md
parent14a9628f0552d3818cd58fb085e7544cdbb3b5eb (diff)
Try another conversion pass to salvage more of the links.
Diffstat (limited to 'doc/09.RPKI.RP.HierarchicalRsync.md')
-rw-r--r--doc/09.RPKI.RP.HierarchicalRsync.md10
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/09.RPKI.RP.HierarchicalRsync.md b/doc/09.RPKI.RP.HierarchicalRsync.md
index d996379c..196f0d2d 100644
--- a/doc/09.RPKI.RP.HierarchicalRsync.md
+++ b/doc/09.RPKI.RP.HierarchicalRsync.md
@@ -11,10 +11,10 @@ Note
The relying parties in this configuration still perform their own validation, they just let the gatherers do the work of collecting the unvalidated data for them.
A gatherer in a configuration like this would look just like a stand-alone
-relying party as discussed above. The only real difference is that a gatherer
-must also make its unauthenticated data collection available to other relying
-parties. Assuming the standard configuration, this will be the directory
-`/var/rcynic/data/unauthenticated` and its subdirectories.
+relying party as discussed [above][HierarchicalRsync]. The only real difference is that a
+gatherer must also make its unauthenticated data collection available to other
+relying parties. Assuming the standard configuration, this will be the
+directory `/var/rcynic/data/unauthenticated` and its subdirectories.
There are two slightly different ways to do this with rsync:
@@ -84,3 +84,5 @@ Configuration for such a module would look like:
transfer logging = yes
path = /var/rcynic/data/unauthenticated
comment = Unauthenticated RPKI data
+
+[HierarchicalRsync]: 09.RPKI.RP.HierarchicalRsync.md