General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht <dave@taht.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] keeping the lights on at bufferbloat.net
Date: Mon, 4 Feb 2019 12:29:50 -0800	[thread overview]
Message-ID: <CAA93jw7Yt6A0cmZEP8gs+NbFmuywZkze094kEcayV9dYoW=rww@mail.gmail.com> (raw)
In-Reply-To: <87ef8n74m3.fsf@taht.net>

And patreon is reporting "down for maintenance" as I write. While
we're doing ironic today, the other big grant we failed to get last
year was from the shuttleworth foundation - and that conf
call/interview took place during a 50 minute major internet-wide
outage ( http://blog.cerowrt.org/post/bufferbloat_on_the_backbone/ )
and I could barely hear or see the other participants (nor they, me).

anyway, I'm getting off my duff today to put in at least a grant
proposal to nlnet for getting the ns3 cake work done (under jonathan),
and another to maybe get babeld-dtls done (a vestige of the cerowrt
effort) with comcast... but still I'd kind of hoped that the fq_codel
for wifi work would have had every wifi, lte, and ethernet over
powerline vendor salivating to add it to their product soonest. I'm
really delighted by the penetration sqm and fq_codel and cake now
have, sad that we aren't seeing dsl ISPs in particular, mandating cake
and terribly disappointed by the early 5G results. Still... in 8 years
of operation we made a big difference in the internet and millions of
people now benefit in the OSX, IOS, Linux and freebsd worlds from an
AQM/FQ perspective and the world as a whole from all the wonderful
work done e2e with bql, pacing, bbr, etc. Perhaps, as Matt Mathis
said, 3 years ago "The tree is cut, it is falling", we need do no more
here.

Another irony today is GSOC expects a shiny logo to be part of the
application and we've never done that. Wish we'd done t-shirts and
coffee mugs at some point, also.

  reply	other threads:[~2019-02-04 20:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 16:55 Dave Taht
2019-02-04 17:13 ` Jonathan Foulkes
2019-02-04 19:09   ` Dave Taht
2019-02-04 20:29     ` Dave Taht [this message]
2019-02-04 22:03       ` Jonathan Foulkes
2019-02-05  8:48         ` Toke Høiland-Jørgensen
2019-02-05 13:45           ` Jonathan Foulkes

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='CAA93jw7Yt6A0cmZEP8gs+NbFmuywZkze094kEcayV9dYoW=rww@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave@taht.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