Bug 186188 – Need to implement WebRTC "Unified Plan" for multiple streams

• Status: NEW
• Component: WebRTC

[Clement Wehrung]

Firefox only supports unified plan and Chrome has now aggressively started moving towards it. Chrome has started supporting both, will move to unified plan by default soon and expects to completely drop support for Plan B by 2019. 

https://bugs.chromium.org/p/chromium/issues/detail?id=465349

Testing: https://groups.google.com/forum/#!searchin/discuss-webrtc/unified-plan$20plan-b%7Csort:date/discuss-webrtc/x8lcqHRlWmA/2ycvCHE4AwAJ

The following email provides their expected timeline: https://groups.google.com/forum/#!searchin/discuss-webrtc/unified$20plan%7Csort:date/discuss-webrtc/9mVuJ7g3vgs/0yCYoRoxBAAJ

"End of April 2018: “Unified Plan” and the new APIs stabilizes. We encourage everyone to switch to UnifiedPlan semantics and the new APIs.

July 2018: Default SdpSemantics changes to UnifiedPlan. APIs listed under “Removed APIs” (except CreateSender) are removed at the same time.

No earlier than end of year 2018: PlanB semantics removed and UnifiedPlan becomes the only option."

[Clement Wehrung]

Chrome spec: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/Qgwfl-nD0Zs

[Philipp Hancke]

the timeline in that post turned out to be somewhat unrealistic (in particular given that this would have interop impact with Safari).

https://webrtc.org/web-apis/chrome/unified-plan/ has a more up-to-date timeline.