Re: HTTP 2.0 in the clear and over TLS

William Chan (陈智昌) <willchan@chromium.org> Mon, 29 July 2013 21: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 A4E9111E814D for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 29 Jul 2013 14:03:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.676
X-Spam-Level:
X-Spam-Status: No, score=-9.676 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 GIX6HM3jptmi for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 29 Jul 2013 14:03:45 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 8810321F9AF8 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 29 Jul 2013 14:03:44 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1V3uaL-0003vt-Tk for ietf-http-wg-dist@listhub.w3.org; Mon, 29 Jul 2013 21:02:29 +0000
Resent-Date: Mon, 29 Jul 2013 21:02:29 +0000
Resent-Message-Id: <E1V3uaL-0003vt-Tk@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <willchan@google.com>) id 1V3uaC-0003qM-Qi for ietf-http-wg@listhub.w3.org; Mon, 29 Jul 2013 21:02:20 +0000
Received: from mail-oa0-f46.google.com ([209.85.219.46]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <willchan@google.com>) id 1V3ua6-0006Ns-7b for ietf-http-wg@w3.org; Mon, 29 Jul 2013 21:02:20 +0000
Received: by mail-oa0-f46.google.com with SMTP id h1so14310343oag.33 for <ietf-http-wg@w3.org>; Mon, 29 Jul 2013 14:01:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=NPfcQ3/9muNOX8Auzn364wlzUnVuIgEd82Wd7wx5Xls=; b=Xpg0foaxo2ymiEaRdmrBF0W7wnd70oDxyhpJRasVNglqMNk3rXEzM04gkoL97JTyQU mV4DTcVvLn84DPFNyqyznQ6V32prqqclJW4QBo6bssdkfQUd9WdqGEMZCawF3rAVCKNL NHrt7etJHNp32TosMHl8pKe8uthZBS2WtckjQ76x8W//IWJWDXjW7yPUaQebpaGavnii wxdJSOIQsobyJghu78vM0wGuSoW5p3Jr/UXaxVrIwEFjQPPwV7SF4Ujn8g0xSZCf4o7W HNl0IWZNvAkYXllV55hVmgEzmTkIFJDRmQfl+I/l+XS1jlE1O5RoNUBOehCS6rWYzAL1 BnjQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=NPfcQ3/9muNOX8Auzn364wlzUnVuIgEd82Wd7wx5Xls=; b=Qo8ZSpW+26p2o36PC/H9cW0W9jpXrT6FnpKFVkNW7ll0wVzYRPjrPcCBfyo0awdpF5 B5ak4GK0w2T+Ye/9dnO3eewEZBizRyL9BLtUdD2DQYO0Gwrb7/3nohsEETl9sI3Ddh7d HwpGOcTYplPkEQl/SJiCfTlIxapmfbPBlG660=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=NPfcQ3/9muNOX8Auzn364wlzUnVuIgEd82Wd7wx5Xls=; b=JcetBkrJ0dW3ANw8BE82f917+k68xesPkQ++gGgp9nr/KzfhzCZFGTf5r5k3yUbhYS +M6P0zHlFKb2oznpVXGHNXUvQjHupuejN54N8XviLs1oTciIoI4hjzu8LNM8sjzzTISQ NBvM8Ahif3+fbATWF++dHGjhxHeRSFgzhsDRisMfWPdu08EDSVvbrmQwY29zjsPcBmjz T7l4hwwEd0wpZPM/ig872VLLjaZy23UcBvfppU0jx0JxQIQLIIvRLoqAx6YSzhA/t1O8 HxO/AkcFrUElQb0IwJNwOBwUd7mMhT0UxKOnHy57iC+k3pDpTyQVl11+XOQuXP3rcObE jspA==
MIME-Version: 1.0
X-Received: by 10.50.102.68 with SMTP id fm4mr781014igb.45.1375131706319; Mon, 29 Jul 2013 14:01:46 -0700 (PDT)
Sender: willchan@google.com
Received: by 10.64.23.7 with HTTP; Mon, 29 Jul 2013 14:01:46 -0700 (PDT)
In-Reply-To: <CAA4WUYhj0-h4MeL7pJC-gq_bZjnj7KHHUv5YQJGkf_7wGkyGFA@mail.gmail.com>
References: <32754_1375115822_51F69A2E_32754_8403_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB906C6BC40@PEXCVZYM14.corporate.adroot.infra.ftgroup> <CAA4WUYhj0-h4MeL7pJC-gq_bZjnj7KHHUv5YQJGkf_7wGkyGFA@mail.gmail.com>
Date: Mon, 29 Jul 2013 14:01:46 -0700
X-Google-Sender-Auth: V3LquNzdixKqxIVh7q_3VeIoLsk
Message-ID: <CAA4WUYj9W0abSpwxf7eGR3CMWkOpqDL1kzyRxfSXRj5bphjsiw@mail.gmail.com>
From: "William Chan (陈智昌)" <willchan@chromium.org>
To: "emile.stephan@orange.com" <emile.stephan@orange.com>
Cc: Michael Sweet <msweet@apple.com>, Eliot Lear <lear@cisco.com>, Zhong Yu <zhong.j.yu@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="047d7b10c9f9e00b3304e2accca6"
X-Gm-Message-State: ALoCoQkWg+1dyUEcLD4VVTUXqQLhTfxD3z12ZoMWclbQsdGhCNREmOF/ssWVsWz1bDbnpbrhXkdfI+WjARidn4xHyukpZc7wyRA/oVJA8sUIqetGIdyR0mIF8hr7M9eaBc6NWOHK5j1tg/6AKWLT4fapifxqk2dTwGERntJk8p03PIecON+xmW04WusGQPaBJsrskRH/WBgf
Received-SPF: pass client-ip=209.85.219.46; envelope-from=willchan@google.com; helo=mail-oa0-f46.google.com
X-W3C-Hub-Spam-Status: No, score=-4.3
X-W3C-Hub-Spam-Report: AWL=-1.966, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.528, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1V3ua6-0006Ns-7b 40efbbd38b49e62677a9413f515c7b7e
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/CAA4WUYj9W0abSpwxf7eGR3CMWkOpqDL1kzyRxfSXRj5bphjsiw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18966
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>

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>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> 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 <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> 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.
>>
>>
>