BCP 238

RFC 9455

Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes, August 2023

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Also available: XML file for editing
 
Status:
BEST CURRENT PRACTICE
Authors:
Z. Yan
R. Bush
G. Geng
T. de Kock
J. Yao
Stream:
IETF
Source:
sidrops (ops)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9455

Discuss this RFC: Send questions or comments to the mailing list sidrops@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9455


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.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search