RFC 6816: Simple Low-Density Parity Check (LDPC) Staircase 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 Low-Density Parity Check (LDPC) Staircase codes that can be used to protect media streams along the lines defined by FECFRAME. These codes have many interesting properties: they are systematic codes, they perform close to ideal codes in many use-cases, and they also feature very high encoding and decoding throughputs. LDPC-Staircase codes are therefore a good solution to protect a single high bitrate source flow or to protect globally several mid-rate flows within a single FECFRAME instance. They are also a good solution whenever the processing load of a software encoder or decoder must be kept to a minimum.
Document record
- Document ID
- RFC6816
- Published
- December 2012
- Authors
- V. Roca; M. Cunche; J. Lacan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6865Simple Reed-Solomon Forward Error Correction (FEC) Scheme for FECFRAMECurrent
February 2013
- 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?