From: Rich Brown <richb.hanover@gmail.com>
To: Eric Schultz <eschultz@prplfoundation.org>
Cc: make-wifi-fast@lists.bufferbloat.net,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Cerowrt-devel] Save WiFi from the FCC - DEADLINE is OCTOBER 9 now.
Date: Tue, 8 Sep 2015 14:31:37 -0400 [thread overview]
Message-ID: <7409D5C4-FA83-40BB-B6D3-706B2DA53EF1@gmail.com> (raw)
In-Reply-To: <CAMkzgA5Cw_94uPb6eZ97=ub18fkAvHjaJ_4BGOkK4+FrKhaN5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
Hi Eric,
Yes, I agree that it is confusing. And you're right - it's OCTOBER 9. Here's the supporting documentation:
https://apps.fcc.gov/edocs_public/attachmatch/DA-15-956A1.pdf <https://apps.fcc.gov/edocs_public/attachmatch/DA-15-956A1.pdf>
(TL;DR - read paragraph 4 to cut through the blah, blah blah)
Rich
> On Sep 8, 2015, at 11:58 AM, Eric Schultz <eschultz@prplfoundation.org> wrote:
>
> All,
>
> I just wanted to make sure everyone knows that the deadline is October 9 which the FCC announced on August 25 (https://www.fcc.gov/document/extension-comments-equipment-authorization <https://www.fcc.gov/document/extension-comments-equipment-authorization>). I know this is super confusing but the FCC is apparently not known for user friendliness. This is further confused by the FCC's mess of a transition of their apps over the weekend. I'd send the PDF of the extension but, again, the FCC screwed up their transition.
>
> I'm sorry this is wildly confusing. I need to work on explaining this better.
>
> Eric
>
> --
> Eric Schultz, Community Manager, prpl Foundation
> http://www.prplfoundation.org <http://www.prplfoundation.org/>
> eschultz@prplfoundation.org <mailto:eschultz@prplfoundation.org>
> cell: 920-539-0404
> skype: ericschultzwi
> @EricPrpl
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
[-- Attachment #2: Type: text/html, Size: 2789 bytes --]
parent reply other threads:[~2015-09-08 18:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAMkzgA5Cw_94uPb6eZ97=ub18fkAvHjaJ_4BGOkK4+FrKhaN5Q@mail.gmail.com>]
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=7409D5C4-FA83-40BB-B6D3-706B2DA53EF1@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=eschultz@prplfoundation.org \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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