From: Michael Richardson <mcr@sandelman.ca>
To: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] 300ms Telecommunication Latency and FTL Communication
Date: Fri, 07 Jun 2024 13:34:35 -0400 [thread overview]
Message-ID: <4897.1717781675@obiwan.sandelman.ca> (raw)
In-Reply-To: <2F6A4FBA-AFBE-43D3-9F02-4E74A1B2983A@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]
Sebastian Moeller via Starlink <starlink@lists.bufferbloat.net> wrote:
> [SM] I fully agree, that is what I meant with unintended
> collisions... and as long as we are in the regime with little talking
> over each other I expect little differences between the modalities.
Back in 2002, the FreeS/WAN project moved from STU-III phones (I had two of
them with a two-line conference phone, so we could have three locations
connected) to H323 over IPsec [dog fooding]. Of course, each meeting started with 15-30
minutes to debugging: when IPsec didn't rekey right, we'd often wind up with
unidirectional communications. (It was a very good way to debug dog food issues)
A point that ||ugh made at the time was that he didn't think that we it was
actually useful to be in radio mode: that all of the subsequent digital
systems were designed to emulate the properties of the radio, which was that
the *general* as allowed to shout lounder than everyone else until they all
shut up and listened.
The question was our conferencing systems couldn't just accept audio from
each participant, put it in a queue, and play it out. Some participants
might hear comments in different orders. I don't know if anyone has tried
this.
It seems that such a system would be useful for in a Earth/Luna conference
where speed of light delays are 1-2s. Beyond that, one gets into sending
video-grams as one sees in Expanse.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
prev parent reply other threads:[~2024-06-07 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3171.1717601612.1074.starlink@lists.bufferbloat.net>
2024-06-05 17:58 ` Colin_Higbie
2024-06-06 7:22 ` Sebastian Moeller
2024-06-06 13:43 ` Colin_Higbie
2024-06-07 14:07 ` Sebastian Moeller
2024-06-07 14:55 ` David Lang
2024-06-07 15:32 ` Sebastian Moeller
2024-06-07 16:46 ` Colin_Higbie
2024-06-07 16:56 ` David Lang
2024-06-07 17:00 ` Colin_Higbie
2024-06-07 17:34 ` Michael Richardson [this message]
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=4897.1717781675@obiwan.sandelman.ca \
--to=mcr@sandelman.ca \
--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