Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: ecn-sane@lists.bufferbloat.net,
	bloat <bloat@lists.bufferbloat.net>,
	 Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] [Ecn-sane] My (controversial) position paper on TCP
Date: Wed, 20 Mar 2019 15:28:31 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1903201524440.3161@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw7pr3jmRfxwa0iVQYZf=UwqoTTMWXZn0QMJfJSj1-GUsA@mail.gmail.com>

On Mon, 18 Mar 2019, Dave Taht wrote:

> Another ietf idea that makes me crazy is the motto of "no host changes" 
> in homenet, and "dumb endpoints" - when we live in an age where we have 
> quad cores and AI coprocessors in everybody's hands.

This isn't a resource problem, it's a code problem. The IETF wants 10-15 
year old hosts to be able to connect to a network and perform basic 
networking. It might not be very optimized, but the basic function should 
be there. New functionality can optimize for different factors, but making 
older host stop working is frowned upon.

If the endpoints are going to be smarter (and they will, question is how 
fast), how do we keep the smarts updated with new functionality?

TCP does the same thing, it wants to be backwards compatible and that's 
why QUIC has been more free to innovate in some fashions. I also believe 
it's perhaps time to cut TCP off and come up with something new, the bad 
part is that it seems all innovation then has to be done over UDP which 
has its own drawbacks (because of NATs).

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

      reply	other threads:[~2019-03-20 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 10:04 [Cake] " Dave Taht
2019-03-20 14:28 ` Mikael Abrahamsson [this message]

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/cake.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.20.1903201524440.3161@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@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