IETF Logo Mail Archive

Re: [hybi] first draft of WS mux extension

John Tamplin <jat@google.com> Mon, 24 October 2011 09:00 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 DF6F821F8CB0 for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 02:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.811
X-Spam-Level:
X-Spam-Status: No, score=-105.811 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_UNSUB18=0.131, 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 1TzhHFrIU-IG for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 02:00:23 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 2433E21F8CAB for <hybi@ietf.org>; Mon, 24 Oct 2011 02:00:22 -0700 (PDT)
Received: from wpaz24.hot.corp.google.com (wpaz24.hot.corp.google.com [172.24.198.88]) by smtp-out.google.com with ESMTP id p9O90LE2025059 for <hybi@ietf.org>; Mon, 24 Oct 2011 02:00:21 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1319446821; bh=Scd64cmABEOChbKblSmyEHZobwI=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=ABo7gthxxyRC6F57bwr+9TUB6zJHzUqXGOTYe/Jyaxw+w2PO4vuPiXk6oY9k5xejy 62b08m6bH5l9T98A5UZkQ==
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=Q4a2Kz0hLk3P+LcaFdEGLIZpu52wPOoZ0VTd9HwjQH1N/DqoOtM+xWAmgsOjViAAD tqVuRaTdGEnB/igyV4DWw==
Received: from vcbfl15 (vcbfl15.prod.google.com [10.220.204.79]) by wpaz24.hot.corp.google.com with ESMTP id p9O8xQ5r004314 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Mon, 24 Oct 2011 02:00:20 -0700
Received: by vcbfl15 with SMTP id fl15so8434263vcb.5 for <hybi@ietf.org>; Mon, 24 Oct 2011 02:00:20 -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=23bEgKBtEKWtm8InnoSv/6ft9RxBPnkXNNOLbIS6xos=; b=hn6SxU2tFqoBMNuN5RhHkQOdHdDLRQmzCt1npOmkLpwm2e3BZTUuEfJUAjdG4TOtWd WxU+zPPQ81MwkJwwJAgg==
Received: by 10.229.219.20 with SMTP id hs20mr525904qcb.37.1319446820252; Mon, 24 Oct 2011 02:00:20 -0700 (PDT)
Received: by 10.229.219.20 with SMTP id hs20mr525898qcb.37.1319446820115; Mon, 24 Oct 2011 02:00:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.134.1 with HTTP; Mon, 24 Oct 2011 02:00:00 -0700 (PDT)
In-Reply-To: <21d301cc9227$26c55c30$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>
From: John Tamplin <jat@google.com>
Date: Mon, 24 Oct 2011 05:00:00 -0400
Message-ID: <CABLsOLBkjZrRiw6bD=f51+u7m6OyJU8SZpsT=4r3uTW17HEUew@mail.gmail.com>
To: Len Holgate <len.holgate@gmail.com>
Content-Type: multipart/alternative; boundary="00163628385003540904b007a73a"
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 09:00:24 -0000

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

> No, you'd just use the existing framing in the base protocol and all
> fragments would have the FIN bit set. Thus any channel can interleave
> without changing any rules from the base protocol. You'd then have a single
> FIN bit in the extension data, before the channel id, which acts as the fin
> bit for this channel's data.
>
> Your example in 7 becomes
>
> 81 06 [FIN BIT HERE = 0]01 "Hello" 81 04 [FIN BIT HERE = 1]02 "bye" 81 07
> [FIN BIT HERE = 1]01 " world"


Then those same intermediaries would have to understand the MUX extension in
order to do anything with frames anyway -- I don't see what this gains.

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

v2.23.0 | Report a Bug | By Email