Expand description

RTR: the RPKI to Router Protocol.

RPKI, the Resource Public Key Infrastructure, is a distributed database of signed statements by entities that participate in Internet routing. A typical setup to facilitate this information when making routing decisions first collects and validates all statements into something called a local cache and distributes validated and normalized information from the cache to the actual routers or route servers. The standardized protocol for this distribution is the RPKI to Router Protocol or RTR for short.

This crate implements both the server and client side of RTR. Both of these are built atop Tokio. They are generic over the concrete socket type and can thus be used with different transports. They also are generic over a type that provides or consumes the data. For more details, see the Server and Client types.

The crate implements both versions 0 and 1 of the protocol. It does not, currently, support router keys, though.

You can read more about RPKI in RFC 6480. RTR is currently specified in RFC 8210.


pub use self::client::Client;
pub use self::payload::Action;
pub use self::payload::Payload;
pub use self::payload::Timing;
pub use self::server::Server;
pub use self::state::State;
pub use self::state::Serial;


The RTR client.

The data being transmitted via RTR.

Raw protocol data.

The RTR server.

Session state.