Guidelines for End-to-End Support of the RTP Control Protocol in Back-to-Back User Agents
RFC 8079, “Guidelines for End-to-End Support of the RTP Control Protocol in Back-to-Back User Agents”, is a Proposed Standard document published in February 2017 by L. Miniero, S. Garcia Murillo, V. Pascual. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8079 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8078 Managing DS Records from the Parent via CDS/CDNSKEY
- RFC 8080 Edwards-Curve Digital Security Algorithm for DNSSEC
- RFC 8077 Pseudowire Setup and Maintenance Using the Label Distribution Protocol
- RFC 8081 The "font" Top-Level Media Type
- RFC 8076 A Usage for Shared Resources in RELOAD
- RFC 8082 Using Codec Control Messages in the RTP Audio-Visual Profile with Feedback with Layered Codecs
- RFC 8075 Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol
- RFC 8083 Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions