Guidelines to support RTCP end-to-end in Back-to-Back User Agents (B2BUAs)
draft-miniero-straw-b2bua-rtcp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Lorenzo Miniero , Sergio Garcia Murillo , Victor Pascual | ||
| Last updated | 2014-04-23 (Latest revision 2013-10-20) | ||
| 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
SIP Back-to-Back User Agents (B2BUAs) are often envisaged to also be on the media path, rather than just intercepting signalling. This means that B2BUAs often implement an RTP/RTCP stack as well, whether to act as media transcoders or to just passthrough the media themselves, thus leading to separate media legs that the B2BUA correlates and bridges together. If not disciplined, though, this behaviour can severely impact the communication experience, especially when statistics and feedback information contained in RTCP packets get lost because of mismatches in the reported data. This document defines the proper behaviour B2BUAs should follow when also acting on the media plane in order to preserve the end-to-end functionality of RTCP.
Authors
Lorenzo Miniero
Sergio Garcia Murillo
Victor Pascual
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)