From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: Michael Richardson <mcr@sandelman.ca>,
"starlink@lists.bufferbloat.net"
<starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink power use & satellite tracking
Date: Sat, 18 Feb 2023 02:52:46 -0800 (PST) [thread overview]
Message-ID: <9o926n83-59qp-2p27-459r-q66n48s58n1n@ynat.uz> (raw)
In-Reply-To: <59d5e2b7-ee1e-9019-fb98-3a81fd8bf545@auckland.ac.nz>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On Sat, 18 Feb 2023, Ulrich Speidel via Starlink wrote:
> This requires the satellite to be in view of both terminal and gateway. There
> is, however, no reason why a user's packets could not travel via a diversity
> of satellites.
In theory you are correct, but I don't think they are doing that yet. We had a
discussion of the signaling protocol and someone posted that they had done
research and found that there was only one satellite illuminating a cell at a
time. IIRC this was when the paper came out on using starlink signals for
positioning.
As they launch more satellites and get the in-space routing up and running, I
expect that they will change that at some point.
it is an interesting question.
David Lang
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-02-18 10:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 23:08 Ulrich Speidel
2023-02-16 23:12 ` Nathan Owens
2023-02-16 23:14 ` Nathan Owens
2023-02-16 23:25 ` Jonathan Bennett
2023-02-16 23:23 ` David Lang
2023-02-16 23:36 ` David Lang
2023-02-17 1:24 ` Bruce Perens
2023-02-17 5:27 ` Ulrich Speidel
2023-02-17 5:31 ` Nathan Owens
2023-02-17 15:43 ` Michael Richardson
2023-02-17 19:13 ` Bruce Perens
2023-02-18 10:25 ` Ulrich Speidel
2023-02-18 10:52 ` David Lang [this message]
2023-02-18 12:36 ` Ulrich Speidel
2023-02-18 20:13 ` Bruce Perens
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=9o926n83-59qp-2p27-459r-q66n48s58n1n@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