From: "Fries, Justus" <justus.fries@tum.de>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
Rpm <rpm@lists.bufferbloat.net>,
"Sam Crawford" <sam@samknows.com>
Subject: Re: [Bloat] [Rpm] An 8 years perspective on broadband in the usa - fcc data
Date: Mon, 20 Jun 2022 14:38:11 +0000 [thread overview]
Message-ID: <a793341b359a4f159708b1f19c04e4a6@tum.de> (raw)
In-Reply-To: <CAA93jw7qjvyxVeSpYVatNJxUf7NPpwYujyXC_=3tOEv=0GwcFA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
No, we do not have that data aggregated.
________________________________
From: Dave Taht <dave.taht@gmail.com>
Sent: 20 June 2022 16:19:22
To: Fries, Justus
Cc: bloat; Rpm; Sam Crawford
Subject: Re: [Bloat] [Rpm] An 8 years perspective on broadband in the usa - fcc data
I would characterize a goodly percentage of the bufferbloat.net<http://bufferbloat.net> members' outputs as a war between creators and consumers, as a fight to keep networks usable during uploads. Do you have the upload latencies over time somewhere?
On Mon, Jun 20, 2022, 5:37 AM Justus via Bloat <bloat@lists.bufferbloat.net<mailto:bloat@lists.bufferbloat.net>> wrote:
We are using the latency under downstream load data for the paper.
Regards
Justus
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net<mailto:Bloat@lists.bufferbloat.net>
https://lists.bufferbloat.net/listinfo/bloat
[-- Attachment #2: Type: text/html, Size: 2629 bytes --]
next prev parent reply other threads:[~2022-06-20 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 12:37 Justus
2022-06-20 14:19 ` Dave Taht
2022-06-20 14:38 ` Fries, Justus [this message]
2022-06-20 21:49 ` Dave Collier-Brown
-- strict thread matches above, loose matches on Subject: below --
2022-06-19 15:32 [Bloat] " Dave Taht
2022-06-19 15:46 ` Sebastian Moeller
2022-06-19 19:39 ` [Bloat] [Rpm] " Matt Mathis
2022-06-19 19:51 ` Sam Crawford
2022-06-19 21:18 ` Sebastian Moeller
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a793341b359a4f159708b1f19c04e4a6@tum.de \
--to=justus.fries@tum.de \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=rpm@lists.bufferbloat.net \
--cc=sam@samknows.com \
/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