From: Dave Taht <dave.taht@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Subject: [NNagain] 2015 flashback
Date: Sat, 28 Oct 2023 23:18:07 -0700 [thread overview]
Message-ID: <CAA93jw5u6zWtUaWvhQZhQE6TqW--MtjoCn0RtzEh8Gfpqus_Zg@mail.gmail.com> (raw)
We had many notables have key and prophetic things to say about the
internet's problems and future... back in 2015,
when we were fighting to keep home routers open enough to fix them.
https://docs.google.com/document/d/1HT2NjsHR1bGQM0PeawYuF60B_m3Hisa3_Q1MB2aVNs4/edit?usp=sharing
I do not think any of the contributors to this document have changed
their opinions much since then, and while I think the situation less
dire, the overall scope of these problems outlined above, wider.
--
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos
next reply other threads:[~2023-10-29 6:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 6:18 Dave Taht [this message]
2023-10-29 19:28 ` rjmcmahon
2023-10-30 14:20 ` Livingood, Jason
2023-10-30 15:58 ` Robert McMahon
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/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5u6zWtUaWvhQZhQE6TqW--MtjoCn0RtzEh8Gfpqus_Zg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=nnagain@lists.bufferbloat.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