From: Pete Heist <pete@heistp.net>
To: ecn-sane@lists.bufferbloat.net
Subject: [Ecn-sane] proving out SCE
Date: Sat, 16 Mar 2019 11:11:42 +0100 [thread overview]
Message-ID: <862FC3E9-1059-4722-BF3E-6036DC176400@heistp.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
I’m starting to read Jon’s proposal for modifying TCP CC for SCE (https://github.com/dtaht/bufferbloat-rfcs/blob/master/sce/ELR%20Proposal%203%20(TCP).txt <https://github.com/dtaht/bufferbloat-rfcs/blob/master/sce/ELR%20Proposal%203%20(TCP).txt>), and get the (perhaps misplaced) feeling that it’s not that big a stretch to implement, and that proving basic efficacy may not be that hard. I’d like to do what I can to help before IETF, so please do post what needs doing, and meanwhile I’ll just keep reading.
Pete
p.s.- at least we don’t have to justify bifurcating Internet congestion control
[-- Attachment #2: Type: text/html, Size: 1021 bytes --]
next reply other threads:[~2019-03-16 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 10:11 Pete Heist [this message]
2019-03-16 13:37 ` Jonathan Morton
2019-03-16 14:58 ` Jonathan Morton
2019-03-16 16:21 ` Pete Heist
2019-03-16 16:49 ` Jonathan Morton
2019-03-16 18:44 ` Pete Heist
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=862FC3E9-1059-4722-BF3E-6036DC176400@heistp.net \
--to=pete@heistp.net \
--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