Re: [hybi] Flow control quota

Takeshi Yoshino <tyoshino@google.com> Fri, 01 June 2012 11:04 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 C690921F864C for <hybi@ietfa.amsl.com>; Fri, 1 Jun 2012 04:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.847
X-Spam-Level:
X-Spam-Status: No, score=-102.847 tagged_above=-999 required=5 tests=[AWL=0.129, 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 mr1zKXVwtlcr for <hybi@ietfa.amsl.com>; Fri, 1 Jun 2012 04:04:43 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id F1AAA21F8642 for <hybi@ietf.org>; Fri, 1 Jun 2012 04:04:42 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so1801843ggn.31 for <hybi@ietf.org>; Fri, 01 Jun 2012 04:04:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=sUy1hrmwNegQbHx+muVLuvEj+F+RaFGD8KXMdl314jg=; b=Mf4Ws0qqXyBcqpqz8zEHv2ZIvrQUPssFVIllyZbQhK1LhyBzOluTP0Wal0vD/UbFti 2tpYQYSrmAfpLUs/+Nk7K94PpFIjaWxef36tt0XamGNUJsGN5TlhSI1v7x/my2nK5bSW rU+EkEB7pjFrpltxx8CjD3cpBGlJj4XUPQ/RAyCQTutPV3Mr4Mcv6OykfcDOWLzlPvDh HWkQzCwAEYIWt0uSF3TvivOtNYA2ha8ZtJ0sAX8Zu31GNJidGNaXBiop2QkI6uL01WQT VyNiznQNCF582ZtLeYh9Lx/nYaJr3EnEKOsd3XQAX2XnIni3MdxKSnu38pfGlblssQmj /Q4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record:x-gm-message-state; bh=sUy1hrmwNegQbHx+muVLuvEj+F+RaFGD8KXMdl314jg=; b=hBBxgGf16Nhws4pNzHeWLl9LD3WaMSkenetW5nyzuepPomWwHttnOUiycWN3zaSd2t l/UbvLBCEYf7LP4cTfmWL1Jo9d5tHZO1xuPYKO5DHCM3hmuB0pblIFiUPUrfEfOhPXxn jOAw8V8PVvEm//glLKzYOFl7ZmwKmR3y8x0kJZmcyt7GEXoGX1xdy7pPCoOs9vIkyc8C UL3YQCuRuKxWTy1D7ipOsufGe+lHCyu8Fr1xn+gP7KPOIcjR2jsM0hJ+IRIstLN3FRln RU8DD4my81daP4l8fAyYApyf4/z79jksDN4L2DFQSZ155uYj77RGGE7JWFnzqUH/lLuf Zz6w==
Received: by 10.43.69.83 with SMTP id yb19mr1175005icb.29.1338548682055; Fri, 01 Jun 2012 04:04:42 -0700 (PDT)
Received: by 10.43.69.83 with SMTP id yb19mr1174992icb.29.1338548681930; Fri, 01 Jun 2012 04:04:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.66.7 with HTTP; Fri, 1 Jun 2012 04:04:21 -0700 (PDT)
In-Reply-To: <000e01cd3f1c$af15ad40$0d4107c0$@noemax.com>
References: <001a01cd3e69$4a221c10$de665430$@noemax.com> <4FC732DC.3000308@250bpm.com> <000e01cd3f1c$af15ad40$0d4107c0$@noemax.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Fri, 01 Jun 2012 20:04:21 +0900
Message-ID: <CAH9hSJZmuBt=18N28EpRjmJv_FshxUq42CXw5BoXeaFrhV=ukQ@mail.gmail.com>
To: Arman Djusupov <arman@noemax.com>
Content-Type: multipart/alternative; boundary="bcaec51b1ea3b3783e04c16726cb"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQn4umgh/Sr6HJriI/RGeZo83gNLUkb6VhMcN5WD0mhKTctkVoWsdbpgbRmGdB/lVGNzGIyj9Dh88NFruPcYUQ4Vm8eb3+4ZBje9CGa0bEbL0Nf2Z6ihxu/C57g272u1xNVJ612A
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 11:04:43 -0000

Hi Arman,

Thanks for point out these risks.

OK, we should note that the quota need to be replenished to some quantity
without waiting for full consumption, maybe with the example of compression
extension you mentioned.

On Thu, May 31, 2012 at 8:01 PM, Arman Djusupov <arman@noemax.com> 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.
>
> 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.
>

Yes, the multiplexing code need to feed back to extensions behind it to
control fragment size.

Limiting quota to very small value such as 1 byte persistently is not
practical. The bandwidth will be quota / RTT. It's really slow. I think
that warning the risk of dead lock is enough.