ACM Home Page
Please provide us with feedback. Feedback
Pitfalls in the design of distributed routing algorithms
Full text PdfPdf (1.15 MB)
Source Applications, Technologies, Architectures, and Protocols for Computer Communication archive
Symposium proceedings on Communications architectures and protocols table of contents
Stanford, California, United States
Pages: 43 - 54  
Year of Publication: 1988
ISBN:0-89791-279-9
Also published in ...
Authors
R. Perlman  Digital Equipment Corp., Littleton, MA
G. Varghese  Digital Equipment Corp., Littleton, MA
Sponsors
SIGCOMM: ACM Special Interest Group on Data Communication
SRI Intl :
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 5,   Downloads (12 Months): 30,   Citation Count: 7
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/52324.52330
What is a DOI?

ABSTRACT

The bridge algorithm adopted by the IEEE 802.1 committee for interconnecting 802 LANs requires the topology of the Extended LAN to be a Spanning Tree. A distributed algorithm to compute a spanning tree dynamically has already been published [1], and adopted by the IEEE 802.1 committee [2]. In this paper, however, we describe an alternative distributed algorithm to compute a spanning tree. This algorithm, variants of which have been implemented, initially appears simpler than the IEEE 802.1 algorithm; we show, however, that it has subtle failure modes that makes it unattractive in practice. We also show that some failure modes of the Spanning Tree Algorithm introduced in this paper are characteristic of a broader class of distributed graph algorithms. Such algorithms potentially examine all possible path combinations between a source and destination in a graph. Thus, they suffer from exponential message overhead in topologies that have an exponential number of paths between source and destination. Attempts to fix this problem lead to extra complexity (in terms of CPU, bandwidth, memory) when compared to other algorithms. We briefly describe a second example belonging to this class, and propose that designers avoid such algorithms if restricting the topology or scale of the network is unacceptable.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
"MAC Bridges,~ Draft IEEE Standard 802.1: Part D Rev C, IEEE 802.1 Document Number iEEE-802.87 1.563, Aug 1987.
 
3
F. Backes, "Transparent Bridges for Interconnection of IEEE 802 LANS,' IEEE Network, vol 2, No. 1, January 1988.
 
4
D.A. Pitt, "Source Routing for Bridged LANs,' IEEE Network, vol 2, No. 1, January 1988.
 
5
D.R. Boggs, J.F.Shoch, E.A. Taft, and R.M. Metcalfe, "PUP: An Internetwork Architecture," IEEE Transactions on Communications, April 1980.
6
7
 
8
N. Strole, ~A Local Communications Network Based on Interconnected Token-Access Rings: A Tutorial," IBM J. Res. Develop, Vol 27, No 5, Sept., 1983.
9
 
10
 
11
J.M. McQuillan, I. Richer, E.C. Rosen, ~The New Routing Algorithm for the Arpanetf IEEE Transactions on Communications, vol com-28, no. 5, May 1980.
 
12
M. Soha and R. Perlman, ~Comparison of two LAN Bridge Approaches~~ IEEE Network, vol 2, No. 1, January 1988.