<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.lennox-avtcore-rtp-multi-stream" target="https://datatracker.ietf.org/doc/html/draft-lennox-avtcore-rtp-multi-stream-02">
   <front>
      <title>RTP Considerations for Endpoints Sending Multiple Media Streams</title>
      <author initials="J." surname="Lennox" fullname="Jonathan Lennox">
         <organization>Vidyo</organization>
      </author>
      <author initials="M." surname="Westerlund" fullname="Magnus Westerlund">
         <organization>Ericsson</organization>
      </author>
      <author initials="Q." surname="Wu" fullname="Qin Wu">
         <organization>Huawei</organization>
      </author>
      <author initials="C." surname="Perkins" fullname="Colin Perkins">
         <organization>University of Glasgow</organization>
      </author>
      <date month="February" day="25" year="2013" />
      <abstract>
	 <t>   This document expands and clarifies the behavior of the Real-Time
   Transport Protocol (RTP) endpoints when they are sending multiple
   media streams in a single RTP session.  In particular, issues
   involving Real-Time Transport Control Protocol (RTCP) messages are
   described.

   This document updates RFC 3550 in regards to handling of multiple
   SSRCs per endpoint in RTP sessions.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-lennox-avtcore-rtp-multi-stream-02" />
   
</reference>
