Skip to main content

Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in Back-to-Back User Agents (B2BUAs)
RFC 8079

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'SIP Back-to-Back User Agents (B2BUAs) are often designed to also be on the media path, rather …
Received changes through RFC Editor sync (changed abstract to 'SIP Back-to-Back User Agents (B2BUAs) are often designed to also be on the media path, rather than just to intercept signalling. This means that B2BUAs often implement an RTP or RTP Control Protocol (RTCP) stack as well, thus leading to separate multimedia sessions that the B2BUA correlates and bridges together. If not disciplined, this behaviour can severely impact the communication experience, especially when statistics and feedback information contained in RTCP messages get lost because of mismatches in the reported data.

This document defines the proper behaviour B2BUAs should follow when acting on both the signalling plane and media plane in order to preserve the end-to-end functionality of RTCP.')
2017-02-22
(System)
Received changes through RFC Editor sync (created alias RFC 8079, changed title to 'Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in …
Received changes through RFC Editor sync (created alias RFC 8079, changed title to 'Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in Back-to-Back User Agents (B2BUAs)', changed abstract to 'SIP Back-to-Back User Agents (B2BUAs) are often designed to also be on the media path, rather than just to intercept signalling. This means that B2BUAs often implement an RTP or RTP Control Protocol (RTCP) stack as well, thus leading to separate multimedia sessions that the B2BUA correlates and bridges together. If not disciplined, this behaviour can severely impact the communication experience, especially when statistics and feedback information contained in RTCP messages get lost because of mismatches in the reported data.', changed pages to 16, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2017-02-22, changed IESG state to RFC Published)
2017-02-22
(System) RFC published