For that kind of DRM to work, your browser would have to be turned into a black box that is difficult to inspect, designed to be controlled entirely from remote, and illegal to alter.
If this series of events were to unfold, closing the browser would not be done to benefit the content industry directly. They don't need that to deliver content, because they can always just put out an app and pump out their stuff that way. They can also just make a plugin if they want to deliver video content through the browser - which would possible with current technology today. That's not why they are proposing this. Instead this move would serve solely to restrict user freedom to use anything but approved apps for approved content.
So to make it clear why this outrage exists: there is absolutely no technical need to include this natively in HTML5. The proposal does not aim to give something to the content industry, it is instead designed to take something away from everybody else. That's not a subtle difference. But, as I said earlier, it's doubtful it will/could play out this way. The only way to achieve this "dream" is by making the web as it exists today illegal to use, and then enforce that ban through extensive ISP surveillance. In which case a DRM solution for HTML5 wouldn't matter anyway.
ORLY? How does encryption work then? One could say "in order to properly encrypt your stuff, you actually need to make sure nobody is outside your window with binoculars", but that's not the job of encryption is it. I guess it would ultimately boil down to possession of private and public keys, and making it illegal to transmit those. So? As you said, they can deliver their stuff in proprietary apps already, what is lost when they use proprietary keys instead?
Fortunately, that's still a bit too expensive to consider. Also, it will be broken by the first bored hacker with a soldering iron.
We're talking about a web standard, not some company's broken software.
That aside, not having DRM for html5 would likely do more harm to the open web than not doing it. Take ABC for example, they only let you view their content through flash or through a native app. This hurts the open web more than giving them DRM in html5.
They are already closing the "analog loophole" everywhere else with HDCP and DRM enabled theater projectors, it's pretty clear that's where "content owners" want to be.
With DRM built in, you can adhere to the standards all you want, you still can't render all the content unless have access to the secret keys, which can only be granted to you by the powers-that-be.
The only viable client-software will be that controlled by a few major companies in cahoots with the content-industry, and they will dictate terms on the rest of us, tearing down whatever "open" is left. Average users are not going to install an open, non-DRM client if that doesn't allow them to use Hulu, Netflix, YouTube, BBC etcetera.
Thanks to "open", the total monopoly if Microsoft's IE6 was broken and the web moved forward. With DRM, that will no longer be a viable option. Google, Microsoft and Apple together will decide how we experience the web.
If you think "open" will still play a role in that, you must haven been living under a rock for the past 10 years. Even Google's love for "open" and "neutral" has been reduced to mostly marketing.
> Today, you can build a browser that can render all content on the web that
> adheres to the open standards.
Actually, if your browser would only show that kind of content you wouldn't see much. Very little content on the web follows any standard at all. > Google, Microsoft and Apple together will decide how
> we experience the web
You forgot Mozilla. And anyone making web browsers. That how it always was, that how it always be: browsers vendors will decide that. > and they will dictate terms on the rest of us, tearing down whatever "open" is left.
> Average users are not going to install an open, non-DRM client if that doesn't allow
> them to use Hulu, Netflix, YouTube, BBC etcetera.
And there you have it: the amount of "whatever "open" left" is immensely bigger than all hulus and netflixes. I cannot see hulu and netflix anyway, does that mean I have no access to the open web already?
What does it mean "non DRM" client anyway? The one that only shows DRM'ed content? Does this exist? Back in the days of ITMS selling DRMed audio content iTunes still could play any mp3 you threw at it, and it still can do the same today. Just because some client will allow you to play DRMed content it in no way means that it won't be able to play open content. And because of that all this outrage is quite moronic.> If you think "open" will still play a role in that, you must haven been living under a rock > for the past 10 years. Even Google's love for "open" and "neutral" has been reduced to mostly marketing.
Yes, I do. Your argument is just stupid.
Surely the implication was that Mozilla, and any other browser maker who does not or cannot support these locked-down content models, risk becoming irrelevant because the vast majority of people will use browsers that do support the protected content?
[1] https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-med...
More reading
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20944 http://arstechnica.com/business/2012/02/unethical-html-video...
How so? It requires the ability to have "locked" content and a mechanism to "unlock" it, but how does this affect anything else? Honest question.