Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh, December 2022
- File formats:
- Also available: XML file for editing
- PROPOSED STANDARD
- RFC 8481
- R. Bush
- sidrops (ops)
Cite this RFC: TXT | XML | BibTeX
Discuss this RFC: Send questions or comments to the mailing list email@example.com
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9324
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.