From: Frantisek Borsik <frantisek.borsik@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: [Starlink] Fwd: [ih] Internet in the Air: Was Re: Internet at Sea
Date: Sat, 4 Oct 2025 22:06:32 +0200 [thread overview]
Message-ID: <CAJUtOOjE6ChKmYkz1M_iMFwVbbgkBn8dFUz+Ag=dy2e5fqB4Mg@mail.gmail.com> (raw)
In-Reply-To: <5b424221-b47b-4913-ad6a-0f58233b1d11@iwl.com>
Not exactly Starlink, but some goodies from Karl Auerbach et al re:
"Internet in the Air" on Internet-history mailing list:
https://elists.isoc.org/pipermail/internet-history/2025-October/011163.html
Hit "Next message, by thread" a couple of times and get all the stuff.
Also, feel free to join:
https://elists.isoc.org/mailman/listinfo/internet-history
All the best,
Frank
Frantisek (Frank) Borsik
*In loving memory of Dave Täht: *1965-2025
https://libreqos.io/2025/04/01/in-loving-memory-of-dave/
https://www.linkedin.com/in/frantisekborsik
Signal, Telegram, WhatsApp: +421919416714
iMessage, mobile: +420775230885
Skype: casioa5302ca
frantisek.borsik@gmail.com
---------- Forwarded message ---------
From: Karl Auerbach via Internet-history <internet-history@elists.isoc.org>
Date: Fri, Oct 3, 2025 at 8:01 PM
Subject: [ih] Internet in the Air: Was Re: Internet at Sea
To: <internet-history@elists.isoc.org>
Thinking of Internet at Sea, there is also "Internet in the Air" (there
is also "Internet in automobiles", which has some similar issues.)
Several years back we did some work with the FAA and Boeing who were
trying to figure out how to improve air traffic control over the
mid-Pacific. At that time there was not solid voice connectivity to
aircraft way out in the middle of the Pacific. (There were some lower
frequency radios that could do the job, much of the time, but they were
not particularly favored.)
We put modified Cisco routers and other gear onto some commercial
trans-Pacific aircraft and played. Because pilots are used to
push-to-talk systems and long response times, we could cache voice
spurts and interleave those with other traffic. That gave us a lot of
flexibility about adding things like redundancy in case of RF noise.
We began our experiments with geo-synch satellites. We intended to move
to low earth orbit satellites, and then aircraft-to-aircraft relays
(with each airplane acting as an ever-moving IP router) but we ran out
of funding. (It can be expensive working with trans-oceanic capable
aircraft.)
For pilots the geo-synch links worked. (I wanted to experiment with
tokenized voice like what had been done earlier at SDC for
communications with certain kinds of manned undersea vehicles. ATC
communications are highly stylized with a small core vocabulary. This
would have allowed common words to be converted to nice short tokens.
The voice of a given speaker would not be reproduced accurately, but the
words would be synthetically generated at the receiving end and
generally were rather more clear to the listener than typical ATC voice.)
The geo-synch path worked wasn't so great for passengers. As usual a
lot of onboard caching helped.
By-the-way, one of the lessons I took from the DARPA Robotics Challenge
(I worked on that for several years) is that we networking people can
learn a lot from the undersea sound/communications people at places at
MBARI and Woods Hole. I was amazed at how they were able to pull a
usable signal from a very noisy channel even without forward error
correction.
(On the geosync system we were using access was moderated via a ground
station in Texas. One got to that moderator using Aloha style access.
The moderator came back with a time slot (usually a few hundred
milliseconds beginning at a specified time.) So, apart from the need
for well synchronized clocks on the aircraft the typical access time to
the main channel could be several seconds. Again, that was OK for the
pilots, but not for passengers.)
There are, of course, issues that are too often overlooked when using a
single bent-pipe link via a geosync satellite, such as solar blanking
(when either the satellite transits the face of the sun from the point
of the view of the sending or receiving ground station or when the
satellite's view of a ground station is blinded because or a reflection
of the sun off of the earth. At that time tracking low earth satellites
from a moving platform was not well developed - At Sun we had designed
some highly portable antenna capabilities to track low earth satellites
from Steve Robert's bicycle, but for that project we were aiming only at
about 32kbits/second, which is OK, but marginal, for non-tokenized voice.
I of course suggested a technology we created on the Interop Show net
back in 1998: "Gaganet", trans-relativistic networking:
https://www.cavebear.com/cb_catalog/techno/gaganet/
(Some people actually believe that this was real, and not a joke.)
--karl--
--
Internet-history mailing list
Internet-history@elists.isoc.org
https://elists.isoc.org/mailman/listinfo/internet-history
-
Unsubscribe:
https://app.smartsheet.com/b/form/9b6ef0621638436ab0a9b23cb0668b0b?The%20list%20to%20be%20unsubscribed%20from=Internet-history
next parent reply other threads:[~2025-10-04 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bb3b9c10-7b9e-4569-899a-289589a436b0@iwl.com>
[not found] ` <CAHQj4CdR2WD_z4tak0kaYW0V-s5oeATa3OXTFu=6_+_SFWLJyw@mail.gmail.com>
[not found] ` <b9ade4f6-c929-4110-83e7-845ae9cbf79a@iwl.com>
[not found] ` <2551d373-b594-4607-8fa2-b0423ce31cba@3kitty.org>
[not found] ` <emd96997aa-83df-439b-b479-0ea8aa5c5b89@25459e5e.com>
[not found] ` <2B3C5E38-BB28-45F5-A7F2-96BFE66A1533@pch.net>
[not found] ` <5b424221-b47b-4913-ad6a-0f58233b1d11@iwl.com>
2025-10-04 20:06 ` Frantisek Borsik [this message]
2025-10-04 20:12 ` [Starlink] " Frantisek Borsik
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='CAJUtOOjE6ChKmYkz1M_iMFwVbbgkBn8dFUz+Ag=dy2e5fqB4Mg@mail.gmail.com' \
--to=frantisek.borsik@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