From: David Lang <david@lang.hm>
To: davecb@spamcop.net
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Ecn-sane] My (controversial) position paper on TCP
Date: Wed, 20 Mar 2019 13:29:43 -0700 (PDT) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1903201327260.4946@qynat-yncgbc> (raw)
In-Reply-To: <e36d561b-b651-1c45-ae0c-6189d50e0e21@rogers.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On Wed, 20 Mar 2019, David Collier-Brown wrote:
> On 2019-03-20 10:28 a.m., Mikael Abrahamsson wrote:
>>
>> 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 (;-))
I have quite a number of consumer devices from 2000 or earlier still running,
consumer endpoints (aka IoT devices) do not get updated very much, if at all.
David Lang
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2019-03-20 20:29 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
2019-03-20 20:29 ` David Lang [this message]
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=nycvar.QRO.7.76.6.1903201327260.4946@qynat-yncgbc \
--to=david@lang.hm \
--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