From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: Michael Richardson <mcr@sandelman.ca>, starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Starlink and Iran
Date: Fri, 16 Jan 2026 17:07:53 -0700 (MST) [thread overview]
Message-ID: <915noro0-sso2-6p29-oon5-3ss407p3957q@ynat.uz> (raw)
In-Reply-To: <1412cd78-ec8e-487f-8086-6ea51b4301a5@auckland.ac.nz>
Ulrich Speidel wrote:
> On 17/01/2026 8:03 am, Michael Richardson wrote:
>> Ulrich Speidel via Starlink <starlink@lists.bufferbloat.net> wrote:
>> here. Why? Because there is a limit on the amount of power per square metre
>> and MHz of bandwidth (EPFD) that systems such as Starlink may project onto
>> the surface of the Earth. It's an ITU-imposed limit, so the FCC can't really
>> do much about it. SpaceX are on public record for not being happy with it and
>> with their v2's they're riding right up against that limit.
>> 1. Who checks/enforces this ITU limit?
> The licensing authorities in the respective countries (i.e., the FCC in the
> US - and they're held to account by their competitors, of which SpaceX has a
> few in the US). At an international level, if one country were to ignore
> this, so would everyone else, which would make space-to-ground comms in these
> bands pretty unworkable pretty quickly as there'd be a lot of "my output
> power is bigger than yours" happening. One of the main reasons for having
> this limit is to ensure GEO sats can get their signals through. Whether the
> current level that the limit is set at and the way it's computed is
> appropriate is another question, and SpaceX have certainly tried to litigate
> that before the FCC.
have you looked at what the latest changes allow?
>> 2. Could the physically satellites go higher over some territory? How much
>> higher?
>> I assume it's software controlled.
> A satellite has three types of energy that determine its orbital motion:
> Potential energy from orbital height, kinetic energy from moving, and energy
> stored in its thruster fuel.
I think he's talking about the radio energy at the receiver, not satellite
energy.
David Lang
next prev parent reply other threads:[~2026-01-17 0:08 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <176851123059.1249.8585659892308012167@gauss>
2026-01-15 21:49 ` [Starlink] Re: Starlink and Iran Colin_Higbie
2026-01-15 23:15 ` Frantisek Borsik
2026-01-16 0:13 ` Ulrich Speidel
2026-01-16 1:29 ` David Lang
2026-01-16 22:55 ` Frantisek Borsik
2026-01-16 23:06 ` J Pan
[not found] ` <13187.1768590201@obiwan.sandelman.ca>
2026-01-16 23:30 ` Ulrich Speidel
2026-01-17 0:07 ` David Lang [this message]
2026-01-17 21:56 ` Ulrich Speidel
2026-01-19 20:39 ` David Lang
2026-01-28 3:09 ` Ulrich Speidel
2026-01-28 3:30 ` David Lang
2026-01-28 4:02 ` Mike Puchol
2026-01-28 9:05 ` Ulrich Speidel
2026-01-28 9:53 ` David Lang
2026-01-28 20:43 ` Ulrich Speidel
2026-01-28 20:55 ` David Lang
2026-01-17 18:32 ` Michael Richardson
2026-01-17 18:38 ` Inemesit Affia
2026-01-17 19:25 ` Michael Richardson
2026-01-17 22:12 ` Ulrich Speidel
[not found] <176849731431.1249.14387618908540773471@gauss>
2026-01-15 17:42 ` Colin_Higbie
2026-01-15 18:56 ` Jim Forster
2026-01-15 20:15 ` Ulrich Speidel
2026-01-15 20:27 ` Ulrich Speidel
2026-01-15 20:30 ` Hayden Simon
2026-01-15 21:06 ` Ulrich Speidel
2026-01-15 21:09 ` Hayden Simon
2026-01-15 21:20 ` Ulrich Speidel
2026-01-15 21:23 ` Hayden Simon
2026-01-15 14:50 David Fernández
2026-01-15 16:11 ` Oleg Kutkov
2026-01-15 17:13 ` J Pan
-- strict thread matches above, loose matches on Subject: below --
2026-01-15 9:51 [Starlink] " Ulrich Speidel
2026-01-15 10:06 ` [Starlink] " Inemesit Affia
2026-01-15 10:30 ` Ulrich Speidel
2026-01-15 10:44 ` Inemesit Affia
2026-01-15 11:16 ` Ulrich Speidel
2026-01-15 10:32 ` Inemesit Affia
2026-01-15 10:51 ` Ulrich Speidel
2026-01-15 11:17 ` David Lang
2026-01-15 11:59 ` Sauli Kiviranta
2026-01-15 14:08 ` David Lang
2026-01-15 15:29 ` Sauli Kiviranta
[not found] ` <3af2ac06-e098-4c79-869d-9c389959ca07@gmail.com>
[not found] ` <q9304244-661o-3qsr-o6rp-9q1nqq09r419@ynat.uz>
[not found] ` <4ba64a41-bbbf-4fb5-adb0-c77c15e4ca0f@gmail.com>
2026-01-15 16:20 ` Inemesit Affia
2026-01-15 20:12 ` Ulrich Speidel
2026-01-15 17:10 ` J Pan
2026-01-15 20:07 ` Ulrich Speidel
2026-01-15 21:47 ` Oleg Kutkov
2026-01-16 4:18 ` Ulrich Speidel
2026-01-16 8:12 ` Frantisek Borsik
2026-01-16 8:24 ` Inemesit Affia
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=915noro0-sso2-6p29-oon5-3ss407p3957q@ynat.uz \
--to=david@lang.hm \
--cc=mcr@sandelman.ca \
--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