RFC 8079: Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in Back-to-Back User Agents (B2BUAs)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8079
- Published
- February 2017
- Authors
- L. Miniero; S. Garcia Murillo; V. Pascual
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 16
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8081The "font" Top-Level Media TypeCurrent
February 2017
- RFC 8076A Usage for Shared Resources in RELOAD (ShaRe)Current
March 2017
- RFC 8082Using Codec Control Messages in the RTP Audio-Visual Profile with Feedback with Layered CodecsCurrent
March 2017
- RFC 8088How to Write an RTP Payload FormatUpdated
May 2017
- RFC 8089The "file" URI SchemeUpdated
February 2017
- RFC 8068Session Initiation Protocol (SIP) Recording Call FlowsCurrent
February 2017
- RFC 8098Message Disposition NotificationCurrent
February 2017
- RFC 8048Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceCurrent
December 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?