Guidelines for using the Multiplexing Features of RTP to Support Multiple Media Streams
draft-ietf-avtcore-multiplex-guidelines-03

Document Type Expired Internet-Draft (avtcore WG)
Last updated 2015-04-11 (latest revision 2014-10-08)
Replaces draft-westerlund-avtcore-multiplex-architecture
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Nov 2016 - Submit Guidelines fo... )
Document shepherd Roni Even
IESG IESG state Expired
Consensus Boilerplate Unknown
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-ietf-avtcore-multiplex-guidelines-03.txt

Abstract

The Real-time Transport Protocol (RTP) is a flexible protocol that can be used in a wide range of applications, networks, and system topologies. That flexibility makes for wide applicability, but can complicate the application design process. One particular design question that has received much attention is how to support multiple media streams in RTP. This memo discusses the available options and design trade-offs, and provides guidelines on how to use the multiplexing features of RTP to support multiple media streams.

Authors

Magnus Westerlund (magnus.westerlund@ericsson.com)
Bo Burman (bo.burman@ericsson.com)
Colin Perkins (csp@csperkins.org)
Harald Alvestrand (harald@alvestrand.no)

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