From: Dave Taht <dave.taht@gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: starlink@lists.bufferbloat.net, J Pan <Pan@uvic.ca>
Subject: Re: [Starlink] Measuring a Low-Earth-Orbit Satellite Network
Date: Fri, 15 Sep 2023 11:03:16 -0700 [thread overview]
Message-ID: <CAA93jw4gQQBDanR6q_GV_xeFCVYwyocrESf8jyuXoL8n_Lc0pA@mail.gmail.com> (raw)
In-Reply-To: <6244255c-f9c5-490c-b740-38353af2e60a@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]
On Fri, Sep 15, 2023 at 3:58 AM Alexandre Petrescu via Starlink <
starlink@lists.bufferbloat.net> wrote:
>
> Le 17/08/2023 à 18:42, Dave Taht via Starlink a écrit :
> > On Thu, Aug 17, 2023 at 7:47 AM Dave Taht <dave.taht@gmail.com> wrote:
> >> This paper, at first glance, looks really, really good, measuring
> >> detailed topology of the starlink network:
> >> https://arxiv.org/abs/2307.06863
> >>
> >> Thank you J Pan for passing it along!
> > More recent data here:
> >
> https://www.reddit.com/r/StarlinkEngineering/comments/15p76j4/impressive_improvement_in_three_months_no_longer/
>
> Sorry but I do not understand the graphs. The URL sounds great.
>
>
I have cc´d the author.
> For my part, I can tell that I follow one particular sat chosen
> arbitrarily (STARLINK-6064) on a public database since some weeks now
> and it keeps at around 360km altitude. That is much lower than
> 500-or-so usual. Maybe it is that lower altitude that permits a higher
> performance (lower latencies).
>
Pretty neat!
>
> (there are other sats even lower, but not sure whether they're there in
> error or on their way up).
>
this was really good:
https://radionavlab.ae.utexas.edu/wp-content/uploads/2023/01/starlink_structure.pdf
Getting more correlated results from two or more stations in the same cell
would help.
> Alex
>
> >
> >>
> >> ---------- Forwarded message ---------
> >> From: J Pan <Pan@uvic.ca>
> >> Date: Wed, Aug 16, 2023 at 11:02 PM
> >> Subject: starlink
> >> To: dave.taht@gmail.com <dave.taht@gmail.com>
> >>
> >>
> >> Hi Dave: thanks for your libreqos work. did you see
> >> https://arxiv.org/abs/2307.06863 ? cheers. -j
> >> --
> >> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA,
> Web.UVic.CA/~pan
> >>
> >>
> >> --
> >> Podcast: https://www.youtube.com/watch?v=bxmoBr4cBKg
> >> Dave Täht CSO, LibreQos
> >
> >
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
--
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos
[-- Attachment #2: Type: text/html, Size: 4547 bytes --]
next prev parent reply other threads:[~2023-09-15 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHn=e4gXDRmiEOrSSm5GQRSbFDNS7Rz9L9C2VsMhoBYHgFHhtQ@mail.gmail.com>
2023-08-17 14:47 ` Dave Taht
2023-08-17 16:42 ` Dave Taht
2023-09-15 10:58 ` Alexandre Petrescu
2023-09-15 17:44 ` David Lang
2023-09-15 18:03 ` Dave Taht [this message]
2023-09-21 12:26 ` Alexandre Petrescu
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=CAA93jw4gQQBDanR6q_GV_xeFCVYwyocrESf8jyuXoL8n_Lc0pA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=Pan@uvic.ca \
--cc=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