Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] ESA IRIS2 draft response
Date: Fri, 20 Dec 2024 10:19:18 -0800	[thread overview]
Message-ID: <CAA93jw7_OM5RtuzZN-cD3nsNaB-zjW43T3nO=5ke5cMnMOp=HQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7L9Hdh=qJRH+tY7cGLBkGpgJkN3qrK454KWAuBBWqkhQ@mail.gmail.com>

Thank you all for your comments and suggestions!

I'm going to sleep on it til monday, and perhaps try to create a diagram or two.

On Thu, Dec 19, 2024 at 11:00 AM Dave Taht <dave.taht@gmail.com> wrote:
>
> We decided to file a request for clarification on their "bufferbloat"
> RFP, if anyone would like to contribute,
> an early draft is here. H/T to dave cb for helping drive it along.
>
> https://docs.google.com/document/d/1-9CB7r8Ks8CdYHPTKancLYWPfDPrJHMDsQ8JtXIXvEE/edit?usp=sharing
>
> It's not due til 2/25/25, but I'd like to get it out this year.  I
> don't really know if we'll actually bid or not, and I just hit peak
> pedant mode on both this and the NTIA bandwidth guidelines and need a
> break. :( In particular I'd like to find examples of satcom
> scheduling, to this day I have no idea how the request/grant (or
> other) scheduling means are used at these rtts. My assumption for
> starlink is that these assignments are coarse at the 15s level...
>
> --
> Dave Täht CSO, LibreQos



-- 
Dave Täht CSO, LibreQos

      parent reply	other threads:[~2024-12-20 18:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 19:00 Dave Taht
2024-12-19 19:51 ` Brandon Butterworth
2024-12-20 18:19 ` Dave Taht [this message]

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='CAA93jw7_OM5RtuzZN-cD3nsNaB-zjW43T3nO=5ke5cMnMOp=HQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --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