Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: "Livingood, Jason" <jason_livingood@comcast.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] What is the difference between "broadband" and "Internet"?
Date: Mon, 6 Nov 2023 13:56:21 +0000	[thread overview]
Message-ID: <2C03C48A-3D6D-41C9-8404-C78900E0F5CA@comcast.com> (raw)
In-Reply-To: <CAA93jw5mN5YJ3nrO72FOTtkZA6h8WL5=iECAPugT+3emDFRJSA@mail.gmail.com>

On 11/6/23, 13:48, "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 

> https://www.lightreading.com/5g/the-telecom-industry-looks-rotten-to-the-core "The telecom industry looks rotten to the core"

The author says "telecom" but more narrowly seems to define it as 5G equipment vendors and maybe also MNOs. Putting aside the hyperbole of the title, it seems to me there's a normal technology transition happening. The tech stack in mobile is a little behind-the-times IMO - most MNOs seem to still rely on vertically integrated single-vendor solutions. OpenRAN seems like one approach to try to disaggregate the various functional components of a 5G network. As that happens, MNOs may take on more of a software integration role from the traditional vendors and eventually even software dev in some areas, with a shift of labor need from the legacy vendors to others. But that is just my guess - I only observe 5G networks from afar.  

JL



  reply	other threads:[~2023-11-06 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 12:47 Dave Taht
2023-11-06 13:56 ` Livingood, Jason [this message]
2023-11-06 14:02 ` 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=2C03C48A-3D6D-41C9-8404-C78900E0F5CA@comcast.com \
    --to=jason_livingood@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