Feedback-free multicast prefix protocols

Y. Bartal, J. W. Byers, M. Luby, D. Raz

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

13 Scopus citations

Abstract

Developing scalable, reliable multicast protocols for lossy networks presents an array of challenges. In this work we focus on scheduling policies which determine what data the sender places into each sent packet. Our objective is to develop scalable policies which provably deliver a long intact prefix of the message to each receiver at each point in time during the transmission. To accurately represent conditions in existing networks, our theoretical model of the network allows bursty periods of packet loss which can vary widely and arbitrarily over time. Under this general model, we give a proof that there is an inherent performance gap between algorithms which use encoding schemes such as forward error correction (FEC) and those which do not. We then present simple, feedback-free policies which employ FEC and have guaranteed worst-case performance. Our analytic results are complemented by trace-driven simulations which demonstrate the effectiveness of our approach in practice.

Original languageEnglish
Title of host publicationProceedings - 3rd IEEE Symposium on Computers and Communications, ISCC 1998
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages135-141
Number of pages7
ISBN (Print)0818685387, 9780818685385
DOIs
StatePublished - 1998
Externally publishedYes
Event3rd IEEE Symposium on Computers and Communications, ISCC 1998 - Athens, Greece
Duration: 30 Jun 19982 Jul 1998

Publication series

NameProceedings - 3rd IEEE Symposium on Computers and Communications, ISCC 1998

Conference

Conference3rd IEEE Symposium on Computers and Communications, ISCC 1998
Country/TerritoryGreece
CityAthens
Period30/06/982/07/98

Bibliographical note

Publisher Copyright:
© 1998 IEEE.

Fingerprint

Dive into the research topics of 'Feedback-free multicast prefix protocols'. Together they form a unique fingerprint.

Cite this