RTP Control Protocol Extended Reports
RFC 3611, “RTP Control Protocol Extended Reports”, is a Proposed Standard document published in November 2003 by T. Friedman, R. Caceres, A. Clark. The canonical text is published by the RFC Editor.
Abstract
This document defines the Extended Report (XR) packet type for the RTP Control Protocol (RTCP), and defines how the use of XR packets can be signaled by an application if it employs the Session Description Protocol (SDP). XR packets are composed of report blocks, and seven block types are defined here. The purpose of the extended reporting format is to convey information that supplements the six statistics that are contained in the report blocks used by RTCP's Sender Report (SR) and Receiver Report (RR) packets. Some applications, such as multicast inference of network characteristics (MINC) or voice over IP (VoIP) monitoring, require other and more detailed statistics. In addition to the block types defined here, additional block types may be defined in the future by adhering to the framework that this document provides.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3611 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3610 Counter with CBC-MAC
- RFC 3612 Applicability Statement for Restart Mechanisms for the Label Distribution Protocol
- RFC 3609 Tracing Requirements for Generic Tunnels
- RFC 3613 Definition of a Uniform Resource Name Namespace for the Middleware Architecture Committee for Education
- RFC 3608 Session Initiation Protocol Extension Header Field for Service Route Discovery During Registration
- RFC 3614 A Uniform Resource Name Namespace for the Motion Picture Experts Group
- RFC 3607 Chinese Lottery Cryptanalysis Revisited: The Internet as a Codebreaking Tool
- RFC 3615 A Uniform Resource Name Namespace for SWIFT Financial Messaging