--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/1a4c04a8-0515-4127-909c-8cb4fc442a98%40googlegroups.com.
Implementations MAY choose to reject attempts by the application to set the multiplexing policy to "negotiate".
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CABc02_%2BNhYDPeKC%3DCpuF%3DoUZ7%2BwB_wicuJFG0KB5n2Yxha8W2Q%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAK35n0Y8A-Si1e32oQh6Am8uST45gjCscLSWFS2-NoJqrttr%3DQ%40mail.gmail.com.
Huh, can you mark it "At risk" in the specification then?
☆PhistucK
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CABc02_JCc%2BRHL%3DZmpQmmFVbFRZZrzfFt8T5-2jy%3DhnriFXts3Q%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAK35n0bkqmHMQRk1Kf0bjJR8Ea6M6r8zHoiomrDEe66urBH-Xg%40mail.gmail.com.
No real idea, but if you already know the feature is at a high risk, I suspect sooner is better than later.
☆PhistucK
On Fri, Jan 20, 2017 at 8:08 AM, 'Taylor Brandstetter' via discuss-webrtc <discuss...@googlegroups.com> wrote:
Should that happen now, or when WebRTC advances beyond the "Working Draft" stage? (just a question about W3C process)I'll also make sure we follow the Blink deprecation process, by the way: https://www.chromium.org/blink/deprecating-features
On Thu, Jan 19, 2017 at 9:46 PM, PhistucK <phis...@gmail.com> wrote:
Huh, can you mark it "At risk" in the specification then?
☆PhistucK
☆PhistucK
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/1a4c04a8-0515-4127-909c-8cb4fc442a98%40googlegroups.com.
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CABc02_%2BNhYDPeKC%3DCpuF%3DoUZ7%2BwB_wicuJFG0KB5n2Yxha8W2Q%40mail.gmail.com.
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAK35n0Y8A-Si1e32oQh6Am8uST45gjCscLSWFS2-NoJqrttr%3DQ%40mail.gmail.com.
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CABc02_JCc%2BRHL%3DZmpQmmFVbFRZZrzfFt8T5-2jy%3DhnriFXts3Q%40mail.gmail.com.
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/b6e3b2ec-3d10-4659-a588-fc9090641f03%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CABc02_KMpWce78nnp%3DOa_mCLBhqTW9nsJFcTWE9JdsXiFR3Vag%40mail.gmail.com.
☆PhistucK
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/b6e3b2ec-3d10-4659-a588-fc9090641f03%40googlegroups.com.
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/da8766d6-eb24-40af-a36a-7cfcee9265dc%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/bf908fca-50c8-4333-b202-3d7a14e19194%40googlegroups.com.
Does this mean the removal will be done in M58?
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/ce5c1134-fc10-4cb4-82df-37d73bcd305d%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/ce4d9f15-b946-44c5-99ec-1074c5726249%40googlegroups.com.
Some newer applications that do not require backward compatibility with peers that cannot multiplex RTCP might choose to not implement separation of RTP and RTCP. Examples of such applications are W3C WEBRTC [W3C.WD-webrtc-20120209] applications, that are not required to interoperate with non-WEBRTC clients.
I understand the desire for simplification but as already stated in this conversations some platforms/apps are reliant on this at present so please be cautious about removing this.
surely the API specification needs to clearly state what API options are mandatory or optional to implement
Could you clarify whether https://tools.ietf.org/html/draft-ietf-mmusic-mux-exclusive-11 be supported for the "require" option?
I understand the desire for simplification but as already stated in this conversations some platforms/apps are reliant on this at present so please be cautious about removing this.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/3e03ebba-30f7-4c66-9088-f4608c0ae6c4%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
Hi Peter,I understand what is in JSEP but I don't believe the reference to JSEP in the W3C Spec is sufficient and I personally only interpreted it as a reference to the description on what the policy means for ICE candidate gathering as it states: "As described in [JSEP] (section 4.1.1.), the RtcpMuxPolicy affects what ICE candidates are gathered to support non-multiplexed RTCP."
It does not, at least in my interpretation, defer to JSEP for what policies need to be implemented surely the API specification needs to clearly state what API options are mandatory or optional to implement.
Could you clarify whether https://tools.ietf.org/html/draft-ietf-mmusic-mux-exclusive-11 be supported for the "require" option?The issues around the exclusive option are also discussed in draft-ietf-mmusic-mux-exclusive which for example includes the text below:Some newer applications that do not require backward compatibility with peers that cannot multiplex RTCP might choose to not implement separation of RTP and RTCP. Examples of such applications are W3C WEBRTC [W3C.WD-webrtc-20120209] applications, that are not required to interoperate with non-WEBRTC clients.I understand the desire for simplification but as already stated in this conversations some platforms/apps are reliant on this at present so please be cautious about removing this.
You received this message because you are subscribed to a topic in the Google Groups "discuss-webrtc" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/discuss-webrtc/eM57DEy89MY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/3e03ebba-30f7-4c66-9088-f4608c0ae6c4%40googlegroups.com.
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/823faa2d-0cfe-4e8c-ac90-f4f272206963%40googlegroups.com.
We've updated the console message to say "may be removed no earlier than M62, around October 2017"; see this thread for the motivation.We don't have any more specific plans than that, since we're waiting to see how the usage statistics change. But if they're something that's preventing you from implementing muxed RTCP, let us know so we can help (if possible).
On Fri, Jun 30, 2017 at 4:19 AM, Padma Prasad Dharmaraja <prasa...@gmail.com> wrote:
When is rtcpmuxPolicy:negotiate offically getting deprecated.Any time lines or any specific Chrome version after which the rtcpMuxPolicy:require is mandatory.
On Friday, 23 December 2016 10:47:36 UTC+5:30, Taylor Brandstetter wrote:As of the most recent Chrome Canary build, the default RTCP multiplexing policy is "require", instead of "negotiate". This will affect the next Chrome release, M57.This means that offer/answer negotiation with an endpoint that doesn't support RTCP multiplexing will fail, resulting in the error: "ERROR_CONTENT. Session error description: Failed to setup RTCP mux filter." We can probably make this error more descriptive, but the bottom line is that setRemoteDescription will fail if the SDP does not contain "a=rtcp-mux".For any application that doesn't yet support RTCP multiplexing, you can get the old behavior by explicitly setting the RTCRtpMuxPolicy to "negotiate" in the RTCConfiguration. For example:pc = new RTCPeerConnection({rtcpMuxPolicy: "negotiate"})
Here are the related webrtc/chromium bug entries, for more background:
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/54e1e873-7bab-4cf6-ae1a-73013b4faade%40googlegroups.com.