KEYNOTE: Demystifying RPKI: Exploring Tools to Simplify ROA Planning and Visualize Validation#

Steve Wallace, Internet2 (NSF-supported, OAC-2530871)

• Why: ROA creation is the single biggest friction point in RPKI adoption — operators fear creating a ROA that accidentally invalidates their own (or a customer's) more-specific announcements. This is a set of free, working tools that directly address that fear, plus an early look at ASPA object planning.
• What: Three web tools hosted at rootbeer.internet2.edu: an RPKI-ROA Planner that computes candidate ROAs for a prefix and the safest order to create them; an RPKI-ROA Visualizer that walks through Route Origin Validation bit by bit (useful for training staff who don't intuit maxLength semantics); and an experimental RPKI-ASPA Planner that suggests a draft ASPA object for an ASN.
• How: The ROA Planner correlates three data sources — IRR route objects, currently observed Internet routes, and historical routing data — to derive the set of plausible origins for a prefix, then lets the user pick which apply and sequences ROA creation to avoid transient Invalid states. The ASPA Planner builds its suggestion from CAIDA AS-relationship data ("and some magic," per the speaker).
• Where applicable: Broadly applicable to any operator with ARIN-region resources; the tools are public and free. The ASPA Planner is explicitly experimental and should be treated as a starting draft, not a turnkey ASPA — ASPA semantics are still moving through the IETF.