Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>
Cc: fcc@lists.prplfoundation.org,
	make-wifi-fast@lists.bufferbloat.net, cake@lists.bufferbloat.net,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>,
	OpenWrt Development List <openwrt-devel@lists.openwrt.org>
Subject: Re: [Cake] [Battlemesh] [OpenWrt-Devel] the cerowrt project's letter to the fcc about the wifi lockdown is nearly final
Date: Tue, 6 Oct 2015 17:17:36 +0200	[thread overview]
Message-ID: <20151006151736.GI12763@odroid> (raw)
In-Reply-To: <CANjd3ndr7WBSvmB2SaLi0FQmyNYZ10w09L7SFkZw1JNN45O8EQ@mail.gmail.com>

On Tue, Oct 06, 2015 at 04:21:38PM +0200, Benjamin Henrion wrote:
> On Tue, Oct 6, 2015 at 3:49 PM, Linus Lüssing <linus.luessing@c0d3.blue> wrote:
> > On Tue, Oct 06, 2015 at 02:13:36AM +0200, Dave Taht wrote:
> >> Comment away!
> >
> > There are many good points made in this text.
> >
> > I like the Volkswagen example and the suggestion to require
> > opening up the firmware.
> >
> > For the latter, had been thinking about that before briefly,
> > but kind of dismissed it early, basically because the reasoning in
> > my head was that FCC shouldn't make any requirements regarding
> > the form of the software at all. They should only regulate the
> > result.
> 
> Blobs cannot be trusted to do the right thing.

I know (and I guess we all do here?). I don't get the purpose of
this comment, sorry :(.

      reply	other threads:[~2015-10-06 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06  0:13 [Cake] " Dave Taht
2015-10-06 12:03 ` [Cake] [Bloat] " Rich Brown
2015-10-06 13:49 ` [Cake] [OpenWrt-Devel] " Linus Lüssing
2015-10-06 14:21   ` [Cake] [Battlemesh] " Benjamin Henrion
2015-10-06 15:17     ` Linus Lüssing [this message]

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=20151006151736.GI12763@odroid \
    --to=linus.luessing@c0d3.blue \
    --cc=battlemesh@ml.ninux.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=fcc@lists.prplfoundation.org \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=openwrt-devel@lists.openwrt.org \
    /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