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

Considering non-BUNDLE is mostly for backwards-compat, is there any reason why we would even want to support different header extensions on different m= sections? Maybe the API should be per-kind (audio or video) but be copy-pasted to all m= sections of the same kind, regardless if BUNDLE or non-BUNDLE is used. Why make it complicated for a use case that's not interesting?

Just a thought... thinking aloud

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/140#issuecomment-1410454435 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:28:45 UTC