On Wed, Nov 12, 2014 at 4:03 PM, Scheffenegger, Richard wrote:
> Hi Martin,
>
> I believe these papers may qualify that requirement:
>
> http://ipv6.cablelabs.com/wp-content/uploads/2014/06/DOCSIS-AQM_May2014.pdf
This documents the docsis-pie implementation which has rather a few
basic improvemen
"Scheffenegger, Richard" writes:
> * adopt the document draft-hoeiland-joergensen-aqm-fq-codel-01 as an
> AQM working group item, heading towards publication as informational.
Well I'm obviously in favour ;)
Still being fairly new to this process, however, could someone please
explain to me the
Hi,
The chairs would like to confirm that the AQM WG community agrees to
* adopt the document draft-hoeiland-joergensen-aqm-fq-codel-01 as an AQM
working group item, heading towards publication as informational.
Richard Scheffenegger
> -Original Message-
> From: aqm [mailto:aqm-bou
"Scheffenegger, Richard" writes:
> I believe these papers may qualify that requirement:
I'll add to that the results I presented yesterday in ICCRG:
http://www.ietf.org/proceedings/91/slides/slides-91-iccrg-4.pdf
However, I don't believe there has been any *theoretical* analysis of
either alg
Am 12.11.14 um 14:03 schrieb Scheffenegger, Richard:
Hi Martin,
I believe these papers may qualify that requirement:
http://ipv6.cablelabs.com/wp-content/uploads/2014/06/DOCSIS-AQM_May2014.pdf
http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=6925768
https://www.duo.uio.no/handle/10852
Hi Martin,
I believe these papers may qualify that requirement:
http://ipv6.cablelabs.com/wp-content/uploads/2014/06/DOCSIS-AQM_May2014.pdf
http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=6925768
https://www.duo.uio.no/handle/10852/37381
tl;dr - both pie and codel camps did some independent
[writing not as AD, but as random IETF participant]
Sorry for this blunt question:
Is there any other analysis made by an independent source, i.e., where
not the PIE authors are running an analysis of PIE?
Thanks,
Martin
Am 10.11.14 um 21:15 schrieb Rong Pan (ropan):
Please see our analy
On 11/12/2014 1:39 PM, Fred Baker (fred) wrote:
>> Abstract
>>
>>Bufferbloat is a phenomenon where excess buffers in the network cause
>>high latency and jitter.
>
> How about: Buffer bloat is a phenomenon in which transports such as
> TCP using loss-based or mark-based congestion contro
> Abstract
>
>Bufferbloat is a phenomenon where excess buffers in the network cause
>high latency and jitter.
How about: Buffer bloat is a phenomenon in which transports such as TCP using
loss-based or mark-based congestion control procedures create excessive buffer
occupancy, resulting
