From: Dave Taht <dave.taht@gmail.com>
To: fcc@lists.prplfoundation.org,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>,
make-wifi-fast@lists.bufferbloat.net
Subject: [Cerowrt-devel] draft of my letter to the fcc
Date: Tue, 8 Sep 2015 05:19:52 -0700 [thread overview]
Message-ID: <CAA93jw7Wv9OSVQRqp-ef6=dbP5MWJAfnN+Yy1QCehjBW9tgz6w@mail.gmail.com> (raw)
this is a draft letter to the fcc. It kind of needs a title, more
footnotes, and other formatting - and if more folk here are willing to
sign, we can get rid of the first person stuff and make it "we". A
review for accuracy would be nice, and I can put it up on google docs
for a group edit if you like.
I'll also argue the closing sentences could be stronger.
http://snapon.lab.bufferbloat.net/~d/fcc_alternate_guidelines.odt
but I need a break. was up all night.
--
Dave Täht
endo is a terrible disease: http://www.gofundme.com/SummerVsEndo
next reply other threads:[~2015-09-08 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 12:19 Dave Taht [this message]
2015-09-08 12:37 ` Toke Høiland-Jørgensen
2015-09-08 12:41 ` Dave Taht
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='CAA93jw7Wv9OSVQRqp-ef6=dbP5MWJAfnN+Yy1QCehjBW9tgz6w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=fcc@lists.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