RFC 9319: The Use of maxLength in the Resource Public Key Infrastructure (RPKI)

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…

Read RFC 9319 on the RFC Editor

Outgoing relationships (12 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 4271: A Border Gateway Protocol 4 (BGP-4)
Normative reference — RFC 1918: Address Allocation for Private Internets
Normative reference — RFC 6480: An Infrastructure to Support Secure Internet Routing
Normative reference — RFC 6482: A Profile for Route Origin Authorizations (ROAs)
Normative reference — RFC 6811: BGP Prefix Origin Validation
Normative reference — RFC 7115: Origin Validation Operation Based on the Resource Public Key Infrastructure (RPKI)
Informative reference — RFC 8205: BGPsec Protocol Specification
Informative reference — RFC 5737: IPv4 Address Blocks Reserved for Documentation
Informative reference — RFC 6907: Use Cases and Interpretations of Resource Public Key Infrastructure (RPKI) Objects for Issuers and Relying Parties
Informative reference — RFC 7999: BLACKHOLE Community

Incoming relationships (2 related RFCs)

Informatively referenced by — RFC 9582: A Profile for Route Origin Authorizations (ROAs)
Informatively referenced by — RFC 9774: Deprecation of AS_SET and AS_CONFED_SET in BGP