UNLIMITED FREE
ACCESS TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Select Your Free Newsletters

Industry Newsletters

Select Your Free Product Alerts

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

IETF RFC 8035

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

active, Most Current
Buy Now
Organization: IETF
Publication Date: 1 November 2016
Status: active
Page Count: 7
scope:

Introduction

RFC 5761 [RFC5761] specifies how to multiplex RTP data packets and RTP Control Protocol (RTCP) packets on a single UDP port, and how to negotiate usage of such multiplexing using the SDP offer/answer mechanism [RFC3264] with an "a=rtcp-mux" attribute. However, the text is unclear on whether an answerer is allowed to include the attribute in an answer even if the associated offer did not contain an attribute.

This document updates RFC 5761 [RFC5761] by clarifying that an answerer can only include an "a=rtcp-mux" attribute in an answer if the associated offer contained the attribute. It also clarifies that the negotiation of RTP and RTCP multiplexing is for usage in both directions

Document History

IETF RFC 8035
November 1, 2016
Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP Multiplexing
Introduction RFC 5761 [RFC5761] specifies how to multiplex RTP data packets and RTP Control Protocol (RTCP) packets on a single UDP port, and how to negotiate usage of such multiplexing using the...

References

This document references:
RFC 3264 - An Offer/Answer Model with the Session Description Protocol (SDP)
Published by IETF on June 1, 2002
A description is not available for this item.
This document is referenced by:
TS 124 371 - Universal Mobile Telecommunications System (UMTS); LTE; Web Real-Time Communications (WebRTC) access to the IP Multimedia (IM) Core Network (CN) subsystem (IMS); Stage 3; Protocol specification
Published by ETSI on May 1, 2022
The present document provides the details for allowing Web Real-Time Communication (WebRTC) IMS Clients (WIC) to access the IP Multimedia (IM) Core Network (CN) subsystem. The present document is...
This document is referenced by:
TS 123 334 - Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface: Procedures descriptions
Published by ETSI on July 1, 2022
Annex G of 3GPP TS 23.228 [2] gives out an IMS Application Level Gateway (IMS-ALG) and IMS Access Media Gateway (IMS-AGW) based reference model to support NAPT-PT, gate control and traffic policing...
This document is referenced by:
TS 124 229 - Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3
Published by ETSI on January 1, 2024
The present document defines a call control protocol for use in the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP), and the associated Session...
This document is referenced by:
IETF RFC 8858 - Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)
Published by IETF on January 1, 2021
Abstract 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...
View Less
View All
Advertisement