A Mechanism for Negotiating Multi-Stream Continuous Presence Video in SIP

Document Type Expired Internet-Draft (individual)
Last updated 2012-06-25 (latest revision 2011-12-23)
Stream (None)
Intended RFC status (None)
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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The NextGen video conferencing clients require multiple concurrent video streams to provide a User eXperience (UX) in which multiple participants can be viewed at the same time, this user experience is called Continuous Presence (CP) video. The multi-stream CP video provides more client control of the UX and less processing on the conference server since the video streams are relayed by the server rather than mixed to compose a CP video stream. The client CP layout, processing power and bandwidth limitations require a per stream bandwidth and resolution to be negtiated in the SIP Offer/ Answer with the conference server. Standard methods are used to achieve this negotiation in addition to a new SDP parameter. This document explains the methodology and solution to achieve this in SIP and SDP.


Adel Mostafa (amostafa@avaya.com)

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