From: "Mohit P. Tahiliani" <tahiliani@nitk.edu.in>
To: grenville armitage <gja.ietf@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Fwd: New Version Notification for draft-tahiliani-tsvwg-fq-pie-01.txt
Date: Sun, 23 Mar 2025 22:52:12 +0530 [thread overview]
Message-ID: <CAPwoALzxaud7Pu1ZX6jRSMcjQQ7mHH37=9ALjwVUT9EaoYA9wQ@mail.gmail.com> (raw)
In-Reply-To: <2e9b4ba8-10b6-4182-9b12-deed12279ab3@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]
Hi Grenville,
Thanks for the email.
I have replied inline below:
On Sun, Mar 23, 2025 at 2:28 AM grenville armitage <gja.ietf@gmail.com>
wrote:
> Hi Mohit,
>
> Thanks for doing the comparison!
>
> As for "*any other material related to this?*" I've had a dig around, and
> there is not a lot. Rasool (the FreeBSD fq-pie author) did write up a
> university tech report in April 2016, "*Dummynet AQM v0.2 – CoDel,
> FQ-CoDel, PIE and FQ-PIE for FreeBSD’s ipfw/dummynet framework*" (wayback
> machine link
> <https://web.archive.org/web/20241018123533/http://caia.swin.edu.au/reports/160418A/CAIA-TR-160418A.pdf>).
> There's also a small mention in an LCN 2017 paper titled "*Characterising
> LEDBAT Performance Through Bottlenecks Using PIE, FQ-CoDel and FQ-PIE
> Active Queue Management*" (ieee link
> <http://doi.ieeecomputersociety.org/10.1109/LCN.2017.22>, author preprint
> <http://gja.space4me.com/things/ralsaadi-lcn2017-preprint-aqm_on_ledbat-preprint-4oct17.pdf>).
> Hope these are of some (historical) interest to your I-D (and the wider
> bufferbloat mailing list, too).
>
Thanks for sharing these links. I will go through the material.
> I'm unaware of any production deployment of FreeBSD's fq-pie.
>
Thanks for letting me know.
I presented the FQ-PIE ID in the recently concluded IETF at tsvwg. I
believe there was interest in the group to have a specification for FQ-PIE.
It would be great if you could share your views on the tsvwg mailing list
when you get a chance.
Thanks and Regards,
Mohit P. Tahiliani
[-- Attachment #2: Type: text/html, Size: 3548 bytes --]
next prev parent reply other threads:[~2025-03-23 17:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <174103000203.525445.13919970625670214659@dt-datatracker-5dd67b77bb-4k4zh>
2025-03-10 19:01 ` Mohit P. Tahiliani
2025-03-10 23:51 ` grenville armitage
2025-03-18 7:34 ` Mohit P. Tahiliani
2025-03-22 20:58 ` grenville armitage
2025-03-23 17:22 ` Mohit P. Tahiliani [this message]
2025-03-11 9:50 ` [Bloat] " Michael Welzl
2025-03-18 8:04 ` Sebastian Moeller
2025-03-19 9:00 ` Sebastian Moeller
2025-03-19 9:02 ` Mohit P. Tahiliani
2025-03-19 9:04 ` Sebastian Moeller
2025-03-23 17:14 ` Mohit P. Tahiliani
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='CAPwoALzxaud7Pu1ZX6jRSMcjQQ7mHH37=9ALjwVUT9EaoYA9wQ@mail.gmail.com' \
--to=tahiliani@nitk.edu.in \
--cc=bloat@lists.bufferbloat.net \
--cc=gja.ietf@gmail.com \
/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