Re: Feedback on Fallback

Ilari Liusvaara <ilari.liusvaara@elisanet.fi> Mon, 22 September 2014 20:13 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BD351A1B0E for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 22 Sep 2014 13:13:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.688
X-Spam-Level:
X-Spam-Status: No, score=-7.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LwXeMPQ0V8xU for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 22 Sep 2014 13:13:09 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F2B51A1B51 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 22 Sep 2014 13:13:09 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1XW9vh-0008Jy-R1 for ietf-http-wg-dist@listhub.w3.org; Mon, 22 Sep 2014 20:09:49 +0000
Resent-Date: Mon, 22 Sep 2014 20:09:49 +0000
Resent-Message-Id: <E1XW9vh-0008Jy-R1@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <ilari.liusvaara@elisanet.fi>) id 1XW9vL-0008Ib-EE for ietf-http-wg@listhub.w3.org; Mon, 22 Sep 2014 20:09:27 +0000
Received: from emh03.mail.saunalahti.fi ([62.142.5.109]) by lisa.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <ilari.liusvaara@elisanet.fi>) id 1XW9vJ-0005LF-Pl for ietf-http-wg@w3.org; Mon, 22 Sep 2014 20:09:27 +0000
Received: from LK-Perkele-VII (a88-112-44-140.elisa-laajakaista.fi [88.112.44.140]) by emh03.mail.saunalahti.fi (Postfix) with ESMTP id AA427188797; Mon, 22 Sep 2014 23:09:00 +0300 (EEST)
Date: Mon, 22 Sep 2014 23:09:00 +0300
From: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
To: Mike Bishop <Michael.Bishop@microsoft.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20140922200900.GA15270@LK-Perkele-VII>
References: <152c2ec3edb04e048252116634915828@BL2PR03MB132.namprd03.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <152c2ec3edb04e048252116634915828@BL2PR03MB132.namprd03.prod.outlook.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
Received-SPF: pass client-ip=62.142.5.109; envelope-from=ilari.liusvaara@elisanet.fi; helo=emh03.mail.saunalahti.fi
X-W3C-Hub-Spam-Status: No, score=-3.2
X-W3C-Hub-Spam-Report: AWL=-3.207, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1XW9vJ-0005LF-Pl 963cb4005d55158cb6aabf5af66a5ed9
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Feedback on Fallback
Archived-At: <http://www.w3.org/mid/20140922200900.GA15270@LK-Perkele-VII>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/27153
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 Mon, Sep 22, 2014 at 07:24:48PM +0000, Mike Bishop wrote:

> Some apps we support depend on the ability to emit raw HTTP protocol
> text. 

Are there any HTTP/1.1 messages that can't be gatewayed into HTTP/2?

I know earlier there were some, but I thought those problems have
been fixed.

> Others require client certs as a matter of local law and we don't
> have a way to retrieve the client cert without renegotiation. 

Renegotiation is dangerous in multiplexed protocols. And even more
dangerous with typical usage of HTTP.

I thought there was proposal for httpauth and TLS extensions to
tackle usage of client certificates in HTTP/2? What's the status
of those?

Also, I think those extensions, along with some other stuff
could be useful in order to implement usable client certificate
authentication (right now, CC is infamous for terrible UX).


-Ilari