Avoiding Route Origin Authorizations Containing Multiple IP Prefixes
RFC 9455, “Avoiding Route Origin Authorizations Containing Multiple IP Prefixes”, is a Best Current Practice document published in August 2023 by Z. Yan, R. Bush, G. Geng, T. de Kock, J. Yao. The canonical text is published by the RFC Editor.
Abstract
When using the Resource Public Key Infrastructure (RPKI), address space holders need to issue Route Origin Authorization (ROA) object(s) to authorize one or more Autonomous Systems (ASes) to originate BGP routes to IP address prefix(es). This memo discusses operational problems that may arise from ROAs containing multiple IP prefixes and recommends that each ROA contain a single IP prefix.
What “Best Current Practice” means
Documents the IETF community's recommended operational or procedural practice rather than a protocol specification.
The canonical text of RFC 9455 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9454 Update to OSPF Terminology
- RFC 9456 Updates to the TLS Transport Model for SNMP
- RFC 9453 Applicability and Use Cases for IPv6 over Networks of Resource- constrained Nodes
- RFC 9457 Problem Details for HTTP APIs
- RFC 9452 Network Service Header Encapsulation for In Situ OAM Data
- RFC 9451 Operations, Administration, and Maintenance Packet and Behavior in the Network Service Header
- RFC 9459 CBOR Object Signing and Encryption : AES-CTR and AES-CBC
- RFC 9450 Reliable and Available Wireless Use Cases