- From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Date: Fri, 24 Oct 2014 18:31:54 +0900
- To: Mark Watson <watsonm@netflix.com>, Domenic Denicola <domenic@domenicdenicola.com>
- CC: David Dorwin <ddorwin@google.com>, Henri Sivonen <hsivonen@hsivonen.fi>, www-tag <www-tag@w3.org>
On 2014/10/24 05:35, Mark Watson wrote: > Large content providers are not all going to migrate to HTTPS overnight. > As mentioned on another thread, I will have some data on server performance > related to this to share soon. The significant costs of this migration will > totally outweigh any W3C fiat and browsers who choose to support only HTTPS > will find their customers either still using plugins, or cut off from > services - a different kind of fragmentation of the web. > > Given this, I think it likely that all DRM providers will have solutions > which can be used on HTTP origins. This is what we are doing on IE, Chrome > and Safari today. I doubt they would refuse to provide those same solutions > to smaller UAs (at least for those who provide the DRM as a separate > product). Just a (maybe stupid) question from a non-expert: When you speak about HTTPS, would that require transmitting all the content (huge video files,...) over HTTPS, or would that only/mainly apply to credential exchanges/signup/... or whatever it's called that goes on before the actual content is served? Regards, Martin.
Received on Friday, 24 October 2014 09:32:26 UTC