IETF Logo Mail Archive

Re: [hybi] Flow control quota

Martin Sustrik <sustrik@250bpm.com> Mon, 25 June 2012 09:39 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 59BD921F8494 for <hybi@ietfa.amsl.com>; Mon, 25 Jun 2012 02:39:56 -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 E6OT8QBCPGYj for <hybi@ietfa.amsl.com>; Mon, 25 Jun 2012 02:39:55 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id B815121F8474 for <hybi@ietf.org>; Mon, 25 Jun 2012 02:39:55 -0700 (PDT)
Received: from [89.173.20.49] (chello089173020049.chello.sk [89.173.20.49]) by mail.moloch.sk (Postfix) with ESMTPSA id 03F99182BCCB; Mon, 25 Jun 2012 11:39:52 +0200 (CEST)
Message-ID: <4FE831E8.90207@250bpm.com>
Date: Mon, 25 Jun 2012 11:39:52 +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: Takeshi Yoshino <tyoshino@google.com>
References: <CAH9hSJaWrUX6gFNLT4xkXLYKHSUH5+Y7AvqN9cD_CwekvsNu3A@mail.gmail.com> <001001cd4000$fe2c82c0$fa858840$@noemax.com> <4FCCAE6B.1010306@250bpm.com> <002d01cd4262$747957b0$5d6c0710$@noemax.com> <20120607022312.GA26406@jl-vm1.vm.bytemark.co.uk> <000e01cd449d$1c0ed220$542c7660$@noemax.com> <CAH_y2NE6+3r_9pkYXhMOiRWfGJXGauEYCqg-8GvtOoCT9Ch0mA@mail.gmail.com> <000401cd4566$d5f6bb70$81e43250$@noemax.com> <CAH9hSJY9d3dS_2vTZ-AXwuX0WnJuwZXrFyJtWik5SoKnQ3kWmw@mail.gmail.com> <4FD85D7C.3000902@250bpm.com> <20120623023915.GT5812@jl-vm1.vm.bytemark.co.uk> <CAH9hSJaqd1PgXXTdYxrCNtNRZviAmFVysXWDPJgYg2NR+anKuA@mail.gmail.com>
In-Reply-To: <CAH9hSJaqd1PgXXTdYxrCNtNRZviAmFVysXWDPJgYg2NR+anKuA@mail.gmail.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: Mon, 25 Jun 2012 09:39:56 -0000

On 25/06/12 11:28, Takeshi Yoshino wrote:
> On Sat, Jun 23, 2012 at 11:39 AM, Jamie Lokier <jamie@shareable.org
> <mailto:jamie@shareable.org>> wrote:
>
>     Martin Sustrik wrote:
>      > On 13/06/12 08:50, Takeshi Yoshino wrote:
>      >
>      > >It's also an option that we give up frame-level extensions other
>     than mux.
>      >
>      > That makes sense IMO. Fragmentation is an integral part of
>      > multiplexing. Using it for other purposes is just asking for
>      > trouble.
>
>
> Based on the context, I think that Martin just agreed with me in terms
> of avoiding use of fragmentation for other extensions such as
> compression but didn't mean that fragmentation should be exclusive for
> multiplexing.

Yes. Exactly. Fragments can be used by layers below (WS protocol as 
such) but not by the layers above (other extensions, applications etc.)

Compare that to TCP/IP:

Packets are defined at IP level and used for control messages (SYN, RST, 
...) by TCP. They are also used for transporting fragmented data.

However, no layer on top (compression on top of TCP, application using 
TCP) can mess with the fragmentation.

Martin

v2.23.0 | Report a Bug | By Email