- From: Tim Panton via GitHub <sysbot+gh@w3.org>
- Date: Mon, 30 Apr 2018 07:25:20 +0000
- To: public-webrtc-logs@w3.org
One thing I did yearn for when I was looking at this from a telco/pbx perspective a few years ago was the ability to use the _same_ client certificate in webRTC as was used in the https which downloaded the origin page. The reason being that telcos like to split the media from the signalling at as early stage as possible, this might allow the media provenance to be identified in a media server (and billed for) in a way that the IdP mechanism would struggle to do. This could probably be done by an extension of the existing IndexDb certificate storage. However I'm not convinced that there is any current demand for it, you'd need to ask others closer to the PBX space to know. -- GitHub Notification of comment by steely-glint Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1853#issuecomment-385328096 using your GitHub account
Received on Monday, 30 April 2018 07:25:23 UTC