Multiple Synchronization sources (SSRC) in RTP Session Signaling
draft-westerlund-avtcore-max-ssrc-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Magnus Westerlund  , Bo Burman  , Fredrik Jansson 
Last updated 2012-04-26 (latest revision 2011-10-24)
Stream (None)
Formats
Expired & archived
pdf htmlized bibtex
Additional Resources
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
https://www.ietf.org/archive/id/draft-westerlund-avtcore-max-ssrc-00.txt

Abstract

RTP has always been a protocol that supports multiple participants each sending their own media streams in an RTP session. Unfortunately many implementations are designed only for point to point voice over IP with a single source in each end-point. Even client implementations aimed at video conferences have often been built with the assumption around central mixers that only deliver a single media stream per media type. Thus any application that wants to allow for more advance usage where multiple media streams are sent and received by an end-point has an issue with legacy implementations. This document describes the problem and proposes a solution for how to use multiple SSRCs within one RTP session and at the same time handle the legacy issues.

Authors

Magnus Westerlund (magnus.westerlund@ericsson.com)
Bo Burman (bo.burman@ericsson.com)
Fredrik Jansson (fredrik.k.jansson@ericsson.com)

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