Using SDP with Large Numbers of Media Flows
draft-roach-rtcweb-plan-a-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2013-11-08 (latest revision 2013-05-07) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
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-roach-rtcweb-plan-a-00.txt
Abstract
A recurrent theme in WebRTC has been the need to handle very large numbers of media flows. Unfortunately, naive uses of SDP do not handle this case particularly well. This document describes a modest set of extensions to SDP which allow it to cleanly handle arbitrary numbers of flows while still retaining a large degree of backward compatibility with existing and non-RTCWEB endpoints.
Authors
Adam Roach
(adam@nostrum.com)
Martin Thomson
(martin.thomson@skype.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)