From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: Mark Handley <mark@handley.org.uk>,
"starlink@lists.bufferbloat.net"
<starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink hidden buffers
Date: Wed, 24 May 2023 17:17:11 -0700 (PDT) [thread overview]
Message-ID: <7079qr6p-07ss-03q0-7so0-21527r78rrnr@ynat.uz> (raw)
In-Reply-To: <dbefb743-0a63-e17c-fe17-f93855541431@auckland.ac.nz>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On Thu, 25 May 2023, Ulrich Speidel via Starlink wrote:
> Also, I don't get the impression that path latency minimisation is top
> priority for Starlink. My impression is that as long as RTT is what you might
> see on a terrestrial connection to the other side of the globe, it's good
> enough for Starlink.
I agree, I don't think they have latency as one of their top priorities. I think
they are focusing on expanding the network and jusst increasing bandwidth.
I think having multiple satellites servicing a single cell is a much higher
priority than minimizing latency).
I also think that in-space-routing is a higher priority than minimizing latency.
But I think latency is something they care about, just not their top priority.
As long as it's "good enough" they are working on other things (and "good
enough" is not fiber-connected good, but more like slow-dsl-good)
It's important to keep the market in mind, they aren't aiming the service at
people who can get high speed DSL/Cable/Fiber, they are aiming it at the people
who can't, who get slow DSL, dialup, cell service (LTE, not 5G), wireless ISPs,
or do without.
David Lang
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-05-25 0:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 10:10 Ulrich Speidel
2023-05-13 11:20 ` Sebastian Moeller
2023-05-13 12:16 ` Ulrich Speidel
2023-05-13 23:00 ` David Lang
2023-05-13 22:57 ` David Lang
2023-05-14 6:06 ` Ulrich Speidel
2023-05-14 6:55 ` David Lang
2023-05-14 8:43 ` Ulrich Speidel
2023-05-14 9:00 ` David Lang
2023-05-15 2:41 ` Ulrich Speidel
2023-05-15 3:33 ` David Lang
2023-05-15 6:36 ` Sebastian Moeller
2023-05-15 11:07 ` David Lang
2023-05-24 12:55 ` Ulrich Speidel
2023-05-24 13:44 ` Dave Taht
2023-05-24 14:05 ` David Lang
2023-05-24 14:49 ` Michael Richardson
2023-05-24 15:09 ` Dave Collier-Brown
2023-05-24 15:31 ` Dave Taht
2023-05-24 18:30 ` Michael Richardson
2023-05-24 18:45 ` Sebastian Moeller
2023-05-24 13:59 ` David Lang
2023-05-24 22:39 ` Ulrich Speidel
2023-05-25 0:06 ` David Lang
2023-07-27 20:37 ` Ulrich Speidel
2023-05-24 15:18 ` Mark Handley
2023-05-24 21:50 ` Ulrich Speidel
2023-05-25 0:17 ` David Lang [this message]
2023-05-14 9:06 ` Sebastian Moeller
2023-05-14 9:13 ` David Lang
2023-05-14 9:57 ` Oleg Kutkov
2023-05-14 9:59 ` Oleg Kutkov
2023-05-24 15:26 ` Bjørn Ivar Teigen
2023-05-24 21:53 ` Ulrich Speidel
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=7079qr6p-07ss-03q0-7so0-21527r78rrnr@ynat.uz \
--to=david@lang.hm \
--cc=mark@handley.org.uk \
--cc=starlink@lists.bufferbloat.net \
--cc=u.speidel@auckland.ac.nz \
/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