If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[meta] Validate that no unsupported changes have been made on SDP passed to SetLocal/Remote

NEW
Unassigned

Status

()

Core
WebRTC: Signaling
P3
normal
Rank:
21
3 years ago
a month ago

People

(Reporter: bwc, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Comment hidden (empty)
(Reporter)

Updated

3 years ago
Duplicate of this bug: 928081
(Reporter)

Updated

2 years ago
Summary: Validate that no unsupported changes have been made on SDP passed to SetLocal/Remote → [meta] Validate that no unsupported changes have been made on SDP passed to SetLocal/Remote
Keywords: meta
I'm giving this a priority so we can do a bug breakdown.  

Byron -- would it be reasonable (time-wise) for you to do a bug breakdown on this between now and the end of this month (November)?  Or are you too swamped?
Rank: 19
Flags: needinfo?(docfaraday)
Keywords: meta
Priority: -- → P1
One issue that came up recently when abr was helping a developer:  The dev made changes to the SDP that we chose not to act on, but we currently fail silently instead of making setLocalDescription fail.  That would be a good first bug to file (blocking this bug) and fix.
(Reporter)

Comment 4

2 years ago
We have a partial breakdown in the code over here: https://dxr.mozilla.org/mozilla-central/source/media/webrtc/signaling/src/jsep/JsepSessionImpl.cpp?case=true&from=JsepSessionImpl.cpp#1773

Some time/thought needs to be put into this. I suspect simulcast is going to keep me pretty busy.
Flags: needinfo?(docfaraday)
Given our other priorities, I need to lower this slightly (to a high P2).
Rank: 19 → 21
Priority: P1 → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.