CurrentPROPOSED STANDARDIETF stream

RFC 8035: Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP Multiplexing

In plain English — editorial summary, not part of the RFC

This document updates RFC 5761 by clarifying the SDP offer/answer negotiation of RTP and RTP Control Protocol (RTCP) multiplexing. It makes it clear that an answerer can only include an "a=rtcp-mux" attribute in a Session Description Protocol (SDP) answer if the associated SDP offer contained the attribute.

Document record

Document ID
RFC8035
Published
November 2016
Authors
C. Holmberg
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
7
Also known as
Updates:
RFC 5761

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/8035-session-description-protocol-sdp-offer-answer-clarifications-for-rtp-rtcp-multip