Contact emails
h...@chromium.org, ptha...@chromium.org
Explainer
None. Feature is already in spec.
Design doc/Spec
http://w3c.github.io/webrtc-pc/#rtcpeerconnection-interface
https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-24
In addition to the spec, we’ll add an enum called “SdpFormat” into the RTCConfiguration dictionary, with an initial default of “plan-b”. When we change the default generated SDP, the default will be changed to “unified-plan; when usage of the “plan-b” value is sufficiently low, the item will be removed.
This feature will be behind the “WebRTCUnifiedPlan” runtime enabled feature flag.
Summary
Under this label, we’ll switch the RTCPeerConnection SDP mode for initial SDP offers from our current nonstandard format (“Plan B”) to the agreed-upon format (“Unified Plan” or “JSEP”).
Motivation
In the development of WebRTC, a long debate was had about the way multiple streams of audio or video data should be represented in SDP (“Plan A” and “Plan B”). While the bodies debated, Google shipped “Plan B”. The various standards bodies agreed on a variant of “Plan A”, now known as “Unified Plan”, and Firefox shipped according to that plan.
Chrome, Edge and Safari all ship “Plan B” in the default first offer, which creates interoperability problems.
Eradicating PlanB and fully supporting Unified Plan will unlock several features that
Risks
Interoperability and Compatibility
The biggest interoperabillity risk is with installed Chrome when the default is changed. Chrome versions older than <number> will not be able to parse Unified Plan, and thus will be unable to set up WebRTC sessions with Chrome unless the flag is used to force “old mode” (which is undesirable).
Edge: Under consideration
Firefox: Shipped
Safari: No signals
Web developers: In favor of interoperability. 177 stars on https://bugs.chromium.org/p/chromium/issues/detail?id=465349
Interoperability can be tested using KITE: http://dashboard.cosmosoftware.io:4443/testing/public#
Ergonomics
This is part of the WebRTC API.
Activation
The intent is to take a phased approach - first to allow people to test the feature by changing the default, then changing the default and allowing people to opt out (hopefully few do), and then by removing the ability to use the old style (and rip out the code).
Debuggability
SDP produced and consumed, and errors, can be observed using chrome://webrtc-internals
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes
OWP Launch tracking bug:
Is this feature fully tested by web-platform-tests?
Chrome to Chrome: Yes. web-platform-tests’ webrtc/ subdirectory is the impacted test suite.
We believe shipping this feature will improve the number of tests passed, since the tests assume that Unified Plan is in effect.
Link to entry on the feature dashboard
https://www.chromestatus.com/features/5723303167655936
Requesting approval to ship?
No. The transition plan needs fleshing out before we ship this.
Contact emails
h...@chromium.org, ptha...@chromium.org
Explainer
None. Feature is already in spec.
Design doc/Spec
http://w3c.github.io/webrtc-pc/#rtcpeerconnection-interface
https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-24
In addition to the spec, we’ll add an enum called “SdpFormat” into the RTCConfiguration dictionary, with an initial default of “plan-b”. When we change the default generated SDP, the default will be changed to “unified-plan; when usage of the “plan-b” value is sufficiently low, the item will be removed.
This feature will be behind the “WebRTCUnifiedPlan” runtime enabled feature flag.
Summary
Under this label, we’ll switch the RTCPeerConnection SDP mode for initial SDP offers from our current nonstandard format (“Plan B”) to the agreed-upon format (“Unified Plan” or “JSEP”).
Motivation
In the development of WebRTC, a long debate was had about the way multiple streams of audio or video data should be represented in SDP (“Plan A” and “Plan B”). While the bodies debated, Google shipped “Plan B”. The various standards bodies agreed on a variant of “Plan A”, now known as “Unified Plan”, and Firefox shipped according to that plan.
Chrome, Edge and Safari all ship “Plan B” in the default first offer, which creates interoperability problems.
Eradicating PlanB and fully supporting Unified Plan will unlock several features that
Interoperability and Compatibility
The biggest interoperabillity risk is with installed Chrome when the default is changed. Chrome versions older than <number> will not be able to parse Unified Plan, and thus will be unable to set up WebRTC sessions with Chrome unless the flag is used to force “old mode” (which is undesirable).
Edge: Under consideration
Requesting approval to ship?
No. The transition plan needs fleshing out before we ship this.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOqqYVE383T2uu-4SEr%3DGSV_ZMXJkTLRv4Myq%2BS6wp4JXuRZEQ%40mail.gmail.com.