RFC 6330: RaptorQ 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 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]
Document record
- Document ID
- RFC6330
- Published
- August 2011
- Authors
- M. Luby; A. Shokrollahi; M. Watson; T. Stockhammer; L. Minder
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 69
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6323Sender RTT Estimate Option for the Datagram Congestion Control Protocol (DCCP)Current
July 2011
- RFC 6356Coupled Congestion Control for Multipath Transport ProtocolsCurrent
October 2011
- RFC 6297A Survey of Lower-than-Best-Effort Transport ProtocolsCurrent
June 2011
- RFC 6363Forward Error Correction (FEC) FrameworkUpdated
October 2011
- RFC 6364Session Description Protocol Elements for the Forward Error Correction (FEC) FrameworkCurrent
October 2011
- RFC 6384An FTP Application Layer Gateway (ALG) for IPv6-to-IPv4 TranslationCurrent
October 2011
- RFC 6392A Survey of In-Network Storage SystemsCurrent
October 2011
- RFC 6182Architectural Guidelines for Multipath TCP DevelopmentCurrent
March 2011
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?