Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Livingood, Jason" <jason_livingood@comcast.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] fcc NOI response due Dec 1
Date: Tue, 28 Nov 2023 17:58:00 -0500	[thread overview]
Message-ID: <CAA93jw5uLGByjObGtKqzsDOx6eQhmvh8Cy8rdm6j66k+AkKHhg@mail.gmail.com> (raw)
In-Reply-To: <508649BC-C509-4748-8624-BF496857E2F3@comcast.com>

Thank you. I think they have a pretty substantial track record now!

Vs a vs the seeming silence from many other RDOF "winners"...

On Tue, Nov 28, 2023 at 10:42 AM Livingood, Jason
<jason_livingood@comcast.com> wrote:
>
> > I am unfamiliar with the processes by which Starlink was disqualified
> from the RDOF?
>
> RDOF Phase 1 was in 2020 and IIRC Starlink had only launched initial service in 2019 - so not much track record and probably at that time they could not have provided very dense coverage in unserved areas given the # of satellites then in orbit.
>
> JL
>
>


-- 
:( My old R&D campus is up for sale: https://tinyurl.com/yurtlab
Dave Täht CSO, LibreQos

  reply	other threads:[~2023-11-28 22:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 15:53 Dave Taht
2023-11-27 16:06 ` Frantisek Borsik
2023-11-27 18:31 ` J Pan
2023-11-28 15:42 ` Livingood, Jason
2023-11-28 22:58   ` Dave Taht [this message]
2023-12-07 11:49 ` Alexandre Petrescu
2023-12-07 12:25   ` Sebastian Moeller

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=CAA93jw5uLGByjObGtKqzsDOx6eQhmvh8Cy8rdm6j66k+AkKHhg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=jason_livingood@comcast.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