From: Dave Taht <dave.taht@gmail.com>
To: Satadal Sengupta <satadal.sengupta@cs.princeton.edu>
Cc: Jennifer Rexford <jrex@cs.princeton.edu>,
Joon Kim <hyojoonk@cs.princeton.edu>,
Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] [Network-quality-workshop] the princeton paper and the long tail above 90%
Date: Tue, 1 Feb 2022 10:12:56 -0800 [thread overview]
Message-ID: <CAA93jw4FOgAgeGycaSfAVJDUxJBLgNWOobS80FFfMCSdniqoyQ@mail.gmail.com> (raw)
In-Reply-To: <CAM6jzEAFe5tvXybXdiTzu4FsBq0+1bcXCtDS15vsOSDAyTURXw@mail.gmail.com>
how y'all been doing on the data from princeton?
On Sun, Oct 3, 2021 at 11:13 AM Satadal Sengupta
<satadal.sengupta@cs.princeton.edu> wrote:
>
> Hi Dave,
>
> Thanks for reaching out and for your insights! We'll do this real soon and let you know what we find.
>
> Regards,
> Sata
>
> On Sat, Oct 2, 2021 at 7:01 PM Dave Taht <dave.taht@gmail.com> wrote:
>>
>> I just wanted to reach out to the folk that presented a paper from
>> Princeton, which I cannot remember
>> the title of (?)...
>>
>> ... in the hope that they could look over their data again vs a vs
>> dropbox (instead of youtube), and to learn what they see above the
>> 90th percentile. As I'd pointed out in the discussion, the youtube
>> traffic was typically sender side limited, dropbox's is not, and they
>> both use BBR, which is the best-in-class congestion control we have
>> right now.
>>
>>
>>
>>
>> --
>> Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
>>
>> Dave Täht CEO, TekLibre, LLC
>>
>> --
>> Network-quality-workshop mailing list
>> Network-quality-workshop@iab.org
>> https://www.iab.org/mailman/listinfo/network-quality-workshop
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2022-02-01 18:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAM6jzEAFe5tvXybXdiTzu4FsBq0+1bcXCtDS15vsOSDAyTURXw@mail.gmail.com>]
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=CAA93jw4FOgAgeGycaSfAVJDUxJBLgNWOobS80FFfMCSdniqoyQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=hyojoonk@cs.princeton.edu \
--cc=jrex@cs.princeton.edu \
--cc=rpm@lists.bufferbloat.net \
--cc=satadal.sengupta@cs.princeton.edu \
/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