RTP Payload Format for Flexible Forward Error Correction (FEC)

Document Type Expired Internet-Draft (payload WG)
Last updated 2018-01-04 (latest revision 2017-07-03)
Stream IETF
Intended RFC status (None)
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Mar 2017 - Submit RTP Payload F... )
Revised I-D Needed - Issue raised by WGLC
Document shepherd Roni Even
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Roni Even" <roni.even@mail01.huawei.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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 a source media encapsulated in RTP. These parity codes are systematic codes, where a number of repair symbols are generated from a set of source symbols. These repair symbols are sent in a repair flow separate from the source flow that carries the source symbols. The non-interleaved and interleaved parity codes which are defined in this specification offer a good protection against random and bursty packet losses, respectively, at a cost of decent complexity. Moreover, alternate FEC codes may be used with the payload formats presented. The RTP payload formats that are defined in this document address the scalability issues experienced with the earlier specifications including RFC 2733, RFC 5109 and SMPTE 2022-1, and offer several improvements. Due to these changes, the new payload formats are not backward compatible with the earlier specifications, but endpoints that do not implement the scheme can still work by simply ignoring the FEC packets.


Varun Singh (varun.singh@iki.fi)
Ali Begen (ali.begen@networked.media)
Mo Zanaty (mzanaty@cisco.com)
Giridhar Mandyam (mandyam@qti.qualcomm.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)