From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <david@lang.hm>
Received: from mail.lang.hm (unknown [66.167.227.145])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by lists.bufferbloat.net (Postfix) with ESMTPS id 7E3463CB37
 for <starlink@lists.bufferbloat.net>; Sun, 18 Jul 2021 15:17:35 -0400 (EDT)
Received: from dlang-laptop.local (unknown [10.2.0.162])
 by mail.lang.hm (Postfix) with ESMTP id 7D371FF6EF;
 Sun, 18 Jul 2021 12:17:34 -0700 (PDT)
Date: Sun, 18 Jul 2021 12:17:29 -0700 (PDT)
From: David Lang <david@lang.hm>
X-X-Sender: dlang@dlang-laptop
To: Michael Richardson <mcr@sandelman.ca>
cc: David Lang <david@lang.hm>, Nathan Owens <nathan@nathan.io>, 
 "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>, 
 "David P. Reed" <dpreed@deepplum.com>
In-Reply-To: <15095.1626468660@localhost>
Message-ID: <nycvar.QRO.7.76.6.2107181214400.1440203@qynat-yncgbc>
References: <mailman.3.1625846401.13780.starlink@lists.bufferbloat.net>
 <1625856001.74681750@apps.rackspace.com>
 <nycvar.QRO.7.76.6.2107091556260.1440203@qynat-yncgbc>
 <BD260482-EDC1-4866-9826-2B09B06D9415@commscope.com>
 <nycvar.QRO.7.76.6.2107161005210.1440203@qynat-yncgbc>
 <CALjsLJs48rK7XBwcmS2VgqmhcuxdJSOj=6Zn=RyqSoh=Ma8u2A@mail.gmail.com>
 <nycvar.QRO.7.76.6.2107161020500.1440203@qynat-yncgbc>
 <15095.1626468660@localhost>
User-Agent: Alpine 2.21.1 (DEB 209 2017-03-23)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Subject: Re: [Starlink] Starlink and bufferbloat status?
X-BeenThere: starlink@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Starlink has bufferbloat. Bad." <starlink.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/starlink>,
 <mailto:starlink-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/starlink>
List-Post: <mailto:starlink@lists.bufferbloat.net>
List-Help: <mailto:starlink-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/starlink>,
 <mailto:starlink-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Sun, 18 Jul 2021 19:17:35 -0000

On Fri, 16 Jul 2021, Michael Richardson wrote:

> David Lang <david@lang.hm> wrote:
>    > As there are more staellites, the up down time will get closer to 4-5ms
>    > rather then the ~7ms you list, and with laser relays in orbit, and terminal
>    > to terminal routing in orbit, there is the potential for the theoretical
>    > minimum to tend lower, giving some headroom for other overhead but still
>    > being in the 20ms range.
>
> I really want this to happen, but how will this get managed?
> We will don't know shit, and I'm not convinced SpaceX knows either.
>
> I'm scared that these paths will centrally managed, and not based upon
> longest prefix (IPv6) match.

unless you are going to have stations changing their IPv6 address frequently, I 
don't see how you would route based on their address. The system is extremely 
dynamic, and propgating routing tables would be a huge overhead. Remember, 
stations are not in fixed locations, they move (and if on an airliner or rocket, 
they move pretty quickly)

I expect that initially it's going to be centrally managed, but over time I 
would expect that it would become more decentralized.

David Lang