metasystema.org
CurrentBEST CURRENT PRACTICEIETF streamBCP238

RFC 9455: Avoiding Route Origin Authorizations (ROAs) Containing Multiple IP Prefixes

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9455
Published
August 2023
Authors
Z. Yan; R. Bush; G. Geng; T. de Kock; J. Yao
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
ops
Pages
6
Also known as
BCP238

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9455-avoiding-route-origin-authorizations-roas-containing-multiple-ip-prefixes