rpki
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rpki [2021/11/25 10:28] – [ROV] philip | rpki [2021/11/25 11:03] (current) – [RPKI Notes] philip | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | {{: | + | ====== RPKI Notes ====== |
+ | Basically BGP implementations should/must not send a route refresh when receiving updated RPKI data, and are recommended instead to retain the received prefix that was marked as invalid should the future RPKI state change. | ||
- | ====== | + | It has been noted by several operators that their Cisco routers implementing ROV were bombarding peers with Route Refresh requests. This is difficult for those routers which are " |
+ | |||
+ | Refer to [[https:// | ||
+ | |||
+ | Also presented at [[https:// | ||
===== ROV ===== | ===== ROV ===== | ||
- | ^ Vendor | + | The following table documents ROV behaviours on receipt of updated RPKI information from validators. |
+ | |||
+ | " | ||
+ | |||
+ | ^ Implementation | ||
| Cisco IOS-XE | No | VRP update triggers a route-refresh | Workaround is to turn on " | | Cisco IOS-XE | No | VRP update triggers a route-refresh | Workaround is to turn on " | ||
| Cisco IOS-XR | No | VRP update triggers a route-refresh | Workaround is to turn on " | | Cisco IOS-XR | No | VRP update triggers a route-refresh | Workaround is to turn on " | ||
Line 12: | Line 21: | ||
| Bird 2.0.8 | ? | handles VRP updates locally | "rpki reload on" is default in 2.0.8 [[https:// | | Bird 2.0.8 | ? | handles VRP updates locally | "rpki reload on" is default in 2.0.8 [[https:// | ||
| Arista EOS | Default | VRP updated handled locally | Adj-RIB-In can be turned off | | | Arista EOS | Default | VRP updated handled locally | Adj-RIB-In can be turned off | | ||
+ | | FRR 8.1 | ? | ? | ? | | ||
[[start| Back to Home page]] | [[start| Back to Home page]] |
rpki.txt · Last modified: 2021/11/25 11:03 by philip