Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
| rpki [2021/11/25 10:55] – [ROV] philip | rpki [2021/11/25 10:56] – [ROV] philip |
|---|
| The following table documents ROV behaviours on receipt of updated RPKI information from validators. | The following table documents ROV behaviours on receipt of updated RPKI information from validators. |
| |
| "Adj-RIB-In" is the BGP table as received from BGP peers, prior to processing by inbound policy. Retaining this BGP table requires extra memory (not a hardship in this day and age), and makes process BGP policy changes simple. Without Adj-RIB-In, the router has to send a [[https://datatracker.ietf.org/doc/html/rfc2918 | Route Refresh]] to the peer to request all BGP updates again. Which can be exciting when today's IPv4 table is heading to 900k prefixes, and IPv6 table is heading to 150k prefixes. | "Adj-RIB-In" is the BGP table as received from BGP peers, prior to processing by inbound policy. Retaining this BGP table requires extra memory (not a hardship in this day and age), and makes processing incoming BGP policy changes simple. Without Adj-RIB-In, the router has to send a [[https://datatracker.ietf.org/doc/html/rfc2918 | Route Refresh]] to the peer to request all BGP updates again. Which can be exciting when today's IPv4 table is heading to 900k prefixes, and IPv6 table is heading to 150k prefixes. |
| |
| ^ Implementation ^ Adj-RIB-In ^ ROV behaviour ^ Notes ^ | ^ Implementation ^ Adj-RIB-In ^ ROV behaviour ^ Notes ^ |
