- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Sat, 21 Apr 2018 01:41:18 +0000
- To: public-webrtc-logs@w3.org
I don't understand why we didn't just add a "reofferCodecs" parameter to `RTCAnswerOptions` to address this (https://github.com/w3c/webrtc-pc/pull/988). It would be so simple to implement... Looking at the Jan 25 2017 VI minutes, it looks like the conclusion was "we'll try to solve this in JSEP first"? Given that the "MAY" doesn't really solve this (it just "MAYbe" solves it), maybe it's time to reopen PR #988? -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1838#issuecomment-383258196 using your GitHub account
Received on Saturday, 21 April 2018 01:41:22 UTC