From: Rich Brown <richb.hanover@gmail.com>
To: nnagain@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] FCC NOI Response has been filed
Date: Fri, 1 Dec 2023 17:02:11 -0500 [thread overview]
Message-ID: <C0B08F55-4F1C-424A-B29F-382736188395@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
Folks,
In Dave's stead, I pulled the trigger on the Bufferbloat.net community response to the FCC NOI about 10 minutes ago. Here's the final PDF (although I'm pretty sure it won't make it through as an attachment...)
We will figure out how to get the PDF posted somewhere real soon.
This has been a terrific group effort. Thanks to all who contributed.
Rich Brown
[-- Attachment #2: Bufferbloat.net FCC NOI response-1Dec2023.pdf --]
[-- Type: application/pdf, Size: 1629424 bytes --]
next reply other threads:[~2023-12-01 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 22:02 Rich Brown [this message]
2023-12-01 23:03 ` [Bloat] [NNagain] " Dick Roy
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C0B08F55-4F1C-424A-B29F-382736188395@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=nnagain@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