Differences

This shows you the differences between two versions of the page.

--- rpki [2021/11/25 10:56] – [ROV] philip
+++ rpki [2021/11/25 11:03] (current) – [RPKI Notes] philip
@@ Line 1: / Line 1: @@
 ====== RPKI Notes ======
-Refer to [[https://datatracker.ietf.org/doc/html/draft-ymbk-sidrops-rov-no-rr | RPKI-Based Policy Without Route Refresh]] for context.
+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.
-Basically BGP implementations should/must not send a route refresh when receiving updated RPKI data, and are recommended instead to retain the prefix 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 "control plane challenged" and can be construed as a denial of service on those peering routers. There are instances where networks have been depeered because of this.
+Refer to [[https://datatracker.ietf.org/doc/html/draft-ymbk-sidrops-rov-no-rr | RPKI-Based Policy Without Route Refresh]] for context.
 Also presented at [[https://ripe83.ripe.net/archives/video/636 | RIPE 83]] for additional background and context.
-It has been noted by several operators that their Cisco routers implementing ROV were bombarding peers with Route Refresh requests. This is challenging for those routers which are "control plane challenged" and can be construed as a denial of service on those peering routers.
 ===== ROV =====