RFC 6015: RTP Payload Format for 1-D Interleaved Parity Forward Error Correction (FEC)
In plain English — editorial summary, not part of the RFC
This document defines a new RTP payload format for the Forward Error Correction (FEC) that is generated by the 1-D interleaved parity code from a source media encapsulated in RTP. The 1-D interleaved parity code is a systematic code, where a number of repair symbols are generated from a set of source symbols and sent in a repair flow separate from the source flow that carries the source symbols. The 1-D interleaved parity code offers a good protection against bursty packet losses at a cost of reasonable complexity. The new payload format defined in this document should only be used (with some exceptions) as a part of the Digital Video Broadcasting-IPTV (DVB- IPTV) Application-layer FEC specification. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6015
- Published
- October 2010
- Authors
- A. Begen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5956Forward Error Correction Grouping Semantics in the Session Description ProtocolCurrent
September 2010
- RFC 5725Post-Repair Loss RLE Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)Current
February 2010
- RFC 5775Asynchronous Layered Coding (ALC) Protocol InstantiationCurrent
April 2010
- RFC 5651Layered Coding Transport (LCT) Building BlockCurrent
October 2009
- RFC 6683Guidelines for Implementing Digital Video Broadcasting - IPTV (DVB-IPTV) Application-Layer Hybrid Forward Error Correction (FEC) ProtectionCurrent
August 2012
- RFC 5170Low Density Parity Check (LDPC) Staircase and Triangle Forward Error Correction (FEC) SchemesCurrent
June 2008
- RFC 5053Raptor Forward Error Correction Scheme for Object DeliveryCurrent
October 2007
- RFC 3695Compact Forward Error Correction (FEC) SchemesObsoleted
February 2004
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?