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

Incremental Manifest Updates #31

Open
technogeek00 opened this issue Aug 25, 2021 · 2 comments
Open

Incremental Manifest Updates #31

technogeek00 opened this issue Aug 25, 2021 · 2 comments
Assignees
Labels
use case consideration Use cases to consider formalizing
Milestone

Comments

@technogeek00
Copy link
Collaborator

technogeek00 commented Aug 25, 2021

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

  • DASH MPD Patch Updates and HLS Delta Updates are the equivalent specification mechanisms

Open Questions

  • Are there differences in update communication ability between the two forms?
  • Does this manifest mechanism have any constraints on the underlying media?
@technogeek00 technogeek00 added the use case consideration Use cases to consider formalizing label Aug 25, 2021
@technogeek00
Copy link
Collaborator Author

A number of interesting deployment scenarios around mechanism usage:

  • direct patch providing to clients
  • creating patches at the mid-tier/edge from full sources
  • creating full sources via patches at the mid-tier/edges

@technogeek00
Copy link
Collaborator Author

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

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: In Editorial
Development

No branches or pull requests

1 participant