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] BEAD guidelines phase 2
Date: Wed, 18 Oct 2023 13:33:45 -0700	[thread overview]
Message-ID: <CAA93jw7un3nYqgqw3EhP71hQhZ4y1BYcB95Fs1F-2_ptOnQjUw@mail.gmail.com> (raw)

Prior to NN coming back into view, I was primarily trying to put some
sense into the BEAD processes and priorities.
I strongly approved of the idea of the central government handing the
issues for the states to try and handle, they are just as understaffed
and low on clue technologically, and I figured the odds were oh, 7 out
of 50 that might establish good programs for it.

I have now seen a few nice proposals funded, including one up in main
that connects to canada. But oh! the profusion of rules required, to
seek to do a build out, only covering CAPEX, in each state, is hard to
get through, and I think, like many here, we wish it would go away.
Hereś some if you wish to while away a lazy friday afternoon. Pick one
randomly. Let us know if you see anything good, or sane, or hilareous,
or horrible?

https://www.linkedin.com/posts/brooke-coleman-broadband_bead-grant-internetforall-activity-7120436030196903937-kP6O

PS the P99conf I am in this week is VERY good and clued, and 100% online.

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

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 20:33 Dave Taht [this message]
2023-10-19 13:25 ` Livingood, Jason
2023-10-19 16:35   ` rjmcmahon
2023-10-19 18:02     ` [NNagain] [EXTERNAL] " 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=CAA93jw7un3nYqgqw3EhP71hQhZ4y1BYcB95Fs1F-2_ptOnQjUw@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