Re: [hybi] Flow control quota

"Arman Djusupov" <arman@noemax.com> Thu, 31 May 2012 11:01 UTC

Return-Path: <arman@noemax.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 BABFA21F8592 for <hybi@ietfa.amsl.com>; Thu, 31 May 2012 04:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.065
X-Spam-Level:
X-Spam-Status: No, score=-2.065 tagged_above=-999 required=5 tests=[AWL=0.534, 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 uKngP5jRt6ew for <hybi@ietfa.amsl.com>; Thu, 31 May 2012 04:01:20 -0700 (PDT)
Received: from mail.noemax.com (mail.noemax.com [64.34.201.8]) by ietfa.amsl.com (Postfix) with ESMTP id E868E21F858E for <hybi@ietf.org>; Thu, 31 May 2012 04:01:19 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; t=1338462077; x=1339066877; s=m1024; d=noemax.com; c=relaxed/relaxed; v=1; bh=Klnjml2W7u/deIfiAoTAl+zcA0A=; h=From:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding:In-Reply-To:References; b=hvZ1oth4WRIM4lxwCbglqUdqRyfBufvQ3yJtlZK2TBqtrVPZmZgHELFBaEw+LYZxAyiIlRMy0JmsFMZ7vi9mpjeHRyyMannihIUIVXCTYu1/yz2x1jArmP+17vu2Ii1LYxhWjMzt2Tgm2LvgXfEN36HMPcLL49Yz93d2eVps1Y0=
Received: from mail.noemax.com by mail.noemax.com (IceWarp 10.4.0) with ASMTP (SSL) id PQG27916; Thu, 31 May 2012 14:01:16 +0300
From: Arman Djusupov <arman@noemax.com>
To: 'Martin Sustrik' <sustrik@250bpm.com>
References: <001a01cd3e69$4a221c10$de665430$@noemax.com> <4FC732DC.3000308@250bpm.com>
In-Reply-To: <4FC732DC.3000308@250bpm.com>
Date: Thu, 31 May 2012 14:01:01 +0300
Message-ID: <000e01cd3f1c$af15ad40$0d4107c0$@noemax.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: AQDnHEYxNcL9Xb2UVJoRm1lbL/BkAQFoH3KRmKSpWoA=
Content-Language: en-us
Cc: hybi@ietf.org
Subject: Re: [hybi] Flow control quota
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, 31 May 2012 11:01:20 -0000

When the per-frame compression extension is being used on a logical channel,
it is impossible to create a frame of exactly the desired size. A few bytes
of quota will always be unutilized unless some padding is used. The mux
specification prohibits sending frames bigger than the available quota. When
per-frame compression is applied on the payload before mux, this payload
cannot be fragmented any more. Even if we make compression extension mux
aware, it cannot produce a 1 byte compressed frame, it can only flag a frame
as uncompressed and simply send 1 byte. In general, sending 1 byte in a
separate frame is not desirable.

Extensions that set RSV bits prohibit frame fragmentation. This causes a
general incompatibility issue with mux FC when an extension is applied
before the mux. We need to consider whether there is a solution to this.

With best regards,
Arman

-----Original Message-----
From: Martin Sustrik [mailto:sustrik@250bpm.com] 
Sent: Thursday, May 31, 2012 11:59 AM
To: Arman Djusupov
Cc: 'Takeshi Yoshino'; hybi@ietf.org
Subject: Re: [hybi] Flow control quota

On 30/05/12 15:36, Arman Djusupov wrote:

> Sometimes the sending side cannot fully utilize the remaining quota 
> available (a typical example is when the remaining quota is too small)

That's interesting. Can you provide a concrete example?

It seems to me that even if the quota is 1 byte, you can send a frame with 1
byte.

Martin