From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] fq_codel wikipedia page in progress
Date: Mon, 15 Nov 2021 14:47:25 -0800 [thread overview]
Message-ID: <3c9eaed6-5fe0-29b6-b91a-c1be365f5c7a@sewingwitch.com> (raw)
In-Reply-To: <5073d33a-8201-beeb-e6a2-0e20d1170134@sewingwitch.com>
On 11/15/2021 2:15 PM, Kenneth Porter wrote:
>
> I'd also suggest changing the page title to match the capitalization
> and hyphen of the RFC.
>
> https://datatracker.ietf.org/doc/html/rfc8290
Following my own advice to mimic other protocol pages, I suggest that
the title be the full, unabbreviated name of the protocol:
Flow Queue Controlled Delay Packet Scheduler and Active Queue Management
Algorithm
Or maybe some subset of that. Use the acronym FQ-CoDel (taken from the
RFC) in the body.
Obviously steal material from the bufferbloat site. ;)
https://www.bufferbloat.net/projects/codel/wiki/
next prev parent reply other threads:[~2021-11-15 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 16:40 Dave Taht
2021-11-15 22:15 ` Kenneth Porter
2021-11-15 22:47 ` Kenneth Porter [this message]
2021-11-16 17:57 ` Jan Ceuleers
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=3c9eaed6-5fe0-29b6-b91a-c1be365f5c7a@sewingwitch.com \
--to=shiva@sewingwitch.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