Quantum-safe routing · Eval 1

RPKI Cost Explorer

The full RPKI (547k objects from an rpki-client snapshot), re-costed with post-quantum signatures. Choose a trust-root algorithm and an algorithm for everything below it, then turn Merkle batching on or off.

Try

Trust rootSigns the ~5 trust-anchor certificates

Everything below the rootCA certs, CRLs, ROAs, manifests, ASPAs

Merkle batchingOne signature covers a tree of N ROAs / manifests / ASPAs

Off: every object carries its own key and signature

642561k4k16k

Repository size

–

What every relying party downloads on a fresh sync

Full verify time

–

CPU time to validate every signature once, single core

Signature + key share of bytes

–

Trust-anchor certificate

–

Trust-anchor verify

–

Size by algorithm

today's RPKI (RSA-2048, no batching)

Verify time by algorithm

today's RPKI (RSA-2048, no batching)

Compare side by side

Today's RPKI is the fixed reference. Pin a setup to keep it here while you try others; tap a pinned setup to load it again.

All numbers for this trust root

Model. Each object keeps its measured non-crypto payload; its RSA-2048 signatures and public keys are swapped for the chosen algorithm's. With batching, a ROA, manifest or ASPA carries a Merkle inclusion path of ⌈log₂N⌉ SHA-256 hashes plus a 1/N share of one signature and key. CA certificates and CRLs are never batched. Verify times come from measured per-operation benchmarks.

Source. data/rpki_cost_matrix.csv (shared with the BGPsec demo via assets/data.js), exported from the paper's Eval 1 (python -m pqeval.rpki_cost_model).