Re: [hybi] Flow control quota

Martin Sustrik <sustrik@250bpm.com> Fri, 01 June 2012 08:43 UTC

Return-Path: <sustrik@250bpm.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 F1D3A21F85A2 for <hybi@ietfa.amsl.com>; Fri, 1 Jun 2012 01:43:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level:
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
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 hS8UKaEkfKek for <hybi@ietfa.amsl.com>; Fri, 1 Jun 2012 01:43:24 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 035B321F85A0 for <hybi@ietf.org>; Fri, 1 Jun 2012 01:43:24 -0700 (PDT)
Received: from [192.168.0.5] (host47-36-dynamic.181-80-r.retail.telecomitalia.it [80.181.36.47]) by mail.moloch.sk (Postfix) with ESMTPSA id F3FA118011A3; Fri, 1 Jun 2012 10:43:20 +0200 (CEST)
Message-ID: <4FC880A7.9070007@250bpm.com>
Date: Fri, 01 Jun 2012 10:43:19 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111109 Thunderbird/3.1.16
MIME-Version: 1.0
To: Arman Djusupov <arman@noemax.com>
References: <001a01cd3e69$4a221c10$de665430$@noemax.com> <4FC732DC.3000308@250bpm.com> <000e01cd3f1c$af15ad40$0d4107c0$@noemax.com>
In-Reply-To: <000e01cd3f1c$af15ad40$0d4107c0$@noemax.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Fri, 01 Jun 2012 08:43:25 -0000

On 31/05/12 13:01, Arman Djusupov wrote:
> 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.

That seems to suggest there's some kind of mis-layering happening here. 
Frames are used for flow control. Does it make sense to use them for 
compression as well? Shouldn't the compression rather happen on top of 
mutliplexing layer?

The situation is similar to compressing the payload in TCP packets. It 
is feasible, but in corner cases it can clash with MTU limits, cause 
re-fragmentation etc. The clean solution would be to layer compression 
on top of TCP layer.

Martin