ORTC Support in Edge Chromium

tomorgan  Thanks for your comments and suggestions.  You are correct that the existing ORTC implementation in Edge is not supported in the new Edge builds.  Until we can provide more detailed guidance, here are some things that developers should consider. 

1. Developers who were using Edge ORTC to build WebRTC 1.0 applications running on all browsers via the adapter.js shim should test those applications on the new Edge code base.  Since the adapter.js shim correctly detects the difference between the new and older Edge code bases we believe that many of those applications will continue to run or will require only minor changes. If you are encountering issues with adapter.js applications on the new Edge code base, please let us know so we can investigate the problems. 

2. Developers who were supporting Chrome "Plan B" in their applications are advised to test their "Plan B" applications on the new Edge code base.  Since "Unified Plan" is the default in the new Edge code base, you will specifically need to request "Plan B" when constructing an RTCPeerConnection, as follows: 

pc = new RTCPeerConnection({sdpSemantics: 'plan-b' }); 

It is our expectation that existing "Plan B" applications will run on the new Edge code base with little or no changes.  If you are encountering issues, please let us know. 

3. Developers that were developing native ORTC applications but did not support "Plan B" in Chrome are advised to consider migrating to "Unified Plan" in the new Edge code base.  Some advice on adoption of "Unified Plan" is available here: 

https://webrtc.internaut.com/itexpo-2019/slides/ITEXPO-2019_Leveraging_WebRTC.pdf

While "Unified Plan" is still a "work-in-progress", it does support the RtpSender and RtpReceiver objects from ORTC as well as the RtpTransceiver, and can provide standards-based functionality not present in Edge ORTC (such as support for simulcast).  "Unified Plan" also provides support for standards-based statistics beyond what was available in Edge ORTC. 

Documentation on the APIs supported in the new Edge code base are available here: 

WebRTC 1.0 Candidate Recommendation: 

https://rawgit.com/w3c/webrtc-pc/master/webrtc.html

WebRTC-Stats API: https://w3c.github.io/webrtc-stats/

WebRTC-ICE: https://w3c.github.io/webrtc-ice/

RTCQuicTransport trial documentation: https://github.com/shampson/RTCQuicTransport-Origin-Trial-Documentation

A final note.  While not appropriate for use in production applications, the new Edge code base also provides support for experimental APIs such as those for the QuicTransport and IceTransport objects (inspired by ORTC): 

https://developers.google.com/web/updates/2019/01/rtcquictransport-api