Don't exclude a @serviceLocation for a time-limited period equal to the last steering server TTL

[edouardbe]

Hi

Following the issue #22

n 20-c we say: "it shall exclude that @serviceLocation for a time-limited period equal to the last steering server TTL that it received."
We are also interested on why decoupling TTL and penalty period is a specific use case.
We are happy to collect feedback if this requirement causes issues in practical deployments, If so please file a new issue that explains the problem. Thank you

Thanks Thomas for asking.

This issue is linked to the #23 manage the content steering response in a static base64 data uri. If there is no need to call any external content steering service because the content steering manifest is static and written in the MPD directly, then there is no TTL on the content steering manifest anymore. If there is no more TTL on the content steering manifest and the exclusion duration of a service location is coupled with the content steering manifest TTL, it means the exclusion duration will be infinite.

I heard again in the DASH-IF Special Session: MPEG-DASH 6th Edition Feature video recording that the team tries to converge with the HLS content steering feature. If they can do it, why can't we with DASH?

Regards
Ed

[haudiobe]

Live TF 2024/04/19

• We could support the feature by replacing the current functionality (using TTL) with a default value (or we could even add a new attribute).
• Would need an amendment to our specification
• Please provide feedback if amending the according to the above principle is a good way forward.