Skip to main content

Guidelines for using the Multiplexing Features of RTP

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Magnus Westerlund , Bo Burman , Colin Perkins , Harald T. Alvestrand
Last updated 2013-04-22 (Latest revision 2013-02-25)
Replaced by draft-ietf-avtcore-multiplex-guidelines, draft-ietf-avtcore-multiplex-guidelines, RFC 8872
RFC stream (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-avtcore-multiplex-guidelines, draft-ietf-avtcore-multiplex-guidelines
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:


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.


Magnus Westerlund
Bo Burman
Colin Perkins
Harald T. Alvestrand

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