a6df70ef55
This PR revises how updates are dispatched. Instead of having separate status and payload updates, these are now merged into one with a payload update implying a status change to healthy. This should avoid the potential for strange races between setting the status back to healthy and updating the data. A resulting limitation is that if a unit wants to change from stalled to healthy it has to submit a payload update, but in practice this health status change is pretty much always triggered by a new payload update becoming available, so this should be fine. This is a breaking change.
RTRTR – An RPKI data proxy
RTRTR is an RPKI data proxy, designed to collect Validated ROA Payloads from one or more sources in multiple formats and dispatch it onwards. It provides the means to implement multiple distribution architectures for RPKI such as centralised RPKI validators that dispatch data to local caching RTR servers.
RTRTR can read RPKI data from multiple RPKI Relying Party packages via RTR and JSON and, in turn, provide an RTR service for routers to connect to. The HTTP server provides the validated data set in JSON format, as well as a monitoring endpoint in plain text and Prometheus format.
If you have feedback, we would love to hear from you. Don’t hesitate to create an issue on Github or post a message on our RPKI mailing list or Discord server.
Getting Started
Getting started with RTRTR is really easy by installing a binary package for either Debian and Ubuntu or for Red Hat Enterprise Linux (RHEL) and compatible systems such as Rocky Linux. Alternatively, you can run with Docker or build from the source code using Cargo, Rust’s build system and package manager.
Please refer to the comprehensive documentation to learn what works best for you.