Open Bug 1421063 Opened 8 years ago Updated 3 years ago

Don't offer RTP header extensions with non-matching direction

Categories

(Core :: WebRTC: Signaling, enhancement, P3)

Product:
Core
Component:
WebRTC: Signaling
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox59 --- affected

People

(Reporter: drno, Unassigned)

Details

Example: v=0 o=mozilla...THIS_IS_SDPARTA-59.0a1 6383857165618045614 0 IN IP4 0.0.0.0 s=- ... a=recvonly a=extmap:1/sendonly urn:ietf:params:rtp-hdrext:ssrc-audio-level a=extmap:2 urn:ietf:params:rtp-hdrext:sdes:mid ... It makes no sense to offer to send the ssrc-audio-level RTP header extension if we are going to receive the RTP stream only. In this case we should not offer that extension.
Rank: 25
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.