Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

M. Zanaty
V. Singh
A. Begen
G. Mandyam

Stream:

IETF

Source:

payload (art)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8627

Discuss this RFC: Send questions or comments to the mailing listpayload@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8627

Abstract

This document defines new RTP payload formats for the Forward ErrorCorrection (FEC) packets that are generated by the non-interleavedand 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 setof source packets from one or more source RTP streams. These FECrepair packets are sent in a redundancy RTP stream separate from thesource RTP stream(s) that carries the source packets. RTP sourcepackets that were lost in transmission can be reconstructed using thesource and repair packets that were received. The non-interleavedand interleaved parity codes that are defined in this specificationoffer a good protection against random and bursty packet losses,respectively, at a cost of complexity. The RTP payload formats thatare defined in this document address scalability issues experiencedwith the earlier specifications and offer several improvements. Dueto these changes, the new payload formats are not backward compatiblewith earlier specifications; however, endpoints that do not implementthis specification can still work by simply ignoring the FEC repairpackets.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.