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

Tobias Oberstein <tobias.oberstein@tavendo.de> Wed, 22 May 2013 15:13 UTC

Return-Path: <tobias.oberstein@tavendo.de>
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 4943721F8E87 for <hybi@ietfa.amsl.com>; Wed, 22 May 2013 08:13:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 1v21J1rNnnVD for <hybi@ietfa.amsl.com>; Wed, 22 May 2013 08:13:48 -0700 (PDT)
Received: from EXHUB020-4.exch020.serverdata.net (exhub020-4.exch020.serverdata.net [206.225.164.31]) by ietfa.amsl.com (Postfix) with ESMTP id BFF7B21F8607 for <hybi@ietf.org>; Wed, 22 May 2013 08:13:45 -0700 (PDT)
Received: from [10.157.82.16] (89.204.138.16) by smtpx20.serverdata.net (206.225.164.36) with Microsoft SMTP Server (TLS) id 8.3.264.0; Wed, 22 May 2013 08:13:44 -0700
Message-ID: <519CE075.4000106@tavendo.de>
Date: Wed, 22 May 2013 17:12:53 +0200
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
References: <CAH9hSJZxr+aG7GZa4f-dUOTGj4bnJ+3XxivUX4jei5CMyqN4LQ@mail.gmail.com> <CAH9hSJZUG1f+3Uk=t2=A5i4O9=wPvAisspM=pgmGEH9emTL9-Q@mail.gmail.com> <CAH9hSJZai_UuxW4O6mZcEJT2DJoURtLo16XNci1qkYVWv4HVdg@mail.gmail.com> <007501ce56f0$67f74080$37e5c180$@noemax.com> <519CD6A1.7080708@ericsson.com>
In-Reply-To: <519CD6A1.7080708@ericsson.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
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: Wed, 22 May 2013 15:13:53 -0000

Am 22.05.2013 16:30, schrieb Salvatore Loreto:
> <as individual>
> I tend to agree with the fact that if we want standardize mux in
> WebSocket we should speed up simplifying the spec.

+1 for the simplest possible mux that does the core job.

However, I currently think that having a per-logical channel flow 
control is required to make it useful (cannot be dropped for the sake of 
simplification). I might be wrong.

So the practical question: in what areas could we simplify the current 
mux spec?

>> much longer to form into the final specification. In any case,
>> hybi-mux must be reviewed and finalized in a very short time, plus it
>> should be simpler and easier to implement than both SDPY and HTTPbis
>> based multiplexing.

Yep, I agree.

>>
>> With best regards,
>>
>> Arman
>>
>> *From:*hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] *On Behalf
>> Of *Takeshi Yoshino
>> *Sent:* Sunday, May 19, 2013 7:31 AM
>> *To:* hybi@ietf.org
>> *Subject:* Re: [hybi] Call for interest: multiplexing dedicated for
>> WebSocket
>>
>> I got one comment about this.
>>
>> He/she suggested that we finish the WebSocket dedicated multiplexing
>> quickly even by simplifying the spec much e.g. cutting some
>> functionality in it that would take much time to get consensus, and
>> when HTTP/2.0 is matured, switch to that.
>>
>>
>>
>> _______________________________________________
>> hybi mailing list
>> hybi@ietf.org
>> https://www.ietf.org/mailman/listinfo/hybi
>
>