The Use of maxLength in the Resource Public Key Infrastructure (RPKI), October 2022
- File formats:
- BEST CURRENT PRACTICE
- Y. Gilad
- sidrops (ops)
Discuss this RFC: Send questions or comments to firstname.lastname@example.org
This document recommends ways to reduce the forged-origin hijack attack surface by prudently limiting the set of IP prefixes that are included in a Route Origin Authorization (ROA). One recommendation is to avoid using the maxLength attribute in ROAs except in some specific cases. The recommendations complement and extend those in RFC 7115. This document also discusses the creation of ROAs for facilitating the use of Distributed Denial of Service (DDoS) mitigation services. Considerations related to ROAs and RPKI-based Route Origin Validation (RPKI-ROV) in the context of destination-based Remotely Triggered Discard Route (RTDR) (elsewhere referred to as "Remotely Triggered Black Hole") filtering are also highlighted.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.