Abstract
Implementing BGP route processing in an event-driven manner appears to be advantageous in terms of scalability. However, the inter-domain routing system as a whole would be overwhelmed without some type of rate limiting on BGP update streams. At first glace, an event-driven, pipelined route processing model does not seem to fit well with the traditional timer-based way of implementing BGP rate-limiting. In this paper we present a lazy event-driven BGP route processing pipeline that easily accommodates rate limiting.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
