Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Dick Roy" <dickroy@alum.mit.edu>
To: "'David Lang'" <david@lang.hm>
Cc: "'Daniel AJ Sokolov'" <daniel@falco.ca>,
	<starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink Roaming
Date: Tue, 22 Feb 2022 15:14:09 -0800	[thread overview]
Message-ID: <45F9E26E99754134B3A17B804BEF319B@SRA6> (raw)
In-Reply-To: <s2n3o351-1356-5o3-1022-9o43o9sr76r2@ynat.uz>

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

 

 

-----Original Message-----
From: David Lang [mailto:david@lang.hm] 
Sent: Tuesday, February 22, 2022 12:55 AM
To: Dick Roy
Cc: 'David Lang'; 'Daniel AJ Sokolov'; starlink@lists.bufferbloat.net
Subject: RE: [Starlink] Starlink Roaming

 

On Mon, 21 Feb 2022, Dick Roy wrote:

 

> My thinking is that the laser links will make it possible to route the

> traffic

>> from wherever I am to the appropriate ground station that I'm registered

> with as opposed to the current bent-pipe approach where, if I move to far
from 

> my registered location, I need to talk to a different ground station.

> 

> 

> 

> [RR] It is important to remember there is no need to go through a
particular

> ground station.  What is necessary is to authenticate the dishy to the

> network. Authentication servers will probably be distributed so that it
can

> happen quickly and the resulting flows and paths can be configured

> independently.

 

long term you are correct, short term I expect that dishes are assigned a 

specific ground station. It's a choice that would get them up and running 

faster, and with a fixed bent-pipe arrangement, doesn't really hurt that
much 

(again, short term)

[RR] Agreed! Many of these early decisions on system architecture will
likely change going forward with no problems.

 

RR 

 

David Lang


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

      reply	other threads:[~2022-02-22 23:14 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 19:53 Jonathan Bennett
2022-02-14 20:29 ` David Lang
2022-02-14 21:43   ` Mike Puchol
2022-02-14 21:53     ` Jonathan Bennett
2022-02-14 21:59       ` Mike Puchol
2022-02-21  7:22   ` Larry Press
2022-02-21  7:29     ` David Lang
2022-02-21 20:31       ` Dick Roy
2022-02-21 20:43         ` Mike Puchol
2022-02-21 20:52           ` David Lang
2022-02-21 21:17             ` Dick Roy
2022-02-21 21:32               ` David Lang
2022-02-21 21:58                 ` Nathan Owens
2022-02-21 22:26                   ` Dick Roy
2022-02-21 23:08                   ` Steve Golson
2022-02-21 23:15                     ` Nathan Owens
2022-02-22  1:19                       ` Dick Roy
2022-02-21 22:02             ` Daniel AJ Sokolov
2022-02-22  2:17               ` David Lang
2022-02-22  5:34                 ` Mike Puchol
2022-02-22  7:20                   ` Dick Roy
2022-02-22  7:42                     ` Mike Puchol
2022-02-22  7:51                       ` Dick Roy
2022-02-22  9:03                       ` Sebastian Moeller
2022-02-22  9:40                         ` Mike Puchol
2022-02-22  9:46                           ` Sebastian Moeller
2022-02-22 10:01                             ` Mike Puchol
2022-02-22 10:37                               ` Vint Cerf
2022-02-22 11:14                                 ` Mike Puchol
2022-02-22  7:58                     ` Ulrich Speidel
2022-02-22  8:51                   ` David Lang
2022-02-22  7:47                 ` Dick Roy
2022-02-22  8:55                   ` David Lang
2022-02-22 23:14                     ` Dick Roy [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=45F9E26E99754134B3A17B804BEF319B@SRA6 \
    --to=dickroy@alum.mit.edu \
    --cc=daniel@falco.ca \
    --cc=david@lang.hm \
    --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