Copyright © 2005 Elsevier B.V. All rights reserved.
End-host controlled multicast routing
Available online 7 September 2005.
References and further reading may be available for this article. To view references and further reading you must purchase this article.
Abstract
The last decade has seen a deluge of proposals for supporting multicast in the Internet. These proposals can be categorized as either infrastructure-based, with the multicast functionality provided by specialized network nodes, or host-based, with the multicast functionality provided by the members of the multicast group itself. In this paper, we present the design and evaluation of a hybrid multicast architecture wherein the infrastructure provides packet forwarding, and the end-hosts implement the control plane. End-hosts build multicast trees by setting up forwarding state in the infrastructure. This division of functionality enables our architecture to combine the efficiency of infrastructure-based solutions and the flexibility and deployability of host-based solutions. We present scalable and efficient algorithms for distributed tree construction and maintenance, and for reliable packet delivery. We have implemented the algorithms using i3 as the forwarding infrastructure. We evaluate our techniques using a combination of event-driven packet-level simulations, and our implementation over the PlanetLab testbed.
Keywords: Multicast; Routing; Architecture; End-host control; Overlay
Article Outline
- 1. Introduction
- 2. Infrastructure support
- 2.1. Overview
- 2.1.1. Packet forwarding and replication
- 2.1.2. Trigger chains
- 2.1.3. Anycast
- 3. Scalable tree construction and maintenance
- 3.1. Basic tree building algorithm
- 3.2. Infrastructure-based realization of the tree construction algorithm
- 3.2.1. Distance computation
- 3.2.2. Discussion
- 4. Scalable tree maintenance
- 5. Reliable packet delivery
- 6. Simulations
- 6.1. Tree construction
- 6.2. Scalable trigger refreshing
- 6.3. Reliability
- 7. Implementation
- 8. Related work
- 9. Discussion
- 10. Conclusion
- References






E-mail Article
Add to my Quick Links

Cited By in Scopus (1)






ids denotes an ID of size m, where idp represents the prefix of the k most significant bits, and ids the suffix of the m − k least significant bits. (c) Trigger chains: Replace the receiver address in the second field of a trigger with another trigger ID.