Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] community gateways
Date: Thu, 18 Jan 2024 10:17:29 +0100	[thread overview]
Message-ID: <47b6b36e-a1cc-4c8a-ae46-5009b2e0ba69@gmail.com> (raw)
In-Reply-To: <99959931-2769-4c64-a2ea-f9fe84daac20@gmail.com>


Le 17/01/2024 à 21:57, Inemesit Affia via Starlink a écrit :
> I don't think the idea of advertising with the association of fiber is 
> only about latency.
>
> Think "symmetrical link" which isn't common even for Enterprise satcom.
IT is true.  That symmetrical aspect - upload speed similar to download 
bandwidth, compared to a higher ratio ul/dl - is a great benefit in 
fiber and ADSL for home users.  Maybe the latency ratio could also be 
considered.
>
>
> Also the SLA. Wonder if we can test this link somehow. How performant 
> is it vs the Ku Band service? Anyone has a connection to the customer?

I suppose it is not yet possible to compare the SLA of starlink 
Community gateways, since the starlink Community gateways seem not to be 
deployed already.  But I dont really know.

Alex

PS:

I am not sure what you mean by the SLA aspect (service-level 
agreement).  Maybe you mean a form of higher reliability and stability 
of the user link.

Ku band (12GHz-18GHz) is what typical starlink uses to end users.

Starlink Community gateways might also use Ku band, I think. However, 
the photos show these spheres of 'teleports' which probably use 
something higher than Ku.  I dont know what freqs these teleports use; 
and dont know either whether the Community gateways will use that Ku, or 
use the D-band (120-170GHz) recently reserved by 'ESSAFI II for starlink 
at ITU.

Then there is this Starlink Direct which promisses data (maybe higher 
bandwidths?) to unmodified smartphone users in year 2025, which might 
also be used for communities, albeit much smaller ('tethering' WiFi 
technology).  That is at 2.6 or 3.6 GHz (unmodified smartphones).

JIOSpace fiber seems to be at MEO altitudes and also for unmodified 
smartphones,, hence around 2.6 or 3.6GHz.

Do you think the 'SLA' of smartphones is high?


>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink

  reply	other threads:[~2024-01-18  9:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 10:39 Dave Taht
2024-01-17 14:03 ` Alexandre Petrescu
2024-01-17 15:13   ` Inemesit Affia
2024-01-17 16:48     ` Alexandre Petrescu
2024-01-17 16:53       ` Marc Blanchet
2024-01-17 20:51         ` Alexandre Petrescu
2024-01-17 20:57           ` Inemesit Affia
2024-01-18  9:17             ` Alexandre Petrescu [this message]
2024-01-18 12:44               ` Inemesit Affia
2024-01-18 20:06                 ` 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=47b6b36e-a1cc-4c8a-ae46-5009b2e0ba69@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