RFC 6865: Simple Reed-Solomon Forward Error Correction (FEC) Scheme for FECFRAME
In plain English — editorial summary, not part of the RFC
This document describes a fully-specified simple Forward Error Correction (FEC) scheme for Reed-Solomon codes over the finite field (also known as the Galois Field) GF(2^^m), with 2 <= m <= 16, that can be used to protect arbitrary media streams along the lines defined by FECFRAME. The Reed-Solomon codes considered have attractive properties, since they offer optimal protection against packet erasures and the source symbols are part of the encoding symbols, which can greatly simplify decoding. However, the price to pay is a limit on the maximum source block size, on the maximum number of encoding symbols, and a computational complexity higher than that of the Low-Density Parity Check (LDPC) codes, for instance.
Document record
- Document ID
- RFC6865
- Published
- February 2013
- Authors
- V. Roca; M. Cunche; J. Lacan; A. Bouabdallah; K. Matsuzono
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6816Simple Low-Density Parity Check (LDPC) Staircase Forward Error Correction (FEC) Scheme for FECFRAMECurrent
December 2012
- RFC 5775Asynchronous Layered Coding (ALC) Protocol InstantiationCurrent
April 2010
- RFC 5740NACK-Oriented Reliable Multicast (NORM) Transport ProtocolCurrent
November 2009
- RFC 3695Compact Forward Error Correction (FEC) SchemesObsoleted
February 2004
- RFC 3452Forward Error Correction (FEC) Building BlockObsoleted
December 2002
- RFC 5576Source-Specific Media Attributes in the Session Description Protocol (SDP)Current
June 2009
- RFC 8627RTP Payload Format for Flexible Forward Error Correction (FEC)Current
July 2019
- RFC 2738Corrections to "A Syntax for Describing Media Feature Sets"Current
December 1999
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?