<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-avt-rtcp-guidelines" target="https://datatracker.ietf.org/doc/html/draft-ietf-avt-rtcp-guidelines-04">
   <front>
      <title>Guidelines for Extending the RTP Control Protocol (RTCP)</title>
      <author initials="C." surname="Perkins" fullname="Colin Perkins">
         <organization>University of Glasgow</organization>
      </author>
      <author initials="J." surname="Ott" fullname="Joerg Ott">
         <organization>Aalto University</organization>
      </author>
      <date month="May" day="11" year="2010" />
      <abstract>
	 <t>The RTP Control Protocol (RTCP) is used along with the Real-time Transport Protocol (RTP) to provide a control channel between media senders and receivers.  This allows constructing a feedback loop to enable application adaptation and monitoring, among other uses.  The basic reporting mechanisms offered by RTCP are generic, yet quite powerful and suffice to cover a range of uses.  This document provides guidelines on extending RTCP if those basic mechanisms prove insufficient.  This document is not an Internet Standards Track specification; it is published for informational purposes.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-avt-rtcp-guidelines-04" />
   
</reference>
