By Topic

On characterizing BGP routing table growth

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

3 Author(s)
Tian Bu ; Massachusetts Univ., Amherst, MA, USA ; Lixin Gao ; D. Towsley

BGP routing table sizes have increased by an order of magnitude over the last six years. This dramatic growth can decrease packet forwarding speed and demand more router memory space. We explore the extent that various factors contribute to the routing table size and characterize the growth of each contribution. We begin with a measurement study using the routing tables of an Oregon route views server to determine the contributions of multi-homing, load balancing, address fragmentation, and failure-to-aggregate to routing table size. Address fragmentation makes the greatest contribution and it is three times those of multihoming or load balancing. The contribution of failure-to-aggregate is the least. Although multihoming and load balancing contribute less to routing table size than address fragmentation, we observe that their contributions grow faster than the routing table does and that load balancing has surpassed multihoming, becoming the fastest growing contributor. Moreover, we find that both load balancing and multihoming contribute to routing table growth by introducing more prefixes of length between 17 and 25, which are the fastest growing prefixes. Next, we examine the growth routable IP addresses, and conclude that their growth is much slower than that of routing table size. Lastly, we demonstrate that our findings based on views derived from the Oregon server are accurate through an evaluation using 15 additional routing tables collected from different locations in the Internet.

Published in:

Global Telecommunications Conference, 2002. GLOBECOM '02. IEEE  (Volume:3 )

Date of Conference:

17-21 Nov. 2002