<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-avtcore-multiplex-guidelines" target="https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-multiplex-guidelines-10">
   <front>
      <title>Guidelines for using the Multiplexing Features of RTP to Support Multiple Media Streams</title>
      <author initials="M." surname="Westerlund" fullname="Magnus Westerlund">
         <organization>Ericsson</organization>
      </author>
      <author initials="B." surname="Burman" fullname="Bo Burman">
         <organization>Ericsson</organization>
      </author>
      <author initials="C." surname="Perkins" fullname="Colin Perkins">
         <organization>University of Glasgow</organization>
      </author>
      <author initials="H. T." surname="Alvestrand" fullname="Harald T. Alvestrand">
         <organization>Google</organization>
      </author>
      <author initials="R." surname="Even" fullname="Roni Even">
         <organization>Huawei</organization>
      </author>
      <date month="February" day="14" year="2020" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-avtcore-multiplex-guidelines-10" />
   
</reference>
