Re: [hybi] I-D Action: draft-ietf-hybi-websocket-multiplexing-01.txt

Greg Wilkins <gregw@intalio.com> Tue, 22 May 2012 09:11 UTC

Return-Path: <gregw@intalio.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 4913521F853D for <hybi@ietfa.amsl.com>; Tue, 22 May 2012 02:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level:
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_38=0.6, RCVD_IN_DNSWL_LOW=-1]
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 4buJErlSFm+u for <hybi@ietfa.amsl.com>; Tue, 22 May 2012 02:11:40 -0700 (PDT)
Received: from mail-qa0-f44.google.com (mail-qa0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8DA4F21F8450 for <hybi@ietf.org>; Tue, 22 May 2012 02:11:40 -0700 (PDT)
Received: by qadz3 with SMTP id z3so2207099qad.10 for <hybi@ietf.org>; Tue, 22 May 2012 02:11:39 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=VxcW/YNc/58ueHB3kMcTuSTIiiALayKHA4H6HInk/KY=; b=dmTw5/tb52rNMdOtfAiX6z3Tk4rhdL/nPqwLK3I27roj9yqW44XjVPR6G8DJJ2hcTH V6NMvTWRYNajZagKvk32oiX3zXqIF7cEqwelMzc0giLXXI6QN3OV33lVCMJrzsdcmoOB oWnrkPBQ/0idFcVl7fy9FjKd0ZrPlAy5Hrd71J7TnO49bhprYrqCoUUu3LnQ+2TwiPsL CGXitYwaDJcHdyj4el8hh0lasg7r1+q14cC+N+Mzb8c1gbl5OaJIH60qyDmdvi/ewk1f 9VI84TcO+u0knfRvJ1iZsaf8+yP8OjdpHPcd9VtaRxcgxtDeKVJ+u8VkKvKtPbfHyOZ5 23zQ==
MIME-Version: 1.0
Received: by 10.224.190.68 with SMTP id dh4mr43430998qab.5.1337677899829; Tue, 22 May 2012 02:11:39 -0700 (PDT)
Received: by 10.229.72.97 with HTTP; Tue, 22 May 2012 02:11:39 -0700 (PDT)
In-Reply-To: <CAH9hSJZGjHLzuSz2KZVSuBLtyeC3wfed4raRux0TU1Ymt1VQ4A@mail.gmail.com>
References: <20120420050004.2740.14810.idtracker@ietfa.amsl.com> <CAH9hSJZGjHLzuSz2KZVSuBLtyeC3wfed4raRux0TU1Ymt1VQ4A@mail.gmail.com>
Date: Tue, 22 May 2012 11:11:39 +0200
Message-ID: <CAH_y2NHpcriaGO1k0h7J-5rvAr8T6O6sfY67rEC3Fe3QHkMC0Q@mail.gmail.com>
From: Greg Wilkins <gregw@intalio.com>
To: Takeshi Yoshino <tyoshino@google.com>
Content-Type: multipart/alternative; boundary="20cf300fad190b133c04c09c68db"
X-Gm-Message-State: ALoCoQlHYgK8NgckvBmmkuWNeuD9tI73xGJCAWcRWNaiEnV7Fn53deCXLBDxlwGtD98cqnobFxCi
Cc: hybi@ietf.org
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-websocket-multiplexing-01.txt
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, 22 May 2012 09:11:41 -0000

I think we should note the discussion happening over in SPDY-dev about
their flow control and concerns about it

  https://groups.google.com/forum/?fromgroups#!topic/spdy-dev/JB_aQPNI7rw

Our mux proposal with it's send quotas has effectively the same problem -
namely that a fixed quota per channel can cause a significant under
utilisation of a fast link, but can also represent a significant over
allocation of capacity if many channels are present.  I think we need to
closely follow that discussion to see what solutions may be developed
before we commit to a per channel window flow control.

cheers



On 20 April 2012 08:08, Takeshi Yoshino <tyoshino@google.com> wrote:

> Hi all,
>
> Here's the ietf -01 version of multiplexing spec.
>
> Diff:
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-hybi-websocket-multiplexing-01.txt
>
> Changes from -00 are:
> - now multiplex control blocks MUST be interpreted when the entire message
> containing them has arrived
> - now the base for delta-encode of handshake is the last
> AddChannelRequest/Response with Enc=identity
> - clarified how much the send quota is until receiving reply
> -- note that this is still open for discussion
> - a server MUST _Fail the Physical Channel_ when there's inconsistency
> between Sec-WebSocket-Extensions in AddChannelRequest/AddChannelResponse
> (e.g. some value that need to be the same for all logical channels is
> altered)
> -- another option is to just _Fail the Logical Channel_
> - style/readability
> -- new term "multiplexed connection" to clarify the difference between
> logical channels (used for both control and transferring multiplexed
> connection's data) and multiplexed WebSocket connections
> -- new term "Implicitly Opened Connection" defined to reduce text
> -- made definition of send quota and quota parameter in Flow Control
> section more detailed
>
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>