Guidelines for Extending the RTP Control Protocol (RTCP)
draft-ott-avt-rtcp-guidelines-01

Document Type Replaced Internet-Draft (individual)
Authors Joerg Ott  , Colin Perkins 
Last updated 2008-06-15
Replaced by RFC 5968
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-avt-rtcp-guidelines
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ott-avt-rtcp-guidelines-01.txt

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 adaptivity 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.

Authors

Joerg Ott (jo@netlab.hut.fi)
Colin Perkins (csp@csperkins.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)