technogeek00
commented
6 months ago 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 |
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
Open Questions