From: "Dick Roy" <dickroy@alum.mit.edu>
To: "'Sebastian Moeller'" <moeller0@gmx.de>,
"'Network Neutrality is back! Let´s make the technical aspects
heard this time!'" <nnagain@lists.bufferbloat.net>,
"'Sebastian Moeller via Nnagain'" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] The rise and fall of the 90's telecom bubble
Date: Thu, 16 Nov 2023 09:02:41 -0800 [thread overview]
Message-ID: <FE1CE23C2AD04DFB8EE8972D2348FC49@SRA6> (raw)
In-Reply-To: <B4C98180-D598-42DB-A6F1-D50712EC8BB6@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 4939 bytes --]
_____
From: Sebastian Moeller [mailto:moeller0@gmx.de]
Sent: Thursday, November 16, 2023 3:02 AM
To: Network Neutrality is back! Let´s make the technical aspects heard this
time!; Sebastian Moeller via Nnagain; Dick Roy
Subject: Re: [NNagain] The rise and fall of the 90's telecom bubble
Update, mmmh,
Virginia is apparently not only for 'lovers' but also for LTE, along the
trip with the silver line to Dulles, my phone reported 4G, aka LTE, while in
downtown DC EDGE-only it was...
[RR] You are really lucky! It could have said 5G in which case youd have
been down to 19kbps 1980 modem rates! :-):-)
Regards
Sebsstian
On 14 November 2023 13:06:39 CET, Sebastian Moeller via Nnagain
<nnagain@lists.bufferbloat.net> wrote:
Hi Richard,
On Nov 13, 2023, at 16:08, Dick Roy via Nnagain
<nnagain@lists.bufferbloat.net> wrote:
-----Original Message-----
From: Nnagain [mailto:nnagain-bounces@lists.bufferbloat.net] On Behalf Of
Sebastian Moeller via Nnagain
Sent: Monday, November 13, 2023 6:15 AM
To: Network Neutrality is back! Let´s make the technical aspects heard this
time!
Cc: Sebastian Moeller
Subject: Re: [NNagain] The rise and fall of the 90's telecom bubble
Hi Jason,
On Nov 13, 2023, at 08:54, Livingood, Jason via Nnagain
<nnagain@lists.bufferbloat.net> wrote:
Would love to spend some time thinking together about what a smart
manufacturing system would look like in terms of connectivity, latency,
compute availability, anything that occurs to you. I know a guy who does
devops for factories, and he has amazing stories -- might be good to make
that connection as well.
One of the L4S (low latency, low loss, scalable throughput) demos that Nokia
did at a recent IETF hackathon showed a simulated 5G access network to do
low latency remote control of cranes in an industrial port facility. It
seemed like one of their points was that you could remotely operate cargo
container movements with the crane via a remote workforce over a low delay
network connection - even with fairly limited bandwidth (theyd adjust the
throughput down to just a few hundred kbps).
While they did not say much more, I could envision a port operator being
able to gain more efficiency by enabling a skilled operator to control
cranes at several ports around the world on an as-needed basis (vs. being
based in 1 port and having some downtime or low utilization of their
skills/training), even from the comfort of home.
I would stop doing business with such ports... there clearly are
accidents (or sabotage/jamming) just waiting to happen using wireless
connections for such use-cases... Yes, I understand that that is what Nokia
sells, so everything looks like a nail to them, but really "caveat emptor",
just because something can be done does not mean it should be done as
well...
Regards
Sebastian
P.S.: Currently in the US for a conference, getting reminded how shitty
GSM/LTE can be, heck the conference WiFi (with 25K attendees) is more
responsive than GSM... I am sure 5G might be better, but my phone is LTE
only...
[RR] Welcome to the club! We in the US have been dealing with this for
over 30 years
why you ask???? ... answer
CDMA and the IPR behind it! It
was and still is all about the money!. My phone has 5G and when download
rates plummet to the floor, all I have to do is look at the top of the
display, and lo and behold
Im on 5G!!! If you believe 5G is going to be
better, I have a bridge for you that is going to be soooo much better JJJ
All good explanations for what I see, yet this is happening in the
capital... (but truth be told, when I bought this phone I did not pay much
attention to which bands it was suited for, it is not impossible that it at
least partly my phone's fault that I am connecting with EDGE speeds, quite
the throw-back to the 2000s ;) but back then EDGE was indeed cutting edge).
About that bridge, I hope this is in NY city?
Regards
Sebastian
RR
Jason
_____
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
_____
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
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 12616 bytes --]
next prev parent reply other threads:[~2023-11-16 17:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 15:48 Dave Taht
2023-11-12 20:22 ` Nathan Simington
2023-11-13 11:28 ` Dave Taht
2023-11-13 13:54 ` Livingood, Jason
2023-11-13 14:15 ` Sebastian Moeller
2023-11-13 21:08 ` Dick Roy
2023-11-14 12:06 ` Sebastian Moeller
2023-11-14 12:41 ` Dave Taht
2023-11-16 11:01 ` Sebastian Moeller
2023-11-16 17:02 ` Dick Roy [this message]
2023-11-16 17:20 ` Olivier MJ Crépin-Leblond
2023-11-16 17:40 ` Dick Roy
2023-11-16 22:03 ` Frantisek Borsik
2023-11-13 3:46 ` Joe Hamelin
2023-11-14 13:48 ` Mike Hammett
2023-11-13 19:27 odlyzko
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=FE1CE23C2AD04DFB8EE8972D2348FC49@SRA6 \
--to=dickroy@alum.mit.edu \
--cc=moeller0@gmx.de \
--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