Re: HTTPS 2.0 without TLS extension?

Mike Belshe <mike@belshe.com> Mon, 22 July 2013 16: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 6138F21F8D0D for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 22 Jul 2013 09:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.976
X-Spam-Level:
X-Spam-Status: No, score=-9.976 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 4Awd63PDthL4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 22 Jul 2013 09:03:20 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 3851121F9BAB for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 22 Jul 2013 09:03:19 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1V1IYy-0003Ld-LG for ietf-http-wg-dist@listhub.w3.org; Mon, 22 Jul 2013 16:02:16 +0000
Resent-Date: Mon, 22 Jul 2013 16:02:16 +0000
Resent-Message-Id: <E1V1IYy-0003Ld-LG@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <mike@belshe.com>) id 1V1IYp-0003Ku-8u for ietf-http-wg@listhub.w3.org; Mon, 22 Jul 2013 16:02:07 +0000
Received: from mail-bk0-f41.google.com ([209.85.214.41]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <mike@belshe.com>) id 1V1IYo-0000xm-6g for ietf-http-wg@w3.org; Mon, 22 Jul 2013 16:02:07 +0000
Received: by mail-bk0-f41.google.com with SMTP id jc3so2572540bkc.0 for <ietf-http-wg@w3.org>; Mon, 22 Jul 2013 09:01:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=mfVMtmRBUZnW8tmh8/RVD0uYOTB4iP4VhOWCG4RLpw0=; b=e0cgrtY/+39utY6NayLfhvjdoi3xmPNYHoyr9Ce+5d1bwyOkjCey5PteH3lneqegWC sWHAdwfiDSJzbqDTzi7QPhDBLRqlsv3jHVX7wyxrGWu4zCdI8jdrj9PXQv06Pth4YzbJ geqn315EwKBrDIS2OuG2qH87VOIJCYmI90+KO4oCN3NgAnqrGSZYOJGYXzOzW2a27sAO R49kG/TwJ6snQhO7UL6y1jruf0r/hblZMfQzF9p8aCZJhkMriQgDsXWGS68qTW81Ki+D IIprH0NYmfmWJ+4T+Yw756HdZGdsz+PeG+ti0W8THQIZhosRSeuN99sRmTLWn2f95xt+ VaBA==
MIME-Version: 1.0
X-Received: by 10.204.235.6 with SMTP id ke6mr4017227bkb.181.1374508898402; Mon, 22 Jul 2013 09:01:38 -0700 (PDT)
Received: by 10.204.168.130 with HTTP; Mon, 22 Jul 2013 09:01:38 -0700 (PDT)
In-Reply-To: <CACuKZqEBAqXs-cQF1U-g3npaXGR0LEoXZYxDv-3a+ftn-YG=_g@mail.gmail.com>
References: <CACuKZqEBAqXs-cQF1U-g3npaXGR0LEoXZYxDv-3a+ftn-YG=_g@mail.gmail.com>
Date: Mon, 22 Jul 2013 09:01:38 -0700
Message-ID: <CABaLYCtT33y3Gbh5rduHNL8hFsamz34epciG+36pYbkMdwpujQ@mail.gmail.com>
From: Mike Belshe <mike@belshe.com>
To: Zhong Yu <zhong.j.yu@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary=20cf301ee2b7a185c504e21bca41
X-Gm-Message-State: ALoCoQkvzvylC8mbsCBGEAoN+9q6BKJQDTH6KAYtU7VPdF42FEHxPNLmwD1BGNszJdwYG0/U0IAT
Received-SPF: none client-ip=209.85.214.41; envelope-from=mike@belshe.com; helo=mail-bk0-f41.google.com
X-W3C-Hub-Spam-Status: No, score=-4.7
X-W3C-Hub-Spam-Report: AWL=-2.150, BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7
X-W3C-Scan-Sig: maggie.w3.org 1V1IYo-0000xm-6g ad539673b64a2c0a53ccde13cbe49bb4
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTPS 2.0 without TLS extension?
Archived-At: <http://www.w3.org/mid/CABaLYCtT33y3Gbh5rduHNL8hFsamz34epciG+36pYbkMdwpujQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18865
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>

It should be available quite easily through OpenSSL and NSS long before
http/2 ships.

The structured integration with the SSL handshake is a much cleaner
protocol.

Mike



On Mon, Jul 22, 2013 at 5:06 AM, Zhong Yu <zhong.j.yu@gmail.com> wrote:

> The draft mandates TLS extension ALPN for any https 2.0 connections,
> but why is that necessary? Why can't we also establish an https 2.0
> connection through the Upgrade mechanism, without ALPN? TLS extension
> may not be available/convenient on some platforms for some time;
> requiring it may discourage some potential implementers.
>
> Zhong Yu
>
>