On 5/15/2014 5:09 AM, Bob Briscoe wrote:
Wes,
I assume you also want comments on the new version. Is there a deadline
for comments?
Absolutely, yes. There's no deadline at the moment, but it would
be good to get any out sooner rather than later, especially if they're
likely to need more
Gorry,
At 16:55 15/05/2014, go...@erg.abdn.ac.uk wrote:
Great, I look forward to comments on the actual text. I agree the front
part needs more structure and more topics called out. i started adding
that in -04 and would be pleased to add a few more subsections if we get
agreement.
I'll wait
Gorry,
And just on this...
a) Congestion collapse: An AQM cannot prevent congestion collapse -
that is the job of congestion control and, failing that, of policing.
Even isolation (e.g. flow separation) doesn't prevent congestion
collapse, because collapse is caused by the load from new
I agree with the complement language. I don't mind if they are separable.
Integration, however, is highly advantagous.
I started another thread on the backlog issue.
Because scheduling requires policy and AQM doesn't.
Machine gunning down packets randomly until the flows start to behave
