[hybi] Send quota value before receiving AddChannelResponse (was: Re: MUC: channel ID semantics)

Takeshi Yoshino <tyoshino@google.com> Wed, 18 April 2012 08:15 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 B552D21F85FC for <hybi@ietfa.amsl.com>; Wed, 18 Apr 2012 01:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level:
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 xnk7nkAVyf87 for <hybi@ietfa.amsl.com>; Wed, 18 Apr 2012 01:15:27 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id EA81F21F85DD for <hybi@ietf.org>; Wed, 18 Apr 2012 01:15:26 -0700 (PDT)
Received: by iazz13 with SMTP id z13so12309533iaz.31 for <hybi@ietf.org>; Wed, 18 Apr 2012 01:15:26 -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:cc:content-type :x-system-of-record; bh=h3LuKZjGk2wMxZ4kj/Ih+7whdyWxiwUCrZNAspiz+bE=; b=d+cLdmEugl9FwdshUesu4Kz11Pge++0+zbwEII9SAgILIuwaecHY5ce6496R1QRCSJ qD0Jb81VPMnGbPvyaGr8AmUPA8PVRfwFuFtHEH0ji9+Fol6W7E+koFfdOOeeXGge5l6r LRRwnhr7JYFISIMwYCqcnmyzQgtDRwkTV7RxBqxYiwKHrjH8JQeBsYwgzdgSXHy+RVrP /h0C99XsSrK8hcjMrXvViDR8QAnjq18XadXubwSnzt2ttJ55tWMRsZVt4iiyZ1eYtWlJ uwixUB8iujsUZACpSlpattDwr3k93CR1Bqk0w70Jgx2FaOVy99ngw4xTWCf5s6+GJub4 Xxuw==
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:cc:content-type :x-system-of-record:x-gm-message-state; bh=h3LuKZjGk2wMxZ4kj/Ih+7whdyWxiwUCrZNAspiz+bE=; b=PGimJTx3MOY5onPnosw+BxG2MXStiVWdMIJf+jWNFBTxm5blHRsHwsAvCtvY9oZ9Tz l6CbdY+nSt6VN4+toH+ScAAv7RZjTy8Op7yeolwK6r8tf3IlewJFeJa6cFPz1CD/vR8o MfaHZy2pZQlXLL7+Lvq3FSVK6qQh6YjXpgXAZ4vz+shucjNjalc5LbNt4j5xLFsg8pT0 5KFKY5x91mpkuoJjKi1TqvvEzZZ5dNviBkXliUcGkJLHUaxGjA1TkwrBE4ifma2x9PU3 4dskNdpC4W5MXpcXcGkaOWpxYva1iUrOlgxPgGyQhRuqZoRM3NyEGY8/XR85ARJGLgok EWhw==
Received: by 10.50.156.229 with SMTP id wh5mr12151267igb.28.1334736926603; Wed, 18 Apr 2012 01:15:26 -0700 (PDT)
Received: by 10.50.156.229 with SMTP id wh5mr12151258igb.28.1334736926514; Wed, 18 Apr 2012 01:15:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.176.164 with HTTP; Wed, 18 Apr 2012 01:15:06 -0700 (PDT)
From: Takeshi Yoshino <tyoshino@google.com>
Date: Wed, 18 Apr 2012 17:15:06 +0900
Message-ID: <CAH9hSJZP8FhAGANSwPfvdMCQPyfRhG7tqPT68e6VY5ZCAEROTw@mail.gmail.com>
To: Arman Djusupov <arman@noemax.com>
Content-Type: multipart/alternative; boundary="e89a8f2346a95f9f8604bdefa862"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQn4O6OcQbe8+bZKc4ujxxBHTbLOhd+phvPLg7VQSLOG3sxjK629VlZ/UdAAYUZwuUXNy2GHgT8t/ZkZ7msPuqoIMisCNimO/KQ/I3RYkpyzJqSRVTY6OsBx0Rdu4ffDeS/Tq/t3
Cc: hybi@ietf.org
Subject: [hybi] Send quota value before receiving AddChannelResponse (was: Re: MUC: channel ID semantics)
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, 18 Apr 2012 08:15:29 -0000

On Fri, Apr 13, 2012 at 20:09, Arman Djusupov <arman@noemax.com> wrote:

> BTW:
>
> “Different from non-multiplexed WebSocket connection, data frames of multiplexed channel except for the channel 1 opened by default MAY be sent before receiving AddChannelResponse as far as there's sufficient****
>
> send quota.  In case the AddChannelRequest fails, those frames are ignored by the other peer.”****
>
> ** **
>
> As far as I had previously understood, until a new logical channel
> receives the AddChannelResponse its flow control quota is 0. The initial
> quota is assumed to be 64K but this quota applies only once the channel is
> accepted and the handshake did not include/specify a quota that overrides
> this value. Wouldn’t this mean that the logical channel cannot send
> anything prior it was accepted due to the 0 quota even if the specification
> permits it to send messages, or did I miss something?
>

You're right. In the latest spec, it's not explicitly specified what the
value of send quota is until AddChannelResponse is received.

There're several options we can take.

a) specify the fixed value of send quota before AddChannelResponse in the
spec
b) add a new parameter "pre_handshake_quota" to multiplexing extension to
negotiate the value of send quota before AddChannelResponse
c) drop the feature to configure initial quota for each logical channel,
and redefine the quota parameter as pre-handshake send quota for all
logical channels

I'm not sure how many people really want to configure initial quota for
each logical channel independently.

Comment please.