Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: rjmcmahon <rjmcmahon@rjmcmahon.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] BEAD guidelines phase 2
Date: Thu, 19 Oct 2023 09:35:20 -0700	[thread overview]
Message-ID: <269ca6a8cebeaecf9810731bad0b6045@rjmcmahon.com> (raw)
In-Reply-To: <D5CA78B1-8EBA-4F86-BA04-79BA5D323B27@comcast.com>

Hi Jason,

Is there any public information that is accurate and breaks out the 
sustaining and opex costs of an ISP, along with the trend lines of each 
sub category?

Bob
> If you think the BEAD rules are a lot, of course just bear in mind the
> follow-on compliance needs w/r/t Title-II. ;-) In any case, having
> spoken at some recent BEAD events, my focus has been on trying to get
> folks to think "beyond the build" so to speak. What I mean is that the
> main focus has been on the initial physical build. That is of course
> critical in these rural and other unserved locations, but is often the
> easy part in a way. Sustaining ongoing network operations and all that
> operating an ISP these days involves is a bigger deal and likely more
> complex than many perceive.
> 
> JL
> 
> On 10/18/23, 16:34, "Nnagain on behalf of Dave Taht via Nnagain"
> <nnagain-bounces@lists.bufferbloat.net
> <mailto:nnagain-bounces@lists.bufferbloat.net> on behalf of
> nnagain@lists.bufferbloat.net <mailto:nnagain@lists.bufferbloat.net>>
> wrote:
> 
> 
> 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://urldefense.com/v3/__https://www.linkedin.com/posts/brooke-coleman-broadband_bead-grant-internetforall-activity-7120436030196903937-kP6O__;!!CQl3mcHX2A!BAVazn1pE2o686uDjeD0sin7cjod4hmQ9mLslfZxkqelltKeEnadv2oLeIcwZuN1uTqe7trI8GHuSOtxzmuapGF2SbKoVyY8$
> <https://urldefense.com/v3/__https://www.linkedin.com/posts/brooke-coleman-broadband_bead-grant-internetforall-activity-7120436030196903937-kP6O__;!!CQl3mcHX2A!BAVazn1pE2o686uDjeD0sin7cjod4hmQ9mLslfZxkqelltKeEnadv2oLeIcwZuN1uTqe7trI8GHuSOtxzmuapGF2SbKoVyY8$>
> 
> 
> PS the P99conf I am in this week is VERY good and clued, and 100% 
> online.

  reply	other threads:[~2023-10-19 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 20:33 Dave Taht
2023-10-19 13:25 ` Livingood, Jason
2023-10-19 16:35   ` rjmcmahon [this message]
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=269ca6a8cebeaecf9810731bad0b6045@rjmcmahon.com \
    --to=rjmcmahon@rjmcmahon.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