Bug 186188

Summary:	Need to implement WebRTC "Unified Plan" for multiple streams
Product:	WebKit	Reporter:	Clement Wehrung <cwehrung>
Component:	WebRTC	Assignee:	Nobody <webkit-unassigned>
Status:	NEW ---
Severity:	Major	CC:	fippo, lee, youennf
Priority:	P2
Version:	Safari 11
Hardware:	All
OS:	All

Description Clement Wehrung 2018-06-01 01:27:33 PDT

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."

Comment 1 Clement Wehrung 2018-06-01 01:29:32 PDT

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

Comment 2 Philipp Hancke 2018-06-06 01:42:55 PDT

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.