From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] I feel an urge to update this
Date: Tue, 23 Sep 2014 07:48:00 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1409230742000.14735@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw6-eVYtXHzuosCxmcUdE1PFVfDS4UE30e6nYm-H4eH4pg@mail.gmail.com>
On Sat, 20 Sep 2014, Dave Taht wrote:
> http://tools.ietf.org/html/draft-gettys-iw10-considered-harmful-00
>
> I just got some iw10 results on a t1 line... ugh. anyone want a stab at it?
Is it at all possible to create a solution that works well for all cases?
I pitched a proposal at IETF75 and then again a year ago in TCP/TCPM WGs
that it might be good if the connection manager could hint the TCP stack,
or the TCP stack could determine itself by heuristics, that its network
connection were of a few different degrees of a few criteria which might
be speed, loss, jitter etc. I perhaps even could tell my connection
manager that when connected to my home wired or wifi network, "everything"
is reachable via 50 + megabit/s connectivity. If I then speak to a 10GE
connected server, there should be no problem for it to do IW10. Basically,
my thinking is to have something similar to "MSS" but when it comes to
connectivity.
There was no interest anywhere in this, everybody wanted for each
connection to be living in its own universe with little prior knowledge
about what's been going on before it.
I just don't see how we can make things work well when we try to create
TCP to handle everything from 1500ms to 0.1ms of RTT, and everything from
19200bps to 100GE in speed.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2014-09-23 5:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 23:33 Dave Taht
2014-09-20 9:03 ` Steinar H. Gunderson
2014-09-20 15:55 ` Jonathan Morton
2014-09-20 16:47 ` Michael Welzl
2014-09-23 5:48 ` Mikael Abrahamsson [this message]
2014-09-23 8:31 ` Jonathan Morton
2014-09-25 4:16 ` David Lang
2014-09-25 5:32 ` Mikael Abrahamsson
2014-09-25 7:35 ` David Lang
2014-09-25 8:08 ` Mikael Abrahamsson
2014-09-25 11:00 ` David Lang
2014-09-25 13:00 ` Mikael Abrahamsson
2014-09-25 13:25 ` Dave Taht
2014-09-25 14:35 ` Mikael Abrahamsson
2014-09-25 16:09 ` Rick Jones
2014-09-25 17:26 ` Mikael Abrahamsson
2014-09-25 17:49 ` Rick Jones
2014-09-27 8:59 ` Manolis Sifalakis
2014-09-29 17:28 ` Rick Jones
2014-10-04 19:56 ` Manolis Sifalakis
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=alpine.DEB.2.02.1409230742000.14735@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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