Skip to main content

A Unified Plan for Using SDP with Large Numbers of Media Flows

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Adam Roach , Justin Uberti , Martin Thomson
Last updated 2014-01-16 (Latest revision 2013-07-15)
RFC stream (None)
Intended RFC status (None)
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:


A recurrent theme in emerging real-time communications use cases, such as RTCWEB, 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.


Adam Roach
Justin Uberti
Martin Thomson

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