Re: [webrtc-pc] RTCRtcpMuxPolicy of "negotiate" should be marked as an "at-risk" feature

There's an Intent do Deprecate about "negotiate" on blink-dev relevant
 to this:

What is the current state of interop with regards to "negotiate"? 
(Here "interop" means "works the same", not two browsers talking to 
each other.) Is it safe to assume that it works roughly the same in 
Chrome and Firefox due to the shared libwebrtc code?

@ShijunS, will Edge support "negotiate" when RTCPeerConnection ships, 
or is this something that would be valuable to get rid of?

GitHub Notification of comment by foolip
Please view or discuss this issue at 
using your GitHub account

Received on Thursday, 16 February 2017 04:46:56 UTC