From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 39ED920003D for ; Mon, 14 Sep 2015 16:52:14 -0700 (PDT) Received: by oixx17 with SMTP id x17so86033905oix.0 for ; Mon, 14 Sep 2015 16:52:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=o6xRArDkEq3WC5F1O7TCJ4CerIQH8o8V0UJ5iQ9wF1M=; b=Lcw9IHGoSJtxWM7Qock+llrHeug8l046uRQ1RJGGIhpa4Agc8bryViT20tCCW7Bk0M WFfS2WtH1Ibtn27wkatbUw6+VRo/CaNHE0PR90xL9y1ebC+gOEa9lEpvBVWMdP6wxgCg JwFKvEYhWTe0BSCrwKOZU+3mhqE1l0WvB2Iyuh+GZOhIIHVDfdA0hsNtn/a9FpVxEvHL k3lo9ce1eJW3rB6bol/jrDaFHegxVOEXWBTCjLBuh9ZqcACv9kLyaInHCx+yb1nzLUYx pkVageVxCu9d0BJxaNE9iwE5FShSo5uxvxcbCZ4HaPc/q5yDiu6JbkHkj84kzmWovnjc 7VBQ== MIME-Version: 1.0 X-Received: by 10.202.224.130 with SMTP id x124mr13705177oig.110.1442274734024; Mon, 14 Sep 2015 16:52:14 -0700 (PDT) Received: by 10.202.108.212 with HTTP; Mon, 14 Sep 2015 16:52:13 -0700 (PDT) In-Reply-To: References: Date: Mon, 14 Sep 2015 16:52:13 -0700 Message-ID: From: Dave Taht To: fcc@lists.prplfoundation.org, make-wifi-fast@lists.bufferbloat.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Make-wifi-fast] some basic guidance on how to write something for the fcc X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Sep 2015 23:52:37 -0000 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 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=C3=A9cis (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=3DJS5vV2S= bXTD7LHltYX41B9SbcBfLrz19CJz8hgpP2QLWlGCTv1Qn!310921635!-543955373 > > -- > Dave T=C3=A4ht > endo is a terrible disease: http://www.gofundme.com/SummerVsEndo --=20 Dave T=C3=A4ht endo is a terrible disease: http://www.gofundme.com/SummerVsEndo