2012
DOI: 10.1109/tnet.2011.2168610
|View full text |Cite
|
Sign up to set email alerts
|

BGP Churn Evolution: A Perspective From the Core

Abstract: The scalability limitations of BGP have been a major concern lately. An important aspect of this issue is the rate of routing updates (churn) that BGP routers must process. This paper presents an analysis of the evolution of churn in four networks at the backbone of the Internet over a period of seven years and eight months, using BGP update traces from the RouteViews project. The churn rate varies widely over time and between networks. Instead of descriptive "black-box" statistical analysis, we take an explor… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
20
0

Year Published

2013
2013
2023
2023

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 44 publications
(20 citation statements)
references
References 27 publications
0
20
0
Order By: Relevance
“…This solution does not affect neighboring routers and it can be done by a simple software update [18]. However, aggregation may come at the cost of a higher FIB update churn (e.g., see [5]): upon certain BGP updates, aggregated FIB entries may have to be disaggregated again. Frequent FIB updates are problematic as upon each update, internal FIB structures have to be rebuilt to ensure routing consistency.…”
Section: Introductionmentioning
confidence: 99%
“…This solution does not affect neighboring routers and it can be done by a simple software update [18]. However, aggregation may come at the cost of a higher FIB update churn (e.g., see [5]): upon certain BGP updates, aggregated FIB entries may have to be disaggregated again. Frequent FIB updates are problematic as upon each update, internal FIB structures have to be rebuilt to ensure routing consistency.…”
Section: Introductionmentioning
confidence: 99%
“…In the following results, we consider values of ↵ ranging from 10 to 20, and values of of 1, 10, 30, 60, and 600 seconds. We chose these values of because they capture the scales at which BGP routing events take place [7].…”
Section: B Analysis Of Churn Localitymentioning
confidence: 99%
“…While the aggregation of the FIB entries is beneficial in terms of memory, it also entails a potential overhead: As the FIB contents of a router change over time -with peaks of several hundreds to thousands of modifications inside one second [7] -the FIB aggregation algorithm needs to translate every routing update into one or more updates to the aggregated FIB. This is because when applying routing updates as they come to the aggregated FIB, forwarding consistency to the original FIB is likely to be violated [18].…”
mentioning
confidence: 99%
“…Previous works used public BGP dataset in a wide variety of manners, e.g., for analyses on AS-level topology discovery [18], commercial relationships between ASes [27], BGP update churn [28], prefix allocation and aggregation [29], prefix reachability [21], and many more. The significance of contributions that tried to match BGP control-plane data with data-plane measurements was questioned by Bush et al, who showed in [21] that BGP data are inadequate for this goal.…”
Section: Related Workmentioning
confidence: 99%