From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [tsvwg] CONGRESS is about ready to go
Date: Tue, 21 Feb 2023 10:35:10 -0800 [thread overview]
Message-ID: <CAA93jw6bCuPHMZF2_xAWnogh726M56Dn4kmN9w7hyfq6URJ0Qw@mail.gmail.com> (raw)
In-Reply-To: <CAM4esxQwvo-QNiq_1PDx_z8RvxcJwrMdkb+GJLYJDYw6+_gO2g@mail.gmail.com>
---------- Forwarded message ---------
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, Feb 21, 2023 at 9:25 AM
Subject: [tsvwg] CONGRESS is about ready to go
To: <congress@ietf.org>
Hello transport enthusiasts,
I'm pleased to announce that all the pieces are in place to move
forward with congress, the working group focused on congestion control
and related topics.
(1) If you haven't already done so, and are interested, please
subscribe to the congress mailing list:
https://www.ietf.org/mailman/listinfo/congress. This is the last time
I'll crosspost (Bcc:) to multiple WG lists, and I encourage others to
stop as well.
(2) Although the proposed charter has no formal standing at this
time, I'm initiating a "last call". Please have a look and file issues
by the end of this week:
https://github.com/martinduke/congestion-control-charter
The only recent additions to the scope are Fair Queueing and rate
pacing. I'd like to hand this to Zahed, our sponsoring AD, to run
through the IESG process next week.
--
A pithy note on VOQs vs SQM: https://blog.cerowrt.org/post/juniper/
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2023-02-21 18:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAM4esxQwvo-QNiq_1PDx_z8RvxcJwrMdkb+GJLYJDYw6+_gO2g@mail.gmail.com>]
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6bCuPHMZF2_xAWnogh726M56Dn4kmN9w7hyfq6URJ0Qw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@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