search

Dash-Industry-Forum / Guidelines-TimingModel

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

Presentation delay #7

Closed irajs closed 4 years ago

irajs commented 4 years ago

Clients SHALL constrain seeking to the [=effective time shift buffer=]. Clients SHALL NOT attempt to present [=media segments=] that fall entirely outside the [=effective time shift buffer=].

Do we want to make it SHALL or SHOULD?

We also have service description in 4th edition that allows to define the min/max/target delay. Should we use that one?

sandersaares commented 4 years ago

Do we want to make it SHALL or SHOULD?

Is there some particular reason this should not be a SHALL?

We also have service description in 4th edition that allows to define the min/max/target delay. Should we use that one?

I propose we wait to see if widely deployed clients and services even implement service description. I have a gut feeling it is unlikely to be widely implemented. We should not spend DASH-IF time on this unless we have good reason to believe it is an interoperable way to do things (something that can and will be widely implemented).

sandersaares commented 4 years ago

Proposed resolution: close the issue.

Rationale: SHALL seems appropriate here.

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