W3C home > Mailing lists > Public > public-web-and-tv@w3.org > June 2018

Re: [media-and-entertainment] Use of WebRTC for media content distribution

From: François Daoust via GitHub <sysbot+gh@w3.org>
Date: Wed, 27 Jun 2018 07:57:41 +0000
To: public-web-and-tv@w3.org
Message-ID: <issue_comment.created-400578775-1530086260-sysbot+gh@w3.org>
> Supporting the Encrypted Media Extensions API for WebRTC media content distribution could be considered as one of requirements from Media & Entertainment IG. WebRTC 1.0 media stream is secured by SRTCP (Secure Real-time Transport Protocol) but it has no aspect of content protection.

Interestingly, end-to-end encryption scenarios were discussed by the WebRTC WG last week during their F2F. See [summary of e2e encryption discussions](https://lists.w3.org/Archives/Public/public-webrtc/2018Jun/0175.html). Content protection for media distribution would be use case 3 in that summary. 

Note the "It is unclear whether there is sufficient interest in that area" in that email, which suggests that the work won't happen unless people weigh in (the Media & Entertainment IG could do that) and contribute (at a per company level, not much the IG can do there).

Solution-wise, the starting point suggested in the email would use the [Identity provider framework](https://www.w3.org/TR/2018/CR-webrtc-20180621/#sec.identity-proxy) (which will soon move to a separate spec, partly because it is not yet supported across browsers) and [isolated media streams](https://www.w3.org/TR/2018/CR-webrtc-20180621/#isolated-media-streams) coupled with a yet-to-define double encryption mechanism.

-- 
GitHub Notification of comment by tidoust
Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/issues/1#issuecomment-400578775 using your GitHub account
Received on Wednesday, 27 June 2018 07:57:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 27 June 2018 07:57:46 UTC