3 ms·
From http://techblog.netflix.com/2010/12/html5-and-video-streaming.html http://techblog.netflix.com/2010/12/html5-and-video-streamin...: We expect to be able t
by rufo 16y ago
From http://techblog.netflix.com/2010/12/html5-and-video-streaming.html http://techblog.netflix.com/2010/12/html5-and-video-streamin...:
We expect to be able to publish a draft of a Netflix profile describing a limited subset of the MPEG DASH standard early next year. It will define the requirements for premium on-demand streaming services like ours and will take advantage of hooks included in the DASH standard to integrate the DRM technologies that we need to fulfill our contractual obligations to the content providers, thus covering the sixth item on our list.
They aren't very coy about saying they need DRM.
Even leaving the DRM aside, some sort of agreed-upon standard for items 1-5 and 7 would still be very helpful; these are all capabilities that are left to Flash or Silverlight for cross-platform capabilities, and I'd think there would be plenty of use cases that could find one or more of those very helpful. (Adaptive bitrate streaming would be a huge improvement, and I'm sure Justin.tv would love a cross-platform streaming video standard.)
- rwwmike 16y agoThe part I didn't really include is their list of 7 requirements, which are... 1-The acceptable A/V container formats (e.g. Fragmented MP4, WebM, etc.); 2-The acceptable audio and video codecs (e.g. H.264, VP8, AAC, etc.); 3-The streaming protocol (e.g. HTTP, RTP, etc.); 4-A way for the streaming protocol to adapt to available bandwidth; 5-A way of conveying information about available streams and other parameters to the streaming player module; 6-A way of supporting protected content (e.g. with DRM systems); 7-A way of exposing all this functionality into HTML5 So...yeah, definitely DRM. And not coy, as you point out.