From: Rich Brown <richb.hanover@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: openwrt-devel@lists.openwrt.org,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Mailing list to coordinate responses to FCC ruling on router hacking
Date: Mon, 10 Aug 2015 13:02:02 -0400 [thread overview]
Message-ID: <DADEB42F-592C-41BF-BC50-98C2AD9FBAAD@gmail.com> (raw)
In-Reply-To: <CAA93jw6zH8subf4v16bq6S9ZnWcTmHf362yK=-ymtfNCZr0PLQ@mail.gmail.com>
Folks,
Dave Täht pointed out that the FCC has proposed new rules (by issuing a Notification of Proposed Rule Making - NPRM) His one-line summary - "these fcc rules look bad")
The rest of this message has links for the BattleMesh presentation and for submitting public comments, etc. You can read the actual filing at: http://transition.fcc.gov/Daily_Releases/Daily_Business/2015/db0722/FCC-15-92A1.pdf
THE DEADLINE IS 16 AUGUST 2015 (NEXT SUNDAY). I plan to submit a comment saying that any rules that lock down the router firmware will hamper research into important networking technologies, and leave the US in a less competitive situation.
Best,
Rich
On Aug 10, 2015, at 9:59 AM, Dave Taht <dave.taht@gmail.com> wrote:
> these fcc rules look bad
>
>
> ---------- Forwarded message ----------
> From: Jenny Ryan <tunabananas@gmail.com>
> Date: Mon, Aug 10, 2015 at 6:04 AM
> Subject: [Battlemesh] Mailing list to coordinate responses to FCC
> ruling on router hacking
> To: "mesh@lists.sudoroom.org" <mesh@lists.sudoroom.org>, Battle of the
> Mesh Mailing List <battlemesh@ml.ninux.org>, sudo-discuss
> <sudo-discuss@lists.sudoroom.org>
>
>
> In case it slipped through the radar, please join the conversation and
> send an email to the FCC by August 16th re: new regulations preventing
> channel-switching and firmware flashing (eg OpenWRT) on wireless
> routers.
>
> * Mailing List: http://lists.prplfoundation.org/cgi-bin/mailman/listinfo/fcc
> * Public comments form: http://apps.fcc.gov/ecfs/proceeding/view?name=15-170
> * The talk from BattleMesh:
> http://www.cnx-software.com/2015/08/07/openwrt-vs-fcc-forced-firmware-lockdown-presentation-video-and-slides/
> * Current filings:
> http://apps.fcc.gov/ecfs/comment_search/execute;ECFSSESSION=3nr2V8QKjGWghGDngpFgf6TxvXqFDv94FM4Bz4SxQ6bD2f1BTbJb!-1954627099!-1292486409?proceeding=15-170
>
> If someone from sudomesh could start a pad for writing a collective
> response, that would be great. I'll have some time on my nightbus ride
> to Berlin tonight to pitch in but will be unavailable for the next 8
> hours.
>
> Cheers,
> Jenny
>
> Help open a people-powered common space in Oakland, California!
> https://omnicommons.org/donate
>
> `~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
> "Technology is the campfire around which we tell our stories."
> -Laurie Anderson
>
> "Storytelling reveals meaning without committing the error of defining it."
> -Hannah Arendt
>
> "To define is to kill. To suggest is to create."
> -Stéphane Mallarmé
> ~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`
>
> _______________________________________________
> Battlemesh mailing list
> Battlemesh@ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh
>
>
>
> --
> Dave Täht
> worldwide bufferbloat report:
> http://www.dslreports.com/speedtest/results/bufferbloat
> And:
> What will it take to vastly improve wifi for everyone?
> https://plus.google.com/u/0/explore/makewififast
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
prev parent reply other threads:[~2015-08-10 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF0yFe6BN=HJ8pLbpi30iWucDRHcwPNFmrs+5Sv2+_S1G5j+dg@mail.gmail.com>
2015-08-10 13:59 ` [Cerowrt-devel] Fwd: [Battlemesh] " Dave Taht
2015-08-10 17:02 ` Rich Brown [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=DADEB42F-592C-41BF-BC50-98C2AD9FBAAD@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--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