General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Ecn-sane] My (controversial) position paper on TCP
Date: Wed, 20 Mar 2019 14:33:03 -0400	[thread overview]
Message-ID: <e36d561b-b651-1c45-ae0c-6189d50e0e21@rogers.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1903201524440.3161@uplift.swm.pp.se>

[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]

On 2019-03-20 10:28 a.m., Mikael Abrahamsson wrote:
> 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.

Dumb endpoints is a huge change from the design of the internet (and 
ARPAnet), with a dumb middle and smart ends:  I suspect the original 
commentator was talking about mere /relative/ dumbness...

>
> 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.

Fortunately this is a solved problem in capacity planning: you replace 
machines often enough that they're not constantly out of service being 
repaired. 10 to 15 human-years is the equivalent of 70 to 105 of the 
dog-years we use in this silly business (;-))

The oldest machine I use is a dps8-m, and I'll be slightly amazed if we 
can provide native TCP. Right now I ssh into the virtual machine that's 
running it, all so I can continue to fiddle around with Multics.

--dave (DavidBrown.TSDC@HI-Multics.ARPA) c-b

-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |                      -- Mark Twain


[-- Attachment #2: Type: text/html, Size: 2435 bytes --]

  reply	other threads:[~2019-03-20 18:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 10:04 [Bloat] " Dave Taht
2019-03-18 22:03 ` David Collier-Brown
2019-03-20 14:28 ` [Bloat] [Ecn-sane] " Mikael Abrahamsson
2019-03-20 18:33   ` David Collier-Brown [this message]
2019-03-20 20:29     ` David Lang
2019-03-20 21:42       ` David Collier-Brown
2019-03-20 22:28         ` Jonathan Morton
2019-03-20 23:12           ` Dave Collier-Brown
2019-03-20 22:55         ` David Lang

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=e36d561b-b651-1c45-ae0c-6189d50e0e21@rogers.com \
    --to=davec-b@rogers.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=davecb@spamcop.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