RaptorQ Forward Error Correction Scheme for Object Delivery
RFC 6330
Revision differences
Document history
Date | By | Action |
---|---|---|
2020-06-03
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
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 6, … 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 6, for the RaptorQ FEC code and its application to reliable delivery of data objects. RaptorQ codes are a new family of codes that provide superior flexibility, support for larger source block sizes, and better coding efficiency than Raptor codes in RFC 5053. RaptorQ is also a fountain code, i.e., as many encoding symbols as needed can be generated on the fly by the encoder from the source symbols of a source block of data. The decoder is able to recover the source block from almost any set of encoding symbols of sufficient cardinality -- in most cases, a set of cardinality equal to the number of source symbols is sufficient; in rare cases, a set of cardinality slightly more than the number of source symbols is required. The RaptorQ code described here is a systematic code, meaning that all the source symbols are among the encoding symbols that can be generated. [STANDARDS-TRACK]') |
2018-11-08
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
2015-10-14
|
(System) | Notify list changed from rmt-chairs@ietf.org, draft-ietf-rmt-bb-fec-raptorq@ietf.org to (None) |
2015-03-20
|
Naveen Khan | Posted related IPR disclosure: QUALCOMM Incorporated's Statement about IPR related to RFC 6330 |
2013-02-06
|
(System) | Posted related IPR disclosure: QUALCOMM Incorporated's Statement about IPR related to RFC 6330 |
2011-08-12
|
(System) | RFC published |