RFC 3453: The Use of Forward Error Correction (FEC) in Reliable Multicast
In plain English — editorial summary, not part of the RFC
This memo describes the use of Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for one-to-many reliable data transport using IP multicast. One of the key properties of FEC codes in this context is the ability to use the same packets containing FEC data to simultaneously repair different packet loss patterns at multiple receivers. Different classes of FEC codes and some of their basic properties are described and terminology relevant to implementing FEC in a reliable multicast protocol is introduced. Examples are provided of possible abstract formats for packets carrying FEC. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3453
- Published
- December 2002
- Authors
- M. Luby; L. Vicisano; J. Gemmell; L. Rizzo; M. Handley; J. Crowcroft
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3242RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPObsoleted
April 2002
- RFC 3738Wave and Equation Based Rate Control (WEBRC) Building BlockCurrent
April 2004
- RFC 3753Mobility Related TerminologyCurrent
June 2004
- RFC 4019RObust Header Compression (ROHC): Profiles for User Datagram Protocol (UDP) LiteUpdated
April 2005
- RFC 2746RSVP Operation Over IP TunnelsCurrent
January 2000
- RFC 2663IP Network Address Translator (NAT) Terminology and ConsiderationsCurrent
August 1999
- RFC 2475An Architecture for Differentiated ServicesUpdated
December 1998
- RFC 4654TCP-Friendly Multicast Congestion Control (TFMCC): Protocol SpecificationCurrent
August 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?