<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.singh-payload-rtp-1d2d-parity-scheme" target="https://datatracker.ietf.org/doc/html/draft-singh-payload-rtp-1d2d-parity-scheme-00">
   <front>
      <title>RTP Payload Format for Non-Interleaved and Interleaved Parity Forward Error Correction (FEC)</title>
      <author initials="V." surname="Singh" fullname="Varun Singh">
         <organization>Aalto University</organization>
      </author>
      <author initials="A. C." surname="Begen" fullname="Ali C. Begen">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="M." surname="Zanaty" fullname="Mo Zanaty">
         <organization>Cisco</organization>
      </author>
      <date month="October" day="1" year="2014" />
      <abstract>
	 <t>   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 offer a good protection against random and bursty packet
   losses, respectively, at a cost of decent complexity.  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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-singh-payload-rtp-1d2d-parity-scheme-00" />
   
</reference>
