Towards usage restrictions in HTML? - RMLL 2013

Slide 1

Slide 1 text

Towards usage restrictions in HTML? [email protected] RMLL, Bruxelles 2013-07-8

Slide 2

Slide 2 text

Current status:

Slide 3

Slide 3 text

Flash required

Slide 4

Slide 4 text

HTML5 video codecs Control (through patents) how one can make videos on the web

Slide 5

Slide 5 text

HTML video restrictions Control (through DRM) how one can watch videos on the web

Slide 6

Slide 6 text

What's “EME”? Encrypted Media Extension

Slide 7

Slide 7 text

How does EME work?

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

Welcome to W3C Newspeak “the Open Web”

Slide 10

Slide 10 text

“Can you highlight how robust content protection can be implemented in an open source web browser?” he asked. “How do you guard against an open source web browser simply being patched to write the frames/samples to disk to enable (presumably illegal) redistribution of the protected content?” Netflix’s Mark Watson responded to the message and acknowledged that strong copy protection can’t be implemented in an open source Web browser. He deflected the issue by saying that copy protection mechanisms can be implemented in hardware, and that such hardware can be used by open source browsers.

Slide 11

Slide 11 text

Some examples of features that would be in scope for the updated HTML specification: - additions to the HTMLMediaElement element interface, to support use cases such as live events or premium content; for example, additions for: - facilitating adaptive streaming (Media Source Extensions) - supporting playback of protected content - adaptive images - additions to the HTML Canvas 2D Context (HTML Canvas 2D Context, Level 2) - additional new elements and attributes for Web Components

Slide 12

Slide 12 text

On Tue, 29 Nov 2011 10:09:54 GMT In Requirements for Home Networking Scenarios At http://www.w3.org/TR/2011/NOTE-hnreq- 20111201/#content-protection 4.3.10 Content Protection Conforming specifications should support the content protection mechanism for a content item used by a content server in order to play back that content item. Conforming specifications must provide a graceful failure model when a content protection mechanism is not supported.

Slide 13

Slide 13 text

“W3C standards do not normatively require proprietary components. Neither does EME. But in practice, the motivating use-case for EME (let's just say Hollywood content) does require proprietary components.” – Mark Watson

Slide 14

Slide 14 text

“You can certainly implement EME and a CDM under whatever open source terms you choose.” – Mark Watson

Slide 15

Slide 15 text

Keeping DRM out of the web?

Slide 16

Slide 16 text

It's already there… Netflix – Google Chrome OS Netflix – Microsoft “PlayReady”

Slide 17

Slide 17 text

What can we do? Pressure W3C to refuse the stamp of approval of the “open Web”… if you care.