From: Dave Taht <dave.taht@gmail.com>
To: fcc@lists.prplfoundation.org, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] some basic guidance on how to write something for the fcc
Date: Mon, 14 Sep 2015 16:52:13 -0700 [thread overview]
Message-ID: <CAA93jw7xLXKvJK96K28_+Pnv7ASZ2YxOf1YmJp7pD44d_fYzLw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw48=xmzPZeMnvdL3tNEkv1zcRZWGkFHdUBge1oEgaErVg@mail.gmail.com>
I note that I did not write this advice... and I still don't know what
sort of header or signature info should be included.
On Mon, Sep 14, 2015 at 4:09 PM, Dave Taht <dave.taht@gmail.com> wrote:
> * Remember your target audience is policy makers and lawyers.
> * Fully spell out any and all acronyms -- ALL of them.
> * Use footnotes for any detailed discussion of a point where needed.
> Lots of them.
> * Use footnotes to cite others work, claims of specific numbers,
> performance. benefits, costs, etc. Even your own. Do ALOT of this!!!
> * Did I say to use lots of footnotes???? And NOT endnotes - put the
> footnotes at the bottom of each page.
> * If you include any charts in the main body - keep them very simple
> and explain everything in them. Anything more than a very few simple
> charts - put in an appendix.
> * I would recommend any and all technical details in an appendix, etc.
> * Different - but I suggest that you use 12 font times-roman, double
> spaced text for the main body
>
> A bit more meaty items:
>
> * Talk to consumer/public benefits.
> * Talk to costs to implement for providers/carriers/public.
> * Talk to policy perspective vs technical perspective. Refer to
> techie talk in your main body but put all techie details in appendix.
> If you have a short clear précis (redundant terms - but I wanted to
> emphasize the point) put that in a footnote and details in appendix.
>
> Submitting:
>
> overall: https://www.fcc.gov/guides/how-comment
> paper: see https://www.fcc.gov/guides/how-file-paper-documents-fcc
> electronic: http://apps.fcc.gov/ecfs/upload/display;ECFSSESSION=JS5vV2SbXTD7LHltYX41B9SbcBfLrz19CJz8hgpP2QLWlGCTv1Qn!310921635!-543955373
>
> --
> Dave Täht
> endo is a terrible disease: http://www.gofundme.com/SummerVsEndo
--
Dave Täht
endo is a terrible disease: http://www.gofundme.com/SummerVsEndo
prev parent reply other threads:[~2015-09-14 23:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 23:09 Dave Taht
2015-09-14 23:52 ` Dave Taht [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/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=CAA93jw7xLXKvJK96K28_+Pnv7ASZ2YxOf1YmJp7pD44d_fYzLw@mail.gmail.com \
--to=dave.taht@gmail.com \
--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