Re: [hybi] BWTP and flow weigth (MulTCP)

Jamie Lokier <jamie@shareable.org> Mon, 08 March 2010 22:41 UTC

Date: Mon, 08 Mar 2010 22:41:42 +0000
From: Jamie Lokier <jamie@shareable.org>
To: Greg Wilkins <gregw@webtide.com>
Message-ID: <20100308224142.GA16057@shareable.org>
References: <548FC4B9D57A4043AAFFE888A39429031CF203A6AB@ESESSCMS0356.eemea.ericsson.se> <4B94D03F.2060208@webtide.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4B94D03F.2060208@webtide.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] BWTP and flow weigth (MulTCP)
Precedence: list

Greg Wilkins wrote:
> 
> Ingemar,
> 
> note firstly that it is my intention to come up with a reworked BWTP as a
> websocket subprotocol.
> 
> But eitherway, I think that having flow control for BWTP channels would
> be highly desirable, specially as one of the potential uses of BWTP
> is to multiple multiple clients together.

This is flow weight, not flow control.  They are really quite
different, even though they both "control" the flow.

Flow control is absolutely required when multiplexing independent
clients without their cooperation, otherwise one client can block
another from making progress, breaking their independence.

Flow weight is more like bandwidth management or QoS, except I presume
'CC' refers to congestion control.  It does indeed make sense to
include it in multiplexing.  Good multiplexing needs fairness
heuristics in general too.

-- Jamie

Re: [hybi] BWTP and flow weigth (MulTCP) Jamie Lokier
[hybi] BWTP and flow weigth (MulTCP) Ingemar Johansson S
Re: [hybi] BWTP and flow weigth (MulTCP) Greg Wilkins
Re: [hybi] BWTP and flow weigth (MulTCP) Ingemar Johansson S