RFC 5053: Raptor Forward Error Correction Scheme for Object Delivery
In plain English — editorial summary, not part of the RFC
This document describes a Fully-Specified Forward Error Correction (FEC) scheme, corresponding to FEC Encoding ID 1, for the Raptor forward error correction code and its application to reliable delivery of data objects. Raptor is a fountain code, i.e., as many encoding symbols as needed can be generated by the encoder on-the-fly from the source symbols of a source block of data. The decoder is able to recover the source block from any set of encoding symbols only slightly more in number than the number of source symbols. The Raptor code described here is a systematic code, meaning that all the source symbols are among the encoding symbols that can be generated. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5053
- Published
- October 2007
- Authors
- M. Luby; A. Shokrollahi; M. Watson; T. Stockhammer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 46
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5170Low Density Parity Check (LDPC) Staircase and Triangle Forward Error Correction (FEC) SchemesCurrent
June 2008
- RFC 5651Layered Coding Transport (LCT) Building BlockCurrent
October 2009
- RFC 5775Asynchronous Layered Coding (ALC) Protocol InstantiationCurrent
April 2010
- RFC 6015RTP Payload Format for 1-D Interleaved Parity Forward Error Correction (FEC)Current
October 2010
- RFC 3695Compact Forward Error Correction (FEC) SchemesObsoleted
February 2004
- RFC 3452Forward Error Correction (FEC) Building BlockObsoleted
December 2002
- RFC 6683Guidelines for Implementing Digital Video Broadcasting - IPTV (DVB-IPTV) Application-Layer Hybrid Forward Error Correction (FEC) ProtectionCurrent
August 2012
- RFC 5109RTP Payload Format for Generic Forward Error CorrectionCurrent
December 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?