- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Jun 2019 13:53:33 +0000
- To: public-webrtc-logs@w3.org
@henbos > I'm saying the WG is just as confused as you are ;) I can ask around (since I also work in Chrome) but it appears Chrome is doing something outside of specs of the WG. Am not trying to assess blame. `goog-remb` is described by webrtcHacks (https://webrtchacks.com/wp-content/themes/parament/custom-pages/sdp/68.html) as > The prefix goog- means that is still something implemented only by Google and non standard. however, Firefox 69 includes `goog-remb` in the SDP of Mozilla WebRTC implementation (http://lists.w3.org/Archives/Public/public-webrtc-logs/2019Jun/0105.html) > Chromium `a=rtcp-fb:102 goog-remb` > Firefox `a=rtcp-fb:120 goog-remb` The various concerns can sort out the blame, if any, for extending SPD beyond a given specification. Firefox still non-standard `mozCaptureStream()`. Am asking _how_ the feature is intended to work. -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2213#issuecomment-505019803 using your GitHub account
Received on Monday, 24 June 2019 13:53:36 UTC