FEC FRAME Raptor Extensions for Multiple RTP Synchronization Sources
draft-mandyam-rtcweb-fecframebundledssrc-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Giridhar Mandyam , Michael Luby , Thomas Stockhammer | ||
| Last updated | 2015-12-18 (Latest revision 2015-06-16) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The FEC FRAME Raptor code options do not currently address the case of bundled protection of multiple media types over multiple real-time transport protocol (RTP) synchronization sources (SSRC's). This document provides the FEC source and repair payload definitions that enable a single repair flow to be defined for multiple RTP flows
Authors
Giridhar Mandyam
Michael Luby
Thomas Stockhammer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)