From: Dave Taht <dave.taht@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Save WiFi from the FCC - DEADLINE is in 3 days *September* 8
Date: Sat, 5 Sep 2015 15:05:34 -0700 [thread overview]
Message-ID: <CAA93jw4ovypOC3Ts0bwQUbOfW9RUo-SsJMt_6siyUyuaUbAo3Q@mail.gmail.com> (raw)
In-Reply-To: <B6B11CD5-D7BC-40CC-9C23-D9ED215B9ADA@gmail.com>
while the current FCC course sucks, I personally have been unable to
summon the moxy to fight anymore. Decided to migrate to the eu
instead, only to find the same ruling going into play here. Is there
no place left on the planet safe to innovate in?
and: LTE-U is an even greater threat, and I'm low on ideas on how to counter it.
http://www.wsj.com/articles/cell-carriers-battle-for-wi-fi-airwaves-1440543853
On Sat, Sep 5, 2015 at 7:12 AM, Rich Brown <richb.hanover@gmail.com> wrote:
> Folks,
>
> Dave may have buried the lede in his previous note... The date for comments
> to the FCC is not a month away, but only three days away - 8 Sep 2015.
>
> To see the talking points for preparing your comments, go to:
> https://libreplanet.org/wiki/Save_WiFi
>
> To submit a comment, click the green "SUBMIT A FORMAL COMMENT" button on
> https://www.federalregister.gov/articles/2015/08/06/2015-18402/equipment-authorization-and-electronic-labeling-for-wireless-devices
>
> Please post a link to your comments when you're done.
>
> Rich
>
> On Sep 5, 2015, at 6:42 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
> In other news:
>
> I am glad to see the more political save-the-wifi coming online rapidly:
>
> https://libreplanet.org/wiki/Save_WiFi
>
> I HAD NO IDEA that the follow-on rules for 2016 would basically ban
> modifiable firmware entirely, nor that the DFS problem was due to only 41
> old radars that need to be replaced anyway.
>
> Comment deadline for the fcc is sept 8th, not oct 8, which means we should
> strap ourselves into the writing console, like, today.
>
>
--
Dave Täht
endo is a terrible disease: http://www.gofundme.com/SummerVsEndo
next prev parent reply other threads:[~2015-09-05 22:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 10:42 [Make-wifi-fast] cerowrt.org vs make-wifi-fast Dave Taht
2015-09-05 14:04 ` [Make-wifi-fast] [Cerowrt-devel] cerowrt.org vs make-wifi-fast/Network Solutions price is high Rich Brown
2015-09-05 14:12 ` [Make-wifi-fast] Save WiFi from the FCC - DEADLINE is in 3 days *September* 8 Rich Brown
2015-09-05 22:05 ` Dave Taht [this message]
2015-09-06 9:02 ` [Make-wifi-fast] RE : [Bloat] " luca.muscariello
2015-09-08 7:55 ` Dave Taht
2015-09-08 8:22 ` [Make-wifi-fast] [Bloat] RE : " Mikael Abrahamsson
2015-09-08 8:36 ` Dave Taht
2015-09-08 8:55 ` Mikael Abrahamsson
2015-09-08 9:21 ` Dave Taht
2015-09-08 9:55 ` Mikael Abrahamsson
2015-09-08 14:45 ` Michael Richardson
2015-09-08 12:13 ` [Make-wifi-fast] RE : [Bloat] " MUSCARIELLO Luca IMT/OLN
2015-09-07 23:12 ` [Make-wifi-fast] [Cerowrt-devel] " Jonathan Morton
2015-09-08 6:12 ` Rich Brown
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4ovypOC3Ts0bwQUbOfW9RUo-SsJMt_6siyUyuaUbAo3Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=richb.hanover@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