Re: HTTPS 2.0 without TLS extension?

Yoav Nir <ynir@checkpoint.com> Tue, 23 July 2013 17:53 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 A432A11E8312 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 23 Jul 2013 10:53:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level:
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, 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 vmCFsds1Pq1H for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 23 Jul 2013 10:53:32 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id DC7D411E8314 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 23 Jul 2013 10:53:31 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1V1glT-0008B2-Mn for ietf-http-wg-dist@listhub.w3.org; Tue, 23 Jul 2013 17:52:47 +0000
Resent-Date: Tue, 23 Jul 2013 17:52:47 +0000
Resent-Message-Id: <E1V1glT-0008B2-Mn@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <ynir@checkpoint.com>) id 1V1glK-0008AI-N9 for ietf-http-wg@listhub.w3.org; Tue, 23 Jul 2013 17:52:38 +0000
Received: from smtp.checkpoint.com ([194.29.34.68]) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <ynir@checkpoint.com>) id 1V1glJ-0002xc-9q for ietf-http-wg@w3.org; Tue, 23 Jul 2013 17:52:38 +0000
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r6NHq6FD005286; Tue, 23 Jul 2013 20:52:06 +0300
X-CheckPoint: {51EEC2C6-11-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.91]) with mapi id 14.02.0342.003; Tue, 23 Jul 2013 20:52:06 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "William Chan (陈智昌)" <willchan@chromium.org>
CC: Zhong Yu <zhong.j.yu@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Thread-Topic: HTTPS 2.0 without TLS extension?
Thread-Index: AQHOhtQTsno4szXGeU2gyoo0a+EYMZlyVdGAgAAE64A=
Date: Tue, 23 Jul 2013 17:52:05 +0000
Message-ID: <9D94920D-9272-499E-AA06-E8E3EF202BA4@checkpoint.com>
References: <CACuKZqEBAqXs-cQF1U-g3npaXGR0LEoXZYxDv-3a+ftn-YG=_g@mail.gmail.com> <CAA4WUYjS=JXYAYKe0ueqUFbdEUC3pM8xuj--b=F=WPgnSc9xYg@mail.gmail.com>
In-Reply-To: <CAA4WUYjS=JXYAYKe0ueqUFbdEUC3pM8xuj--b=F=WPgnSc9xYg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.31.21.110]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 116614ee8c9a5393829a38c826d242477d19def819
Content-Type: text/plain; charset="utf-8"
Content-ID: <F14512F7BFBEE94C803C24606C6993AB@ad.checkpoint.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Received-SPF: pass client-ip=194.29.34.68; envelope-from=ynir@checkpoint.com; helo=smtp.checkpoint.com
X-W3C-Hub-Spam-Status: No, score=-6.0
X-W3C-Hub-Spam-Report: AWL=-0.950, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1V1glJ-0002xc-9q 38095395fa3264e6618e21b31fe55a53
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTPS 2.0 without TLS extension?
Archived-At: <http://www.w3.org/mid/9D94920D-9272-499E-AA06-E8E3EF202BA4@checkpoint.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18881
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 Jul 23, 2013, at 8:34 PM, William Chan (陈智昌) <willchan@chromium.org> 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.
> 

What about a regular TLS handshake (without the ALPN extension) followed by the HTTP/2 magic?