[hybi] Simplify WebSocket multiplexing

Takeshi Yoshino <tyoshino@google.com> Thu, 30 May 2013 07:17 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 BF1CE21F9590 for <hybi@ietfa.amsl.com>; Thu, 30 May 2013 00:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.458
X-Spam-Level:
X-Spam-Status: No, score=-1.458 tagged_above=-999 required=5 tests=[AWL=0.519, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-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 dWwFRncA6IEC for <hybi@ietfa.amsl.com>; Thu, 30 May 2013 00:17:00 -0700 (PDT)
Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 193A121F88EA for <hybi@ietf.org>; Thu, 30 May 2013 00:16:59 -0700 (PDT)
Received: by mail-ea0-f171.google.com with SMTP id b15so6243842eae.30 for <hybi@ietf.org>; Thu, 30 May 2013 00:16:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=uJ0Xt2+SJghwj94wtSocI/+zT+Td3zg4L93u/+ymB4Y=; b=HmsKBeF0Qrd8z8GMJCI01icqSNBnkyovRAprwIZxhbAZ9DFn/cuO43FiTtoTssnuEA b+UPtZsqMK8Y/EIC2G3KNy4wBREMenyEJXvhJCjIg1gfVSi0HG2Vq+aiETpW4RDQBNv8 jSVsmGU2lNG1c1bA20eipBy7xkKx4/UPRR0UR0m7hb2ew83cABCWrxS8Bt02j2W1X4r4 onBtAWDqb1YhudPTjbBInOsYGs4HAPiOw/IMOVhNc4m2fYZGLRqMloev5ZgVBQUjLn+r MR8FBa9XGmYhC+j+GsKZr3nboNie1CsXbgWCFKLJ05QDVzRbqDQDGpH7sNThA+WrTQtZ 1Yvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :x-gm-message-state; bh=uJ0Xt2+SJghwj94wtSocI/+zT+Td3zg4L93u/+ymB4Y=; b=hSzumZndthQBfQwiflGWFnw0x4gvXeu3auO9eKsbdYi4i3uA0xKyhgBjPNpNzirqeH hz8mOHTEAbgd1w+p9FYYtOW2AqgcjG+QzO8fKIZo/e+mmUhb8B9cEi/SGRFAXHDm+kt6 ofxngH7vJAs57k97xOhlt8fOprRj38ZOKLokZDZ+pPTa9Mwqs/7Nah9wIdCqG1gvwDLF ztJ8p0kM5vrFLc5tswr/O3cktDbl1z7ftR8TbsGUTAwv2qyAytZRVtREoVYuGcmuD5pc S5cqX0pjnzQ92hXDBWzk149/GoHeMWcRoP8mBarQ+tFItjL5lbZ3Y21XgyKwvs5qHy5N 0Bow==
X-Received: by 10.14.194.73 with SMTP id l49mr8550611een.99.1369898218837; Thu, 30 May 2013 00:16:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.86.67 with HTTP; Thu, 30 May 2013 00:16:38 -0700 (PDT)
From: Takeshi Yoshino <tyoshino@google.com>
Date: Thu, 30 May 2013 16:16:38 +0900
Message-ID: <CAH9hSJaUnFRve-JMUm1pzdxreHsd5R13gUa0s9_S2u1t6Y87rQ@mail.gmail.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b343e3ab690bc04ddea482f
X-Gm-Message-State: ALoCoQmFL6qmXss5788d5iteBmcqIWz6N43DovS2Sd8UumauyeF9G7t2sW8AOv5rNfb/grtiiMWtGEwf6qdkEtIWNxBqZ8Bz7x3ARFdTHKZSUDJL2/f9RVffpdjG2hwNWiEqDtqTyCFbJhFcW5o7xPqv1WSPTZciJjSkD1UBpgaVtthkij0IQMn9cwhL4UnHlxNqfCUvPVw9
Subject: [hybi] Simplify WebSocket multiplexing
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: Thu, 30 May 2013 07:17:00 -0000

(Branching from the thread "Call for interest: multiplexing dedicated for
WebSocket")

It seemed that we had rough consensus on accelerating WebSocket dedicated
multiplexing by simplifying it if we keep working on it.

I'd like to hear your opinion on this in this separate thread. Below listed
some points we could drop/simplify including both ones suggested in the
thread and some I came up with now.

1) Header delta encoding in AddChannelRequest
2) Header delta encoding in AddChannelResponse
3) Channel slot
4) Only one mux control in one message
5) Use the length encoding for encoding mux channel ID
6) Drop flow control

----

My opinion is to do 1, 2 and 4.