metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 5109: RTP Payload Format for Generic Forward Error Correction

In plain English — editorial summary, not part of the RFC

This document specifies a payload format for generic Forward Error Correction (FEC) for media data encapsulated in RTP. It is based on the exclusive-or (parity) operation. The payload format described in this document allows end systems to apply protection using various protection lengths and levels, in addition to using various protection group sizes to adapt to different media and channel characteristics. It enables complete recovery of the protected packets or partial recovery of the critical parts of the payload depending on the packet loss situation. This scheme is completely compatible with non-FEC-capable hosts, so the receivers in a multicast group that do not implement FEC can still work by simply ignoring the protection data. This specification obsoletes RFC 2733 and RFC 3009. The FEC specified in this document is not backward compatible with RFC 2733 and RFC 3009. [STANDARDS-TRACK]

Document record

Document ID
RFC5109
Published
December 2007
Authors
A. Li
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
44
Also known as
—
Obsoletes:
RFC 2733, RFC 3009

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 2733 (1999)
  2. RFC 3009 (2000)
  3. RFC 5109 (2007)

Read the full history of RTP Payload Format for Generic Forward Error Correction →

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/5109-rtp-payload-format-for-generic-forward-error-correction