Re: [hybi] Multiple connections serialization and proxies

Jamie Lokier <jamie@shareable.org> Fri, 23 April 2010 00:19 UTC

Return-Path: <jamie@shareable.org>
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 1FC933A67AD for <hybi@core3.amsl.com>; Thu, 22 Apr 2010 17:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.791
X-Spam-Level:
X-Spam-Status: No, score=-2.791 tagged_above=-999 required=5 tests=[AWL=-0.192, BAYES_00=-2.599]
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 CGXFbVGYm-Z3 for <hybi@core3.amsl.com>; Thu, 22 Apr 2010 17:19:12 -0700 (PDT)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115]) by core3.amsl.com (Postfix) with ESMTP id BCB323A6781 for <hybi@ietf.org>; Thu, 22 Apr 2010 17:19:11 -0700 (PDT)
Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from <jamie@shareable.org>) id 1O56bi-0005rI-FH; Fri, 23 Apr 2010 01:18:58 +0100
Date: Fri, 23 Apr 2010 01:18:58 +0100
From: Jamie Lokier <jamie@shareable.org>
To: "Thomson, Martin" <Martin.Thomson@andrew.com>
Message-ID: <20100423001858.GA22326@shareable.org>
References: <4BCF4932.8040303@gmail.com> <4BD09A2C.6060506@gmail.com> <x2n557ae281004221224i2a9a46c0k6f6f684c94de255c@mail.gmail.com> <8B0A9FCBB9832F43971E38010638454F03E7D06DF7@SISPE7MB1.commscope.com> <20100422225448.GG13951@shareable.org> <8B0A9FCBB9832F43971E38010638454F03E7D06E00@SISPE7MB1.commscope.com> <20100422230957.GI13951@shareable.org> <8B0A9FCBB9832F43971E38010638454F03E7D06E06@SISPE7MB1.commscope.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F03E7D06E06@SISPE7MB1.commscope.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Multiple connections serialization and proxies
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: Fri, 23 Apr 2010 00:19:13 -0000

Thomson, Martin wrote:
> > You did specifically say it will be a problem when something reuses a
> > connection or when a proxy multiplexes.  Clearly -if- those things are
> > ever done, then just do them properly.
> 
> There is currently no mechanism described that would allow either party (browser or server) to identify virtual connections.
> 
> Thus, there is no way to do this "properly".

Correct, there is no mechanism, but also no need for one since reuse
and multiplexing don't occur.  If they're added, a virtual connection
mechanism will be at the same time.

> I was talking about the concrete proposals that exist (even if
> Greg's isn't on the ietf servers yet), and I'm sorry if there was an
> implication to the contrary.

Ok.  The various proposals include, (perhaps implicitly at this
stage), mechanisms for handling your concerns about credentials and
subprotocols from different applications on the same connection.

Those concerns are one of the reasons why transport and application
protocol negotiations should be independent.

It's still an important thing to get right in those proposals so
thanks for bringing it up.

-- Jamie