Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Starlink BufferBloat List <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] IETF side meeting on satellite and deep space networks (Tue Mar 18)
Date: Thu, 06 Mar 2025 18:45:25 -0500	[thread overview]
Message-ID: <12020.1741304725@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAA93jw57bwPEFLN8eMmLD0O_0WsAk=R12j8kgMLgYCsdfX_ftg@mail.gmail.com>

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


Dave Taht <dave.taht@gmail.com> wrote:
    > Without attracting the major players (starlink, nasa, oneweb, etc,
    > etc) to an effort here, I don't know what we could do
    > to move forward in these areas.

Not for a RG :-)

It could be populated entirely by graduate students doing interesting tests
in simulated environment using modified off-the-shelf (i.e. already RFC)
routing protocols.
And then writing papers, with the modifications written up as I-Ds.

I know RPL (RFC6550) quite well, and it has useful properties for space.
(Like, if a link-fails-in-the-forest, but nobody had any data to send, then
the link never failed).  I wouldn't want to use OSPF for this.

What it doesn't have is anything about motion: i.e., expected link failures.

I could see an attribute (a metric) which told of the sender's expected
motion, specifically towards or away from the receiver, and then this needs
to be correlated with occultations.   That would let the network do make-before-break.
I think that there are potentially many ways to do this; maybe it's already
been done.

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





[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 515 bytes --]

  reply	other threads:[~2025-03-06 23:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 16:31 Nishanth Sastry
2025-03-05 19:22 ` Dave Taht
2025-03-05 21:25   ` Nishanth Sastry
2025-03-06 18:48     ` Michael Richardson
2025-03-06 22:37       ` Nishanth Sastry
2025-03-06 23:10         ` Dave Taht
2025-03-06 23:45           ` Michael Richardson [this message]
2025-03-07 10:28           ` mohan
2025-03-07 15:09             ` Nishanth Sastry
2025-03-11 23:03               ` Sirapop Theeranantachai
2025-03-05 19:37 ` Ulrich Speidel
2025-03-05 20:31   ` J Pan
2025-03-07  0:03 Nitinder Mohan

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