Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "David Fernández" <davidfdzp@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] [LibreQoS] [Rpm] On FiWi
Date: Mon, 20 Mar 2023 09:18:01 +0100	[thread overview]
Message-ID: <CAC=tZ0q2-A=SLdoKH8kSh7nUqtuVEGuXr0uweq9iyHevA9d2PQ@mail.gmail.com> (raw)

"lorawan will never get built out across the planet"

Well, roughtly 10% of the globe is covered by cellular connectivity. I
would not expect lorawan to get built across the planet, although
there are IoT via satellite companies, such as Lacuna Space, using
lorawan.

In the map of the Lorawan Alliance website it is indicated that there
are Lorawan networks all around the world.

The main issue with Lorawan seems to be interferences, due to the use
of unlicensed spectrum. NB-IoT does not have that problem and then it
is also the work of the operator all the maintenance to keep the
connectivity running.

Regards,

David

> Date: Sat, 18 Mar 2023 13:40:30 -0700
> From: rjmcmahon <rjmcmahon@rjmcmahon.com>
> To: dan <dandenson@gmail.com>
> Cc: Bruce Perens <bruce@perens.com>, Dave Taht via Starlink
> 	<starlink@lists.bufferbloat.net>, Rpm <rpm@lists.bufferbloat.net>,
> 	Sebastian Moeller <moeller0@gmx.de>, bloat
> 	<bloat@lists.bufferbloat.net>, libreqos
> 	<libreqos@lists.bufferbloat.net>
> Subject: Re: [Starlink] [LibreQoS]  [Rpm] On FiWi
> Message-ID: <569691b3e7dfc57bbf98c4fc168fc6cf@rjmcmahon.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
>   > All of the states use cases are already handled by inexpensive
> lorawan
>> sensors and are already covered by multiple lorawan networks in NYC
>> and most urban centers in the US.  There is no need for a new
>> infrastructure, it’s already there.  Not to mention NBIoT/catm
>> radios.
>>
>> This is all just general cheapness and lack of liability keeping these
>> out of widespread deployment. It’s not lack of tech on the market
>> today.
>
> What is the footprint of lorawan networks and what's the velocity of
> growth? What's the cost per square foot both capex and operations,
> maintaining & monitoring lorawan? What's that compared to the WiFi
> install base, i.e. now we have train even installers and maintainers on
> purpose built technology vs just use what most people know because it's
> common? This all looks like ethernet, token ring, fddi, netbios, decnet,
> etc. where the single approach of IP over WiFi/ethernet with fiber
> fronthaul wave guides and backhauls' waveguides per the ISP seems the
> effective way forward. I don't think it's in society's interest to have
> so disparate networks technologies as we have learned from IP and the
> internet. My guess is lorawan will never get built out across the planet
> as has been done for IP. I can tell that every country is adopting IP
> because they're using a free IP tool to measure their networks.
>
> https://sourceforge.net/projects/iperf2/files/stats/map?dates=2014-02-06%20to%202023-03-18&period=daily
>
> Bob

             reply	other threads:[~2023-03-20  8:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20  8:18 David Fernández [this message]
     [not found] <mailman.2651.1672779463.1281.starlink@lists.bufferbloat.net>
2023-01-03 22:58 ` [Starlink] Researchers Seeking Probe Volunteers in USA David P. Reed
2023-01-09 14:44   ` Livingood, Jason
2023-01-09 15:26     ` Dave Taht
2023-01-09 18:54       ` [Starlink] [EXTERNAL] " Livingood, Jason
2023-01-09 19:19         ` [Starlink] [Rpm] " rjmcmahon
2023-01-09 19:56           ` [Starlink] [LibreQoS] " dan
2023-03-13 10:02             ` [Starlink] [Rpm] [LibreQoS] " Sebastian Moeller
2023-03-13 15:08               ` Jeremy Austin
2023-03-13 15:50                 ` Sebastian Moeller
2023-03-13 16:12                   ` dan
2023-03-13 16:36                     ` Sebastian Moeller
2023-03-13 17:26                       ` dan
2023-03-13 18:14                         ` Sebastian Moeller
2023-03-13 18:42                           ` rjmcmahon
2023-03-13 18:51                             ` Sebastian Moeller
2023-03-13 19:32                               ` rjmcmahon
2023-03-13 20:00                                 ` Sebastian Moeller
2023-03-13 20:28                                   ` rjmcmahon
2023-03-14  4:27                                     ` [Starlink] On FiWi rjmcmahon
2023-03-14 11:10                                       ` Mike Puchol
2023-03-17 16:38                                         ` [Starlink] [Rpm] " Dave Taht
2023-03-17 19:01                                           ` Sebastian Moeller
2023-03-17 19:19                                             ` rjmcmahon
2023-03-17 20:37                                               ` Bruce Perens
2023-03-17 20:57                                                 ` rjmcmahon
2023-03-17 22:50                                                   ` Bruce Perens
2023-03-18 18:18                                                     ` rjmcmahon
2023-03-18 19:57                                                       ` [Starlink] [LibreQoS] " dan
2023-03-18 20:40                                                         ` rjmcmahon
2023-03-19 10:26                                                           ` Michael Richardson

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/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC=tZ0q2-A=SLdoKH8kSh7nUqtuVEGuXr0uweq9iyHevA9d2PQ@mail.gmail.com' \
    --to=davidfdzp@gmail.com \
    --cc=starlink@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