From: Dave Taht <dave.taht@gmail.com>
To: Luca Muscariello <luca.muscariello@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Modification of DRR with deficit saving
Date: Thu, 4 Jan 2018 08:39:03 -0800 [thread overview]
Message-ID: <CAA93jw79iVW_V+FAE9vHvxciNcBRhZ-JwSZcx84Dy8=-o4_ghg@mail.gmail.com> (raw)
In-Reply-To: <CAHx=1M49XiQBsXGEsK8A8GJEg0rvHSyzWMSJZxP3bkCaa5oGUw@mail.gmail.com>
On Thu, Jan 4, 2018 at 8:24 AM, Luca Muscariello
<luca.muscariello@gmail.com> wrote:
> That is a big mountain to climb
And this one wasn't? :)
The really ironic thing that I discovered: is that whatsapp is
universal here - it's everywhere - even on business cards - over both
cellular and wifi. Why? Because voice and videoconferencing comms are
so unreliable that store and forward is the only way to communicate
reliably.
So it's kind of like a return of usenet or CB radio, if those
analogies could apply to a culture that had never experienced both.
When I finally figured out why whatsapp was so popular, I laughed and laughed.
Humanity will find a bug and route around it, indeed, far faster than
we can fix the internet. "Can your hear me? Over".
All that work to make better queuing available, so long from
deployment. The radio I'm behind right now (in a bar), has a version
of ubnt's firmware from 5+ years ago on it...
Fiber is being deployed (single mode!), at rates starting at 2Mbit/sec
in san juan del sur, (http://www.cootel.com.ni/ - massive
bufferbloat), on the cheapest hardware imaginable and after I got it
working it failed a few days later two hops into their network ...
why? the fiber got cut a few blocks just out of town... which is still
unfixed, days later.
>
> On Thu, Jan 4, 2018 at 5:20 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>>
>> Done fixing the home. It's time to fix the rest of the internet. And
>> that's not just queue theory but address assignment and routing.
>> Here's
>> a traceroute from where I sit in Nicaragua at the moment, post cake.
>> How to figure out exactly how much NAT is on the path?
>>
>
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-01-04 16:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 14:29 Toke Høiland-Jørgensen
2018-01-04 14:52 ` Dave Taht
2018-01-04 15:01 ` Jonathan Morton
2018-01-04 15:23 ` Luca Muscariello
2018-01-04 15:42 ` Dave Taht
2018-01-04 15:53 ` Luca Muscariello
2018-01-04 16:20 ` Dave Taht
2018-01-04 16:24 ` Luca Muscariello
2018-01-04 16:39 ` Dave Taht [this message]
2018-01-05 8:19 ` Pete Heist
2018-01-04 15:56 ` Sebastian Moeller
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='CAA93jw79iVW_V+FAE9vHvxciNcBRhZ-JwSZcx84Dy8=-o4_ghg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=luca.muscariello@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