Re: HTTP 2.0 in the clear and over TLS
Amos Jeffries <squid3@treenet.co.nz> Tue, 30 July 2013 00:03 UTC
Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2B7121F9B25 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 29 Jul 2013 17:03:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7dPaEW2sM3do for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 29 Jul 2013 17:03:28 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id CF3E421E8054 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 29 Jul 2013 17:03:27 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1V3xPE-0002K9-8V for ietf-http-wg-dist@listhub.w3.org; Tue, 30 Jul 2013 00:03:12 +0000
Resent-Date: Tue, 30 Jul 2013 00:03:12 +0000
Resent-Message-Id: <E1V3xPE-0002K9-8V@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <squid3@treenet.co.nz>) id 1V3xP5-0002JK-QK for ietf-http-wg@listhub.w3.org; Tue, 30 Jul 2013 00:03:03 +0000
Received: from ip-58-28-153-233.static-xdsl.xnet.co.nz ([58.28.153.233] helo=treenet.co.nz) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <squid3@treenet.co.nz>) id 1V3xP3-00070a-FN for ietf-http-wg@w3.org; Tue, 30 Jul 2013 00:03:03 +0000
Received: from [192.168.1.218] (ip202-27-218-168.satlan.co.nz [202.27.218.168]) by treenet.co.nz (Postfix) with ESMTP id DD062E6F1E for <ietf-http-wg@w3.org>; Tue, 30 Jul 2013 12:02:36 +1200 (NZST)
Message-ID: <51F7029B.2070801@treenet.co.nz>
Date: Tue, 30 Jul 2013 12:02:35 +1200
From: Amos Jeffries <squid3@treenet.co.nz>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf-http-wg@w3.org
References: <32754_1375115822_51F69A2E_32754_8403_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB906C6BC40@PEXCVZYM14.corporate.adroot.infra.ftgroup> <CAA4WUYhj0-h4MeL7pJC-gq_bZjnj7KHHUv5YQJGkf_7wGkyGFA@mail.gmail.com> <CAA4WUYj9W0abSpwxf7eGR3CMWkOpqDL1kzyRxfSXRj5bphjsiw@mail.gmail.com> <CANmPAYEsngMs+x3WLrUm10YRCoi2vrnzKDDt_N+5V9fdcqk9YA@mail.gmail.com> <CANUYc_R2omr7JC5G5oLcvX-sdp7bSpW4b=cg=vDAqHAmQo9q8Q@mail.gmail.com>
In-Reply-To: <CANUYc_R2omr7JC5G5oLcvX-sdp7bSpW4b=cg=vDAqHAmQo9q8Q@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Received-SPF: pass client-ip=58.28.153.233; envelope-from=squid3@treenet.co.nz; helo=treenet.co.nz
X-W3C-Hub-Spam-Status: No, score=-4.4
X-W3C-Hub-Spam-Report: AWL=-2.499, BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1V3xP3-00070a-FN 53a4a9f2a0de5340fde06740c824c2f5
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP 2.0 in the clear and over TLS
Archived-At: <http://www.w3.org/mid/51F7029B.2070801@treenet.co.nz>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18970
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
On 30/07/2013 11:38 a.m., Fred Akalin wrote: > Why would HTTP 2.0 be faster in the clear than over TLS? > For the same reasons HTTP in the clear is faster than HTTPS. Encryption overheads, cache offloading, proxy multiplexing amongst others. Amos > > On Tue, Jul 30, 2013 at 1:12 AM, Peter Lepeska <bizzbyster@gmail.com > <mailto:bizzbyster@gmail.com>> wrote: > > HTTP 2.0 in the clear will be faster than over TLS. It will be > interesting to see if Google will continue to trade speed for > privacy when the standard supports a faster option. > > Peter > > > On Mon, Jul 29, 2013 at 5:01 PM, William Chan (陈智昌) > <willchan@chromium.org <mailto:willchan@chromium.org>> wrote: > > Sorry, I am inexact. Some people may have previously said > otherwise, but currently to my knowledge no one is vocally > opposing including a HTTP/2.0 in the clear mechanism in the > spec, and the current draft spec does provide such a mechanism. > > > On Mon, Jul 29, 2013 at 2:00 PM, William Chan (陈智昌) > <willchan@chromium.org <mailto:willchan@chromium.org>> wrote: > > No one has said otherwise. Please see the section in the > spec where we provide a way to negotiate HTTP/2.0 in the > clear via HTTP Upgrade: > http://http2.github.io/http2-spec/#discover-http. > > > On Mon, Jul 29, 2013 at 9:37 AM, <emile.stephan@orange.com > <mailto:emile.stephan@orange.com>> wrote: > > Hi, > > HTTP2 must work in the clear and over TLS. This is > required because HTTP1.1 and HTTP2 must coexist to > ease the migration to HTTP2, and to accelerate HTTP2 > deployments. > > Regards > > Emile > > *De :*Michael Sweet [mailto:msweet@apple.com] > *Envoyé :* dimanche 28 juillet 2013 14:12 > *À :* Eliot Lear > *Cc :* William Chan (陈 智昌) ; Zhong Yu; HTTP Working > Group > *Objet :* Re: HTTPS 2.0 without TLS extension? > > ... and don't forgot some of the more obscure usage of > HTTP, such as HTTP over USB in the USB-IF's IPP USB > Specification: > > http://www.usb.org/developers/devclass_docs > > > > There isn't much point in using TLS over USB (and a > lot of cost issues for that class of printer against > it), and we need to continue to use the same USB end > points/interfaces, so upgrade remains an important > feature of HTTP/2.0 for me/Apple... > > > > > Sent from my iPad > > > On 2013-07-28, at 12:46 AM, Eliot Lear <lear@cisco.com > <mailto:lear@cisco.com>> wrote: > > On 7/23/13 7:34 PM, William Chan (陈智昌) wrote: > > FWIW, it seems reasonable to me to have the > spec allow HTTPS 2.0 without TLS extension. If > you want to Upgrade, be my guest. I have no > plans for my browser to support that, and I > don't think Google servers will support it > either, because we care strongly about the > advantages of TLS-ALPN vs Upgrade. > > > Not only that, I don't think we can reasonably > call this HTTP 2.0 if we have no path to do it in > the clear. > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > > > >
- HTTP 2.0 in the clear and over TLS emile.stephan
- Re: HTTP 2.0 in the clear and over TLS William Chan (陈智昌)
- Re: HTTP 2.0 in the clear and over TLS William Chan (陈智昌)
- Re: HTTP 2.0 in the clear and over TLS Peter Lepeska
- Re: HTTP 2.0 in the clear and over TLS Fred Akalin
- Re: HTTP 2.0 in the clear and over TLS William Chan (陈智昌)
- Re: HTTP 2.0 in the clear and over TLS Amos Jeffries
- Re: HTTP 2.0 in the clear and over TLS Peter Lepeska
- Re: HTTP 2.0 in the clear and over TLS Martin Thomson
- Re: HTTP 2.0 in the clear and over TLS Peter Lepeska