Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] fcc NOI response due Dec 1
Date: Thu, 7 Dec 2023 12:49:13 +0100	[thread overview]
Message-ID: <ac21eba0-d61e-4baf-8518-0ad79eb1fcee@gmail.com> (raw)
In-Reply-To: <CAA93jw7nqPYyQ=qJbc_RoVJHRt-df5FwQ3_C08u0222ROfJXaQ@mail.gmail.com>

Thank you for having prepared this response.

It is a US-centric context, but it might apply everywhere else where 
fiber and satcom access are considered in competition.  Besides, the 
latency reduction priming over bandwidth increase, might be discussed in 
a 6G context as well, be that with NTN or without.

Now that the we are past the deadline, I would like to mention two other 
aspects:

- all access kinds in recent years have witnessed combined improvement 
of bandwidhts and latencies.  Within a same access kind (e.g. within 
WiFi, within Ethernet, within cellular) each increase of bandwidth was 
accompanied by a decrease of latency.  As such, it might look surprising 
to argue in favor of latency decrease at the expense of a constant 
bandwidth.  It might not happen, because traditionnaly they are combined.

- a strong argument could be made in favor of satcom over fiber in 
remote areas: satcom avoids the tangled fibers and satcom might pollute 
less than fiber; but at two conditions: satcom should have a sat exit 
strategy (more than just burning upon re-entry, maybe more recover and 
reuse, less visual pollution with maybe more paintings) and (2) satcom 
should aim at a same kind of... latency (yes, that!) that fiber aims 
at.  The 10ms that starlink aims at is way too high compared to what 
fiber access latency aims at.  IT is possible to aim at lower.

Alex

Le 27/11/2023 à 16:53, Dave Taht via Starlink a écrit :
> We started work on a response to the FCC NOI requesting feedback as to
> future broadband bandwidth requirements for the USA early this
> morning.
>
> I am unfamiliar with the processes by which Starlink was disqualified
> from the RDOF?, and a little out of date as to current performance. It
> is very clear they are aiming for 100/20 speedtest performance and
> frequently achieving it.
>
> A drafty draft is here, and some of the language is being toned down
> by popular request. (the pre-readers were lucky! I cut the cuss-words
> out) There is only one joke in the whole thing. I'm slipping!.
>
> https://docs.google.com/document/d/19ADByjakzQXCj9Re_pUvrb5Qe5OK-QmhlYRLMBY4vH4/edit?usp=sharing
>
> I have some starlink info contained in appendix B so far, but I would
> prefer not to cite my own long term plot as I did, and  also cite
> others that have a good latency measurement, I like the 15s irtt plots
> I have seen gone by. If you have research about starlink you would
> like me to cite in this context, please comment on the link above!
>
> The NOI is the first link, and it helpe me, actually, to start with
> the FCC commissioners' comments at the end, rather than read through
> the whole thing. Not that I would not welcome more folk submitting
> themselves to that...
>
>

  parent reply	other threads:[~2023-12-07 11:49 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
2023-12-07 11:49 ` Alexandre Petrescu [this message]
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=ac21eba0-d61e-4baf-8518-0ad79eb1fcee@gmail.com \
    --to=alexandre.petrescu@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