Open Bug 1805484 Opened 1 year ago

We should enforce bundle-policy as answerer

Categories

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

Product:
Core
Component:
WebRTC: Signaling
Type:
defect

Tracking

()

People

(Reporter: bwc, Unassigned)

Details

(Keywords: parity-chrome, parity-edge, parity-safari)

This is causing a failure in bundle.https.html

Spec says that when using 'max-bundle', and the other side does not do bundle, we should only use one transport, on the first m-section. Right now, that will happen when we are the offerer (through the use of a=bundle-only), but when we're the answerer we will open the extra transports. I'm guessing we have a similar bug for 'balanced'.

I doubt this actually breaks anything in practice, but we should fix.

You need to log in before you can comment on or make changes to this bug.