Re: [hybi] Extensibility mechanisms?

Ian Hickson <ian@hixie.ch> Fri, 16 April 2010 20:14 UTC

Return-Path: <ian@hixie.ch>
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 A600D28C1E7 for <hybi@core3.amsl.com>; Fri, 16 Apr 2010 13:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Level:
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[AWL=1.032, 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 ZvTkh04CH-1H for <hybi@core3.amsl.com>; Fri, 16 Apr 2010 13:14:20 -0700 (PDT)
Received: from looneymail-a1.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id A0C363A6B7B for <hybi@ietf.org>; Fri, 16 Apr 2010 13:13:17 -0700 (PDT)
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by looneymail-a1.g.dreamhost.com (Postfix) with ESMTP id 4376415D819; Fri, 16 Apr 2010 13:13:10 -0700 (PDT)
Date: Fri, 16 Apr 2010 20:13:09 +0000
From: Ian Hickson <ian@hixie.ch>
To: Greg Wilkins <gregw@webtide.com>
In-Reply-To: <4BC860FD.8080007@webtide.com>
Message-ID: <Pine.LNX.4.64.1004161952530.751@ps20323.dreamhostps.com>
References: <h2w5c902b9e1004152345j992b815bz5f8d38f06a19181a@mail.gmail.com> <Pine.LNX.4.64.1004160701250.751@ps20323.dreamhostps.com> <4BC860FD.8080007@webtide.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
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: Fri, 16 Apr 2010 20:14:30 -0000

On Fri, 16 Apr 2010, Greg Wilkins wrote:
> 
> The whole point of having a standard like websocket, is so that the 
> network infrastructure can implement the RFC and then we have known 
> semantics over that connection that intermediaries can at least handle 
> correctly, but may also do clever stuff with.

That wasn't even on my list of reasons for originally coming up with 
TCPConnection, let alone the main reason.

The main reason for the Web Socket protocol is to have one protocol that 
the browsers can all implement in an interoperable fashion so that servers 
can implement things once and have them work with all browsers. In the 
ideal deployment the connection is wrapped in end-to-end TLS, so the 
intermediaries can't do anything with it. There were only two reasons for 
even allowing unencrypted Web Socket originally: requiring amateurs to 
figure out TLS seemed like too high a bar, and there is still some concern 
that when the connection is being used for entirely public information, 
the TLS connection overhead is too expensive to justify.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'