We’re hoping to be first here. I’m told that Chrome is implementing it, but I haven’t seen any actual evidence. I’m seeing lots of interest from my old colleagues at Microsoft, but [1].
[1] http://status.modern.ie/webrtcwebrtcv10api On 2014-05-02, at 14:19, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote: > Thanks, Martin! > > Do you know if other UAs are also implementing this API? > > On 2014-05-02, 4:09 PM, Martin Thomson wrote: >> Summary: >> WebRTC enables peer-to-peer communications. Identity features enable the >> identification of WebRTC peers using a generic identity provider interface. >> Stream isolation provides sites a way to foreswear access to media so that - >> in combination with identity - users can be sure that their media is being >> sent to a specific peer (and that media from that peer came from that peer). >> This enables secure calling that does not rely on trust in the web site or >> application that performs signalling. >> >> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=901261 >> Link to standard: http://dev.w3.org/2011/webrtc/editor/webrtc.html#identity >> Platform coverage: Desktop, Android, Firefox OS >> Estimated or target release: 32, Firefox OS 2.0 >> Preference behind which this will be implemented: >> media.peerconnection.identity.enabled (dom.messageChannel.enabled also needs >> to be true) >> >> _______________________________________________ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform >> > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform