<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.hunt-avtcore-monarch" target="https://datatracker.ietf.org/doc/html/draft-hunt-avtcore-monarch-02">
   <front>
      <title>Monitoring Architectures for RTP</title>
      <author initials="G." surname="Hunt" fullname="Geoff Hunt">
         <organization>BT</organization>
      </author>
      <author initials="P." surname="Arden" fullname="Philip Arden">
         <organization>BT</organization>
      </author>
      <author initials="Q." surname="Wu" fullname="Qin Wu">
         <organization>Huawei</organization>
      </author>
      <date month="March" day="28" year="2011" />
      <abstract>
	 <t>This memo proposes an architecture for extending RTCP with a new RTCP
XR (RFC3611) block type to report new metrics regarding media
transmission or reception quality, as proposed in RFC5968.  This memo
suggests that a new block should contain a single metric or a small
number of metrics relevant to a single parameter of interest or
concern, rather than containing a number of metrics which attempt to
provide full coverage of all those parameters of concern to a
specific application.  Applications may then &quot;mix and match&quot; to
create a set of blocks which covers their set of concerns.  Where
possible, a specific block should be designed to be re-usable across
more than one application, for example, for all of voice, streaming
audio and video.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-hunt-avtcore-monarch-02" />
   
</reference>
