From: Nitinder Mohan <mohan@in.tum.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: starlink@lists.bufferbloat.net, "Ricky Mok" <cskpmok@caida.org>,
"Cech, Hendrik" <hendrik.cech@tum.de>
Subject: Re: [Starlink] anyone here using mlabs data?
Date: Fri, 17 Nov 2023 20:29:20 +0000 [thread overview]
Message-ID: <etPan.6557cd2f.3b109d15.219@in.tum.de> (raw)
In-Reply-To: <CAA93jw6-f4td-STwAz2NGO4LaDGdx374zV6puUO+hqDCTNdX+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]
Hi,
We have looked into MLab data at multiple occasions, most recently for our global Starlink analysis: https://arxiv.org/abs/2310.09242.
CC’ing Hendrik who should be able to help (I am not sure about how much free time he has though).
Thanks and Regards
Nitinder Mohan
Technical University Munich (TUM)
https://www.nitindermohan.com/
From: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Reply: Dave Taht <dave.taht@gmail.com>
Date: 17. November 2023 at 18:07:53
To: Ricky Mok <cskpmok@caida.org>
Cc: starlink@lists.bufferbloat.net <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] anyone here using mlabs data?
There are a whole bunch of BGP AS numbers I would like someone with
access to take a look at. (libreqos users). Got time?
AS45230 for one of the bigger examples that gave me permission for
folk to research more publicly.
On Fri, Nov 17, 2023 at 12:56 PM Ricky Mok via Starlink
<starlink@lists.bufferbloat.net> wrote:
>
> We are still using it, but only those processed data in BigQuery (not
> raw files).
>
> Ricky
>
> On 11/17/23 09:24, Dave Taht via Starlink wrote:
> > https://datatracker.ietf.org/meeting/interim-2021-mnqeuws-01/materials/slides-interim-2021-mnqeuws-01-sessa-matt-mathis-preliminary-longitudinal-study-of-internet-responsiveness-00.pdf
> >
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
--
:( My old R&D campus is up for sale: https://tinyurl.com/yurtlab
Dave Täht CSO, LibreQos
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #2: Type: text/html, Size: 3640 bytes --]
prev parent reply other threads:[~2023-11-17 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 17:24 Dave Taht
2023-11-17 17:56 ` Ricky Mok
2023-11-17 18:07 ` Dave Taht
2023-11-17 20:29 ` Nitinder Mohan [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/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=etPan.6557cd2f.3b109d15.219@in.tum.de \
--to=mohan@in.tum.de \
--cc=cskpmok@caida.org \
--cc=dave.taht@gmail.com \
--cc=hendrik.cech@tum.de \
--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