idnits 2.17.1 draft-ietf-rmt-info-fec-03.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3453 5 Title: The Use of Forward Error Correction in Reliable 6 Multicast 7 Author(s): M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, 8 M. Handley, J. Crowcroft 9 Status: Informational 10 Date: December 2002 11 Mailbox: luby@digitalfountain.com, lorenzo@cisco.com, 12 jgemmell@microsoft.com, luigi@iet.unipi.it, 13 mjh@aciri.org, Jon.Crowcroft@cl.cam.ac.uk 14 Pages: 18 15 Characters: 46853 16 Updates/Obsoletes/See Also: None 18 I-D Tag: draft-ietf-rmt-info-fec-03.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3453.txt 22 This memo describes the use of Forward Error Correction (FEC) codes to 23 efficiently provide and/or augment reliability for one-to-many 24 reliable data transport using IP multicast. One of the key properties 25 of FEC codes in this context is the ability to use the same packets 26 containing FEC data to simultaneously repair different packet loss 27 patterns at multiple receivers. Different classes of FEC codes and 28 some of their basic properties are described and terminology relevant 29 to implementing FEC in a reliable multicast protocol is introduced. 30 Examples are provided of possible abstract formats for packets 31 carrying FEC. 33 This document is a product of the Reliable Multicast Transport Working 34 Group of the IETF. 36 This memo provides information for the Internet community. It does 37 not specify an Internet standard of any kind. Distribution of this 38 memo is unlimited. 40 This announcement is sent to the IETF list and the RFC-DIST list. 41 Requests to be added to or deleted from the IETF distribution list 42 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 43 added to or deleted from the RFC-DIST distribution list should 44 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 46 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 47 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 48 help: ways_to_get_rfcs. For example: 50 To: rfc-info@RFC-EDITOR.ORG 51 Subject: getting rfcs 53 help: ways_to_get_rfcs 55 Requests for special distribution should be addressed to either the 56 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 57 specifically noted otherwise on the RFC itself, all RFCs are for 58 unlimited distribution.echo 59 Submissions for Requests for Comments should be sent to 60 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 61 Authors, for further information.