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

Multi-Key Encryption #47

Open
technogeek00 opened this issue Mar 27, 2024 · 1 comment
Open

Multi-Key Encryption #47

technogeek00 opened this issue Mar 27, 2024 · 1 comment
Labels
use case consideration Use cases to consider formalizing

Comments

@technogeek00
Copy link
Collaborator

Use Case Description

A single media experience where multiple encryption keys are utilized to provide access to varying levels of experience quality depending on the device / environment security level.

Working Notes

  • This differs from key rotation in that key rotation is concerned with the change of key across a single CMAF track while multi-key encryption is concerned with the use of different keys across CMAF aligned switching sets
  • Issue surfaced based on 6th Edition of MPEG DASH providing multi-key encryption examples

Open Questions

  • How much about the security requirements of keys are tied into signaling interoperability?
  • Are there industry best practices relative to multi-key encryption?
@technogeek00 technogeek00 added the use case consideration Use cases to consider formalizing label Mar 27, 2024
@technogeek00
Copy link
Collaborator Author

Net questionnaire score: 10

Question Answer
Does the feature relate to an industry streaming use-case? Yes, Content Security
- What is the commonality of this case? Very Common
- Is this an established or emerging practice? Emerging
Does this feature have related mechanisms in both DASH and HLS? Yes
- What is the maturity of support in both specifications? HLS - Mature , DASH - Mature
- What is the maturity of implementation support for both specifications? HLS - Immature, DASH - Immature
- Are there known interoperability issues between specs? Potentially
- Has anyone implemented this interoperably? Yes
- Are there features missing in a specification with open proposals for it? Unknown, needs investigation
Has the industry defined defacto mechanisms not present in both DASH and/or HLS? No
- Why was functionality defined outside of the main specifications? N/A
- Has the functionality been standardized elsewhere (DASH-IF, CTA, SVA)? N/A
- Is the functionality proprietary or openly developed? N/A
- Could the functionality be incorporated into specifications with evangelism? N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
use case consideration Use cases to consider formalizing
Projects
Status: Potential Specification Work
Development

No branches or pull requests

1 participant