Re: HTTPS 2.0 without TLS extension?
Zhong Yu <zhong.j.yu@gmail.com> Tue, 23 July 2013 18:51 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 8F81A11E8365 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 23 Jul 2013 11:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.724
X-Spam-Level:
X-Spam-Status: No, score=-9.724 tagged_above=-999 required=5 tests=[AWL=0.575, 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 UTYJDY4TxWCK for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 23 Jul 2013 11:50:54 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 4557611E830D for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 23 Jul 2013 11:50:54 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1V1hfS-0000h3-69 for ietf-http-wg-dist@listhub.w3.org; Tue, 23 Jul 2013 18:50:38 +0000
Resent-Date: Tue, 23 Jul 2013 18:50:38 +0000
Resent-Message-Id: <E1V1hfS-0000h3-69@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <zhong.j.yu@gmail.com>) id 1V1hfI-0000dq-O4 for ietf-http-wg@listhub.w3.org; Tue, 23 Jul 2013 18:50:28 +0000
Received: from mail-ob0-f170.google.com ([209.85.214.170]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <zhong.j.yu@gmail.com>) id 1V1hfI-0004ss-4R for ietf-http-wg@w3.org; Tue, 23 Jul 2013 18:50:28 +0000
Received: by mail-ob0-f170.google.com with SMTP id ef5so11107180obb.29 for <ietf-http-wg@w3.org>; Tue, 23 Jul 2013 11:50:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3WCC0nBReDRl9yIH9N7q9Q/Dlm8phf8llsLo64QIjyo=; b=Lie/CqSfTdIlaegC42DQlskIEz1PF8wL3BHpqrVbMMDs+jvVDGJ9J0tgRIpzFjy+U2 ofUmIho7cXo3ODKO/miYQUb1a72sjV3pfNNSrfXmOE+Cc2YS1mUsiUUCXp2w3kOVtFiw ULy5iX4ysTLuRgvQ4xgGUy7hH4Okxi2Tdrz41gmyqGV+GTl46C80xif6NL4tfyYRvdtp 2/XVTrydTZQtCkj4VG6mK13xb6Axv9MvU7w0p8eVjlZ7yaOrDZh7TkVSZk3WfQ+hJ1R5 miBBBWLrK2+v8rSk0RtjKwQhIAWxdH9IwoU/Mgs55Hu8yxvkfxkEbNSZj8Ro5ayr5JDa 73qw==
MIME-Version: 1.0
X-Received: by 10.182.237.82 with SMTP id va18mr26566183obc.0.1374605401214; Tue, 23 Jul 2013 11:50:01 -0700 (PDT)
Received: by 10.76.180.106 with HTTP; Tue, 23 Jul 2013 11:50:01 -0700 (PDT)
In-Reply-To: <CACuKZqGjYtmkFBEEDX+s=n=_15frt+qoQws4TWgiDEijBE+Mow@mail.gmail.com>
References: <CACuKZqEBAqXs-cQF1U-g3npaXGR0LEoXZYxDv-3a+ftn-YG=_g@mail.gmail.com> <CAA4WUYjS=JXYAYKe0ueqUFbdEUC3pM8xuj--b=F=WPgnSc9xYg@mail.gmail.com> <CACuKZqGjYtmkFBEEDX+s=n=_15frt+qoQws4TWgiDEijBE+Mow@mail.gmail.com>
Date: Tue, 23 Jul 2013 13:50:01 -0500
Message-ID: <CACuKZqHJ-x3Q69Uvtoj4C1TGy4F+PeUyqzbdUxEUVZOVr2KEnA@mail.gmail.com>
From: Zhong Yu <zhong.j.yu@gmail.com>
To: "William Chan (陈智昌)" <willchan@chromium.org>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="ISO-8859-1"
Received-SPF: pass client-ip=209.85.214.170; envelope-from=zhong.j.yu@gmail.com; helo=mail-ob0-f170.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.666, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1V1hfI-0004ss-4R e6a012b8b9a644300552711f14b2f479
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTPS 2.0 without TLS extension?
Archived-At: <http://www.w3.org/mid/CACuKZqHJ-x3Q69Uvtoj4C1TGy4F+PeUyqzbdUxEUVZOVr2KEnA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18884
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 Tue, Jul 23, 2013 at 1:46 PM, Zhong Yu <zhong.j.yu@gmail.com> wrote: > Therefore if the spec allows TLS-Upgrade, it might as well mandate it. I mean, "it might as well mandate all compliant implementations to support the Upgrade mechanism on a TLS connection"
- HTTPS 2.0 without TLS extension? Zhong Yu
- Re: HTTPS 2.0 without TLS extension? Mike Belshe
- Re: HTTPS 2.0 without TLS extension? Zhong Yu
- Re: HTTPS 2.0 without TLS extension? Ilari Liusvaara
- Re: HTTPS 2.0 without TLS extension? Yoav Nir
- Re: HTTPS 2.0 without TLS extension? Amos Jeffries
- Re: HTTPS 2.0 without TLS extension? David Morris
- Re: HTTPS 2.0 without TLS extension? William Chan (陈智昌)
- Re: HTTPS 2.0 without TLS extension? Yoav Nir
- Re: HTTPS 2.0 without TLS extension? Martin Thomson
- Re: HTTPS 2.0 without TLS extension? Zhong Yu
- Re: HTTPS 2.0 without TLS extension? Zhong Yu
- Re: HTTPS 2.0 without TLS extension? William Chan (陈智昌)
- Re: HTTPS 2.0 without TLS extension? Ryan Hamilton
- Re: HTTPS 2.0 without TLS extension? Martin Thomson
- Re: HTTPS 2.0 without TLS extension? Amos Jeffries
- Re: HTTPS 2.0 without TLS extension? Zhong Yu
- Re: HTTPS 2.0 without TLS extension? Yoav Nir
- Re: HTTPS 2.0 without TLS extension? Zhong Yu
- Re: HTTPS 2.0 without TLS extension? Roberto Peon
- Re: HTTPS 2.0 without TLS extension? Eliot Lear
- Re: HTTPS 2.0 without TLS extension? Michael Sweet