From: Rich Brown <richb.hanover@gmail.com>
To: ecn-sane@lists.bufferbloat.net
Subject: [Ecn-sane] Questions about TSVWG call
Date: Thu, 30 Apr 2020 13:28:58 -0400 [thread overview]
Message-ID: <2937CA62-6FCC-4E32-B7F5-11A6A485F1EE@gmail.com> (raw)
Folks,
I have been a bystander in these discussions, and could only listen in to part of the TSVWG conference call. But here are a couple questions that come to mind from what (I think) I heard...
1) Has anyone run RRUL tests on L4S gear? What would be involved setting up such a test? Why hasn't it already been done?
2) If I understand correctly, the L4S proposal is to use the ECT(1) bit as an input to the routing algorithm. If it's set, the router can assume that it's latency-sensitive traffic and use special routing rules/queues/etc. How does L4S guard against DoS/cheating? Has such a proposal been implemented and tested?
3) The L4S proposal is designed to decrease latency. Can there be a successful L4S deployment in the face of the millions of current CPE that have no notion of latency control?
4) I have a personal bias toward helping people with dreadfully slow ISP service. (My home can only get 7mbps/768kbps DSL; others in my town only get 3mbps/500kbps service.) Does L4S help for slow links like these?
Forgive me if this is all common knowledge, or if answers have been summarized elsewhere. (I would love to have a link.) Thanks.
Rich
next reply other threads:[~2020-04-30 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 17:28 Rich Brown [this message]
2020-04-30 17:55 ` Jonathan Morton
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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2937CA62-6FCC-4E32-B7F5-11A6A485F1EE@gmail.com \
--to=richb.hanover@gmail.com \
--cc=ecn-sane@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