[webrtc-extensions] Not clear what should happen if header extensions are inconsistent across bundled transports (#140)

henbos has just created a new issue for https://github.com/w3c/webrtc-extensions:

== Not clear what should happen if header extensions are inconsistent across bundled transports ==
Quoting @alvestrand out of context from https://github.com/w3c/webrtc-extensions/issues/132#issuecomment-1336412605:

> (It's a side effect of the Unified Plan decision that headers are negotiated per media session, but the result has to be consistent across all media sections bundled to a single transport.)

That made me wonder, what if I use BUNDLE and on transceiverA I set header extension X but not Y and on transceiverB I set header extension Y but not X.

If I'm reading the spec right, it doesn't look like we're ensuring consistency here. Does that mean the SDP offer may be rejected?

Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/140 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 31 January 2023 14:20:24 UTC