From: David Lang <david@lang.hm>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] FW: [Dewayne-Net] Ajit Pai caves to SpaceX but is still skeptical of Musk's latency claims
Date: Thu, 11 Jun 2020 11:56:43 -0700 (PDT) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2006111149350.16262@qynat-yncgbc> (raw)
In-Reply-To: <1591901205.85717618@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]
On Thu, 11 Jun 2020, David P. Reed wrote:
> But I doubt that is where they are going. Instead, I suspect they haven't
> thought about anything other than a packet at a time, with no thought to
> reporting congestion by drops or ECN.
>
> And it's super easy to build up seconds of lag on TCP if you don't signal
> congestion. TCP just keeps opening its window, happy as a clam.
I expect that the bottleneck is going to be in the connection to the Internet.
starlink station to starlink station is one issue
starlink station to Internet is a different issue.
given the download heavy nature of most use, the biggest bottleneck is probably
going to be at their internet connected uplink stations (which I do not expect
to be the consumer stations connected to the internet, but something different)
as for the station to station communications, as I understand it, each satellite
has 4-5 sattelite-satellite connections with one upload/download connection, so
it's going to depend how many satellite hops the packet has to take, but there's
a really good chance that there will be excess bandwidth available in the
sattelite mesh and it will not be the bottleneck.
We will see, but since the answer to satellite-satellite communication being the
bottleneck is to launch more satellites, this boils down to investment vs
service quality. Since they are making a big deal about the latency, I expect
them to work to keep it acceptable.
David Lang
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2020-06-11 18:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 16:03 David P. Reed
2020-06-11 16:14 ` Jonathan Morton
2020-06-11 18:46 ` David P. Reed
2020-06-11 18:56 ` David Lang [this message]
2020-06-11 19:16 ` David P. Reed
2020-06-11 19:28 ` David Lang
2020-06-12 15:39 ` Michael Richardson
2020-06-13 5:43 ` David Lang
2020-06-13 18:41 ` David P. Reed
2020-06-14 0:03 ` David Lang
2020-06-14 0:36 ` Michael Richardson
2020-06-14 1:17 ` David Lang
2020-06-14 15:40 ` David P. Reed
2020-06-14 15:57 ` Michael Richardson
2020-06-14 21:04 ` David P. Reed
2020-06-14 23:13 ` Michael Richardson
2020-06-12 15:30 ` Michael Richardson
2020-06-12 19:50 ` David P. Reed
2020-06-13 21:15 ` Michael Richardson
2020-06-13 23:02 ` Jonathan Morton
2020-06-14 0:06 ` David Lang
2020-06-14 11:23 ` Roland Bless
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.2006111149350.16262@qynat-yncgbc \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dpreed@deepplum.com \
/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