From: dpreed@reed.com
To: "Jim Reisert AD1C" <jjreisert@alum.mit.edu>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] FCC: We aren’t banning DD-WRT on Wi-Fi routers
Date: Thu, 12 Nov 2015 18:18:11 -0500 (EST) [thread overview]
Message-ID: <1447370291.021815395@apps.rackspace.com> (raw)
In-Reply-To: <CAK-n8j4riw_HJx91y4nK3Yi0dfua2Dqdba_KROMJ4_x4cKpgCg@mail.gmail.com>
It's a start. (I'm optimistic that there is room to move the ball farther and that the FCC folks are willing to listen, though they didn't directly address concerns about the security closed, buggy quality of the factory software as being important and in the public interest).
On Thursday, November 12, 2015 5:22pm, "Jim Reisert AD1C" <jjreisert@alum.mit.edu> said:
> http://arstechnica.com/information-technology/2015/11/fcc-we-arent-banning-dd-wrt-on-wi-fi-routers/
>
> From the article:
>
> Today, the FCC issued an updated version of the guidance that strips
> out the DD-WRT reference. Instead, it now says:
>
> Describe, if the device permits third-party software or firmware
> installation, what mechanisms
> are provided by the manufacturer to permit integration of such
> functions while ensuring that
> the RF parameters of the device cannot be operated outside its
> authorization for operation
> in the US. In the description include what controls and/or
> agreements are in place with
> providers of third-party functionality to ensure the devices’
> underlying RF parameters are
> unchanged and how the manufacturer verifies the functionality.
>
> FCC Engineering and Technology Chief Julius Knapp also wrote a blog
> post titled, "Clearing the Air on Wi-Fi Software Updates."
>
> https://www.fcc.gov/blog/clearing-air-wi-fi-software-updates
>
>
> --
> Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
prev parent reply other threads:[~2015-11-12 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 22:22 Jim Reisert AD1C
2015-11-12 23:18 ` dpreed [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=1447370291.021815395@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=jjreisert@alum.mit.edu \
/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