RTCP Reporting by Translators
draft-hunt-avt-rtcptrans-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Geoff Hunt | ||
| Last updated | 2007-11-12 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo addresses RTCP reporting by and through RTP translators. It collects existing guidance from RFC 3550, systematises translators' reporting behaviour by considering potential sources of information and the policy-controlled forwarding of such information, considers naming issues in labelling reports, considers methods of control of reporting behaviour, and presents some examples of architectures for reporting.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)