[e2e] Why was hop by hop flow control eventually abandonded?
barney at databus.com
Wed Jul 17 08:04:16 PDT 2013
What are we talking about when we say "hop-by-hop" - the classic "don't
send me anything on this link because I've got no buffer to receive it"
or "don't send me anything on this flow because something downstream is
pushing back"? I thought these days bufferbloat is the problem, not buffer
depletion. What's an aggregate?
On Wed, Jul 17, 2013 at 09:36:08AM +0100, Jon Crowcroft wrote:
> so i think the design decision to throw out all hop by hop flow
> control was probably an error (not a disastrous one: as many people
> have pointed out, it simplified early router design a lot to be
> completely stateless - but you don't need to keep per-5-tuple based
> e2e state to do hop by hop flow control if its on aggregates, right?)
More information about the end2end-interest