Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Eugene Y Chang <eugene.chang@ieee.org>
Cc: Oleg Kutkov <contact@olegkutkov.me>,
	 Sirapop Theeranantachai <sirapop741@gmail.com>,
	 Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Quick questions about Starlink user terminal
Date: Thu, 11 May 2023 21:28:05 -0700 (PDT)	[thread overview]
Message-ID: <qqpo5p7r-s56q-060o-5so9-rrn92s8non8n@ynat.uz> (raw)
In-Reply-To: <CBC7E0E5-ED3D-4D1E-BB74-DC2C52440F58@ieee.org>

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

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

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink

  reply	other threads:[~2023-05-12  4:28 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 [this message]
2023-05-12  4:39           ` Eugene Y Chang
2023-06-05 19:03             ` Sirapop Theeranantachai

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=qqpo5p7r-s56q-060o-5so9-rrn92s8non8n@ynat.uz \
    --to=david@lang.hm \
    --cc=contact@olegkutkov.me \
    --cc=eugene.chang@ieee.org \
    --cc=sirapop741@gmail.com \
    --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