metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 9324: Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh

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

A BGP speaker performing policy based on the Resource Public Key Infrastructure (RPKI) should not issue route refresh to its neighbors because it has received new RPKI data. This document updates RFC 8481 by describing how to avoid doing so by either keeping a full Adj-RIB-In or saving paths dropped due to ROV (Route Origin Validation) so they may be reevaluated with respect to new RPKI data.

Document record

Document ID
RFC9324
Published
December 2022
Authors
R. Bush; K. Patel; P. Smith; M. Tinka
Status
PROPOSED STANDARD
Stream
IETF
Area
ops
Pages
7
Also known as
—
Updates:
RFC 8481

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/9324-policy-based-on-the-resource-public-key-infrastructure-rpki-without-route-refres