RFC 5052: Forward Error Correction (FEC) Building Block
In plain English — editorial summary, not part of the RFC
This document describes how to use Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for bulk data transfer over IP multicast. This document defines a framework for the definition of the information that needs to be communicated in order to use an FEC code for bulk data transfer, in addition to the encoded data itself, and for definition of formats and codes for communication of that information. Both information communicated with the encoded data itself and information that needs to be communicated 'out-of-band' are considered. The procedures for specifying new FEC codes, defining the information communication requirements associated with those codes and registering them with the Internet Assigned Numbers Authority (IANA) are also described. The requirements on Content Delivery Protocols that wish to use FEC codes defined within this framework are also defined. The companion document titled "The Use of Forward Error Correction (FEC) in Reliable Multicast" describes some applications of FEC codes for delivering content. This document obsoletes RFC 3452. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5052
- Published
- August 2007
- Authors
- M. Watson; M. Luby; L. Vicisano
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 25
- Also known as
- —
- Obsoletes:
- RFC 3452
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 3452 (2002)
- RFC 3695 (2004)
- RFC 5052 (2007)
- RFC 5445 (2009) ✓
Read the full history of Basic Forward Error Correction (FEC) Schemes →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5053Raptor Forward Error Correction Scheme for Object DeliveryCurrent
October 2007
- RFC 5049Applying Signaling Compression (SigComp) to the Session Initiation Protocol (SIP)Updated
December 2007
- RFC 5048Internet Small Computer System Interface (iSCSI) Corrections and ClarificationsObsoleted
October 2007
- RFC 5047DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)Updated
October 2007
- RFC 5046Internet Small Computer System Interface (iSCSI) Extensions for Remote Direct Memory Access (RDMA)Obsoleted
October 2007
- RFC 5045Applicability of Remote Direct Memory Access Protocol (RDMA) and Direct Data Placement (DDP)Updated
October 2007
- RFC 5044Marker PDU Aligned Framing for TCP SpecificationUpdated
October 2007
- RFC 5043Stream Control Transmission Protocol (SCTP) Direct Data Placement (DDP) AdaptationUpdated
October 2007
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?