Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] The rise and fall of the 90's telecom bubble
Date: Mon, 13 Nov 2023 09:15:14 -0500	[thread overview]
Message-ID: <4154C0D8-EF61-4483-97F9-7CDE82CD803D@gmx.de> (raw)
In-Reply-To: <6318C91C-A664-464E-8A9E-4C2A0FFD9C05@comcast.com>

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 (they’d 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... 


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


  reply	other threads:[~2023-11-13 14:15 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 [this message]
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
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=4154C0D8-EF61-4483-97F9-7CDE82CD803D@gmx.de \
    --to=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