Re: [hybi] WebSocket, TLS and intermediaries

Greg Wilkins <gregw@webtide.com> Wed, 21 July 2010 00:36 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 42EB43A6976 for <hybi@core3.amsl.com>; Tue, 20 Jul 2010 17:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.623
X-Spam-Level:
X-Spam-Status: No, score=-1.623 tagged_above=-999 required=5 tests=[AWL=0.353, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 fm1URPI-nzss for <hybi@core3.amsl.com>; Tue, 20 Jul 2010 17:36:13 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 520D73A6A56 for <hybi@ietf.org>; Tue, 20 Jul 2010 17:35:51 -0700 (PDT)
Received: by fxm1 with SMTP id 1so3550588fxm.31 for <hybi@ietf.org>; Tue, 20 Jul 2010 17:35:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.110.67 with SMTP id m3mr6093637fap.24.1279672542699; Tue, 20 Jul 2010 17:35:42 -0700 (PDT)
Received: by 10.223.112.129 with HTTP; Tue, 20 Jul 2010 17:35:42 -0700 (PDT)
In-Reply-To: <AANLkTiko_Pjie0FNRvLHsh5PAotW2a6OH=6oapEhJBOQ@mail.gmail.com>
References: <h2w5c902b9e1004152345j992b815bz5f8d38f06a19181a@mail.gmail.com> <Pine.LNX.4.64.1004160701250.751@ps20323.dreamhostps.com> <4BC860FD.8080007@webtide.com> <Pine.LNX.4.64.1004161952530.751@ps20323.dreamhostps.com> <35EFEA5E-9017-48A1-BB66-A0AF947E159F@d2dx.com> <AANLkTinihlL2sn3Kiwtcl7QYKhFlvmj9lvmH4_z02xF7@mail.gmail.com> <FC1F510E-6D48-4D75-A356-F455C9FD5BD8@apple.com> <AANLkTiko_Pjie0FNRvLHsh5PAotW2a6OH=6oapEhJBOQ@mail.gmail.com>
Date: Wed, 21 Jul 2010 10:35:42 +1000
Message-ID: <AANLkTikGLuKhFKd5YcuAKPit5TKzH2y6hYrC6rAyxG-c@mail.gmail.com>
From: Greg Wilkins <gregw@webtide.com>
To: Roberto Peon <fenix@google.com>
Content-Type: multipart/alternative; boundary="001636c9246e562269048bdafb71"
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] WebSocket, TLS and intermediaries
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, 21 Jul 2010 00:36:14 -0000

On 21 July 2010 10:15, Roberto Peon <fenix@google.com> wrote:

>
> Schools and other institutions will block port 443 if they feel
> unacceptable content is flowing over it and they have other means of dealing
> with it.
> I believe that this means that we need an 'authorized proxy' model. No
> proxy would be fully transparent (unless it was a reverse proxy representing
> the real endpoint), however it should be exceptionally easy to install a
> policy allowing the proxy explicitly. It is a hair more annoying for the
> user than no proxy, but it gives schools, etc. a way to control the
> computers that they own without blocking port 443 for everyone and
> everything.
>

+1

As Mike has said, there are good motives and bad motives for intermediaries.
We have to find a way to allow the good motives to be supported, even if
that costs a bit of complexity in the handshake/protocol.

Having explicit intermediaries would be very useful for knowing  timeouts,
optimizing keepalives and security considerations.

cheers