dash: Begin DASH Annex I handling - #1882
Open
peaBerberian wants to merge 1 commit into
Open
Conversation
peaBerberian
added
Priority: 3 (Low)
peaBerberian
force-pushed
the
dash-annex-i-parser
branch
from
August 18, 2026 14:49
28bf910 to
92aff8f
Compare
|
✅ Automated performance checks have passed on commit DetailsPerformance tests 1st run outputNo significative change in performance for tests:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Based on #1880
I'm currently implementing supplementary DASH features (mostly the last revision of ContentSteering).
While doing that, I saw a feature of both DASH and DASH-IF IOPs that the RxPlayer is not properly handling yet:
DASH Annex I: Flexible Insertion of URL Parameters.It mainly allows to construct query strings when requesting resources like the segments and MPD by e.g. taking a value from the original MPD HTTP request's query string or header.
This can for example allow to forward a token in subsequent requests, without having it explicitly defined in the MPD.
Note that this PR does not implement any of the logic yet. It just properly parses those when in
EssentialProperty/SupplementalPropertydescriptors in the MPD but does not handle them yet.The actual implementation will come in a future PR. Splitting it in two is done to facilitate reviewing.
Also note that the recent (2026) DASH v6 specification (but not yet in DASH-IF IOP) seems to favor a new element,
<RequestParam>, for the same use case.Ultimately we may also do it (shaka does it, but not yet dash.js, yet both do Annex I) but for now I'll focus on what actually is present in the DASH-IF IOP and most DASH players.