Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: "Dick Roy" <dickroy@alum.mit.edu>
To: "'Dave Cohen'" <craetdave@gmail.com>,
	"'Network Neutrality is back! Let´s make the technical aspects
	heard this time!'" <nnagain@lists.bufferbloat.net>
Cc: "'Livingood, Jason'" <jlivin00@comcast.com>
Subject: Re: [NNagain] On "Throttling" behaviors
Date: Fri, 6 Oct 2023 08:56:28 -0700	[thread overview]
Message-ID: <6896987296844AA9A48D2B26A0D35D44@SRA6> (raw)
In-Reply-To: <ED3AE27D-5346-4E6E-942C-B65EA9F5E5E0@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 5400 bytes --]

 

 

  _____  

From: Dave Cohen [mailto:craetdave@gmail.com] 
Sent: Thursday, October 5, 2023 3:54 PM
To: dickroy@alum.mit.edu; Network Neutrality is back! Let´s make the technical aspects heard this time!
Cc: Livingood, Jason
Subject: Re: [NNagain] On "Throttling" behaviors

 

I admittedly know little about the service from the radio out in FWA deployments like this but have done a lot of work in the aggregation and backhaul arenas in both environments. The advantage the FWA folks have is that it is significantly more financially viable to not oversubscribe (or oversubscribe less) when you deliver more users from a more centralized next hop location. In other words, it’s easier and cheaper to have 100 Gbps serving 1000 users from a single location than it is to have 1 Gbps serving 10 users from 100 different locations. Which is not to say that there aren’t other challenges in FWA environments relative to FTTx environments, but system capacity (you can always add more radios, with enough available spectrum, at least) isn’t one of them.

[RR] Well, yes and no.  Turns out this is a convex optimization problem (or at least can be converted in to one) that involves things like amount of spectrum, density of let’s call them access points (or APs), the capabilities of each AP in terms of tx power, number of antennas, how sophisticated the signal processing is that can be supported in those APs, and a few other things like adjacent channels and their pollution and constraints placed on the APs because they are secondary users of the band …

OK, with that as background  the question becomes at it’s simplest (leaving out for the moment things like OPEX, property leases, etc.):

“How many customers can I serve with X amount of infrastructure investment and Y amount of spectrum available to me (purchased or otherwise).  I am somewhat suspicious, though I have not done the analysis yet which is why I asked the question actually, that to use your example, supplying 100Gbps aggregate service to 1000 customers using FWA is not within the feasible region of the optimization space and therefore something has to give! :-) :-) :-)  FTR, FWA has been around for 3 decades or more (the company I started was selling such units in the mid-90’s, albeit largely for voice services since that what was wanted back then).  The systems that are still operational (and that’s a large number of them) have been upgraded to offer data services, however the number of subscribers needs to be capped well below that which ISPs using other newer technologies can support.  This is why I am interested to find out what the “state-of-ply” is today! :-) :-)

Cheers,

RR

Dave Cohen

craetdave@gmail.com





On Oct 5, 2023, at 6:17 PM, Dick Roy via Nnagain <nnagain@lists.bufferbloat.net> wrote:

 

Has anyone done an analysis of the capacity of FWA systems (in bits/sec/Hz/km^3)????  I am suspicious that the capacity falls way short of that which cable guys have at their disposal, and that as the FWA networks get loaded, performance is going to degrade dramatically ultimately resulting in churn back to the cable guys.  It's very expensive to compete with already sunk FTTH or even FTTC.  

 

RR

 

-----Original Message-----
From: Nnagain [mailto:nnagain-bounces@lists.bufferbloat.net] On Behalf Of Livingood, Jason via Nnagain
Sent: Thursday, October 5, 2023 1:25 PM
To: Network Neutrality is back! Let´s make the technical aspects heard this time!
Cc: Livingood, Jason
Subject: Re: [NNagain] On "Throttling" behaviors

 

> On 10/4/23, 13:45, "Nnagain on behalf of David Lang 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:

 

> It's an unfortunate fact of reality that the enviornment in the US is one where 

there is very little competition in the ISP space 

 

The SEC 10-K filings of ISPs no longer support that. Most wireline ISPs are losing subscribers (at material levels) to one of the three new national 5G FWA ISPs (Verizon, T-Mobile, AT&T). In addition, we will in a few years see the effects of $45B+ of grant money dedicated to underwrite new broadband access network construction - that is also pretty material. 

 

Per https://telecoms.com/523519/growth-in-5g-fwa-kit-matches-operator-hype/

- " 5G FWA customer premises equipment shipments more than doubled to 7.4 million last year and should reach 13.8 million – that’s 86% growth – this year "

- " The GSA survey shows overall FWA CPE shipments of 25.5 million units last year, "

- " Statistics shared by Leichtman Research Group recently showed that T-Mobile and Verizon together recorded the best part of 900,000 5G FWA net adds in the second quarter of this year, significantly more than the virtually flat cable segment and ahead of the wireline broadband market, which lost almost 62,000 customers in the three months. "

 

JL

 

_______________________________________________

Nnagain mailing list

Nnagain@lists.bufferbloat.net

https://lists.bufferbloat.net/listinfo/nnagain

_______________________________________________
Nnagain mailing list
Nnagain@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/nnagain




[-- Attachment #2: Type: text/html, Size: 16102 bytes --]

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

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01 17:15 [NNagain] Some backstory on the nn-again mailing list Dave Taht
2023-10-01 18:56 ` Frantisek Borsik
2023-10-01 19:51   ` [NNagain] On "Throttling" behaviors Dave Taht
2023-10-01 20:50     ` Dave Cohen
2023-10-01 22:01       ` Patrick Maupin
2023-10-02  1:34         ` dan
2023-10-02  7:28           ` Sebastian Moeller
2023-10-02 16:29             ` dan
2023-10-04  7:30               ` Sebastian Moeller
2023-10-02 15:30           ` Andy Ringsmuth
2023-10-02 18:28             ` Nathan Loofbourrow
2023-10-02 20:34               ` Colin_Higbie
2023-10-02 21:04                 ` Dave Cohen
2023-10-02 21:07                 ` rjmcmahon
2023-10-02 21:43                   ` Colin_Higbie
2023-10-02 21:55                     ` rjmcmahon
2023-10-03 19:29                       ` Colin_Higbie
2023-10-03 19:45                         ` rjmcmahon
2023-10-04  0:57                     ` David Lang
2023-10-03  7:50                 ` Sebastian Moeller
2023-10-03  8:10                   ` Karl Auerbach
2023-10-03 14:41                     ` Sebastian Moeller
2023-10-03 15:34                   ` dan
2023-10-03 16:54                   ` rjmcmahon
2023-10-03 17:55                     ` Sebastian Moeller
2023-10-03 18:09                       ` Frantisek Borsik
2023-10-03 18:14                         ` dan
2023-10-03 19:44                         ` Dick Roy
2023-10-03 18:10                       ` dan
2023-10-03 19:23                         ` rjmcmahon
2023-10-04  1:05                         ` David Lang
2023-10-04  0:39                       ` David Lang
2023-10-03 20:26                   ` Colin_Higbie
2023-10-03 21:40                     ` dan
2023-10-04 15:56                       ` Colin_Higbie
2023-10-04 17:45                         ` David Lang
2023-10-05 20:24                           ` Livingood, Jason
2023-10-05 22:17                             ` Dick Roy
2023-10-05 22:47                               ` Jeremy Austin
2023-10-05 22:53                               ` Dave Cohen
2023-10-06 15:56                                 ` Dick Roy [this message]
2023-10-06 15:58                                 ` rjmcmahon
2023-10-04 17:59                         ` rjmcmahon
2023-10-04 19:26                         ` Dick Roy
     [not found]                       ` <MN2PR16MB3391A66B0DC222C43664DAD6F1CBA@MN2PR16MB3391.namprd16.prod.outlook.com>
2023-10-05  8:44                         ` Sebastian Moeller
2023-10-05 19:07                           ` David Lang
2023-10-03 23:17                     ` Mark Steckel
2023-10-04  7:51                       ` Sebastian Moeller
2023-10-02  6:48         ` Sebastian Moeller
2023-10-02 13:43         ` Livingood, Jason
2023-10-02 14:51           ` Mark Steckel
2023-10-02 18:09             ` Livingood, Jason
2023-10-02 18:15               ` Patrick Maupin
2023-10-02 19:18               ` Dick Roy
2023-10-02  6:34     ` Sebastian Moeller
2023-10-02 13:27     ` Livingood, Jason
2023-10-02  6:06   ` [NNagain] Some backstory on the nn-again mailing list Sebastian Moeller
2023-10-02 12:36 ` Bless, Roland (TM)
2023-10-03  7:15   ` Sebastian Moeller
2023-10-02 20:18 [NNagain] On "Throttling" behaviors Livingood, Jason
2023-10-02 20:28 ` 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/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=6896987296844AA9A48D2B26A0D35D44@SRA6 \
    --to=dickroy@alum.mit.edu \
    --cc=craetdave@gmail.com \
    --cc=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