%% You should probably cite rfc6849 instead of this I-D. @techreport{ietf-mmusic-media-loopback-19, number = {draft-ietf-mmusic-media-loopback-19}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-mmusic-media-loopback/19/}, author = {Hadriel Kaplan and Kaynam Hedayat and Nagarjuna Venna and Paul Jones and Nathan Stratton}, title = {{An Extension to the Session Description Protocol (SDP) and Real-time Transport Protocol (RTP) for Media Loopback}}, pagetotal = 33, year = 2012, month = jul, day = 13, abstract = {The wide deployment of Voice over IP (VoIP), Text and Video over IP services has introduced new challenges in managing and maintaining real-time voice/text/video quality, reliability, and overall performance. In particular, media delivery is an area that needs attention. One method of meeting these challenges is monitoring the media delivery performance by looping media back to the transmitter. This is typically referred to as "active monitoring" of services. Media loopback is especially popular in ensuring the quality of transport to the edge of a given VoIP, Real-time Text or Video over IP service. Today in networks that deliver real-time media, short of running 'ping' and 'traceroute' to the edge, administrators are left without the necessary tools to actively monitor, manage, and diagnose quality issues with their service. The extension defined herein adds new SDP media types and attributes, which enable establishment of media sessions where the media is looped back to the transmitter. Such media sessions will serve as monitoring and troubleshooting tools by providing the means for measurement of more advanced VoIP, Real-time Text and Video over IP performance metrics.}, }