W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: I revised the pro/contra document

From: Michael Sweet <msweet@apple.com>
Date: Sat, 23 Nov 2013 19:01:08 -0500
Message-id: <85CA44C5-7E05-47F3-9CA8-2403D7D528B0@apple.com>
Cc: Tim Bray <tbray@textuality.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
To: Alexandre Anzala-Yamajako <anzalaya@gmail.com>

There is a processing overhead associated with encryption - I've seen up to a 40% speed penalty for printers, for example. When applied to streaming of large files like movies (which already have their own layer of protections), that generally means the provider needs more servers with hardware accelerated TLS, and similarly more processing needs to be done on each client which may limit the quality/quantity of video that can be played. And imagine the increased power usage - not the direction most people are trying to go...

Aside from the basic resource issues, consider printing again. Most printers are not used in environments that need encryption. Those that do often do not have stable addresses or host names, making authentication and certificate management a greater challenge. So for printers I have personally fought hard for all TLS support but not necessarily to enable it by default. 

Sent from my iPad

> On Nov 23, 2013, at 4:27 PM, Alexandre Anzala-Yamajako <anzalaya@gmail.com> wrote:
> I am sorry if these points were discussed before but i don't get why tls isn't appropriate for media files or why we shouldn't secure our connections to printers ?
> Cheers
Received on Sunday, 24 November 2013 00:01:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:20 UTC