87f73eeca1
This PR removes the serial number and optional diff from payload::Update. The serial number was never actually used anywhere so has always been unnecessary. However, it did provide a sort of safety net for using the optional diff in case an update was missed somehow. This, however, only ever happened with the RTR target, so dropping the diff and re-calculating is probably acceptable both from a performance and reliability perspective.
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.