From: "Dick Roy" <dickroy@alum.mit.edu>
To: "'Ulrich Speidel'" <u.speidel@auckland.ac.nz>,
"'David Lang'" <david@lang.hm>
Cc: <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink Digest, Vol 12, Issue 6
Date: Sat, 5 Mar 2022 10:26:50 -0800 [thread overview]
Message-ID: <A1F910FE79BB42EF902E692B207AFEED@SRA6> (raw)
In-Reply-To: <c5a14d49-d20a-6821-e745-ca9f69b4b696@auckland.ac.nz>
[-- Attachment #1: Type: text/plain, Size: 2756 bytes --]
_____
From: Ulrich Speidel [mailto:u.speidel@auckland.ac.nz]
Sent: Saturday, March 5, 2022 1:43 AM
To: dickroy@alum.mit.edu; 'David Lang'
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink Digest, Vol 12, Issue 6
On 5/03/2022 7:38 pm, Dick Roy wrote:
-----Original Message-----
From: Starlink [mailto:starlink-bounces@lists.bufferbloat.net] On Behalf Of
Ulrich Speidel
Sent: Friday, March 4, 2022 4:14 PM
To: David Lang
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink Digest, Vol 12, Issue 6
True, but Starlink is designed as a high bandwidth, low latency (OK, we
won't mention their bufferbloat issues again here), and (currently) low
user density service.
Bandwidth-wise, good old Shannon and Hartley are agnostic about whether
you divide your channel between 1 or a million users.
[RR] But they are assuming a "single" channel in the time domain. When you
can take advantage of other dimensions (eg. space) to create more channels,
(aka SDMA) the capacity goes up!
Taken as read - but it's beside the point. Shannon-Hartley allows you to do
what was proposed - turning a channel that supplies a small number of users
with a lot of capacity each into one that supplies a large number of users
with a little capacity each, and of course if you add diversity (space,
polarisation, ...) then this applies even more so. But the point is that
each communication system is designed around an expectation of how many
users will access it, and that you can't simply take an existing technology
and somehow assume that it will work with a larger number of users just
because it's theoretically possible. Basically, you can't simply throw more
dishys at the problem if you need to serve more users.
[RR] Actually, to a certain extent it depends on how the "dishys are/could
be connected" and how the satellites overhead are "configured", but that's a
story for another day and related to the point about the Maverick show ))).
That said, I agree that systems have to be and are designed/optimized to
handle a specified load (really a range of loads) and can not be expected to
perform as well outside that range, and I agree that anyone who thinks that
Shannon can be simply be ignored (as was tried in the past by a very famous
corporation we all know all too well) is simply delusional. As the saying
goes, "you can not make chicken salad out of chicken feathers!"
--
****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************
[-- Attachment #2: Type: text/html, Size: 11707 bytes --]
next prev parent reply other threads:[~2022-03-05 18:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1943.1646344903.1267.starlink@lists.bufferbloat.net>
2022-03-03 23:47 ` David P. Reed
2022-03-04 5:06 ` Ulrich Speidel
2022-03-04 7:00 ` Mike Puchol
2022-03-04 8:41 ` David Lang
2022-03-04 9:44 ` Ulrich Speidel
2022-03-04 17:07 ` Larry Press
2022-03-04 23:58 ` Ulrich Speidel
2022-03-04 17:08 ` Dave Täht
2022-03-04 17:10 ` Dave Taht
2022-03-04 18:14 ` David Lang
2022-03-04 18:21 ` Ben Greear
2022-03-04 18:30 ` David Lang
2022-03-05 0:14 ` Ulrich Speidel
2022-03-05 6:38 ` Dick Roy
2022-03-05 9:42 ` Ulrich Speidel
2022-03-05 10:10 ` David Lang
2022-03-05 18:26 ` Dick Roy [this message]
2022-03-05 15:25 ` Larry Press
2022-03-06 1:50 ` Ulrich Speidel
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=A1F910FE79BB42EF902E692B207AFEED@SRA6 \
--to=dickroy@alum.mit.edu \
--cc=david@lang.hm \
--cc=starlink@lists.bufferbloat.net \
--cc=u.speidel@auckland.ac.nz \
/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