Yes, I agree subject to the outcome of WebRTC's API. I think this is an area that can remain in the area of experimentation. ORTC Lib stubbed this API because it was not friendly to applications that are full apps and not browser based and they did not make sense for applications with the assumptions that were originally designed. Perhaps that has or will change though.
As far as I can tell, there are no implementations of the identity mechanism in ORTC and only one in WebRTC. Should we mark it as "at risk"?
Related WebRTC 1.0 issue: w3c/webrtc-pc#1074
The text was updated successfully, but these errors were encountered: