Guidelines for Extending the RTP Control Protocol
RFC 5968, “Guidelines for Extending the RTP Control Protocol”, is an Informational document published in September 2010 by J. Ott, C. Perkins. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5968 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5967 The application/pkcs10 Media Type
- RFC 5969 IPv6 Rapid Deployment on IPv4 Infrastructures -- Protocol Specification
- RFC 5966 DNS Transport over TCP - Implementation Requirements
- RFC 5970 DHCPv6 Options for Network Boot
- RFC 5965 An Extensible Format for Email Feedback Reports
- RFC 5971 GIST: General Internet Signalling Transport
- RFC 5964 Specifying Holes in Location-to-Service Translation Service Boundaries
- RFC 5972 General Internet Signaling Transport State Machine