Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: [NNagain] FCC CyberSecurity Label comments due today
Date: Fri, 6 Oct 2023 11:06:02 -0700	[thread overview]
Message-ID: <CAA93jw7B-VEsXkpVD+_Guy7gn2p4EZpQNWhSv38T5MqnEyCckw@mail.gmail.com> (raw)

The genesis of the nnagain list came from here:

https://news.ycombinator.com/item?id=37392676

And while I have reviewed some of the nist and cybersecurity stuff, I
just put in a small reference to
http://www.taht.net/~d/fcc_saner_software_practices.pdf so long as to
stay in the game for the follow-on comment period after the initial
batch of comments is processed.

If you want to learn more about this particular proceeding, please
read past that thread and into the underlying stuff. I am delighted
that finally fixing home routers is obliquely on the table.

-- 
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos

                 reply	other threads:[~2023-10-06 18:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/nnagain.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw7B-VEsXkpVD+_Guy7gn2p4EZpQNWhSv38T5MqnEyCckw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --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