Guidelines for using the Multiplexing Features of RTP
draft-westerlund-avtcore-multiplex-architecture-03

 
Document Type Replaced Internet-Draft (individual)
Last updated 2013-04-22 (latest revision 2013-02-25)
Replaced by draft-ietf-avtcore-multiplex-guidelines
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-avtcore-multiplex-guidelines
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

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-multiplex-architecture-03.txt

Abstract

Real-time Transport Protocol (RTP) is a flexible protocol possible to use in a wide range of applications and network and system topologies. This flexibility and the implications of different choices should be understood by any application developer using RTP. To facilitate that understanding, this document contains an in-depth discussion of the usage of RTP's multiplexing points; the RTP session and the Synchronisation Source Identifier (SSRC). The document tries to give guidance and source material for an analysis on the most suitable choices for the application being designed.

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.)