Download paper

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Network tap wikipedia , lookup

Airborne Networking wikipedia , lookup

Peering wikipedia , lookup

CAN bus wikipedia , lookup

Backpressure routing wikipedia , lookup

Deep packet inspection wikipedia , lookup

Recursive InterNetwork Architecture (RINA) wikipedia , lookup

Passive optical network wikipedia , lookup

IEEE 1355 wikipedia , lookup

IEEE 802.1aq wikipedia , lookup

Dijkstra's algorithm wikipedia , lookup

Routing wikipedia , lookup

Routing in delay-tolerant networking wikipedia , lookup

Transcript
FCl.4
9:45am-lO:OOam
Robust Routing for Local Area Optical Access Networks
Muriel Mtdard, LIDS, Massachusetts Institute of Technology
Room 35-212,77 MassachusettsAvenue, Cambridge,MA 02139, [email protected]
Steven S. Lumetta, CSRL,, University of Illinois at Urbana-Champaign
1308 West Main St., Urbana, IL 61801, [email protected]
One approach to providing the benefits of the high data rates afforded by optics is to attempt to implement traditional electronic and electro-optic approaches using optical technologies. In electronics, operations such as buffering, adding packets and dropping packets, or merging packet streams, are done with
ease. In optics, however, buffering is onerous. Operations such as retrieving a packet from a traffic stream
affect the whole stream. The routing approach we propose seeks to make use of the strengths of optics and
avoids operations that are cumbersome or expensive in optics. Our goal is to provide robust and reliable
approaches to access at optical data rates. Our design rationale is the following:
Avoid buffering. Buffering in the network, with the attendant issues of cost and possibility of overflow,
is to be avoided. Therefore, we avoid traffic merging. Traffic splitting, on the other hand, does not require
buffering.
Do not use a switch unless necessary. While traffic to remote locations should be handled by such
switches, local traffic need not be handled by these switches. It is desirable to isolate local traffic from the
vagaries of congestion associated with extemal traffic. Finally, switches are expensive and extensibility is
often difficult. Thus, allowing traffic that does not need to be routed through switches to bypass switches
avoids unnecessary costs and disruptions caused by switch upgrades.
Use the optical layer to provide recovery. Our routing is well suited to packet-switched traffic, but
does not rely on a specific protocol such as IP or ATM. Instead, our access scheme operates below such
protocols. Recovery is performed at the optical layer, in a manner which is robust, simple and rapid enough
that recovery at higher layers does not need to be triggered.
We consider routings that allow automatic recovery from link failures. An undirected graph G = ( N ,E )
is a set of nodes N and edges E. With each edge [z,y] of an undirected graph, we associate two directed
arcs (z,y) and (y, z), Each arc corresponds to one of the fibers forming the link. We assume that if an edge
[z, y] fails, then arcs (z,y) and (y, z) fail. Assume that the graph G is two edge-connected, i.e.,removal of
an edge leaves the graph connected, which is necessary to make recovery from link failures feasible.
We describe a routing such that recovery is possible even in the event of any link failure. Our routing
consists of two parts: a ‘‘collection’’ portion and a “distribution” portion. The collection portion allows
all nodes to place their traffic on the access wavelength(s) and the distribution portion ensures that packets
can reach all nodes. The architecture we consider is the following: nodes place traffic on a shared optical
medium (we consider a single wavelength onto which traffic is written and a single wavelength off of which
traffic is read). Traffic that needs to be sent to or received from outside the local area can go through a
switch, which acts as any other node, placing traffic onto the collection wavelength and retrieving traffic off
the collection wavelength. Local traffic need not be handled by the switch.
The collection portion of the routing is constructed as follows. We select a root node and build a depthfirst search (DFS) numbering beginning at the root node. The routing is a walk that traverses nodes as they
are considered by the DFS numbering algorithm. A collection routing traverses every node at least once.
Moreover, it traverses each edge at most twice. If an edge is traversed twice, it is in opposite directions at
each time. Thus, each arc is traversed at most once and so a single wavelength, in both directions, is sufficient
to establish the collection portion of the routing. The solid lines in Figure 1 show a DFS construction on a
sample network.
0-7803-6252-7/00/$10.0002000IEEE
39
Figure 1: Example DFS tree and labeling. The graph shown is the NJ LATA network. An expanded version of node 7 is labeled
with ancestor (A), descendant (D), and tree (T) markings. Link styles indicate their use in the access collection recovery protocol.
The distribution portion of the routing is a directed spanning tree rooted at the last node traversed by
the collection routing. Call this tree the primary tree. Robustness is afforded in the distribution section by
constructing a secondary tree, which shares the root but no arcs with the primary tree, and such that removal
of any edge (and its two associated arcs) leaves the root connected to every node on at least one of the
trees. Such trees were first introduced in [l, 41, using s-t numberings ([2]), and a more general method of
constructing them was given in [3]. A single wavelength, used in both directions, is sufficient to construct
the primary and secondary trees. The roots of the primary and secondary tree must therefore be able to
perform wavelength conversion, by placing the traffic from the collection routing onto the distribution trees.
We only require two nodes to perform wavelength conversion.
Our algorithm performs recovery separately both in the collection and the distribution portions of the
routing, even though they co-exist over a common physical infrastructure. The crux of our algorithm lies
in our method of performing link recovery in the collection portion of the routing. Suppose that link [i,j ]
fails. If link [i,j ] is not included in the DFS tree, then its failure leaves the collection routing unaffected.
We therefore need only consider the case where link [i,j ] is included in the DFS tree. Assume wlog that the
node i is the ancestor of j . Failure of [i, j ] entails disconnection of all the descendants of i. From the DFS
construction and the fact that that we have a two-edge-connected graph, some descendant of j must have an
edge connecting it to some ancestor of i. We have developed a distributed algorithm that uniquely selects
one such link and uses it to reconnect j and its descendants to the upper partition of the collection route. For
the distribution portion, each node downstream of a link failure in the primary tree switches to receiving on
the secondary tree.
We have extended this approach to node failures and have developed an algorithm for implementing this
routing and the associated recovery.
References
[ 11 A. Itai, M. Rodeh, “The Multi-Tree Approach to Reliability in Distributed Networks,” Information and Computation, Vol. 79, 1988, pp. 43-59.
[2] A. Lempel, S. Even, I. Cederbaum, “An Algorithm for Planarity Testing of Graphs,” in Theory of Graphs,
International Symposium, July 1966, pp. 21 5-232.
[3] M. Midard, S. G. Finn, R. A. Bany, R. G . Gallager, “Redundant Trees for Preplanned Recovery in Arbitrary
Vertex-Redundant or Edge-Redundant Graphs,” in IEEEIACM Transactions on Networking, 1999.
[4] A. Zehavi, A. Itai, “Three Tree-Paths,” JournalofGraph Theory,vol. 13, no. 2,1989, pp. 175-188.
40