On 2014-05-18 04:01, Boris Zbarsky wrote:
On 5/17/14, 7:30 PM, Jim wrote:
..
I summarized my understanding of the proposal in my last email to you.
I'm afraid I'm missing a crucial part of your proposal: how do you
plan to get the CDM to play along with it?
If the player is defined in a JS/EME web browser then the CDM would play
along. It does require that the JS component communicating with the CDM
via the EME is a standard. Netflix might refuse to support this
standard, but you could try.
If you are sandboxing the CDM, and if the CDM only verifies that it is
running in this sandbox, then it should make no difference if it is part
of a web browser or part of a dedicated media player, so it could be
re-purposed for use in such a media player.
This would allow the DRM media player to be kept out of the web. A
general declarative HTML extension could be used to invoke the player.
How is that fundamentally different from launching a plug-in?
This would keep DRM out of the web
How so, if the user experience is still seamless?
The web browser and DRM player are separate. The DRM player could
operate alone given a URL, and the player could be remote from the
browser for even more secure sandboxing. No DRM extensions would be
added to web standards.
The content distributors want the EME rather than such a solution so
they can lock the user into using their web base media player, adding
their own proprietary JS to complete player, and to be able to provide a
rich[sic] experience. This is what Mozilla have decided to support, not
the viewing of DRM movies. You don't need to take my word for it,
Netflix communicated this in the W3C mailing lists, but when pressured
to articulate their use cases they clammed up.
Jim
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance
