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

On the Resiliency of Static Forwarding Tables

Abstract: Fast Reroute (FRR) and other forms of immediate failover have long been used to recover from certain classes of failures without invoking the network control plane. While the set of such techniques is growing, the level of resiliency to failures that this approach can provide is not adequately understood. In this paper, we embarked upon a systematic algorithmic study of the resiliency of forwarding tables in a variety of models (i.e., deterministic/probabilistic routing, with packet-header-rewriting, with pack… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
88
0

Year Published

2017
2017
2023
2023

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 44 publications
(88 citation statements)
references
References 39 publications
0
88
0
Order By: Relevance
“…For destination-based routing, observe that we do not need to forward to a node with a depth exactly one smaller, but any smaller depth (or higher version) would suffice. In this context, fault-tolerance could benefit benefit from link-disjoint forwarding trees [15], which can be computed efficiently [16], along with appropriate optimization for route lengths [17,18].…”
Section: Discussion: Speed Up and Fault-tolerancementioning
confidence: 99%
“…For destination-based routing, observe that we do not need to forward to a node with a depth exactly one smaller, but any smaller depth (or higher version) would suffice. In this context, fault-tolerance could benefit benefit from link-disjoint forwarding trees [15], which can be computed efficiently [16], along with appropriate optimization for route lengths [17,18].…”
Section: Discussion: Speed Up and Fault-tolerancementioning
confidence: 99%
“…For routing decisions we assume that forwarding rules can match packet header fields as well as the in-port (the port from which a packet arrives at v, already used in [15] for fast reroute), and depending on this match, define the outgoing port to which a packet is forwarded at v. In other words, the focus of this paper is on oblivious (i.e., static) routing algorithms which do not rely on any dynamic state at nodes (e.g., counters) or in packets: we do not allow packet tagging. While tagging can improve the robustness of routing [16], [17], it is often undesirable in practice to change header fields.…”
Section: Modelmentioning
confidence: 99%
“…In particular, thanks to the possibility to match the in-port and the source of a packet, a node can be traversed multiple times during failover, without ending up in an infinite loop. That is, failover routes may not be simple paths but form walks, e.g., consider a network with a dead-end, forcing the packets to return along the same link [16].…”
Section: Modelmentioning
confidence: 99%
See 1 more Smart Citation
“…In [32], [33], Chiesa et al conjecture [32], [33] that is at least always possible to deterministically achieve what they call ideal resilience: to preserve connectivity in a k-(edge-)connected network if there are at most k − 1 link failures. Today, it is still unknown whether this conjecture holds.…”
Section: Further Related Workmentioning
confidence: 99%