FEC FRAME Raptor Extensions for Multiple RTP Synchronization Sources
draft-mandyam-rtcweb-fecframebundledssrc-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Giridhar Mandyam , Mike Luby , Thomas Stockhammer | ||
| Last updated | 2015-12-18 (latest revision 2015-06-16) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-mandyam-rtcweb-fecframebundledssrc-00.txt
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
(mandyam@quicinc.com)
Mike Luby
(luby@qti.qualcomm.com)
Thomas Stockhammer
(tsto@qti.qualcomm.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)