Re: [hybi] CML (really the role of intermediaries)

["Shelby Moore" <[e-mail]>]

> On Mon, 2010-08-23 at 00:21 -0400, John Tamplin wrote:
>
>> Also, an intermediary might be used as a front end to a server farm,
>> which receives the connection, aggregates them, and load-balances to
>> backend servers.
>
> +1 on connection management.
>
> If WS is over TLS, this server side intermediary is going to want to
> terminate the TLS off the server as well. That makes it necessary to
> have some kind of non-tls format for it to forward the stream on with.
> (HTTPS/HTTP works well here imo.)

Can we please stop conflating the protocol stack layers?  Here is another
example:

http://www.ietf.org/mail-archive/web/hybi/current/msg03551.html

And yet more examples of wanting to conflate TLS with WebSockets base
protocol, which goes against the principle of letting users (market)
decide:

http://www.ietf.org/mail-archive/web/hybi/current/msg03552.html

It is sub-optimal design, it is often harmful in unforseen ways, and it is
nearly _always_ unnecessary conflation (there is another way to do it).

Tangential to my main point, I personally wouldn't feel that secure about
losing encryption inside the LAN or even inside the server or even inside
the database server (end-to-end security please!):

https://bugzilla.mozilla.org/show_bug.cgi?id=588704#c43