| M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, M. Handley, and J. Crowcroft, "The use of forward error correction (FEC) in reliable multicast," RFC 3453, December 2002. |
....has become more popular, the uses of erasure correcting codes have broadened. Rizzo employs them to avoid retransmission in point to point [20] and multicast [21] communication protocols. This work has resulted in standardization efforts for such codes in multicast scenarios from the IETF [15, 16]. Additional uses of Reed Solomon codes have been in cryptography [8] distributed data structures [10] energy efficient wireless communication [7] and distributed checkpointing [18] The advent of wide area and peer to peer storage systems has further motivated the need for erasure correcting ....
M. Luby, L. Vicisano, J. Gemmell, L. Rizo, M. Handley, and J. Crowcroft. The use of forward error correction (FEC) in reliable multicast. IETF RFC 3453 (http://www.ietf.org/rfc/rfc3453.txt),December 2002.
....no feedback information from the receivers in that case. The principal motivation for this work is our Multicast Library (MCLv3) 17] which implements the ALC protocol family and provides an integrated solution for the reliable and highly scalable multicast delivery of bulk data. Previous work [1, 9] and the experienced gained with MCLv3 [19, 18] have highlighted the importance of the two parameters (k, n) in the global e#ciency achievable at application level: a large n k ratio is beneficial because it reduces the probability of packet duplication at a receiver. Indeed, since the same ....
.... of new FEC codes and how they can be used to create a reliable multicast protocol (which lead to the design of the ALC [6] protocol family) This code, Tornado Z, has performances that are several orders of magnitude higher than that of Reed Solomon FEC codes, but this is a proprietary code (see [9] for the list of patents) In fact Tornado belongs to the same category as LDPC: codes on graphs, that have been introduced in the 1960 s by Gallager [2] 9] introduces expandable codes, that can produce an infinite number of parity packets (n 1) while operating on large blocks. Yet very ....
[Article contains additional citation context not shown here]
M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, M. Handley, and J. Crowcroft. The use of Forward Error Correction (FEC) in reliable multicast, Dec. 2002. IETF Request for Comments, RFC3453.
.... on the base layer experience no losses, because such losses usually trigger an important distortion in the reconstructed video (inter layer dependencies) One solution to provide this transmission discrepancy is to protect data sent on the base layer with FEC (Forward Error Correction) techniques [13]. Another solution is to rely on a QoS di erentiation mechanism within the network (Int Serv or Di Serv) and to a ect packets of the base layer to a prioritized service [2] 22] The major practical limitation of this approach is the requirement to have a QoS service deployed between the source ....
....scalable in terms of number of receivers. ALC is well suited to the transmission of popular content in an on demand mode, where clients join an ALC session, retrieve data, and leave at their own discretion. This is made possible by the large use of FEC (Forward Error Correction) encoding [13], and by the transmission of all the packets (data and FEC) in a random order and continuously on the various ALC layers [5] 20] This on demand mode is very speci c to ALC and other reliable multicast approaches (e.g. NORM and TRACK) are limited to a push synchronous model where all clients ....
[Article contains additional citation context not shown here]
M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, M. Handley, and J. Crowcroft. The use of Forward Error Correction (FEC) in reliable multicast, Dec. 2002. Request for Comments 3453.
....scalable in terms of number of receivers. ALC is well suited to the transmission of popular content in an on demand mode, where clients join an ALC session, recover data, and leave the session at their own discretion. This is made possible by the use of FEC (Forward Error Correction) encoding [4], and by the transmission of all the packets, data of FEC, in a random order and continuously on the various ALC layers. This on demand mode is very specific to ALC and other reliable multicast approaches (e.g. NORM and TRACK) are limited to a push synchronous transmission model where all ....
M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, M. Handley, and J. Crowcroft. The use of Forward Error Correction (FEC) in reliable multicast, Feb. 2002. Work in Progress: <draft-ietf-rmt-info-fec-02.txt>.
.... add n k FEC encoded redundant symbols total of n symbols (or packets) sent mReceiver: as soon as it receives any k symbols out of the n, it reconstructs the original k symbols k = 5 n = 7 original data reconstructed source receiver network FEC classification l several FEC codes exist [FECinfo02] msmall block FEC codes mlarge block FEC codes mexpandable FEC codes mother codes exist but are meither lossy codes (ok for video audio transmission) mor dedicated to low level bit stream transmissions over noisy channels (i.e. modify the bit stream rather than erasing packets) mnot for ....
M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, M. Handley, J. Crowcroft, The use of Forward Error Correction (FEC) in Reliable Multicast", RMT Working Group, draft-ietf-rmt-info-fec-02.txt, February 2002. l NORM documents reliable multicast protocol (NORM)", RMT Working Group, draft-ietf-rmt-pinorm -04.txt, March 2002.
No context found.
M. Luby,L.Vicisano, J. Gemmell, L. Rizzo, M. Handley,and J. Crowcroft, "The Use of ForwardError Correction (FEC) in Reliable Multicast", RFC 3453, December 2002.
No context found.
M. Luby,L.Vicisano, J. Gemmell, L. Rizzo, M. Handley,and J. Crowcroft, "The Use of ForwardError Correction (FEC) in Reliable Multicast", RFC 3453, December 2002.
No context found.
Luby, M., Vicisano, L., Gemmell, J., Rizzo, L., Handley, M. and J. Crowcroft, "The Use of Forward Error Correction (FEC) in Reliable Multicast", RFC 3453, December 2002.
No context found.
Luby, M., Vicisano, L., Gemmell, J., Rizzo, L., Handley, M. and J. Crowcroft, "The Use of Forward Error Correction (FEC) in Reliable Multicast", RFC 3453, December 2002.
No context found.
Luby, M., Vicisano, L., Gemmell, J., Rizzo, L., Handley, M. and J. Crowcroft, "The Use of Forward Error Correction (FEC) in Reliable Multicast", RFC 3453, December 2002.
No context found.
Luby, M., Vicisano, L., Gemmell, J., Rizzo, L., Handley, M. and J. Crowcroft, "The Use of Forward Error Correction (FEC) in Reliable Multicast", RFC 3453, December 2002.
No context found.
Luby, M., Vicisano, L., Gemmell, J., Rizzo, L., Handley, M. and J. Crowcroft, "The Use of Forward Error Correction (FEC) in Reliable Multicast", RFC 3453, December 2002.
No context found.
M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, M. Handley, and J. Crowcroft, "The use of forward error correction (FEC) in reliable multicast," RFC 3453, December 2002.
No context found.
Luby, M., Vicisano, L., Gemmell, J., Rizzo, L., Handley, M. and J. Crowcroft, "The Use of Forward Error Correction (FEC) in Reliable Multicast", RFC 3453, December 2002.
No context found.
M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, M. Handley, and J. Crowcroft, The use of Forward Error Correction (FEC) in reliable multicast, Dec. 2002, Request for Comments 3453.
No context found.
Luby, M., Vicisano, L., Gemmell, J., Rizzo, M., Handley, M. and J. Crowcroft, "The Use of Forward Error Correction (FEC) in Reliable Multicast", RFC 3453, December 2002.
No context found.
M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, M. Handley, and J. Crowcroft. The use of Forward Error Correction (FEC) in reliable multicast, Dec. 2002. IETF Request for Comments, RFC3453.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC