I have reviewed this draft, and my only complaint is that the new text:

"Packets arriving at a full buffer SHOULD be dropped" is really jarring,
where it landed, in section 4.4.

If this MUST be discussed somewhere, I'd suggest opening a new section
for it entirely. Still... I'd suggest dropping this sentence entirely
and letting the fq_codel draft handle it.

There are, incidentally, several strategies for a dealing with a full
buffer in a multi-queue system besides drop tail (which the above
appears to recommend for codel).

How fq_codel does drop on full, incidentally, has improved greatly since
we created the last version of the fq_codel draft, based on field
testing.

https://patchwork.ozlabs.org/patch/617307/

And I'd be willing to update some future fq_codel.bis document to
reflect that.

...

I like the new definitions section.

...

Aside from that, I have not looked at this in going on two years, and
bits are falling out of date, and NONE of my nits are substantive
enough to warrant holding up publication a microsecond longer. It's a
*experimental* draft, not a standard.

If we want to discuss how to produce a fq_codel.bis and codel.bis, and
for that matter pie.bis and fq_pie.bis... on standards track, one day, great.

[email protected] writes:

> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> This draft is a work item of the Active Queue Management and Packet 
> Scheduling WG of the IETF.
>
>         Title           : Controlled Delay Active Queue Management
>         Authors         : Kathleen Nichols
>                           Van Jacobson
>                           Andrew McGregor
>                           Janardhan Iyengar
>       Filename        : draft-ietf-aqm-codel-09.txt
>       Pages           : 25
>       Date            : 2017-09-29
>
> Abstract:
>    This document describes a general framework called CoDel (Controlled
>    Delay) that controls bufferbloat-generated excess delay in modern
>    networking environments.  CoDel consists of an estimator, a setpoint,
>    and a control loop.  It requires no configuration in normal Internet
>    deployments.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-aqm-codel/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-aqm-codel-09
> https://datatracker.ietf.org/doc/html/draft-ietf-aqm-codel-09
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-codel-09
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> aqm mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/aqm

_______________________________________________
aqm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/aqm

Reply via email to