From: Wesley Eddy <wes@mti-systems.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Fixing bufferbloat in 2017
Date: Mon, 28 Nov 2016 10:23:22 -0500 [thread overview]
Message-ID: <229474f1-841f-60f9-0c7a-e613adac12fc@mti-systems.com> (raw)
In-Reply-To: <CAA93jw7SMnu0j58gF0NfVEepR2RvjJ61Y=P-Mu-c9Ov7YzQPGQ@mail.gmail.com>
On 11/28/2016 10:12 AM, Dave Taht wrote:
> On Mon, Nov 28, 2016 at 4:48 AM, David Collier-Brown <davec-b@rogers.com> wrote:
>> A short RFC with a clear summary would change the ground on which we stand.
>> Include me in if you're planning one.
> Call me grumpy. Call me disaffected. But it's been 4 years into the
> IETF RFC process with codel and fq_codel with still no end in sight.
>
Hi Dave, while it's been undeniably slow, "no end in sight" is not
really accurate. Here is the correct status, since I am document
shepherd for both:
- The fq-codel draft is completely and totally done in terms of IETF
process, and has been in the RFC Editor's queue simply awaiting the
codel draft to arrive. This is what the "MISSREF" state indicates in
that IETF datatracker tool. It completed the IETF last call and IESG
balloting in March/April earlier this year.
- The codel document completed AQM working group last call, and I
believe is awaiting the authors to make changes requested by the Area
Director in order to go for IETF Last Call and IESG balloting.
The end is most definitely within sight!
next prev parent reply other threads:[~2016-11-28 15:23 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.454.1479929363.3555.bloat@lists.bufferbloat.net>
2016-11-26 15:33 ` Rich Brown
2016-11-27 1:53 ` Aaron Wood
2016-11-27 6:10 ` Mikael Abrahamsson
2016-11-27 21:24 ` Dave Taht
2016-11-28 2:11 ` Kathleen Nichols
2016-11-28 2:16 ` Jim Gettys
2016-11-28 6:00 ` Jan Ceuleers
2016-11-28 12:48 ` David Collier-Brown
2016-11-28 15:12 ` Dave Taht
2016-11-28 15:23 ` Wesley Eddy [this message]
2016-11-28 15:35 ` Dave Taht
2016-11-28 16:58 ` Stephen Hemminger
2016-11-28 17:07 ` Dave Taht
2016-11-28 19:02 ` Jonathan Morton
2016-11-28 17:52 ` Kathleen Nichols
2016-11-28 15:14 ` Pedro Tumusok
2016-11-28 15:23 ` Dave Taht
2016-11-28 15:10 ` Dave Taht
2016-11-28 2:47 ` David Lang
[not found] <mailman.447.1479909940.3555.bloat@lists.bufferbloat.net>
2016-11-23 18:16 ` [Bloat] fixing " Rich Brown
2016-11-23 18:46 ` David Lang
2016-11-23 18:58 ` Jonathan Morton
2016-11-23 19:15 ` David Lang
2016-11-23 20:37 ` Toke Høiland-Jørgensen
2016-11-22 15:32 Dave Taht
2016-11-22 16:19 ` Jan Ceuleers
2016-11-22 16:25 ` Dave Taht
2016-11-22 16:38 ` Jim Gettys
2016-11-23 8:28 ` Mikael Abrahamsson
2016-11-23 11:04 ` Jonathan Morton
2016-11-23 11:59 ` Kelvin Edmison
2016-11-23 13:31 ` Pedro Tumusok
2016-11-23 14:05 ` Mário Sérgio Fujikawa Ferreira
2016-11-23 17:20 ` Mikael Abrahamsson
2016-11-23 17:27 ` Benjamin Cronce
2016-11-23 17:31 ` Mikael Abrahamsson
2016-11-23 17:40 ` Sebastian Moeller
2016-11-23 17:50 ` Noah Causin
2016-11-23 17:56 ` David Lang
2016-11-23 18:05 ` Benjamin Cronce
2016-11-23 18:38 ` David Lang
2016-11-23 19:29 ` Benjamin Cronce
2016-11-23 19:42 ` David Lang
2016-11-23 20:20 ` Dave Taht
2016-11-23 17:54 ` David Lang
2016-11-23 18:09 ` Mikael Abrahamsson
2016-11-23 18:18 ` Sebastian Moeller
2016-11-23 18:24 ` Dave Taht
2016-11-23 20:39 ` Toke Høiland-Jørgensen
2016-11-23 19:13 ` David Lang
2016-11-23 18:17 ` Dave Taht
2016-11-23 15:32 ` Pedretti Fabio
2016-11-23 19:29 ` Stephen Hemminger
2016-11-23 19:22 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=229474f1-841f-60f9-0c7a-e613adac12fc@mti-systems.com \
--to=wes@mti-systems.com \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox