From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: Dave Taht <dave.taht@gmail.com>,
Michael Richardson <mcr+ietf@sandelman.ca>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink Internet Speeds Could Skyrocket to 2 Gigabits Per Second, SpaceX President Says
Date: Sun, 24 Nov 2024 16:39:28 +1300 [thread overview]
Message-ID: <78ba68e7-11a7-4355-9264-b7ff16afab84@auckland.ac.nz> (raw)
In-Reply-To: <CAA93jw6_9becPoREOKmOXFLRWvQpoJTaVaSoVdeKzM_hZ_bzMQ@mail.gmail.com>
On 24/11/2024 9:05 am, Dave Taht wrote:
>> 3. Elon will own the FCC.
> This FCC promises to open up more spectrum. Where?
I think it's not so much a matter of opening up spectrum. SpaceX's
spectrum "reserve" at the moment is Ka-band. That's hitherto been used
for gateways only, but with the lasers, that's becoming less of a
bottleneck because you can in principle uplink from and downlink to a
remote gateway or set of remote gateways (unlike with the end user - I
mean Elon can't simply provide the service Dave's paying for over, say,
New York, rather than where Dave's boat is). So that frees up a bit of
resource to deploy directly to users in tight spots. Except that Dishy
doesn't talk on Ka.
The trouble with Ka is that it's a bit more susceptible to rain fade
than Ku, and also that the amount of spectrum available there isn't
exactly an order of magnitude larger either. To the contrary - the three
Ka-bands in which SpaceX can downlink data have a combined 1.8 GHz of
spectrum - less than for Ku. The pros of Ka are that the shorter
wavelength makes for sharper beams and a nicer link budget with the same
size antennas. As long as you don't get rained on. So you better throw
in some extra antenna gain, which is what they're doing with the 1.85 m
dishes (not Dishys) at their community gateways. But that's an entirely
different business model.
And yes I'm aware that there's some labelling issues as to what counts
as Ka and what doesn't, internationally, and that the FCC's notion of Ka
starts at lower frequencies than some other peoples'.
--
****************************************************************
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/
****************************************************************
next prev parent reply other threads:[~2024-11-24 3:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 22:16 Hesham ElBakoury
2024-11-22 22:33 ` Dave Taht
2024-11-22 23:32 ` Ulrich Speidel
2024-11-23 1:13 ` Brandon Butterworth
2024-11-23 6:05 ` David Lang
2024-11-23 13:30 ` Ulrich Speidel
2024-11-23 18:29 ` Michael Richardson
2024-11-23 20:05 ` Dave Taht
2024-11-24 3:39 ` Ulrich Speidel [this message]
2024-11-25 14:51 ` Sascha Meinrath
2024-11-25 16:59 ` David Lang
2024-11-25 17:20 ` Steve Stroh
2024-11-25 17:29 ` Dave Taht
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=78ba68e7-11a7-4355-9264-b7ff16afab84@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--cc=dave.taht@gmail.com \
--cc=mcr+ietf@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