Re: [hybi] Experiment comparing Upgrade and CONNECT handshakes

Maciej Stachowiak <mjs@apple.com> Wed, 01 December 2010 21:46 UTC

Return-Path: <mjs@apple.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 224483A67DB for <hybi@core3.amsl.com>; Wed, 1 Dec 2010 13:46:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.413
X-Spam-Level:
X-Spam-Status: No, score=-106.413 tagged_above=-999 required=5 tests=[AWL=-0.415, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fb65CfaqPRvj for <hybi@core3.amsl.com>; Wed, 1 Dec 2010 13:46:04 -0800 (PST)
Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 3DB1B3A6783 for <hybi@ietf.org>; Wed, 1 Dec 2010 13:46:04 -0800 (PST)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out3.apple.com (Postfix) with ESMTP id 486A4BC48962 for <hybi@ietf.org>; Wed, 1 Dec 2010 13:47:18 -0800 (PST)
X-AuditID: 11807137-b7bf5ae000001937-fd-4cf6c266d37e
Received: from et.apple.com (et.apple.com [17.151.62.12]) by relay16.apple.com (Apple SCV relay) with SMTP id 55.11.06455.662C6FC4; Wed, 1 Dec 2010 13:47:18 -0800 (PST)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_nOXnBhhgxxj9yYB96DdPpQ)"
Received: from [17.73.146.44] by et.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LCR0073IR6QLN40@et.apple.com> for hybi@ietf.org; Wed, 01 Dec 2010 13:47:18 -0800 (PST)
From: Maciej Stachowiak <mjs@apple.com>
In-reply-to: <AANLkTinLmAdKr3gOkk-k=TXPX-HhX0xea5r_AkgfM=cP@mail.gmail.com>
Date: Wed, 01 Dec 2010 13:47:13 -0800
Message-id: <7163BB66-CBE9-4025-A229-FA6A5D0695AE@apple.com>
References: <AANLkTik0wR-Oag5YJJDmdiSy67WW6TMaHmqWEo4o5kGW@mail.gmail.com> <AANLkTimwEtKrJm5KxTYZ4wrtONBYDTGjE5LF7__AHBEU@mail.gmail.com> <20101201183540.GF19021@1wt.eu> <AANLkTi=r-is4ZqJc6itsaBkyrmW746xXj8OV78M_Qbi3@mail.gmail.com> <20101201184828.GH19021@1wt.eu> <AANLkTinLmAdKr3gOkk-k=TXPX-HhX0xea5r_AkgfM=cP@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: Hybi <hybi@ietf.org>, Zhong Yu <zhong.j.yu@gmail.com>
Subject: Re: [hybi] Experiment comparing Upgrade and CONNECT handshakes
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Dec 2010 21:46:05 -0000

On Dec 1, 2010, at 11:00 AM, Eric Rescorla wrote:

> 
> 
> On Wed, Dec 1, 2010 at 10:48 AM, Willy Tarreau <w@1wt.eu> wrote:
> On Wed, Dec 01, 2010 at 01:43:59PM -0500, John Tamplin wrote:
> > AFAIK, the Hello frames do not appear in any draft and only in Greg's
> > proposal.  Personally, I am not sure what exactly they buy us and I
> > don't know if we want to pay the extra round trip for them.
> 
> I'm sorry, I thought we had that in -03. At some point I'm getting lost
> between proposals and drafts :-)
> 
> > So, if we really want this to be incremental, it would be a change
> > from Ian's last draft.
> 
> That's what I wanted indeed.
> 
> > As I understand it, these are the components of Adam's latest proposal:
> >  1) use CONNECT instead of GET+Upgrade
> >  2) use a fixed, bogus host header and mask the real headers
> >  3) mask all payload data
> 
> I thought that we already agreed on this point weeks ago.

I think what's new now is that we are approaching consensus on adopting point (1).

It sounds like we don't yet have consensus on (2) - people would rather adopt (1) first, and then examine it further.

I don't recall the state of the discussion on (3). I think the new XOR-masking likely addresses the concerns with the original AES masking.

Regards,
Maciej