search

Dash-Industry-Forum / Guidelines-TimingModel

DASH-IF implementation guidelines: the DASH timing model
9 stars 1 forks source link

MPD validity duration #6

Closed irajs closed 4 years ago

irajs commented 4 years ago

A dynamic MPD SHALL conform to the constraints in this document not only at its moment of initial publishing but through the entire MPD validity duration, which is a period of MPD@minimumUpdatePeriod starting from the moment the MPD download is started by a client, unless overridden by [[#inband|in-band validity signaling]].

"Unless..." is true only if inband validity expiration event is supported by all client. Should we make it a SHALL?

sandersaares commented 4 years ago

Yes, further clarification on this is beneficial. I have adjusted the relevant chapter to increase understandability and remove ambiguity. Changes not yet published as I don't want to change the verison at the URL under community review but you can see them in the separate post-communityreview branch.

sandersaares commented 4 years ago

Proposed resolution: close the issue; text was clarified to increase understandability.

haudiobe commented 4 years ago

(IOPv5 20/02/05): No other comments. If no further comments are received, the issue will be closed during the next (IOPv5 20/02/12)

haudiobe commented 4 years ago

(IOPv5 20/02/12): No comments received. Closed