Re: [hybi] Call for interest: multiplexing dedicated for WebSocket

Takeshi Yoshino <tyoshino@google.com> Tue, 28 May 2013 06:23 UTC

Return-Path: <tyoshino@google.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BAAD21F8EA4 for <hybi@ietfa.amsl.com>; Mon, 27 May 2013 23:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.677
X-Spam-Level:
X-Spam-Status: No, score=-1.677 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_24=0.6, NO_RELAYS=-0.001, WEIRD_PORT=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iZTWU8Hq9m0R for <hybi@ietfa.amsl.com>; Mon, 27 May 2013 23:23:01 -0700 (PDT)
Received: from mail-ea0-x233.google.com (mail-ea0-x233.google.com [IPv6:2a00:1450:4013:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id CFD9B21F8481 for <hybi@ietf.org>; Mon, 27 May 2013 23:23:00 -0700 (PDT)
Received: by mail-ea0-f179.google.com with SMTP id z16so4337245ead.10 for <hybi@ietf.org>; Mon, 27 May 2013 23:22:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=alB3WFcjFlnHHPGgyLUd+OYJhC233sCjMO9vaLiW5pk=; b=iBcElCQy6zJZd+09PH0JSGwa7wrzEN9E8aDfydLGydA9OH5eRdxhiRykNh/jvfsCAA 2jFhDDa0bIqHElZSu+A1GnSIp/g+9SGbXnPTRPrazGUd5iuw+MaUrmv7Ev7r9l4FT9Ju +Hw8m5T8Oo/s7w9pZgLptFclrXH6V2Ht6s4oUpjSxAcTtK/cQuNn2VRauwugYErSh85r sRVfz34/H4huMWrUZp1P9WQeq+HJgm79NuBbFitk+SMb6Xk10CT3aBlgmXeTN2K928EC m7ZbqXT4qDZTc+08pXYQp2OHBZ+XfE9o5XJhhK3+TylwCqUlvHOw0CKW6dBymOgpH4DH AtOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=alB3WFcjFlnHHPGgyLUd+OYJhC233sCjMO9vaLiW5pk=; b=d++hTGlrlzSGhRUUJgnkaJFihDeyngHZ9dafsdGU1HCmHAt27MlWGAMEUGbZzn4+2h +FW3UKl58RJYHpLN5ky55Ehj/1uLrJ5+6mE6IcbgA35od8NJAX4mF91Zv+xiNNE5WkMk Dd1xIz+0b/6BuXFBFxAPIJUs4VWPVM9DYMSj2AJqWO57CrBdx2DOE4lGh7c7p9o5kSDD /LqJ/TSWtMwuNMsrO8MJx8b8q7rlgGl8HH42WoUlfr0iK6v8bBF01Ox0dQAQ5LNzFKmn Zh2yCTIgamkNF7kMHVXOOmTsfZmF+ZtR0U69lOPNWzc04vIRoXeUy6qXieWJiOQ8veap HxMg==
X-Received: by 10.15.32.142 with SMTP id a14mr12583678eev.152.1369722179489; Mon, 27 May 2013 23:22:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.86.67 with HTTP; Mon, 27 May 2013 23:22:39 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D4422C3DA774@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJZxr+aG7GZa4f-dUOTGj4bnJ+3XxivUX4jei5CMyqN4LQ@mail.gmail.com> <634914A010D0B943A035D226786325D4422C319646@EXVMBX020-12.exch020.serverdata.net> <CAH9hSJYrrbSM3TTSKCQ=AMcwCfE4zqNAa1kuAvecrXZTLqy2gQ@mail.gmail.com> <634914A010D0B943A035D226786325D4422C3DA774@EXVMBX020-12.exch020.serverdata.net>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Tue, 28 May 2013 15:22:39 +0900
Message-ID: <CAH9hSJaAzpmkm2fvALma5YPhWs-E+5u1vOxdLZggJyJgEYGRUQ@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary=089e01635210f349d304ddc14b7e
X-Gm-Message-State: ALoCoQmKn366fCGkH6GALQomyc70K9KE82ye7sK0sdqWYFpoOVJpqS78NR+zgFZk+goJebZU3m9edlKV/wtQzFo+MTky03s4dABg1LXNFqkjeaCbrc615V1PzznctH5Q+52vOWS04/CraXTHw74IvNkCDGJwqgzWQR6Y8eCdSwQUhPMmkDMMs8tlOL+tzPoNa4mnVCdsfI31
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Call for interest: multiplexing dedicated for WebSocket
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 28 May 2013 06:23:02 -0000

On Mon, May 27, 2013 at 8:59 PM, Tobias Oberstein <
tobias.oberstein@tavendo.de> wrote:

> >>However, when running _different_ apps on the same device connecting to
> the same origin,
>
> >You meant same ws:// address?
>
> Yes, sorry not origin.
>
> I had a look into the MUX RFC again .. couldn't find anser to the
> following (may have missed sth):
>

It's not yet specified.


> What WS addresses would be eligible to be multiplexed over a single WS
> connection?
>
> a) ws://somehost.com:999/
> b) ws://somehost.com:999/foo
> c) ws://somehost.com:999/bar
>
> d) wss://somehost.com:999/
> e) wss://somehost.com:999/foo
> f) wss://somehost.com:999/bar
>
> All of a) - f) are to the same target IP:port and hence could share the
> same TCP.
>

I think it's fine.


> However, d) - f) use wss, and hence have a TLS handshake right after TCP
> establishment.
>

Right unless TLS parameters differ (such as client cert) between paths.

See also SPDY's CREDENTIAL frame.
https://github.com/grmocg/SPDY-Specification/blob/gh-pages/draft-mbelshe-spdy-00.txt


> So d) - f) cannot be multiplexed over the same physical WS as a) - c)?
>

It's fine and up to the client.


> Or can an implementation just "silently" transport a)-c) also over wss,
> and hence multiplex all of a) - f) over 1 physical WS?
>
> Lastly, a)-c) are to the same target IP:port and also WS schema (ws, not
> wss) - and hence can be multiplexed over 1 physical WS even though they are
> to different URL paths?
>
> IOW: in the context of ws-mux, what is "same target"?


Basically ip:port. We don't need to isolate them based on hostname, I
believe, unless it's required by some security/privacy policy.