Here is a How to, the objective is to demonstrate the setup of a PHLS live stream. PHLS means Protected HLS : the custom format of HLS by Adobe. The protection is realized with a AES-128 encryption on the content. To make this configuration, you need a streaming server which will push content via RTMP.
The W3C HTML working group is developing media extension specifications for HTML5 to enable the delivery of commercial video to consumers over the Web. One of these is the Encrypted Media Extensions (EME) specification. The current specification describes an open interface which may be used to implement an EME-compliant Content Decryption Module (CDM) within a User-agent, providing access to a platform DRM component which supports the defined Content Decryption Module interface (CDMi).
Tim Berners-Lee suggests that allowing content protection mechanisms into the HTML5 web standard may be necessary in order to help web standards fight back against the rise of proprietary platforms. But is that tradeoff worth making?
Microsoft today announced their next version of PlayReady digital rights management system. PlayReady is the most widely deployed DRM technology in the world, and this new version will enable content companies to make their content available across devices in a secured way. Microsoft is also releasing client SDK for iOS and Android platforms.
The digital rights management (DRM) market will become a US$1.2 billion (€910 million) market by 2018, while the related conditional access (CAS) market will decline slightly, dropping below US$1.5 billion annually, according to ABI Research stats.
The new ExpressPlay content protection solution-as-a-service makes it dramatically easier to implement DRM for Connected TV and multiscreen services, Intertrust, the company behind the solution, claims. ExpressPlay is designed for use with Marlin DRM, the open-standard content protection system, and can be used with existing Marlin-enabled connected TVs and set-top boxes. The market for this service therefore includes HbbTV-based broadcast/broadband services as well as YouView in the UK. Intertrust says ITV and BT both use the ExpressPlay service for their DRM requirements on YouView. A good proportion of the transactions on the Tivù platform in Italy use the ExpressPlay hosted service. Eutelsat KabelKiosk is going to use this cloud-based content protection.
The Web standards group is going ahead with its Encrypted Media Extensions technology despite some opposition, arguing it's a step in the right direction.
The World Wide Web Consortium has decided to go ahead with a technology that will let companies like Netflix stream encrypted video using Web sites -- against the wishes of the Free Software Foundation, Electronic Frontier Foundation, and 25,600 petition signatories.
The Web standards group announced the move Thursday, to nobody's surprise. Entertainment-industry players had approached the group three years ago to discuss the technology, Microsoft has been helping develop it, and Google already has built the specification, called Encrypted Media Extensions (EME) into Chrome.
The standard doesn't actually handle encryption and digital rights management (DRM) to govern who gets to see or copy video. Instead, it provides a standard mechanism that lets a browser call upon a plug-in that handles the work. In other words, it enables encryption but doesn't do the encryption itself.
thePlatform to Lead with HTML5 in 2013 to Deliver Faster Load Times and Lower Development Costs
SEATTLE, WA – January 29, 2013 – Media and entertainment companies have historically faced a challenge creating a common video player that can be rendered across different browsers and devices, due to continued market fragmentation and a lack of cross-platform standards. Today, thePlatform, the leading white-label video publishing company, unveiled an enhanced video Player Service to address this issue, and has placed HTML5 at the forefront of its efforts.
A few days ago, a new proposal was put forward in the HTML Working Group (HTML WG) by Microsoft, Netflix, and Google to take DRM in HTML5 to the next stage of standardization at W3C. This triggered another uproar about the morality and ethics behind DRM and building it into the Web. There are good arguments about morality/ethics on both sides of the debate but ultimately, the HTML WG will decide whether or not to pursue the specification based on technical merit. I am a member of the HTML WG. I was also the founder of a start-up that focused on building a legal, peer-to-peer, content distribution network for music and movies. It employed DRM much like the current DRM in HTML5 proposal. During the course of 8 years of technical development, we had talks with many of the major record labels. I have first-hand knowledge of the problem, and building a technical solution to address the problem.
The Encrypted Media Extensions (DRM in HTML5) specification does not solve the problem the authors are attempting to solve, which is the protection of content from opportunistic or professional piracy. The HTML WG should not publish First Public Working Drafts that do not effectively address the primary goal of a specification.
Le 27 février, j'ai eu le plaisir d'accueillir David Bouteruche de Nagra, et Romain Bouqueau de Gpac Licensing pour parler de sujet très sensible, la sécurisation des contenus vidéo. Une première intervention, non filmée, a eu lieu au SATIS en novembre dernier, où une carte blanche de
J’ai assisté hier à plusieurs présentations au SATIS, dont la « Carte blanche OVFSquad – DRMs – quel prix pour la sécurité de l’OTT ? ».
La question est importante, car tous les distributeurs de contenus en OTT sont confrontés à l’implémentation des DRM imposées par les ayants droit (pour appuyer sur un fait exprimé par les intervenants, ce n’est pas de gaité de cœur que les sites de VOD mettent en place des DRM ; s’ils ne le font pas, ils n’ont pas les films, point !).
Quelques rappels tout d’abord :
- OTT (Over The Top) veut dire en pratique diffusion en dehors des plateformes IPTV des FAI, donc directement sur Internet; cela s’applique en particulier à la VOD (Vidéo à la Demande) sur PC, Mac, tablettes et TV connectées.
- DRM (Digital Rights Management ou gestion de droits numériques) correspond à la protection du contenu par un système de licence (qui limite l’utilisation du contenu à certaines plages de temps, certains pays, certains terminaux) et un système de chiffrement des contenus (qui évite une utilisation immodérée du contenu).
- ABR (Adaptive Bitrate) correspond à des technologies de streaming qui permettent d’adapter la qualité d’image d’un flux vidéo à la bande passante disponible. L’idée est de préférer une image de moins haute définition à une image qui bloque (freeze) de temps en temps.
Le problème est d’autant plus complexe le nombre de terminaux supportés est important. Supposons que vous développiez une plateforme VOD premium, qui commercialise des long-métrages pour lesquels l’implémentation d’un système de DRM est imposée, et qui désire mettre en place une diffusion ABR. Supporter PC et Mac est relativement facile, quoi que …
FredAndrews writes "The W3C has ruled DRM in-scope for their HTML standard. A lot of big businesses have supported advancing the Encrypted Media Extension, including Google, Microsoft, and Netfix. The BBC calls for a solution with legal sanctions.