General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: David Collier-Brown <davec-b@rogers.com>
To: David Lang <david@lang.hm>, davecb@spamcop.net
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Ecn-sane] My (controversial) position paper on TCP
Date: Wed, 20 Mar 2019 17:42:45 -0400	[thread overview]
Message-ID: <d9965189-2f60-c1f7-69b2-6c5e2be3de14@rogers.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1903201327260.4946@qynat-yncgbc>

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

On 2019-03-20 4:29 p.m., David Lang wrote:

> 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

Interesting thought: I wasn't expecting consumer devices from 14 years 
ago! What do you have?

In our house,

  * the cable modem is about a year old,
  * it's predecessor was about 5 when it died,
  * the old printer was 3 years old
  * the new one is about 4
  * my homemade PVR is about 6, and is starting to look elderly, and
  * the old cable box was about 3,
  * the new one about one
  * and my netbook is older than the PVR by maybe a year or so (;-))

--dave
(I intentionally skipped IOT devices, as I expect they could 
change/pivot hugely about the time the market starts to mature,

-- 
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: 2695 bytes --]

  reply	other threads:[~2019-03-20 21:42 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
2019-03-20 21:42       ` David Collier-Brown [this message]
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=d9965189-2f60-c1f7-69b2-6c5e2be3de14@rogers.com \
    --to=davec-b@rogers.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=davecb@spamcop.net \
    --cc=david@lang.hm \
    /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