Re: [mixed-content] DASH Players and Mixed Content

I work for Ericsson on content delivery solutions (of course from secure
origins). We do get feedback from some media houses and TV providers
(medium sized) that they would like to see mixed content approach for DASH
since the cost for DASH on HTTPS still is perceived as a painful cost for
them in the short term.

What is the latest status on Ryans proposal,
https://lists.w3.org/Archives/Public/public-webappsec/2015Feb/0371.html?

We would be interested in looking into this further (as a complement to
working on lowering the price point for dash-on-tls).

Best regards
Göran

2015-07-23 17:46 GMT+02:00 Daniel Weinberger <daniel.weinberger@bitmovin.net
>:

> I work for bitmovin and we develop our own MSE-based MPEG-DASH player
> bitdash.
>
> We are facing this problem with many of our customers, so a solution is
> very desirable.
>
> Although the idea sounds good, I'm not sure all issues are addressed. For
> example to enable DASH we need to download a manifest file, which we need
> to parse in JS.
> There are also other parts which are probably needed, like
> subtitles/captions. They can be files, but they can be also embedded into
> ISO BMFF (i.e. mp4) fragments. As the MSE does not support all formats
> needed (e.g. WebVTT, TTML, ... / with styling etc.) across browsers, we
> need to parse these mp4 fragments in JS. This won't be possible with the
> proposed solution as the requested content is not accessible in JS.
>
> I know customers can just put these relatively small files on HTTPS while
> serving the actual data using HTTP, most customers want to have all its
> content in one place.
>
> However, I cant think of a solution for this, except separating the files..
> But maybe the smart guys here find a solution.
> Finally I'm not saying these are show stoppers, I just wanted to give some
> insights in what is important for us and our customers.
>
> Daniel Weinberger
>
>
>