Proceedings of the ACM Internet Measurement Conference 2020
DOI: 10.1145/3419394.3423624
|View full text |Cite
|
Sign up to set email alerts
|

BGP Beacons, Network Tomography, and Bayesian Computation to Locate Route Flap Damping

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
9
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 16 publications
(11 citation statements)
references
References 27 publications
0
9
0
Order By: Relevance
“…Since these use cases either rely on route engineering or on understanding route changes, revtr 2.0 should be able to measure these routes in roughly the time period that traffic engineering techniques are given to converge. Announcements every 15 minutes were subject to route flap damping [41], meaning that faster changes impede traffic engineering, and so we want to support quickly bootstrapping outside sources and issuing ≈15,000 reverse traceroutes within 15 minutes. This rate equates to ≈1.4M per day, but, in practice, most studies are more conservative (waiting 90 [82] or 120 [19,25,53,66] minutes between announcements), and so 1.4M per day will suffice to support multiple parallel uses.…”
Section: Goalsmentioning
confidence: 99%
See 1 more Smart Citation
“…Since these use cases either rely on route engineering or on understanding route changes, revtr 2.0 should be able to measure these routes in roughly the time period that traffic engineering techniques are given to converge. Announcements every 15 minutes were subject to route flap damping [41], meaning that faster changes impede traffic engineering, and so we want to support quickly bootstrapping outside sources and issuing ≈15,000 reverse traceroutes within 15 minutes. This rate equates to ≈1.4M per day, but, in practice, most studies are more conservative (waiting 90 [82] or 120 [19,25,53,66] minutes between announcements), and so 1.4M per day will suffice to support multiple parallel uses.…”
Section: Goalsmentioning
confidence: 99%
“…revtr 2.0 supports quick iteration: Reverse traceroute measurements took 9-13 minutes per routing configuration, similar to the other required steps: 15 minutes to wait for BGP convergence and avoid route flap dampening [36,41,53,71,82] and 15 minutes to refresh the atlas. revtr 2.0 can be integrated into automated TE systems, providing scale and coverage that cannot be matched by querying operators or looking glasses.…”
Section: Supporting Traffic Engineeringmentioning
confidence: 99%
“…Path-to-link tomography can also enable efficient estimation of link metrics even when there are no such restrictions [26], [27]. BeCAUSe [28] is an interesting recent work that uses path-to-link tomography to reveal the deployment of route flap damping in BGP routers. Network troubleshooting (identifying and locating faults) is yet another application.…”
Section: B Related Workmentioning
confidence: 99%
“…These variations are mainly due to path hunting and noise reduction techniques (e.g. MRAI and Route Flap Damping [4,6,8,12,19]) and are hardly predictable. (3) Local topological changes.…”
Section: Hunting Bgp Zombiesmentioning
confidence: 99%
“…Understanding prefix withdrawal propagation time is key to differentiate both events. Past research has shown that withdrawals usually lasts a few minutes [11] and in the case of Route Flap Damping up to one hour [8]. From our data set we estimate typical withdrawing time, , by looking at the time duration of ( ) drops, that is − , necessary for prefix to be completely withdrawn ( ( ) = 0 and ( ) > ℎ ).…”
Section: Withdrawal Propagation Timementioning
confidence: 99%