RFC 8858: Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)
In plain English — editorial summary, not part of the RFC
This document defines a new Session Description Protocol (SDP) media-level attribute, 'rtcp-mux-only', that can be used by an endpoint to indicate exclusive support of RTP and RTP Control Protocol (RTCP) multiplexing. The document also updates RFC 5761 by clarifying that an offerer can use a mechanism to indicate that it is not able to send and receive RTCP on separate ports.
Document record
- Document ID
- RFC8858
- Published
- January 2021
- Authors
- C. Holmberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 5761
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8035Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP MultiplexingCurrent
November 2016
- RFC 8829JavaScript Session Establishment Protocol (JSEP)Obsoleted
January 2021
- RFC 9429JavaScript Session Establishment Protocol (JSEP)Current
April 2024
- RFC 8850Controlling Multiple Streams for Telepresence (CLUE) Protocol Data ChannelCurrent
January 2021
- RFC 8843Negotiating Media Multiplexing Using the Session Description Protocol (SDP)Obsoleted
January 2021
- RFC 9143Negotiating Media Multiplexing Using the Session Description Protocol (SDP)Current
February 2022
- RFC 8122Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)Updated
March 2017
- RFC 7825A Network Address Translator (NAT) Traversal Mechanism for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
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?