Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: Aaron Wood <woody77@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	"aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [Cerowrt-devel] [Bloat] Bufferbloat and the policy debate on packet loss in nanog
Date: Sun, 1 Mar 2015 20:10:52 -0500	[thread overview]
Message-ID: <CAGhGL2CZk_sVnMZkMi=g8K1tQQAsxOUxRawiZo47wzjyt5N9=g@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-PSfeHnkgNFCwQzbDhTRDt2-vihNsuydcVNLNmMX_G7YQ@mail.gmail.com>

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

On Sun, Mar 1, 2015 at 7:56 PM, Aaron Wood <woody77@gmail.com> wrote:

> But until the silicon vendors update _their_ forks of OpenWRT,
> commercially available home routers won't have these benefits.  Because the
> home router market is dominated by packaged reference designs from one of a
> very small number of companies that actually make all the chipsets (Dave, I
> know you know this, I'm mostly just choir-preaching myself).
>

​I was talking to one of the major chipset vendors just this last Thursday.​


​
We have to fork-lift upgrade all of these devices, ASAP.

And change how we build/maintain these systems, and do business in embedded
systems.

See my Berkman Center talk here:

http://cyber.law.harvard.edu/events/luncheon/2014/06/gettys​


​We'll be struggling with the policies issues the rest of our lives (which
is why I presented to the Berkman Center).

Also read Dan Geer's policy piece in Lawfare the Lawfare blog.

http://www.lawfareblog.com/2014/04/heartbleed-as-metaphor/

Bruce Schneier's piece in Wired on the IOT is also very good, but aimed at
a mass audience.

I will be publishing and updated version of the talk very soon; the
situation is yet more perilous since June, and my explanations clearer.

Jim

​


> -Aaron
>
> On Sun, Mar 1, 2015 at 3:22 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
>> There's nothing new here, but it was a nice rant to get out of my system:
>>
>> http://permalink.gmane.org/gmane.org.operators.nanog/128201
>>
>> Of late, I have been taking a page from Linus Torvalds' playbook, in
>> realizing that "on the internet, no-one can hear you being subtle",
>> and BOY, am I done with that.
>>
>> --
>> Dave Täht
>> Let's make wifi fast, less jittery and reliable again!
>>
>> https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>

[-- Attachment #2: Type: text/html, Size: 5078 bytes --]

  reply	other threads:[~2015-03-02  1:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-01 23:22 [Cerowrt-devel] " Dave Taht
2015-03-02  0:56 ` [Cerowrt-devel] [Bloat] " Aaron Wood
2015-03-02  1:10   ` Jim Gettys [this message]
2015-03-02  1:19   ` Jonathan Morton
2015-03-02 12:26 ` [Cerowrt-devel] " dpreed

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGhGL2CZk_sVnMZkMi=g8K1tQQAsxOUxRawiZo47wzjyt5N9=g@mail.gmail.com' \
    --to=jg@freedesktop.org \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=woody77@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