New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 4 users

Issue metadata

Status: Fixed
Last visit 27 days ago
Closed: Jan 21
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Sign in to add a comment

Issue 908377: RTCConfiguration.offerExtmapAllowMixed

Reported by, Nov 26 Project Member

Issue description

As of M-71, Chrome will support two-byte RTP header extensions as defined in RFC8285. One- and two-byte RTP header extensions can only be mixed in the same stream if the SDP attribute extmap-allow-mixed is supported by all clients. The problem with extmap-allow-mixed is that prior to Chrome 71, this attribute made the SDP parser to stop parsing due to a bug in the implementation.

The member RTCConfiguration.offerExtmapAllowMixed will therefore be added to make it configurable if the extmap-allow-mixed attribute should be offered or not.

See design doc at http://go/extmap for more details.

Comment 1 by, Nov 26

Status: Started (was: Untriaged)

Comment 2 by, Jan 7

Link to "Intent to Implement and Ship" thread with 3xLGTM:!topic/blink-dev/7z3uvp0-ZAc

Comment 3 by, Jan 9

Project Member

Comment 4 by, Jan 21

Status: Fixed (was: Started)
Tested on a Canary build.

If the RTCPeerConnection object is created as
pc = new RTCPeerConnection({offerExtmapAllowMixed:true});
the offer will include the SDP attribute a=extmap-allow-mixed.

Sign in to add a comment