From: "Livingood, Jason" <jlivin00@comcast.com>
To: Dave Taht via Nnagain <nnagain@lists.bufferbloat.net>
Subject: [NNagain] Section 214 - Public Safety / National Security
Date: Thu, 5 Oct 2023 20:18:53 +0000 [thread overview]
Message-ID: <32CD2DB0-3C56-46C7-BE9A-565303D54AED@cable.comcast.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
Still reading the long FCC NPRM…
So far, the only interesting/new things I see so far compared to last time are some new national security requirements – in some of the Section 214 mentions. Might that trigger de-peering of some China-based networks? There was some other stuff about priority government network access in emergencies IIRC and other ‘public safety’ stuff (CALEA*, TSP, GETS, WPS, WEA/EAS). Folks with better S214 experience may want to look at this, especially as it pertains to protecting end-to-end encryption*.
JL
* Part 35 for example asks how CALEA might be expanded.
[-- Attachment #2: Type: text/html, Size: 3028 bytes --]
next reply other threads:[~2023-10-05 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 20:18 Livingood, Jason [this message]
2023-10-06 21:59 Livingood, Jason
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=32CD2DB0-3C56-46C7-BE9A-565303D54AED@cable.comcast.com \
--to=jlivin00@comcast.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