<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-straw-b2bua-rtcp" target="https://datatracker.ietf.org/doc/html/draft-ietf-straw-b2bua-rtcp-16">
   <front>
      <title>Guidelines to support RTCP end-to-end in Back-to-Back User Agents (B2BUAs)</title>
      <author initials="L." surname="Miniero" fullname="Lorenzo Miniero">
         </author>
      <author initials="S. G." surname="Murillo" fullname="Sergio Garcia Murillo">
         </author>
      <author initials="V. P." surname="Pascual" fullname="Victor Pascual">
         </author>
      <date month="December" day="16" year="2016" />
      <abstract>
	 <t>   SIP Back-to-Back User Agents (B2BUAs) are often designed to also be
   on the media path, rather than just intercepting signalling.  This
   means that B2BUAs often implement an RTP/RTCP stack as well, thus
   leading to separate multimedia sessions that the B2BUA correlates and
   bridges together.  If not disciplined, though, this behaviour can
   severely impact the communication experience, especially when
   statistics and feedback information contained in RTCP messages get
   lost because of mismatches in the reported data.

   This document defines the proper behaviour B2BUAs should follow when
   also acting on the signalling/media plane in order to preserve the
   end-to-end functionality of RTCP.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-straw-b2bua-rtcp-16" />
   
</reference>
