[foms] Proceedings to FOMS

Jeroen Wijering jeroen at longtailvideo.com
Sun Oct 10 04:28:49 PDT 2010

Hey everyone,

I have a question on the "DRM" community goal:

*) Show a demo of how to use DRM with WebM

I think supporting "real" DRM is not required per se. It might be more about offering publishers different ways to protect video content. In the end there's a tradeoff between decent content protection ánd a decent way for users to legidly access the content (cross-platform, fair prices, etc).

That said, there seem to be three general mechanisms for content protection:

*) URL signing (all CDNs / Flumotion): The URL to a video is signed with an MD5/SHA1 digest that includes geo, ip, time, referrer or user-agent restrictions. Protects good against leeching but not really against downloading. Implementation is easy (small module / script) and solely serverside.
*) Data encryption ( Apple HLS / RTMPE): Blocks of video data are encrypted on the server and decrypted inside the client. Protects good against both leeching and downloading. Both serverside and Client-side work is needed though. This can be both in-browser (e.g. by adopting Apple's AES-128 encryption), but it can also be done in javascript: get video data using websockets » decrypt data » use something like videoTag.append(videoData).
*) Rights management (PlayReady, FlashAccess): Individual client access to individual files is centrally managed. Protects good against both leeching and downloading; access can even be revoked. Client-side work is needed, probably inside the UA since the JS layer can be easily compromised. Serverside work is needed too, since there's no "open DRM" server available (contradictio in terminis?). 

Is this a decent overview; are there content protection schemes missing? What is already possible with currently available tools; and what would be interesting to implement?

Kind regards,


> Hi everyone,
> let me start by saying a big thank you to all participants of FOMS - we had a great two days with lots of solution-focused discussions. There was a strong bias towards solving adaptive HTTP streaming, but that just shows that this is the time to do something about it.
> I've updated the Website at http://www.foms-workshop.org/foms2010OVC/ with notes, uploaded the slides, and put links in to blog posts that attendees wrote. Go forage around, in particular in the Proceedings.
> One thing I'd like help with is the Community Goals. We weren't as thorough as in previous years in getting each breakout group to write down a short-term and a long-term goal. So, I have tried to extrapolate some of these goals from the discussion notes. Here's what I've arrived at:
> http://www.foms-workshop.org/foms2010OVC/pmwiki.php/Main/CommunityGoals
> If you have any others to add, please feel free to edit the wiki directly or email a reply.
> There's lots of stuff to do for open media in the coming year and I look forward to the progress made by the next FOMS!
> Cheers,
> Silvia.
> _______________________________________________
> foms mailing list
> foms at lists.annodex.net
> http://lists.annodex.net/cgi-bin/mailman/listinfo/foms

More information about the foms mailing list