[Bug 10902] <video> element needs to support some form of DRM solution


--- Comment #3 from John Foliot <jfoliot@stanford.edu> 2010-10-01 00:01:43 UTC ---
(In reply to comment #1)
> HTML is a presentation layer that can embed flash, silverlight, MP4, Ogg, AVI,
> or a host of other formats,  They are formats.  The problem of DRM belongs to
> them, not this layer.

Does HTML5 'embed' MP4/OGG/WebM content, or does it render it, by using the
browser as a native player and linking (using SRC=) to the file? Assuming a
video which has some form of DRM solution (MP4 with AES encryption?) is linked
using the video element, how does the browser know that the end user is
authorized (or not authorized) to see this video?

Embedding Flash or Silverlight into a webpage *does* hand off DRM to the
player, but with <video> the browser *is* the player (complete with native and
scripted controls, etc.).

I'll pose this as a question: How would Limelight Networks
(http://www.limelightnetworks.com/) use the <video> element to stream videos to
the web, yet at the same time prevent piracy of their clients' commercial

I am sensitive to the many voices that are opposed to DRM (and in fact I am
philosophically opposed to that idea myself), however this is a topic which
must be answered in some way or other if the <video> element is to be used by
more than just hobbyists. I have heard first hand that HTML5's lack of DRM
solutions is a major impediment to commercial adoption.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 1 October 2010 00:01:47 UTC