From: Wesley Eddy <wes@mti-systems.com>
To: codel@lists.bufferbloat.net
Subject: [Codel] forming an IETF AQM working group
Date: Sun, 21 Jul 2013 09:50:54 -0400 [thread overview]
Message-ID: <51EBE73E.9060701@mti-systems.com> (raw)
We are trying to start a working group in the IETF to focus
on Active Queue Management (AQM) and packet scheduling or
fair queuing algorithms.
There is a mailing list setup at:
https://www.ietf.org/mailman/listinfo/aqm
Anyone interested is free and welcomed to join the discussion.
We especially want to have people with different perspectives
participating, including hardware and software developers for
different types of systems, network operators, academics, etc.
There will also be a Birds of a Feather (BoF) meeting at the
IETF meeting in Berlin (http://www.ietf.org/meeting/87) later
this month, which we wanted to make people aware of. The
goal of the meeting is to form a working group following the
meeting.
A draft charter that is being discussed can be found here:
http://www.ietf.org/mail-archive/web/aqm/current/msg00165.html
--
Wes Eddy
MTI Systems
reply other threads:[~2013-07-21 13:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51EBE73E.9060701@mti-systems.com \
--to=wes@mti-systems.com \
--cc=codel@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