frog

Download

frog@lists.frrouting.org

September 2026

2 participants
2 discussions

Subject: Inquiry: ASPA Path Validation Support in FRR Following RTR Protocol v2 Standardization
by Chen Xing 21 Sep '26

21 Sep '26

Hi all, I have a question regarding FRR's roadmap for ASPA (Autonomous System Provider Authorization) path validation. The RPKI-to-Router protocol version 2 (draft-ietf-sidrops-8210bis) introduces ASPA PDU support, enabling routers to receive ASPA objects from RPKI caches and perform AS_PATH verification. Other open-source routing daemons have already started implementing this — for example, OpenBGPD has introduced ASPA verification, and Routinator has added RTR v2 and ASPA payload support (behind an enable-aspa option). From what I can tell, FRR's current RPKI implementation covers Prefix Origin Validation (ROV) via RFC 6810/8210, but I haven't found any indication of ASPA support in the documentation or release notes. I also noticed some recent claims online that FRR "already offers ASPA support," but I could not locate the corresponding code or configuration options, so I wanted to ask here for clarification. My questions are: Is ASPA path validation (or RTR protocol v2 support) currently on the FRR development roadmap? If so, is there an estimated timeline or a tracking issue we could follow? If not, is this something the team would consider for a future release, given the growing deployment of ASPA objects in the wild? Any information would be greatly appreciated. Thanks

1 0

Inquiry: ASPA Path Validation Support in FRR Following RTR Protocol v2 Standardization
by 王森栋 21 Sep '26

21 Sep '26

Hi all, I have a question regarding FRR's roadmap for ASPA (Autonomous System Provider Authorization) path validation. The RPKI-to-Router protocol version 2 (draft-ietf-sidrops-8210bis) introduces ASPA PDU support, enabling routers to receive ASPA objects from RPKI caches and perform AS_PATH verification. Other open-source routing daemons have already started implementing this — for example, OpenBGPD has introduced ASPA verification, and Routinator has added RTR v2 and ASPA payload support (behind an enable-aspa option). From what I can tell, FRR's current RPKI implementation covers Prefix Origin Validation (ROV) via RFC 6810/8210, but I haven't found any indication of ASPA support in the documentation or release notes. I also noticed some recent claims online that FRR "already offers ASPA support," but I could not locate the corresponding code or configuration options, so I wanted to ask here for clarification. My questions are: * Is ASPA path validation (or RTR protocol v2 support) currently on the FRR development roadmap? * If so, is there an estimated timeline or a tracking issue we could follow? * If not, is this something the team would consider for a future release, given the growing deployment of ASPA objects in the wild? Any information would be greatly appreciated. Thanks, John

1 0