1 / 7

Protected Content in Browsers

Protected Content in Browsers. Position Paper. Background. Current Service Provider strategy to deliver protected content Use multimedia framwork that has support for DRM e.g. Silverlight, Flash Browser plugin that handles both DRM and media playback Native Client

npottorff
Download Presentation

Protected Content in Browsers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Protected Content in Browsers Position Paper

  2. Background • Current Service Provider strategy to deliver protected content • Use multimedia framwork that has support for DRM e.g. Silverlight, Flash • Browser plugin that handles both DRM and media playback • Native Client • Legacy plugin architectures have poor security and stability • Major browser vendors are dropping plugin support • New plugin architectures exist, but are not broadly supported • Encrypted Media Extensions (EME) provide APIs to control playback of protected content • DRM system support is up to browser vendor

  3. Current Future Options • Deploy multi-vendor DRM support and adopt to DRM choices of browser vendors • Use native app with DRM support • Potentially based on HTML 5 • Support only one or a few browsers

  4. Browser positions • Chrome • NPAPI dropped Sep 2014, new plugin PPAPI. Widevine CDM • IE • No plugin in future versions, Playready CDM • Firefox • User interaction to allow plugins, not official statement on plugin future • Safari and Opera • No official statement

  5. Statements • In mid-2014, the blocking UI will become more difficult to navigate, as a means of discouraging NPAPI use by developers. With the harsher blocking UI, users will see a puzzle piece in place of the plug-in and a "Blocked plug-in“… • http://www.chromium.org/developers/npapi-deprecation

  6. Conclusion • User experience will suffer because of non-preferred browser or native application • Anti-competitive situation because of the nature of DRM support in different browsers. • Discussion is invited

More Related