Re: [hybi] Extensibility mechanisms?

Greg Wilkins <gregw@webtide.com> Mon, 19 April 2010 09:09 UTC

Return-Path: <gregw@webtide.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 4D6403A691B for <hybi@core3.amsl.com>; Mon, 19 Apr 2010 02:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.78
X-Spam-Level:
X-Spam-Status: No, score=-1.78 tagged_above=-999 required=5 tests=[AWL=0.819, 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 zCznhS4vlghd for <hybi@core3.amsl.com>; Mon, 19 Apr 2010 02:09:10 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by core3.amsl.com (Postfix) with ESMTP id 226DD3A67CC for <hybi@ietf.org>; Mon, 19 Apr 2010 02:09:09 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id 22so1131506fge.13 for <hybi@ietf.org>; Mon, 19 Apr 2010 02:08:56 -0700 (PDT)
Received: by 10.223.15.143 with SMTP id k15mr2533220faa.57.1271668136739; Mon, 19 Apr 2010 02:08:56 -0700 (PDT)
Received: from [192.168.0.100] (host116-234-static.43-88-b.business.telecomitalia.it [88.43.234.116]) by mx.google.com with ESMTPS id 18sm10063624fkq.34.2010.04.19.02.08.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 19 Apr 2010 02:08:56 -0700 (PDT)
Message-ID: <4BCC1DA6.3030207@webtide.com>
Date: Mon, 19 Apr 2010 11:08:54 +0200
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Mike Belshe <mike@belshe.com>
References: <h2w5c902b9e1004152345j992b815bz5f8d38f06a19181a@mail.gmail.com> <Pine.LNX.4.64.1004180246380.751@ps20323.dreamhostps.com> <4BCAB2C1.2000404@webtide.com> <B9DC25B0-CD21-44E7-BD9B-06D0C9440933@apple.com> <Pine.LNX.4.64.1004181812370.751@ps20323.dreamhostps.com> <4BCB6641.70408@webtide.com> <Pine.LNX.4.64.1004182010070.751@ps20323.dreamhostps.com> <4BCB6FD0.7080003@webtide.com> <k2r2a10ed241004181406zf93cf5c4p9652e4a78980027d@mail.gmail.com> <4BCC0BAD.1030209@webtide.com> <w2v2a10ed241004190140qf444bc1q6a82e3cd5ae93f7c@mail.gmail.com>
In-Reply-To: <w2v2a10ed241004190140qf444bc1q6a82e3cd5ae93f7c@mail.gmail.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] Extensibility mechanisms?
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: Mon, 19 Apr 2010 09:09:11 -0000

Mike Belshe wrote:

> On Mon, Apr 19, 2010 at 12:52 AM, Greg Wilkins <gregw@webtide.com
>     But in many deployments, SSL will be terminated on a box
>     remote from the application and the connection will go through
>     intermediaries provided by many vendors for load balancing,
>     aggregation, connection aggregation etc. The specification
>     needs to support such intermediaries in 2020.
> 
> 
> This is a fair point; but intermediaries within your (the site owner)
> control is a solvable problem, whereas intermediaries outside your (the
> user) control are not.

I believe that the vast majority of site owners to not control
the network infrastructure within the data centre in which
they are deployed.

But even if they do control them,  I agree that the problems of
non encrypted websocket interoperability between intermediaries
are definitely solvable.  I also think they should be solved by
this WG.    If not - who else?


cheers