Open technogeek00 opened 3 years ago
A number of interesting deployment scenarios around mechanism usage:
Question | Answer |
---|---|
Does the feature relate to an industry streaming use-case? | Yes, Live Streaming |
- What is the commonality of this case? | Uncommon |
- Is this an established or emerging practice? | Emerging |
Does this feature have related mechanisms in both DASH and HLS? | Yes, not exactly equivalent |
- What is the maturity of support in both specifications? | DASH - Immature, HLS - Immature |
- What is the maturity of implementation support for both specifications? | Needs Investigation, likely Immature for both |
- Are there known interoperability issues between specs? | Yes, due to signaling not explicitly equivalent |
- Has anyone implemented this interoperably? | No |
- Are there features missing in a specification with open proposals for it? | No |
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
Usage of manifest signaling mechanisms to provide incremental information updates instead of full document updates as part of a live presentation playout
Working Notes
Open Questions