[Bug 26332] Applications should only use EME APIs on secure origins (e.g. HTTPS)

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26332

--- Comment #88 from Mark Watson <watsonm@netflix.com> ---
(In reply to Anne from comment #87)
> (In reply to Mark Watson from comment #86)
> > given the high cost of such a requirement on content providers.
> 
> I believe this is still under "citation needed". Clearly there are content
> providers that have managed. With the evolution of HTTP and other new
> platform features it also seems increasingly unlikely you can avoid the
> requirement for any serious application.

We are running some capacity tests and I will share some figures from those
soon. Suffice to say, for the moment, that the costs associated with simply
enabling HTTPS are very significant. A managed migration, at a reasonable pace
with time for software and hardware optimizations to be developed and deployed,
has a different, lower, cost.

Also, HTTPS is not a panacea and we are looking at - and in some contexts have
deployed - other approaches as well.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 16 October 2014 14:52:51 UTC