IETF Logo Mail Archive

Re: [hybi] first draft of WS mux extension

John Tamplin <jat@google.com> Mon, 24 October 2011 15:05 UTC

Return-Path: <jat@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 9A2E421F8E4A for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 08:05:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level:
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 86Cb2UQqQ0i9 for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 08:05:41 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id DE82421F8E46 for <hybi@ietf.org>; Mon, 24 Oct 2011 08:05:40 -0700 (PDT)
Received: from hpaq6.eem.corp.google.com (hpaq6.eem.corp.google.com [172.25.149.6]) by smtp-out.google.com with ESMTP id p9OF5XsQ005238 for <hybi@ietf.org>; Mon, 24 Oct 2011 08:05:34 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1319468734; bh=YyWBamlaFRM7hF1IqplCyBlJkiM=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=YTaquEL87myRi0FSm27aM/5R9D1Kr8iexDIboFatUn4u5P/5NNbGu54+MnlKpjWrg uEd+dKCI72uX4lkOIbq1g==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=mVHbIWjU7X8sS/TKVaAZphtLiUSVoTZpQB33lNRmr1bODVZ3nzjzlorbhiVdBzAy3 fUMEUZiMAvLDboL8O6Sqg==
Received: from vws15 (vws15.prod.google.com [10.241.21.143]) by hpaq6.eem.corp.google.com with ESMTP id p9OF50q8004103 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Mon, 24 Oct 2011 08:05:32 -0700
Received: by vws15 with SMTP id 15so8827895vws.6 for <hybi@ietf.org>; Mon, 24 Oct 2011 08:05:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=hiz5U4dfheOKSQvz/pchaAx16dvdS546cEPBSAcjAI0=; b=IYdqeEpWwwE/Vvk7jR/lqmonEIqJoOP4m1xZ4CM3UFqiJC3BuFsJtGw73Ka0Lrgfzx KwjaZnbCfbK5DvrbNe6g==
Received: by 10.150.135.2 with SMTP id i2mr21242284ybd.44.1319468732303; Mon, 24 Oct 2011 08:05:32 -0700 (PDT)
Received: by 10.150.135.2 with SMTP id i2mr21242269ybd.44.1319468732139; Mon, 24 Oct 2011 08:05:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.96.7 with HTTP; Mon, 24 Oct 2011 08:05:12 -0700 (PDT)
In-Reply-To: <21fe01cc9237$b08dc780$0a00a8c0@Venus>
References: <CABLsOLB3gqQgo0myNkHxGmvr5P55GeKqaUPnYP9RgnUsiVM++g@mail.gmail.com> <CALiegfmc=01Uw0eLZES=WGtWVBKPjQLz3itiPL4TPVwy5mZFmQ@mail.gmail.com> <CABLsOLDi-rXcDp9k_+bkMBrmswY-QbHkqXLKT+2wOQ7Y0ry0VQ@mail.gmail.com> <CALiegf=Tcbys=ekrg3=BdzToy7uw08UmtpmWzZh1ikDxww_4qQ@mail.gmail.com> <CALiegfnTiVLKh6Dvc_7U4oN2YOR5VgH7_YPc-O1WpygU8=gCbw@mail.gmail.com> <CABLsOLBH_b19CH8mfXF7mqE23YZ5skvprk77JD++dpW6DzfvJA@mail.gmail.com> <21c201cc921f$bbd76a00$0a00a8c0@Venus> <CABLsOLAMoa4C6o3nT+NmsS97ifTFgxRSW6SWGXtZrZ7MiPOM8g@mail.gmail.com> <21d301cc9227$26c55c30$0a00a8c0@Venus> <CABLsOLBkjZrRiw6bD=f51+u7m6OyJU8SZpsT=4r3uTW17HEUew@mail.gmail.com> <21e801cc922c$99b712b0$0a00a8c0@Venus> <634914A010D0B943A035D226786325D42D0B036D6F@EXVMBX020-12.exch020.serverdata.net> <21fe01cc9237$b08dc780$0a00a8c0@Venus>
From: John Tamplin <jat@google.com>
Date: Mon, 24 Oct 2011 11:05:12 -0400
Message-ID: <CABLsOLDKg3FgvzACbNMWvX05hEhSya0Zmi7cd-KwGa+SGGVYNg@mail.gmail.com>
To: Len Holgate <len.holgate@gmail.com>
Content-Type: multipart/alternative; boundary="000e0cd5d02612490404b00cc117"
X-System-Of-Record: true
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] first draft of WS mux extension
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: Mon, 24 Oct 2011 15:05:41 -0000

On Mon, Oct 24, 2011 at 6:28 AM, Len Holgate <len.holgate@gmail.com> wrote:

> Ok, sorry, it must fail to enable the extension.
>

While the intermediary could conceivably alter the handshake, in most cases
they are simply observers of the traffic.  If they actually terminate one
connection and create another, they are more properly tw WS endpoints rather
than an intermediary.


> If we don't change the base protocol and the intermediary doesn't care
> about
> payload data then it could allow the extension to be enabled and simply
> deal
> with the normal websocket framing rules and ignore the content of the
> frames
> and any mux specific stuff that's going on.


We aren't changing the base protocol -- the base protocol already allows
extensions to define the meaning of such things.  If existing intermediaries
violate this, then perhaps it is good to get an extension out early that
will break them, so they properly implement the spec.

The whole point of having MUX in the first place is that it can be done
without changing the endpoints.  In a typical scenario, the user agent
automatically reuses existing connections and sends to a mux-aware server,
with application code on both ends neither knowing or caring that this is
taking place.

-- 
John A. Tamplin
Software Engineer (GWT), Google

v2.23.0 | Report a Bug | By Email