RTP Payload Format for Flexible Forward Error Correction (FEC)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 41
- Abstract
- This document defines new RTP payload formats for the Forward Error Correction (FEC) packets that are generated by the non-interleaved and interleaved parity codes from source media encapsulated in RTP. These parity codes are systematic codes (Flexible FEC, or "FLEX FEC"), where a number of FEC repair packets are generated from a set of source packets from one or more source RTP streams. These FEC repair packets are sent in a redundancy RTP stream separate from the source RTP stream(s) that carries the source packets. RTP source packets that were lost in transmission can be reconstructed using the source and repair packets that were received. The non-interleaved and interleaved parity codes that are defined in this specification offer a good protection against random and bursty packet losses, respectively, at a cost of complexity. The RTP payload formats that are defined in this document address scalability issues experienced with the earlier specifications and offer several improvements. Due to these changes, the new payload formats are not backward compatible with earlier specifications; however, endpoints that do not implement this specification can still work by simply ignoring the FEC repair packets.
- Publication Date
- 2019-07-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC8627- Link
- https://doi.org/10.17487/RFC8627
- Author(s)
- Mo ZanatyVarun SinghAli C. BegenGiridhar Mandyam
- Keyword(s)
- Forward Error Correction
Latest version of IETF RFC 8627
Document Versions — IETF RFC 8627
-
▶ IETF RFC 8627 (2019-07-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3264 [Active*]
- IETF RFC 3550 [Active*]
- IETF RFC 4566 [Superseded*]
- IETF RFC 4855 [Active*]
- IETF RFC 4856 [Active*]
- IETF RFC 5956 [Active*]
- IETF RFC 6363 [Active*]
- IETF RFC 6838 [Active*]
- IETF RFC 7022 [Active*]
- IETF RFC 8174 [Active*]
Bibliographic Reference(s)
- 10.5594-SMPTE.ST2022-1.2007 — SMPTE2022-1 EXTERNAL
- IETF.draft-ietf-avtext-rid-09 — RTP-SDES EXTERNAL
- IETF RFC 2326 [Superseded*]
- IETF RFC 2733 [Superseded*]
- IETF RFC 2974 [Active*]
- IETF RFC 3711 [Active*]
- IETF RFC 4301 [Active, Amended*]
- IETF RFC 4585 [Active*]
- IETF RFC 4588 [Active*]
- IETF RFC 5109 [Active*]
- IETF RFC 5725 [Active*]
- IETF RFC 6347 [Superseded*]
- RFC7509 — RFC7509 EXTERNAL
- IETF RFC 7656 [Active*]
- IETF RFC 7826 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8627.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 8627, RTP Payload Format for Flexible Forward Error Correction (FEC). Available at https://doi.org/10.17487/RFC8627
Snippet:
IETF RFC 8627, RTP Payload Format for Flexible Forward Error Correction (FEC). Available at https://doi.org/10.17487/RFC8627
HTML (ISO 690 compliant)
Preview:
IETF RFC 8627, RTP Payload Format for Flexible Forward Error Correction (FEC). Available at https://doi.org/10.17487/RFC8627
Snippet:
<span class="citation"><cite>IETF RFC 8627</cite>, RTP Payload Format for Flexible Forward Error Correction (FEC). Available at <a href="https://doi.org/10.17487/RFC8627" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8627</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 8627, RTP Payload Format for Flexible Forward Error Correction (FEC)
doi: 10.17487/RFC8627
url: https://doi.org/10.17487/RFC8627
doi: 10.17487/RFC8627
url: https://doi.org/10.17487/RFC8627
Snippet:
<li> <cite id="bib-rfc8627">IETF RFC 8627</cite>, RTP Payload Format for Flexible Forward Error Correction (FEC) <span class="doi">10.17487/RFC8627</span> </li>
Referenced By
- IETF RFC 8723 [Active*]
- IETF RFC 8851 [Active*]
- IETF RFC 8853 [Active*]