Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Wayne Workman <wayne.workman2012@gmail.com>
Cc: bufferbloat-fcc-discuss
	<bufferbloat-fcc-discuss@lists.redbarn.org>,
	make-wifi-fast@lists.bufferbloat.net,
	cerowrt-devel@lists.bufferbloat.net, dpreed@reed.com
Subject: Re: [Cerowrt-devel] [bufferbloat-fcc-discuss] arstechnica confirmstp-link router lockdown
Date: Mon, 14 Mar 2016 15:29:16 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1603141529010.25586@nftneq.ynat.uz> (raw)
In-Reply-To: <CAEfCu-pGdkcqHJMHSiXtXBcx=m0XyskVOLmGjC2esS+SY+GgcQ@mail.gmail.com>

On Mon, 14 Mar 2016, Wayne Workman wrote:

> One thing Is for sure - if the FCC can't see this, they will have
> effectively handicapped yet another technology, they will basically kill
> wifi. In the public's minds it will become some gross slow thing.

Agreed.

David Lang

> Again, reminds me of what the FCC, RCA, and copyright courts did to FM back
> at its birth.
> On Mar 14, 2016 2:13 PM, "David Lang" <david@lang.hm> wrote:
>
>> On Mon, 14 Mar 2016, dpreed@reed.com wrote:
>>
>> But it will take working with both the FCC and the chip vendors, and the
>>> home access point vendors with a common purpose and agenda. That agenda
>>> needs to be to find the minimum lock that will satisfy the FCC, and a
>>> sufficiently cheap implementation that, along with the cost saving on
>>> design certification, it is cheaper to make a router that is otherwise
>>> open, than to make one whose certification depends on review of all the
>>> code in the router.
>>>
>>
>> This should never require review of all the code in the router. At most it
>> should require review of the firmware code for the wifi chip.
>>
>> Linux has had this sort of thing in the past, look at the ISDN code that
>> required certification to operate.
>>
>> This is a common design pattern. The DAA for phones is now purchasable as
>>> a single module, FCC precertified, so one can make any kind of cordless
>>> phone be certifiable, merely by using that part. That part is more
>>> expensive than one I could design myself, but it saves on certification
>>> cost, because the rest of the phone or modem doesnt need certification, so
>>> one can innovate.
>>>
>>
>> The problem is how much stuff gets stuffed in this certified component.
>> Cell phones, with their 'baseband processor' are a good example of too much
>> functionality being in the certified component.
>>
>> We want to get more access to what's currently in the wifi chipset
>> firmware, not have it all locked down more.
>>
>> David Lang
>> _______________________________________________
>> bufferbloat-fcc-discuss mailing list
>> bufferbloat-fcc-discuss@lists.redbarn.org
>> http://lists.redbarn.org/mailman/listinfo/bufferbloat-fcc-discuss
>>
>

      parent reply	other threads:[~2016-03-14 22:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 14:02 dpreed
2016-03-14 14:14 ` [Cerowrt-devel] [Make-wifi-fast] " Jonathan Morton
     [not found]   ` <CAEfCu-oCfO+FfdLjpZDSwQmZ7-Mc+X4vDvzZMNrnp+p8ut8OKQ@mail.gmail.com>
2016-03-14 17:49     ` [Cerowrt-devel] [bufferbloat-fcc-discuss] [Make-wifi-fast] " dpreed
2016-03-14 19:04       ` [Cerowrt-devel] [Make-wifi-fast] [bufferbloat-fcc-discuss] " David Lang
2016-03-14 19:07   ` David Lang
2016-03-14 19:13 ` [Cerowrt-devel] " David Lang
     [not found]   ` <CAEfCu-pGdkcqHJMHSiXtXBcx=m0XyskVOLmGjC2esS+SY+GgcQ@mail.gmail.com>
2016-03-14 22:29     ` David Lang [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/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=alpine.DEB.2.02.1603141529010.25586@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=bufferbloat-fcc-discuss@lists.redbarn.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=wayne.workman2012@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