Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sirapop Theeranantachai <sirapop741@gmail.com>
To: Eugene Y Chang <eugene.chang@ieee.org>
Cc: David Lang <david@lang.hm>, Oleg Kutkov <contact@olegkutkov.me>,
	 Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Quick questions about Starlink user terminal
Date: Mon, 5 Jun 2023 12:03:49 -0700	[thread overview]
Message-ID: <CAPcR1Wrsn7ZUsZoHjCAxH8_ftiHZbj51-oJ1=DVqUAhQgxGdfQ@mail.gmail.com> (raw)
In-Reply-To: <D50713D3-0605-48F9-B32D-B3DB0046FC3E@ieee.org>

[-- Attachment #1: Type: text/plain, Size: 2363 bytes --]

Hi, I have a few follow-up questions

We're simulating the Starlink on a + grid topology on the same inclination
angle.

4 ISLs are static (but delay chages). Two of them connect to other sats
within the same orbital plane, and the other connect to the adjacent plane
(+1 or - 1) .

We know that if the dish is connected to one satellite at the a time, the
latency may not be as great when the orbital planes that the two nodes are
connected to are far apart. It can double the RTT if the orbital planes are
on thr opposite side to each other.


If we have two GSL channels, one of them can connect to the satellite that
moves  north-bound, and the other that moves southbound. This assumption
can provide a significant boost on latency.

Oleg mentioned that HP hardware can do that?
Questions are:
Do you think is this the reason why HP has that kind of antenna?
How did you get that information about HP just in case I need a reference.

Thank you so much!
Mark

On Thu, May 11, 2023, 9:39 PM Eugene Y Chang <eugene.chang@ieee.org> wrote:

> The comment (speculation?) about laser communications between satellites
> in different orbital planes suggest challenges in tracking. I am really
> curious about the mechanics of tracking and laser pointing.
>
> Gene
> ----------------------------------------------
> Eugene Chang
> IEEE Communications Society & Signal Processing Society,
>     Hawaii Chapter Chair
> IEEE Hawaii Section, Industry Engagement Coordinator
> IEEE Life Member Affinity Group Hawaii Chair
> IEEE Senior Life Member
> eugene.chang@ieee.org
> m 781-799-0233 (in Honolulu)
>
>
>
> On May 11, 2023, at 6:28 PM, David Lang <david@lang.hm> wrote:
>
> On Thu, 11 May 2023, Eugene Y Chang via Starlink wrote:
>
> What do we know about Starlink’s use of laser links for
> satellite-to-satellite communications? I am most curious about the
> challenges of pointing the laser at a moving target.
>
>
> We know they do it, we see starlink coverage in areas that could not be
> served without such communication. But we have no details of how they do it
> or the problems they solved in creating the system.
>
> David Lang_______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
>
>

[-- Attachment #2: Type: text/html, Size: 4777 bytes --]

      reply	other threads:[~2023-06-05 19:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 21:48 Sirapop Theeranantachai
2023-05-11 21:58 ` Ulrich Speidel
2023-05-11 23:47   ` David Lang
2023-05-11 22:05 ` Oleg Kutkov
2023-05-11 22:12   ` Sirapop Theeranantachai
2023-05-11 22:18     ` Oleg Kutkov
2023-05-11 22:22       ` Sirapop Theeranantachai
2023-05-12  0:43       ` Ulrich Speidel
2023-05-12  4:22       ` Eugene Y Chang
2023-05-12  4:28         ` David Lang
2023-05-12  4:39           ` Eugene Y Chang
2023-06-05 19:03             ` Sirapop Theeranantachai [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='CAPcR1Wrsn7ZUsZoHjCAxH8_ftiHZbj51-oJ1=DVqUAhQgxGdfQ@mail.gmail.com' \
    --to=sirapop741@gmail.com \
    --cc=contact@olegkutkov.me \
    --cc=david@lang.hm \
    --cc=eugene.chang@ieee.org \
    --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