From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fwd: [tsvwg] start of WGLC on L4S drafts
Date: Mon, 23 Aug 2021 17:45:57 -0700 [thread overview]
Message-ID: <CAA93jw77OnuwNLb3VLBEfUvFBjhYwDJKcc-FnxvXeXZQ4eM4VA@mail.gmail.com> (raw)
In-Reply-To: <7dd8896c-4cd8-9819-1f2a-e427b453d5f8@mti-systems.com>
In case anyone wants to weigh in.
---------- Forwarded message ---------
From: Wesley Eddy <wes@mti-systems.com>
Date: Thu, Jul 29, 2021 at 9:18 AM
Subject: [tsvwg] start of WGLC on L4S drafts
To: tsvwg@ietf.org <tsvwg@ietf.org>
This message is starting a combined working group last call on 3 of the
L4S drafts:
- Architecture: https://datatracker.ietf.org/doc/draft-ietf-tsvwg-l4s-arch/
- DualQ:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-aqm-dualq-coupled/
- ECN ID: https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-l4s-id/
The WGLC will last through 4 weeks from today, and then we'll see what
to do next. Please submit any comments you have on these to the TSVWG
list in that timeframe.
The chairs are considering a possible virtual interim following the
close in order to work through feedback received.
The work on the L4S operational guidance draft is continuing in
parallel, but that draft is not being last called yet.
--
Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2021-08-24 0:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <7dd8896c-4cd8-9819-1f2a-e427b453d5f8@mti-systems.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/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=CAA93jw77OnuwNLb3VLBEfUvFBjhYwDJKcc-FnxvXeXZQ4eM4VA@mail.gmail.com \
--to=dave.taht@gmail.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