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

Re: Moving forward on improving HTTP's security

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Thu, 14 Nov 2013 08:39:23 +0000
To: Mike Belshe <mike@belshe.com>
cc: Willy Tarreau <w@1wt.eu>, Martin J. Dürst <duerst@it.aoyama.ac.jp>, Rob Trace <Rob.Trace@microsoft.com>, Michael Sweet <msweet@apple.com>, Tao Effect <contact@taoeffect.com>, Tim Bray <tbray@textuality.com>, James M Snell <jasnell@gmail.com>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <16880.1384418363@critter.freebsd.dk>
In message <CABaLYCsL5kHPETW2OC7ZyTm_s7rCJYoJaFChSc5kAsi-PWJN3A@mail.gmail.com>
, Mike Belshe writes:

>I agree, TLS is too hard to use today.  We need more tools and simpler

And this is one of (many) reasons why I think HTTP/2.0 should be
defined as a protocol to run on a transparent byte-pipe.

That would give us a neatly layered situation, where the mapping
from "http:", "https:", "httpng:", and even "httpNSAsucks:" to
how the byte-pipe is constructed is decoupled from what we move
through the byte-pipe once it is constructed.

Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
Received on Thursday, 14 November 2013 08:39:52 UTC

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