Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DRM: Support Manifest Delivered DRM Keys #2833

Closed
itsjamie opened this issue Jun 24, 2020 · 0 comments
Closed

DRM: Support Manifest Delivered DRM Keys #2833

itsjamie opened this issue Jun 24, 2020 · 0 comments

Comments

@itsjamie
Copy link
Collaborator

itsjamie commented Jun 24, 2020

Now that #2735 is merged, the Fragment class encrypted property now reports true for DRM signalled keys.

During the implementation of this, something I didn't address was MultiDRM streams. Currently, the data model assumes one levelkey per fragment. However, it's possible for there to be multiple levelkey(s) per fragment.

MultiDRM manifests I have found are relatively common and currently are unsupported due to the fact that we only store a single level key on a fragment. This will need to change if we want to support manifest delivered keys in a multi-key system manifest.


After we update the data model from an AES-128 Identity key centric style to support a DRM case, I see the steps roughly as;

  • Discuss the extension property naming for the hls.js public config to signal a preference for manifest delivered keys or initialization segment delivered
  • Add preemptive MediaKeySession negotiation for manifest delivered DRM keys if the preference is given to use them over EME "encrypted" event keys

Originally posted by @itsjamie in #2700 (comment)

@itsjamie itsjamie changed the title DRM - V1 - Preemptitive MediaKeySession DRM: Support Manifest Delivered DRM Keys Jun 24, 2020
@robwalch robwalch pinned this issue Jul 2, 2020
@robwalch robwalch added this to Top priorities in Release Planning and Backlog via automation Aug 12, 2020
@robwalch robwalch moved this from Top priorities to DRM (needs prioritization) in Release Planning and Backlog Aug 12, 2020
@itsjamie itsjamie unpinned this issue Mar 11, 2022
@robwalch robwalch moved this from DRM (needs prioritization) to Top priorities in Release Planning and Backlog Jul 16, 2022
@robwalch robwalch added this to the 1.3.0 milestone Jul 16, 2022
@robwalch robwalch mentioned this issue Sep 28, 2022
3 tasks
@robwalch robwalch moved this from Top priorities to DRM in Release Planning and Backlog Sep 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

2 participants