Optimizations
Cache previously validated routes to avoid re-validation, e.g., if router crashes or neighbor link is lost
Required BGP caching would cover ~89% of UPDATEs
- retain peer cache over route flap
- caching last two distinct paths from a single peer hits another 6% of UPDATEs
Mark routes “withdrawn” for use later, e.g., if link flapped, to speed up validation for reinstated routes
Keep only needed certificate fields in Secure-BGP databases