RTP Payload Format for Generic Forward Error Correction
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 44
- Abstract
- 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]
- Publication Date
- 2007-12-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5109- Link
- https://doi.org/10.17487/RFC5109
- Author(s)
- Adam H. Li
- Keyword(s)
- Forward Error Correction, RTP
Latest version of IETF RFC 5109
Document Versions — IETF RFC 5109
-
▶ IETF RFC 5109 (2007-12-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2198 [Active*]
- IETF RFC 3388 [Superseded*]
- IETF RFC 3550 [Active*]
- IETF RFC 4288 [Superseded*]
- IETF RFC 4566 [Superseded*]
- RFC4756 — 6 EXTERNAL
- IETF RFC 4855 [Active*]
Bibliographic Reference(s)
- RFC2354 — 10 EXTERNAL
- IETF RFC 2733 [Superseded*]
- RFC3009 — 11 EXTERNAL
- IETF RFC 3264 [Active*]
- IETF RFC 3452 [Superseded*]
- IETF RFC 3551 [Active*]
- IETF RFC 3711 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5109.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5109, RTP Payload Format for Generic Forward Error Correction. Available at https://doi.org/10.17487/RFC5109
Snippet:
IETF RFC 5109, RTP Payload Format for Generic Forward Error Correction. Available at https://doi.org/10.17487/RFC5109
HTML (ISO 690 compliant)
Preview:
IETF RFC 5109, RTP Payload Format for Generic Forward Error Correction. Available at https://doi.org/10.17487/RFC5109
Snippet:
<span class="citation"><cite>IETF RFC 5109</cite>, RTP Payload Format for Generic Forward Error Correction. Available at <a href="https://doi.org/10.17487/RFC5109" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5109</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5109, RTP Payload Format for Generic Forward Error Correction
doi: 10.17487/RFC5109
url: https://doi.org/10.17487/RFC5109
doi: 10.17487/RFC5109
url: https://doi.org/10.17487/RFC5109
Snippet:
<li> <cite id="bib-rfc5109">IETF RFC 5109</cite>, RTP Payload Format for Generic Forward Error Correction <span class="doi">10.17487/RFC5109</span> </li>
Referenced By
- An Internet of Things Architecture for Cloud-Fit Professional Media Workflow [Active]
- IETF RFC 6184 [Active*]
- IETF RFC 8285 [Active*]
- SMPTE ST 2022-5:2012 [Superseded]
- SMPTE ST 2022-5:2013 [Active]