Our system is currently under heavy load due to increased usage. We're actively working on upgrades to improve performance. Thank you for your patience.
GLOBECOM 2009 - 2009 IEEE Global Telecommunications Conference 2009
DOI: 10.1109/glocom.2009.5425443
|View full text |Cite
|
Sign up to set email alerts
|

IP Fast Reroute for Double-Link Failure Recovery

Abstract: Abstract-Failure recovery using IP fast reroute (IPFRR) has gained much attention recently. The basic idea is to find backup paths and configure the routing tables in advance. After a failure is detected, the pre-determined backup paths are used immediately to forward the affected packets. Since the calculation and configuration are performed in advance, the recovery can be completed very quickly. IPFFR is considered as a promising approach to enhance the survivability of IP networks.While single failure recov… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
4
0

Year Published

2010
2010
2017
2017

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(4 citation statements)
references
References 19 publications
0
4
0
Order By: Relevance
“…Such solutions support fast recovery for all possible single component failures, and a few can even handle two simultaneous link failures [17], [35]. Nevertheless, they also cause significant side-effects that negatively impact performance: Diverted packets need additional processing that may have to take place in the router slow path, and if they exceed MTU size due to the IP tunnel header or the extra embedded information, they must be fragmented as well.…”
Section: A Previous Work On Ip Fast Reroutementioning
confidence: 97%
“…Such solutions support fast recovery for all possible single component failures, and a few can even handle two simultaneous link failures [17], [35]. Nevertheless, they also cause significant side-effects that negatively impact performance: Diverted packets need additional processing that may have to take place in the router slow path, and if they exceed MTU size due to the IP tunnel header or the extra embedded information, they must be fragmented as well.…”
Section: A Previous Work On Ip Fast Reroutementioning
confidence: 97%
“…We distinguish between approaches that deterministically chose the outgoing port and those that do it in a probabilistic manner. Among the former ones, previous works are limited in several aspects: the proposed heuristics have no provable failover guarantees [13], [14]; failover mechanisms have limited guaranteed resilience against only one single link/node failure [15]- [20] or resiliency to ⌊ k 2 −1⌋ link failures for k-connected graphs [2]; routing focus limited to shortestpath-IP [13], [31], [32]; impossibility of achieving resiliency to any arbitrary number of link failures [16]. For specific topologies, works [35], [36] achieve resiliency to k − 1 link failures but no general methodology is described.…”
Section: Related Workmentioning
confidence: 99%
“…Our work belongs to this category. Previous works are limited in several aspects: the proposed heuristics have no provable failover guarantees [14], [15]; failover mechanisms have limited guaranteed resilience against only one single link/node failure [16]- [21] or ⌊ k 2 − 1⌋resiliency for k-connected graphs [2]; routing focus limited to shortest-path-IP [14], [34], [35]; impossibility of achieving ∞-resiliency [17]. For specific topologies, works [38], [39] achieve k − 1 resiliency but no general methodology is described.…”
Section: Related Workmentioning
confidence: 99%