Raptor Forward Error Correction Scheme for Object Delivery
RFC 5053
Revision differences
Document history
Date | By | Action |
---|---|---|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document describes a Fully-Specified Forward Error Correction (FEC) scheme, corresponding to FEC Encoding ID 1, … Received changes through RFC Editor sync (changed abstract to '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]') |
2015-10-14
|
(System) | Notify list changed from rmt-chairs@ietf.org to (None) |
2013-02-06
|
(System) | Posted related IPR disclosure: QUALCOMM Incorporated's Statement about IPR related to RFC 5053 |
2012-04-05
|
(System) | Posted related IPR disclosure: QUALCOMM Incorporated's Statement about IPR related to RFC 5053 |
2011-03-08
|
(System) | Posted related IPR disclosure: QUALCOMM Incorporated's Statement about IPR related to RFC 5053 |
2010-03-18
|
(System) | Posted related IPR disclosure: QUALCOMM Incorporated's Statement about IPR related to RFC 5053 |
2009-09-08
|
(System) | Posted related IPR disclosure: QUALCOMM Incorporated's Statement about IPR related to RFC 5053 |
2007-10-24
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2007-10-24
|
Amy Vezza | [Note]: 'RFC 5053' added by Amy Vezza |
2007-10-23
|
(System) | RFC published |