Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Re: Starlink Digest, Vol 53, Issue 14
Date: Sun, 28 Sep 2025 18:58:23 -0400	[thread overview]
Message-ID: <13923.1759100303@obiwan.sandelman.ca> (raw)
In-Reply-To: <175909842257.1555.851927488987629950@gauss>


Sebastian Moeller via Starlink <starlink@lists.bufferbloat.net> wrote:
    > I fully agree and am quite puzzled to find zero references in the SCONE
    > draft for any experiments, let alone successful ones that demonstrate
    > the value SCONE might deliver.
    > In my world one starts with such experiments and only writes an
    > internet draft if these experiments demonstrated that an idea has legs
    > to stand on.

I regularly attend the SCONE virtual interim meetings.

I think that there is more occuring than is being published, and I think that
the candidate TRONE and TRAIN and (was there a 3rd?) ideas did have some
spike solutions created.

but, back to my original question:  is there sufficient feedback in the
*starlink* datapath from downlink'ing Satellite, through ISL, to Ground
Station about the actual experienced congestion such that either:
a) packets could be dropped before wasting satellite capacity
b) SCONE (or another mark, including L4S, whether you believe it or not),
   could be applied?

How much does that available bandwidth vary during each of the 15minute
attachments?


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide



       reply	other threads:[~2025-09-28 22:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <175909842257.1555.851927488987629950@gauss>
2025-09-28 22:58 ` Michael Richardson [this message]
     [not found] <175909781525.1555.5289631280302402077@gauss>
2025-09-28 22:58 ` Michael Richardson
     [not found] <175900400148.1561.6981645218542924150@gauss>
2025-09-28 17:32 ` David Fernández
2025-09-28 18:51   ` Sebastian Moeller
     [not found]     ` <6653.1759098417@obiwan.sandelman.ca>
2025-09-29  5:54       ` Sebastian Moeller
     [not found] <175895289005.1561.17970219906621123011@gauss>
2025-09-27 20:13 ` David P. Reed
2025-09-28 10:47   ` Sebastian Moeller
2025-09-28 10:59     ` David Lang

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=13923.1759100303@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --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