Technology and engineering · 2022
RFC 9324: Policy Based on the Resource Public Key Infrastructure (RPKI) without Route Refresh
by R. Bush, K. Patel, P. Smith et al.
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.
Anyone can see what's on the shelves. Open a book with a free account, and stay in touch with its book club.
- First published
- 2022
- Status
- Proposed Standard
- Pages
- 7
- Updates
- RFC 8481
- Copyright
- ✓ Free to read · Copied in full, as published
Where it comes from
RFC Editor · IETF Datatracker · IETF Trust Legal Provisions
Copied in full and unchanged from the RFC Editor, with the RFC's own notices. © IETF Trust and the persons identified as the document authors. The IETF Trust allows copying and distributing an RFC in full and without modification, so Micwyn shows it exactly as published and makes no study guide, audio or other version of it.
Discuss a passage
Select any passage in the reader and press Discuss to talk about it in public.