From: Sebastian Moeller <moeller0@gmx.de>
To: "Bjørn Ivar Teigen" <bjorn@domos.no>
Cc: Mike Puchol <mike@starlink.sx>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
Rpm <rpm@lists.bufferbloat.net>,
Brennen Smith <brennen@ookla.com>
Subject: Re: [Rpm] [Starlink] LUL 220ms flat over starlink
Date: Wed, 3 Aug 2022 11:47:59 +0200 [thread overview]
Message-ID: <F67310C6-A611-40E2-AE25-21FED52469B2@gmx.de> (raw)
In-Reply-To: <CAKf5G6KrcvP8g0PuKKr4=UVXn5a41mpP2dmk-yvMh0+VfKTsew@mail.gmail.com>
Hi All,
a decent reminder that GeoIP really is at best an imprecise heuristic, at worst actively misleading...
Always wondered whether one could not use some sort of triangulation to different endpoints of known location and use the relative RTT differences to restrict the cone of potential locations.... (that would require active probes from remote sites being reflected from the host to be localised, making it not a solution for GeoIP providers, but it might work for participating endpoints).
Regards
Sebastian
> On Aug 3, 2022, at 10:42, Bjørn Ivar Teigen via Rpm <rpm@lists.bufferbloat.net> wrote:
>
> Seems the GeoIP was wrong this time. Interesting to follow though! And also interesting that the LUL is so close to the idle latency.
>
> <image.png>
>
> - Bjørn Ivar
>
>
> On Tue, 2 Aug 2022 at 17:26, Mike Puchol via Starlink <starlink@lists.bufferbloat.net> wrote:
> The status of ISL has improved considerably over the last two months. It is now totally feasible to use in-plane (shown in my simulation, blue lines) and cross-plane (not yet shown, but in use by the constellation) to deliver traffic from Kyiv to Seattle:
>
> <Attachment.png>
>
> Best,
>
> Mike
> On Aug 2, 2022, 17:17 +0200, Brennen Smith via Starlink <starlink@lists.bufferbloat.net>, wrote:
>> Compared to GEO Sat links, this is very reasonable latency and distance.
>>
>> Either GeoIP is wrong, or they’re starting to balance within the mesh for capacity. If you look very closely at the maritime announcement - they’re right on schedule for the latter.
>>
>> On Tue, Aug 2, 2022 at 07:41 Dave Taht <dave.taht@gmail.com> wrote:
>> It is my guess over a path this (inaccurately selected? lasered?)
>> long, the new speedtest doesn't saturate the link.
>>
>> https://twitter.com/olegkutkov/status/1554404854763819008
>>
>> --
>> FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
>> Dave Täht CEO, TekLibre, LLC
>> --
>> Brennen Smith VP Technology
>>
>> (206) 739-0807 | brennen@ookla.com
>> linkedin.com/in/brennensmith
>>
>>
>> This email, its contents and attachments contain information from Ziff Davis, Inc. and/or its affiliates which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee(s) only. If you are not an addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited. If you have received this email in error, please notify the sender by reply email and delete the original message and any copies.
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
>
>
> --
> Bjørn Ivar Teigen
> Head of Research
> +47 47335952 | bjorn@domos.no | www.domos.no
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm
prev parent reply other threads:[~2022-08-03 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 14:41 [Rpm] " Dave Taht
2022-08-02 15:17 ` Brennen Smith
2022-08-02 15:25 ` [Rpm] [Starlink] " Mike Puchol
2022-08-03 8:42 ` Bjørn Ivar Teigen
2022-08-03 9:47 ` Sebastian Moeller [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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F67310C6-A611-40E2-AE25-21FED52469B2@gmx.de \
--to=moeller0@gmx.de \
--cc=bjorn@domos.no \
--cc=brennen@ookla.com \
--cc=mike@starlink.sx \
--cc=rpm@lists.bufferbloat.net \
--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