Fast Rerouting Against Dynamic Failures: 2-Resilience via Ear-Decomposition and Planarity
Abstract
Modern communication networks employ local fast failover mechanisms in the data plane, swiftly reacting to link failures through pre-installed rerouting rules. This paper investigates resilient routing schemes that guarantee packet delivery under up to link failures, provided the source and destination remain connected in the degraded network. While prior theoretical studies have mainly addressed static failures, where multiple links fail simultaneously and permanently, real networks often experience dynamic failures, such as transient link flapping caused by short-lived faults.
We study the limits of basic and source-matched failover routing with packet-header rewriting against dynamic failures in general graphs. In basic routing, forwarding depends only on active links, incoming ports, and the destination, whereas source-matched routing additionally incorporates the source, requiring more memory (and logic) at the router. The -resilient source-matched routing for static failures is shown to fail under permanent but non-simultaneous failures. Moreover, even with source matching, we prove that in planar graphs resilience is impossible without bit rewriting, and in general graphs, perfect -resilience is unachievable by only rewriting bits.
For planar graphs, we introduce ear-decomposition into basic routing and develop novel local rerouting mechanisms that tolerate dynamic failures. These yield tight -resilient basic routing by rewriting only one or two bits, closing the gap between lower bounds and practical routing scheme.
Keywords and phrases:
Resilience, Local Failover, Routing, Dynamic Link Failures, Link FlappingCopyright and License:
2012 ACM Subject Classification:
Networks Routing protocols ; Computer systems organization Dependable and fault-tolerant systems and networksFunding:
German Research Foundation (DFG) project ReNO, Schwerpunktprogramm: Resilienz in Vernetzten Welten – Beherrschen von Fehlern, Überlast, Angriffen und dem Unbekannten (SPP 2378), 2023–2027.Editors:
Andrei Arusoaie, Emanuel Onica, Michael Spear, and Sara Tucci-PiergiovanniSeries and Publisher:
Leibniz International Proceedings in Informatics, Schloss Dagstuhl – Leibniz-Zentrum für Informatik
| Failure | Rewriting | Routing information | Graph | Resilience results for | |
| Type | Bits # | Per-source | Per-dest. | Classes | static & deterministic routing |
| static | no | ✓ | -resilience for , open for [5] | ||
| static | no | ✓ | -resilience for any [5] | ||
| static | no | ✓ | ✓ | -resilience for any [14] | |
| static | ✓ | -resilience [5] | |||
| static | no | ✓ | -resilience [13], no -resilience () [5] | ||
| static | no | ✓ | ✓ | arbitrary -resilience impossible [17] | |
| static | no | ✓ | ✓ | -resilience possible, -resilience impossible [8] | |
| dynamic | no | ✓ | -resilience possible for [10] | ||
| dynamic | no | ✓ | -resilience possible for any [10] | ||
| dynamic | ✓ | -resilience possible for any [10] | |||
| semi-dynamic | ✓ | -resilience possible for any [10] | |||
| dynamic | ✓ | HDR--Bits in [5, Algorithm 2] inapplicable [10] | |||
| dynamic | no | ✓ | -resilience imposs. for (link-circular) [10] | ||
| dynamic | no | ✓ | -resilience possible [10], no -resilience () [5, 10] | ||
| dynamic | no | ✓ | ✓ | -resilience is impossible [Thm. 3] | |
| dynamic | ✓ | ✓ | arbitrary -resilience impossible [Thm. 4] | ||
| semi-dynamic | no | ✓ | ✓ | -resilient algo. (static failures) in [8] inapplicable [Thm. 2] | |
| dynamic | or | ✓ | -resilient basic routing on planar graphs [Thms. 18 & 16] | ||
Legend: ✓indicates that this parameter is included in forwarding function. Graph classes are denoted as -edge-connected, planar, and general.
1 Introduction and Related Work
Communication networks are a critical infrastructure of the digital society. Since link failures – inevitable and increasingly frequent in large-scale systems [18] – can severely degrade service [1, 30, 35], modern networks deploy local fast failover in the data plane to respond faster to failures. These mechanisms rapidly reroute packets along preinstalled backup paths, avoiding global recomputation and enabling recovery times orders of magnitude faster [22, 13].
The core challenge of devising efficient data-plane failover mechanisms is to precompute local rerouting rules ensuring reachability under link failures, without knowledge of downstream link states. This reduces to the following fundamental question:
-
Can we devise a failover routing scheme capable of tolerating any link failures as long as the underlying topology remains connected?
Resilient failover mechanisms have attracted significant attention [13, 7, 5, 16, 8, 31]. Randomized approaches [3, 6], resembling random walks for graph exploration, can offer resilience but are impractical due to packet reordering and limited router support [14]. Similarly, packet duplication techniques such as flooding impose prohibitive overhead.
Standard routers implement basic failover routing by deterministically forwarding packets using only local information such as active links, in-ports, and destinations. Feigenbaum et al. [13] introduced DAG-based failover resilient to a single failure, but perfect resilience – tolerance to arbitrarily many failures – is impossible even in small graphs [15]. Chiesa et al. [5] further proved that basic routing cannot achieve -resilience even in planar graphs. Consequently, research has explored heuristics, extra local inputs [8, 10], header rewriting [4, 5], or dense connectivity [3, 5, 7, 17, 34]. In particular, header rewriting allows routers to modify reserved header bits to guide subsequent forwarding decisions.
For -edge-connected graphs, Chiesa et al. [5] showed that -resilient basic routing can be efficiently computed for , while the case remains open; with header-rewriting, they devised schemes that achieve -resilience in arbitrary -edge-connected graphs using either or header bits.
However, real networks are often sparse with locally dense subregions [11, 16], necessitating the study of general topologies. Dai et al. [8] showed that -resilient routing is feasible in general graphs when forwarding depends on both source and destination (source-matched routing), but -resilience is impossible. Source-matched routing, however, incurs up to -fold overhead in computing and storing per-pair routing tables compared to basic routing.
Most theoretical work assumes simultaneous fail-stop failures, where links fail once and remain unavailable, i.e., static graphs. In practice, however, failures are often asynchronous, with links recovering or flapping [27, 32, 24, 29]. Gill et al. [18] further classify datacenter link failures as long-lived or sporadic short-lived, the latter typically caused by software or transient errors.
As such dynamics turn the network into a time-varying graph, invalidating conventional failover routing schemes, Dai et al. [10] model link failures into three types: dynamic, where unstable links arbitrarily switch between up and down states; semi-dynamic, where fail-stop links may fail during packet traversal; and static, where all fail-stop links fail simultaneously. They revisit the ideal resilience results of [5] under dynamic settings and show that certain established results, e.g., the -bit rewriting, may become ineffective (see Tab. 1 for details).
Hence, this paper investigates deterministic worst-case -resilience on general graphs under the dynamic link failure models of [10], focusing on basic routing augmented with packet-header rewriting. Our work is closely related to Dai et al. [8, 10] and Chiesa et al. [5], as we extend the results of [8] to dynamic failures only on basic routing functions.
We show that in dynamic settings, the power of source-matched routing collapses to that of basic routing.
For instance, although -resilient source-matched routing is always achievable under static failures in general graphs [8], it becomes impossible even for planar graphs (see the counterexample in Fig. 4), as backtracking to the original source may be infeasible.
At the same time, we resolve the open question of [5] by providing the first -resilient basic routing on planar graphs by rewriting one- or two-bit in the packet header, even under dynamic failures. An overview of related results and our contributions is given in Table 1.
1.1 Contributions
This paper initiates the study of perfect resilience of fast rerouting under dynamic, non-simultaneous link failures. A summary of our results is given in Table 1. We prove that the -resilient source-matched routing of Dai et al. [8] already fails under semi-dynamic failures, and that -resilience via source-matched routing is impossible in planar graphs without packet-header rewriting. This impossibility extends to -resilience in general graphs, even with rewritable bits. In contrast, we present the first algorithms achieving -resilience against dynamic failures in planar graphs using basic routing by rewriting only one or two header bits. This is tight with respect to our dynamic lower bounds stated in Theorem 3 and the static lower bound of [5], thereby resolving the open problem of [5]. We can compute the routing scheme in time per destination on planar graphs, whereas source-matched routing [8] needs per source–destination pair, i.e., times slower.
Technical Novelty.
We introduce ear-decomposition into basic routing to design ear-based schemes that mimic source-matched routing, where each ear serves as a local source without interfering with others. Unlike existing approaches [5, 8, 17], which detour along induced cycles containing the failure (and thus risk looping under dynamic failures), our method selects landmark nodes to terminate such detours independently of the failure. Our algorithms leverage structural properties of planar embeddings, and we believe these techniques may be of independent interest for future studies on resilience against dynamic failures.
1.2 Organization
The remainder of this paper is organized as follows. We introduce our formal model in §2, then discuss the limitations of prior methods [5, 8] and present impossibility results for -resilient routing by rewriting bits under dynamic failures in §3. Next, we develop algorithms for computing -resilient basic routing schemes on planar graphs via one- or two-bit rewriting in §4, and conclude in §5 with open questions. We defer lengthy proofs to Appendix A–B.
2 Models and Preliminaries
We model the network as an undirected simple , where vertices in represent routers and undirected edges represent bi-directed links. For , let ; for , denotes the graph obtained by removing and all incident edges. For a subgraph , we write , , and for the neighbors, incident edges, and degree of in , respectively, omitting the subscript when clear from context. Each undirected edge corresponds to two directed arcs and . For and , we slightly abuse notation to let denote the subset of edges in that are incident to . For multigraphs, we extend the graph definition appropriately by allowing multiple distinguishable edges between any two vertices in .
Failure Models.
Let denote a set of link failures in , where each may fail to transfer packets in both directions when its state is down (failed). A link is fail-stop if its down state is permanent. We classify as:
-
Static – all links in are fail-stop and fail simultaneously;
-
Semi-dynamic – all links in are fail-stop but may fail at different times;
-
Dynamic – links in may alternate arbitrarily between up and down states over time.
Failover Routing Functions.
In failover routing, each node stores a predefined, static forwarding (interchangeably, routing) function to deterministically select an outgoing link (out-port) for each incoming packet based solely on local information at . Formally, given a graph , a general routing function at is
where is the destination of the incoming packet; gives the source of the incoming packet, with meaning “no source information”; is the incoming link (in-port) at , with indicating packet origination at ; and is the set of currently active (non-failed) links incident to . For multigraphs, extends naturally.
The routing function is basic if the source is always , and source-matched otherwise. Unless stated, we consider basic routing. Fixing a destination (basic) or a pair of source-destination (source-matched), we write and , omitting when clear. A routing scheme is the collection of routing functions on , e.g., .
It is worth noting that Feigenbaum et al. [13] showed that -resilience against static failures is impossible when using fewer parameters than those available in basic routing.
Header-Rewriting Routing.
Header-rewriting augments a routing scheme by reserving rewritable bits in each packet’s header. A routing function at can interpret and modify these bits to influence the current and subsequent forwarding decisions:
In practice, is limited by competing fields (e.g., TTL, checksums, QoS). Bit-rewriting adds processing overhead, latency, and potential packet loss, so minimizing improves transmission efficiency.
Further Concepts in Failover Routing.
We introduce several commonly used notions in failover routing. A packet is said to get stuck if it halts at a node other than its destination. For deterministic routing without header bit rewriting, a forwarding loop occurs when a packet traverses the same directed link (arc) twice; both directions of an undirected link may each be traversed once without forming a loop. Any loop possible under static failures can also occur under semi-dynamic or dynamic failures. A packet fails to reach its destination if it either gets stuck or enters a forwarding loop. A routing function at node is link-circular if forwards packets through an ordered circular sequence of neighbors, forwarding from to (indices taken modulo ). If link fails, the packet is sent to , and so forth, cycling back to after [5].
Definition 1 (-Resilient Failover Routing Problem).
Let be a graph and let be a designated destination. The -resilient failover routing problem is to compute a -resilient routing scheme for in under the static, semi-dynamic, or dynamic failure models. A forwarding scheme for is -resilient if, for every source and every set of link failures with , the scheme delivers a packet from to in the given failure model whenever and remain connected in . Here, denotes the subgraph obtained by removing all edges in , independent of the failure model.
Note on Definition 1.
The subgraph may have multiple connected components. We assume that dynamic or semi-dynamic failures in do not cause the routing functions to forward packets between distinct components of ; such cases are beyond the scope of our resilient routing model. Static failures are a subset of semi-dynamic failures, which in turn are a subset of dynamic failures; a resilient routing algorithm for one failure type applies to its subsets, while impossibility results extend to its supersets. Since resilient routing may require packets to retrace paths in reverse, dynamic and semi-dynamic failures can introduce inconsistencies in the set of active links perceived by deterministic routing functions, thereby increasing the likelihood of forwarding loops.
We focus on computing a -resilient routing scheme for a fixed destination , as the same algorithm applies to any . For source-matched routing, it suffices to consider a fixed pair , since the algorithm generalizes to any .
Further Notations and Graph Theory Concepts.
We first introduce the graph-theoretic concepts and notations used in this chapter. A path from to in is called a – path. Two paths are edge-disjoint if they share no edges (but may share vertices), and two edge-disjoint – paths and are node-disjoint if .
We focus on edge-connectivity, referred to simply as connectivity. For , two nodes and are (interchangeably, is) -edge-connected (or -connected) if there exist edge-disjoint – paths in . The graph is -edge-connected (or -connected) if any two distinct nodes are -connected. Nodes and are exactly -connected if they are -connected but not -connected.
Given a path , with for , the notation denotes the subpath of from to for . For , the induced subgraph contains all edges with .
A graph is planar if it can be drawn on the Euclidean plane without two edges intersecting except possibly at a common endpoint; such a drawing is a plane embedding of . Given a plane embedding, a face is a connected component of whose boundary consists of vertices and edges of . The unique unbounded face is the outer face (or unbounded face), and all other faces are inner (interior) faces (or bounded faces).
3 Limitations of Previous Approaches and Lower Bounds
In this section, we first highlight the limitations of previous failover approaches under dynamic failures, then show that -resilient source-matched routing is infeasible even for planar graphs, and finally prove that perfect -resilience is impossible with only rewriting bits.
3.1 Limitations of Prior Work
Without utilizing rewritable bits in packet headers, Chiesa et al. [5] proved that -edge-connected (planar) graphs do not admit -resilient routing against static failures. In contrast, Dai et al. [8] developed a -resilient routing algorithm for static failures in general graphs by additionally incorporating source matching. However, achieving -resilience under static failures is already impossible [8].
The -resilient routing algorithm of Dai et al. [8] computes, for each source–destination pair in a general graph , a planar kernel graph that preserves – connectivity under any two edge failures. In this kernel graph, and lie on the boundary of the outer face , and every inner face shares an edge with (see Fig. 1(a)). Routing then proceeds counterclockwise along from to , switching to a clockwise traversal of an inner face upon encountering a failure (Fig. 1(b)).
Compared to basic routing, source-matched routing incurs higher computational and memory costs, as it requires computing and storing routing tables for every pair of nodes, i.e., tables, whereas basic (only destination-based) routing needs only tables.
Dynamic failures transform the overlay graph from a static to a dynamic structure, rendering some classical failover routing rules ineffective.
As a common technique, the bouncing reroute rule, illustrated in Fig. 1(b), upon a failed arc, bounces a packet back via its reverse, detours around the induced cycle, and reencounters the failed edge in reverse to terminate the detour. This technique is widely used [5, 8, 17].
However, as shown in Fig. 1(b), if the dynamic failure becomes recovered on the second visit, the packet falls into a routing loop within the current induced cycle. A similar issue has also been observed in -resilient routing against dynamic failures on -edge-connected graphs using three-bit rewriting [10].
Moreover, in Theorem 2, we show that the -resilient source-matched routing by Dai et al. [8, Algorithm 1] no longer functions correctly even for two semi-dynamic failures. Due to space limitations, we present in Fig. 2 a counterexample that sketches the proof of Theorem 2.
Theorem 2.
There exists a graph where the -resilient source-matched routing of Dai et al. [8, Algorithm 1], designed for static failures, fails under two semi-dynamic failures, even though admits such a routing scheme.
3.2 Impossibility of Handling Dynamic Failures in General Graphs
After discussing the limitations of existing failover approaches under dynamic failures, we show in Theorem 3 that no source-matched routing scheme can tolerate two dynamic failures. The proof idea is illustrated in Fig. 3, while the formal proof is deferred to Appendix A.
Theorem 3.
There exists a -edge-connected planar graph as shown in Fig. 3, where it is impossible to have a -resilient source-matched routing scheme against dynamic failures without rewriting bits in packet headers.
For the counter-example graph as shown in Fig. 3, fixing when , the routing functions at and cannot know whether an incoming packet currently should either continue searching a path towards in or finding a path back to in to try paths in . Simply, by rewriting one bit in packet headers, the source-matched routing functions can resolve this weakness to achieve -resilience against dynamic failures again in . Now, a fundamental question arises: Can we achieve -resilience against dynamic failures in a general graph by only rewriting bits in packet headers?
In light of Theorem 4, we demonstrate that achieving perfect resilience through the modification of bits is impossible and defer its formal proof to Appendix A.
Theorem 4.
There exists graphs for which any resilient source-matched routing that can tolerate dynamic failures needs rewriting of at least bits in packet headers for .
4 -Resilient Routing Against Dynamic Failures on Planar Graphs
In contrast to our impossibility result, we now present algorithms achieving -resilience against dynamic failures on planar graphs. We first reduce the general problem, then introduce the elementary routing rules based on ear-decomposition and faces, and finally describe our -resilient basic routing scheme via one- or two-bit rewriting.
4.1 Problem Reductions and Basic Observations
By Claim 5, we reduce the problem to the case where is a simple -edge-connected plane graph, and in Lemma 6 we highlight an important observation on this simplified structure.
Claim 5 (Problem Reduction).
The problem of devising a -resilient routing algorithm against dynamic failures in a general planar graph can be reduced to the case of -edge-connected planar graphs. Throughout, we can assume that is a simple (plane) graph, i.e., it contains no parallel edges and has a plane embedding already.
Proof.
For a -edge-connected graph , Dai et al. [10] showed that a -resilient routing scheme against dynamic failures can be devised using three arc-disjoint arborescences, building on the original idea of [5]. Alternatively, we can obtain a -edge-connected graph of by replacing any edge in with two edges and , s.t., any -resilient routing scheme for can also work for .
Let be a -edge-connected graph. Define the set of bridges as Removing all bridges yields a collection of connected components of . By contracting each component to a single node , we obtain an abstract tree where every edge connects the two components in that originally joined.
Since is a tree, one can directly construct a -resilient routing on . Moreover, for each component , which is itself a subgraph of with edge-connectivity at least , if we can compute a -resilient routing within that reaches the endpoint corresponding to the bridge edge in , then combining these local routings with the tree routing on yields a global -resilient routing for .
If contains parallel edges between two nodes , each such edge can be replaced by a path of length two, namely and , where is a newly introduced auxiliary node.
Lemma 6.
If is a -edge-connected plane (embedded planar) graph, then each edge is shared by two distinct faces, i.e., and , where ( including the outer face) and .
Proof.
If is -edge-connected, then every edge lies on a cycle. By [12, Lema 4.2.2], each edge on a cycle of must be shared by two distinct faces.
Remark 7.
Even in the reduced setting, the problem remains challenging. Basic routing based solely on faces is already non-trivial: two failures on a face may require traversing its boundary in both clockwise and counterclockwise directions. This necessitates at least one rewritable bit to indicate the current direction, since an arc may be used in opposite directions by two adjacent faces sharing the same edge. This observation motivates us to design routing schemes that exploit not only faces but also additional structural information.
4.2 Routing on Ear Decomposition and Faces
Our -resilient routing algorithms combine ear-based routing with face detours. We begin by introducing the basic routing based on ear-decomposition and faces in the following.
4.2.1 Routing Rules Based on Ear Decomposition
Several variants of ear-decomposition appear in the literature (e.g., [19, 23, 21, 26]). In this work, we adopt the definition provided in the textbook [33].
Ear Decomposition.
An ear decomposition (abbreviately, ) of a graph is a sequence of subgraphs , where is a cycle in , and for each , is a path whose endpoints lie in , while all internal vertices of are disjoint from . The cycle is called the initial ear, and each (for ) is called an ear. If the two endpoints of coincide (so that forms a cycle), it is referred to as a closed ear; otherwise, it is an open ear [33, 19, 23, 25]. In particular, the family forms a partition of ; that is, every edge lies in exactly one ear . Robbins (1939) [25, 33] showed that a graph is -edge-connected if and only if it admits an ear-decomposition, in which each for is either an open ear or a closed ear, and every cycle in a -edge-connected graph can be the initial ear in some such decomposition. More specifically, one can compute an ear decomposition such that a specified vertex is contained in the initial ear [28, 21, 19, 23, 26]. In the following, we assume that the destination is implicitly contained in the initial ear.
Definition 8 (Routing Rules on Ears).
For a closed ear (including the initial ear), itself is a cycle. For an open ear with endpoints and , we form the auxiliary cycle by adding the edge .
For each (either open or closed) ear , we define the left (resp., right) routing on (excluding the added edge if is open) as the traversal of in the direction such that the interior of the corresponding cycle – itself if closed, or if open – lies on the left-hand (resp., right-hand) side during your traversing. In the case of an open ear, the endpoint visited last under the left (resp., right) routing is called the left (resp., right) endpoint. For a closed ear, the left and right endpoints coincide, yielding a unique endpoint.
Finally, for each ear , we define (resp., ) as the directed cycle (resp., path, if is open) obtained by traversing in the right (resp., left) direction, from its left (resp., right) endpoint to its right (resp., left) endpoint.
Since each edge uniquely belongs to some ear , each oriented arc of is uniquely contained in either or , even if is closed.
By Definition 9, we define a function that maps each node to an ear to start routing.
Definition 9.
Since a node may appear in multiple ears of , we define the function that returns the earliest ear (in terms of index ) containing as an internal node in the subgraph . In particular, let .
4.2.2 Routing Rules on Faces of Plane Graph
After defining the ear-based routing rules, Definition 10 presents the face-based routing rules.
Definition 10 (Routing Rules on Faces).
Given a plane embedding of a planar graph , for each inner face of , which is bounded by a cycle , we define the left (resp., right) routing on as the traversal on the boundary (cycle) of in the direction such that the bounded region of lies on the left-hand side (resp., right-hand side) during your traversing. Analogously, for the outer face of , the left (resp., right) routing on is defined as the traversal of the cycle in the direction such that the unbounded region of lies to the left-hand side (resp., right-hand side) of the traverser.
Henceforth, for each face (including ), let (resp., ) denote the directed cycle obtained by traversing the boundary of according to the left (resp., right) routing of . And we define a collection of directed cycles (resp., ).
Lemma 11.
Given a set of faces of a plane graph , fix a routing direction (either left or right) for all faces. Then no two directed cycles in (resp., ) share an arc. Moreover, once the routing direction is fixed (either or ), each orientation of an edge , i.e., an arc or , uniquely determines the corresponding face . In particular, for any edge , if and with and , then .
Proof.
We present the argument for right routing; the case of left routing follows analogously. By Lemma 6, every edge is incident with exactly two distinct faces, say .
Consider an embedding of on the Euclidean plane, and let be an edge shared by and . The infinite line by expanding separates the plane into two half-planes, with lying entirely on one side and entirely on the other. Now, when traversing an arc (resp., ), exactly one of these half-planes (and thus exactly one of the two faces) lies to the right of the traversal. Consequently, in a right routing, the directed cycles and cannot share the same directed arc of . Therefore, once the routing direction is fixed, each arc of an edge is contained in exactly one directed cycle , which uniquely determines the corresponding face .
By definition, for any edge and any face , if the arc belongs to , then the reverse arc belongs to . In Definition 12, we define the rightmost and leftmost nodes on each face respectively, which serve as checkpoints to terminate face-based routing.
Definition 12 (Associated Ear and Leftmost/Rightmost Node of a Face).
Given a -edge-connected plane graph , for each face (including the outer face ), the associated ear of is the first ear (with minimum index ) such that . Given the associated ear of , let be the edge traversed last along the right (resp., left) routing (resp., ) in terms of the edges in . The endpoint visited later in (resp., ) is called the rightmost node (resp., leftmost node) of , denoted by (resp., ). The leftmost or rightmost node of a face is uniquely determined and independent of the traversal direction on faces. We have if they coincide as the unique endpoint of a closed ear .
Lemma 13 shows that our face-based routing can visit all nodes of a face , including the leftmost and rightmost nodes of , provided there is at most one failure in .
Lemma 13.
Given (resp., ), for a dynamic failure , if one of its arcs, say , lies on a directed cycle (resp., ). Then, starting at and traversing along (resp., ), one can visit all nodes of and eventually reach , provided that the face contains at most one failed edge, i.e., .
Proof.
Our proof is carried out for the right routing ; the case of the left routing follows analogously. Suppose is failed. Starting from , the outgoing link (arc) along is not failed, and hence there exists a directed sub-path from to any node that is entirely contained in that is a directed path from to along .
4.3 Dynamic -Resilient Basic Routing with One- or Two-Bit Rewriting
Now, we formally present dynamic -resilient routing schemes on planar graphs using one- or two-bit rewriting. We first describe the two-bit rewriting algorithm and then show how to refine it to a one-bit algorithm. Finally, we provide the runtime analysis of these algorithms.
4.3.1 -Resilient Basic Routing Algorithm by Rewriting Two Bits
We first present our -resilient routing scheme on plane graphs by rewriting two bits, implemented in Algorithm 1 and Algorithm 2, with an illustrative example in Fig. 4.
The core idea of the two-bit rewriting algorithm is to route packets through ears in a waterfall manner towards when : a packet first follows and, upon encountering a failure, switches to . If every ear contains at most one failure, the packet eventually reaches without invoking face-based routing (This case is proved by Lemma 14).
If a second failure occurs on the same ear , routing switches to face-based mode () on the adjacent faces and , with and .
The algorithm first attempts with , and if unsuccessful, retries with . Since at least one of contains a failure, the packet is guaranteed to reach the rightmost node of either or to exit , thereby resuming ear-based routing on some with to finally reach . Note that need not coincide with for .
Lemma 14.
If every ear in contains at most one failure in , then Algorithm 1 routes a packet to the destination under two dynamic failures by only traversing along ears.
Proof.
In Algorithm 1, when a packet begins at an internal node in an (including the initial) ear , it is first routed along the left direction of . Upon encountering a failure, the traversal switches to the right direction . If each ear satisfies , then one of the two routings, i.e., or , always leads to an endpoint of . From there, the packet proceeds into an earlier ear with , and ultimately reaches to arrive at . Since ear indices strictly decrease, no ear is revisited, and thus routing loops cannot occur.
By Lemma 15, if two failures are only shared by distinct faces , then this scenario can be excluded from the resilient routing design, as the node, where a packet is currently staying, and destination lie in separate connected components of .
Lemma 15.
Let be a -edge-connected plane graph with face set . If two distinct faces share two distinct edges , i.e., , then is disconnected.
Proof.
Consider the plane dual graph of , where each vertex corresponds to a face of , and each edge shared by two faces corresponds to an edge . Note that may contain multi-edges even if is simple. Since are common to and , their duals are parallel edges between and ; thus, forms a simple cycle of length two in .
Proof.
By Lemma 14, we may assume that both failures lie on the same ear , and that the packet is currently located at a node between and on ; otherwise, can be reached solely via ear-based routing.
Let be the second failure, with . By Lemma 11, there exist two distinct faces (with one possibly being the outer face), such that and . By Lemma 15, at least one of contains only but not .
We first traverse starting at due to . If no further failure occurs, then by Lemma 13, we reach the rightmost node of , closer to the right endpoint of than along . Note that the directed subpath of from cannot include either or by Definition 12. From , either routing continues along to reach the endpoint of , or is already an internal node of an ear with , from which is reachable by ear-based routing alone. Note that may not be .
If instead traversal of encounters , switching back to ear-based routing either leads to the endpoint of along or to revisiting along . In this case, face-based routing resumes via (since and ), eventually reaching the rightmost of . Although may differ from , the directed subpath of from onward avoids both and . From , the above ear-based procedure applies.
4.3.2 Improved -Resilient Routing Algorithm by Rewriting One Bit
After presenting the -bit rewriting approach, we refine the analysis of structural properties of the plane embedding and reduce the rewriting requirement from two bits to one. This is achieved by traversing all faces exclusively in the rightward direction, i.e., only along .
The key idea of -bit rewriting is as follows: upon hitting a second failed arc ( is the current ear), routing switches to with . If , packet halts at and resumes along to leave . Otherwise, revisiting the first failed arc (also in ), rerouting proceeds via with and .
In this case, packet halts at and continues along to exit . Lemma 17 states that all arcs of belonging to a common ear are oriented consistently, either entirely as or entirely as . This property is used to prove the correctness of detour termination in Algorithm 3. The proof of Lemma 17 is deferred to Appendix B.
Lemma 17.
Given , for each face and an ear with , there cannot exist arcs such that with and . Hence, must be consistent with either or if .
Next, we introduce a -resilient basic routing scheme with one-bit rewriting for plane graphs (Algorithms 1 and 3) and establish its correctness in Theorem 18.
Theorem 18.
Proof.
It remains to consider the case where a packet gets stuck on an ear containing two failures, where first hitting and then encountering .
Let with associated ear and . Then is consistent with (Lemma 17), while its consistency with depends on whether .
If contains only one failure, we will show a traversal along from terminates at either the rightmost node , the leftmost node , or an endpoint of (Algorithm 3, Lines 1–3;), from which ear-based routing resumes to reach . By Lemma 13, all nodes of are eventually visited. If the current node is an endpoint of , the traversal along terminates and routing leaves through this endpoint. We now assume ; otherwise, is itself an endpoint of (Definition 12).
If , then is consistent with . In this case, we can show the traversal must halt at the rightmost node (not at ). Let be the arc preceding along (we may have with ). Suppose . Then, by and Lemma 17, it follows that . By Definition 10, this would imply , contradicting that is the rightmost node of . Hence, it implies and the traversal along halts at . To show that the traversal cannot halt at , assume there exists an arc . If , then by Lemma 17, we have . By Definition 12, must have a neighbor with and . This implies is visited after along , contradicting that is the leftmost node. Hence, implies , indicating that the traversal cannot stop at . Consequently, from the ear-based traversal along leaves without further failures and finally reaches .
If , then can be consistent with either or . Starting at , if consistent with (resp., ), the traversal along stops at (resp., ) since the incoming link (arc) (resp., ). As contains no failure (), the ear-based routing from (resp., ) along (resp., ) always leaves and continue traversing on the ears with to reach .
If there are two failures on , upon hitting (stopping at ), by Lemma 17, we know and since is consistent with . In this case there exists a face with associated ear such that (By Lemma 15, only one failure on ), because is consistent with . If , then traversing from halts at either an endpoint of or at . Then, following from (resp., the endpoint of ) by ear-based routing can leave to eventually reach . However, if , we can argue similarly as above, since no failures on .
Complexity Analysis.
We compute the routing rules of Algorithm 1 in a centralized model. The one- and two-bit rewriting approaches have identical time costs. For a graph with nodes and edges, a planar embedding can be computed in [2, 20], an ear-decomposition in [26], and ear-/face-based routing rules in . In the worst case, recomputing ear-decompositions per destination yields total time. By comparison, source-matched routing [8] needs per source–destination pair, i.e., at least times slower. Memory usage is reduced from tables (source–destination) to only (per destination). Moreover, our reliance on ear-decomposition and planar embeddings – well studied in parallel and distributed computing – underscores the practical feasibility of our routing schemes.
5 Conclusions and Future Work
In this paper, we investigated the resilience achievable by basic routing augmented with packet-header rewriting under dynamic failures. We proved that resilience without any rewriting is impossible in planar graphs, and that, in general graphs, the perfect -resilience is unfeasible by only rewriting bits. For planar graphs, we presented tight -resilient basic routing algorithms that require rewriting only one or two bits. Future work includes designing -resilient basic routing algorithms for general graphs with limited bit rewriting.
References
- [1] Mohammad Alizadeh et al. Data center TCP (DCTCP). In SIGCOMM. ACM, 2010. doi:10.1145/1851182.1851192.
- [2] John Boyer and Wendy Myrvold. On the cutting edge: Simplified o(n) planarity by edge addition. Journal of Graph Algorithms and Applications, 8(3):241–273, January 2004. doi:10.7155/jgaa.00091.
- [3] Marco Chiesa et al. On the resiliency of randomized routing against multiple edge failures. In ICALP, 2016. doi:10.4230/LIPIcs.ICALP.2016.134.
- [4] Marco Chiesa et al. The quest for resilient (static) forwarding tables. In INFOCOM. IEEE, 2016. doi:10.1109/INFOCOM.2016.7524552.
- [5] Marco Chiesa et al. On the resiliency of static forwarding tables. IEEE/ACM Trans. Netw., 25(2):1133–1146, 2017. doi:10.1109/TNET.2016.2619398.
- [6] Marco Chiesa et al. Fast reroute on programmable switches. IEEE/ACM Trans. Netw., 29(2):637–650, 2021. doi:10.1109/TNET.2020.3045293.
- [7] Marco Chiesa et al. A survey of fast-recovery mechanisms in packet-switched networks. IEEE Commun. Surv. Tutorials, 23(2):1253–1301, 2021. doi:10.1109/COMST.2021.3063980.
- [8] Wenkai Dai et al. A tight characterization of fast failover routing: Resiliency to two link failures is possible. In SPAA, pages 153–163. ACM, 2023. doi:10.1145/3558481.3591080.
- [9] Wenkai Dai et al. On the resilience of fast failover routing against dynamic link failures, 2024. doi:10.48550/arXiv.2410.02021.
- [10] Wenkai Dai et al. On the resilience of fast failover routing against dynamic link failures. In IFIP Networking, 2025.
- [11] Fabien de Montgolfier et al. Treewidth and hyperbolicity of the internet. In NCA, pages 25–32. IEEE Computer Society, 2011. doi:10.1109/NCA.2011.11.
- [12] Reinhard Diestel. Graph Theory, 4th Edition, volume 173 of Graduate texts in mathematics. Springer, 2012.
- [13] Joan Feigenbaum et al. Brief announcement: On the resilience of routing tables. In PODC. ACM, 2012. doi:10.1145/2332432.2332478.
- [14] Klaus-Tycho Foerster et al. CASA: congestion and stretch aware static fast rerouting. In INFOCOM. IEEE, 2019. doi:10.1109/INFOCOM.2019.8737438.
- [15] Klaus-Tycho Foerster et al. Brief announcement: What can(not) be perfectly rerouted locally. In DISC, pages 46:1–46:3, 2020. doi:10.4230/LIPIcs.DISC.2020.46.
- [16] Klaus-Tycho Foerster et al. Grafting arborescences for extra resilience of fast rerouting schemes. In INFOCOM, pages 1–10. IEEE, 2021. doi:10.1109/INFOCOM42981.2021.9488782.
- [17] Klaus-Tycho Foerster et al. On the feasibility of perfect resilience with local fast failover. In Symposium on Algorithmic Principles of Computer Systems (APOCS), 2021. doi:10.1137/1.9781611976489.5.
- [18] Phillipa Gill et al. Understanding network failures in data centers: measurement, analysis, and implications. In SIGCOMM. ACM, 2011. doi:10.1145/2018436.2018477.
- [19] S. Hannenhalli et al. A distributed algorithm for ear decomposition. In Proceedings of ICCI’93: 5th International Conference on Computing and Information, pages 180–184, 1993. doi:10.1109/ICCI.1993.315382.
- [20] John Hopcroft and Robert Tarjan. Efficient planarity testing. J. ACM, 21(4):549–568, October 1974. doi:10.1145/321850.321852.
- [21] Louis Ibarra and Dana Richards. Efficient parallel graph algorithms based on open ear decomposition. Parallel Computing, 19(8):873–886, 1993. doi:10.1016/0167-8191(93)90071-R.
- [22] Junda Liu et al. Ensuring connectivity via data plane mechanisms. In NSDI, 2013. URL: https://www.usenix.org/conference/nsdi13/technical-sessions/presentation/liu_junda.
- [23] L. Lovasz. Computing ears and branchings in parallel. In 26th Annual Symposium on Foundations of Computer Science (sfcs 1985), pages 464–467, 1985. doi:10.1109/SFCS.1985.16.
- [24] Athina Markopoulou et al. Characterization of failures in an operational ip backbone network. IEEE/ACM transactions on Networking, 16(4):749–762, 2008. doi:10.1145/1453698.1453699.
- [25] H. E. Robbins. A theorem on graphs, with an application to a problem of traffic control. The American Mathematical Monthly, 46(5):281–283, 1939. doi:10.2307/2303897.
- [26] Jens M. Schmidt. A simple test on 2-vertex- and 2-edge-connectivity. Information Processing Letters, 113(7):241–244, 2013. doi:10.1016/j.ipl.2013.01.016.
- [27] Aman Shaikh et al. A case study of ospf behavior in a large enterprise network. In Proceedings of the 2nd ACM SIGCOMM Workshop on Internet Measurment, IMW ’02, pages 217–230. ACM, 2002. doi:10.1145/637201.637236.
- [28] Y. H. Tsin. On finding an ear decomposition of an undirected graph distributively. Information Processing Letters, 91(3):147–153, 2004. doi:10.1016/j.ipl.2004.04.004.
- [29] Daniel Turner et al. California fault lines: understanding the causes and impact of network failures. In SIGCOMM. ACM, 2010. doi:10.1145/1851182.1851220.
- [30] Balajee Vamanan et al. Deadline-aware datacenter tcp (D2TCP). In SIGCOMM. ACM, 2012. doi:10.1145/2342356.2342388.
- [31] Erik van den Akker and Klaus-Tycho Foerster. Short paper: Towards 2-resilient local failover in destination-based routing. In ALGOCLOUD. Springer, 2024. doi:10.1007/978-3-031-94677-6_2.
- [32] David Watson et al. Experiences with monitoring ospf on a regional service provider network. In Proceedings of the 23rd International Conference on Distributed Computing Systems, ICDCS ’03, page 204, USA, 2003. IEEE Computer Society. doi:10.1109/ICDCS.2003.1203467.
- [33] Douglas B. West. Introduction to Graph Theory. Prentice Hall, 2 edition, September 2000.
- [34] Baohua Yang et al. Keep forwarding: Towards k-link failure resilient routing. In INFOCOM. IEEE, 2014. doi:10.1109/INFOCOM.2014.6848098.
- [35] David Zats et al. Detail: reducing the flow completion time tail in datacenter networks. In SIGCOMM. ACM, 2012. doi:10.1145/2342356.2342390.
Appendix A Deferred Proofs of Theorems and Lemmas in Section 3
We restate the theorems and lemmas before the proofs for ease of readability. See 3
Proof of Theorem 3.
We first assume that a -resilient source-matched forwarding scheme exists in the graph as shown in Fig. 3. Then, for contradiction, we show that a packet originated at cannot be routed to the destination anymore, but is forwarded in a loop when there are two dynamic failures in , even if there exists an path in the graph .
Let and . For each node , we define a forwarding function at , where denotes a subset of dynamic failures that incidents on and the source-destination is used implicitly in this proof. Clearly, the induced graphs and are symmetric. By symmetry, when , an arbitrary node in can be chosen as the outgoing port for the packet originated at . W.l.o.g., we assume that is chosen, i.e., for .
Let dynamic failures be a set of arbitrary links, s.t., and can be empty. Next, we claim that, given with , for each node , its routing function must be link-circular even when are static failures. If has , then , where and denotes its unique neighbor in , otherwise packets get stuck at . This case can be thought as a special case of the link-circular forwarding. If has , i.e., and , a non-link-circular forwarding function at must imply and , where are neighbors of in . However, a non-link-circular forwarding function cannot be -resilient if the only path remained in has to go through the link . For example, when and , if a non-link-circular forwarding function has and , then a packet starting at cannot approach anymore even if is connected via . A similar argument can be established if and , and . Moreover, for each having , a non-link-circular forwarding function at must imply for , which can make become a dead-end node, i.e., a packet cannot traverse from one neighbor of to the other neighbor to approach anymore. Therefore, each must have a link-circular forwarding function.
If has , then its link-circular forwarding function is unique, i.e., from one neighbor to the other neighbor. If has , where , then there are two possible circular orderings for its neighbors , i.e., one clockwise and the other counter-clockwise based on their geometric locations in Fig. 3. For example, at , the clockwise ordering of is and the counter-clockwise ordering of is . Thus, for each that has , its link-circular forwarding function can choose one of two options: clockwise and counter-clockwise, arbitrarily.
Fixing , let (resp., ) be a dynamic failure in if and both have the clockwise (resp., counter-clockwise) of link-circular forwarding functions. In this case, even if are connected in , a packet originated at will enter a forwarding loop: (resp., ), where the dynamic failure (resp., ) is down only for the first hitting but always up since then, but never traverses the link to arrive at . When and have the different type, by fixing , even if there is no dynamic failure in , a forwarding loop: occurs if and take forwarding functions of clockwise and counter-clockwise orderings respectively, otherwise another forwarding loop: exists. Moreover, a similar discussion can be applied when for .
Thus, no -resilient source-matched forwarding scheme against dynamic failures for exists in Fig. 3.
Theorem 4. [Restated, see original statement.]
There exists graphs for which any resilient source-matched routing that can tolerate dynamic failures needs rewriting of at least bits in packet headers for .
Proof of Theorem 4.
We prove Theorem 4 by induction on . Theorem 3 implies that there is a graph as shown in Fig. 3, where any -resilient source-matched routing for needs rewriting at least one bit, proving the initial case of . We assume that there is a general graph , where a -resilient source-matched routing against dynamic failures for a source-destination pair (resp., ) with needs rewriting at least bits.
Now, as illustrated in Fig. 5, we can construct another graph by replacing each edge in with a graph , where is isomorphic to , i.e., and , and nodes . We note that we use and (resp., and ) interchangeably in this proof.
Next, we claim that any -resilient source-matched routing for in needs rewriting at least bits. Let be any dynamic failures in , where for has and has .
In the graph as shown in Fig. 3, we always assume for . Let denote two dynamic failures in . For example, when and , the packet starting at meets the first failure , and it has to go through back to since failed. Clearly, one bit in the packet header must be rewritten to inform whether the packet has already visited , s.t., can decide forwarding it to or provided that is recovered. Similarly, for in , we set and , we still need one bit at to indicate whether the packet has already visited . Still, to go through to arrive at , we need rewriting of additional bits under failures . Thus, we need rewriting bits for dynamic failures in . For other failure cases in , we can similarly map them to scenarios in .
Appendix B Deferred Proofs of Theorems and Lemmas in Section 4
We restate the theorems and lemmas before the proofs for ease of readability. See 17
Proof.
We assume that there is a face and an ear such that , s.t., there are two distinct arcs that satisfies , and , and then we prove the theorem by a contradiction.
For a plane graph , removing any edge preserves planarity [33, 12]. Let denote the plane subgraph after inserting the ear . By the definition of ear-decomposition, only the endpoints of lie in , so adding is equivalent to inserting an edge into (this edge can be a self-loop on the endpoint of if is a closed ear). Moreover, after inserting , the graph is -edge-connected, and by Lemma 6, at least one new face is created in compared to .
Since both and are plane, adding (treated as an edge) can only split a face of (including outer face) into two faces in , otherwise, would not be plane. It implies that the region of any face of must be only contained in a face of .
Consider with an edge that satisfies . Hence, must divide some face of into two faces , sharing as common boundary. Right-routing along and induces the directed paths and , respectively. As further ears are added, faces and may be further subdivided.
Now suppose there exist arcs with , where , and . Then the region of (unbounded if ) would intersect both regions of and in , contradicting the planarity of .
Hence, must be consistent with either or . Specifically, if , then either or , where , (resp., ) implies the common arcs of and (resp., ).
