<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-avtcore-rtp-multi-stream" target="https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rtp-multi-stream-11">
   <front>
      <title>Sending Multiple RTP Streams in a Single RTP Session</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="December" day="11" year="2015" />
      <abstract>
	 <t>This memo expands and clarifies the behavior of Real-time Transport Protocol (RTP) endpoints that use multiple synchronization sources (SSRCs).  This occurs, for example, when an endpoint sends multiple RTP streams in a single RTP session.  This memo updates RFC 3550 with regard to handling multiple SSRCs per endpoint in RTP sessions, with a particular focus on RTP Control Protocol (RTCP) behavior.  It also updates RFC 4585 to change and clarify the calculation of the timeout of SSRCs and the inclusion of feedback messages.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-avtcore-rtp-multi-stream-11" />
   
</reference>
