From: Dave Taht <dave.taht@gmail.com>
To: Justus <justus.fries@tum.de>
Cc: bloat <bloat@lists.bufferbloat.net>,
Rpm <rpm@lists.bufferbloat.net>, Sam Crawford <sam@samknows.com>
Subject: Re: [Rpm] [Bloat] An 8 years perspective on broadband in the usa - fcc data
Date: Mon, 20 Jun 2022 07:19:22 -0700 [thread overview]
Message-ID: <CAA93jw7qjvyxVeSpYVatNJxUf7NPpwYujyXC_=3tOEv=0GwcFA@mail.gmail.com> (raw)
In-Reply-To: <A91C20D5-28C1-488F-830F-D9A26462B07B@tum.de>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
I would characterize a goodly percentage of the 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>
wrote:
> We are using the latency under downstream load data for the paper.
>
> Regards
> Justus
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 1071 bytes --]
next parent reply other threads:[~2022-06-20 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A91C20D5-28C1-488F-830F-D9A26462B07B@tum.de>
2022-06-20 14:19 ` Dave Taht [this message]
2022-06-20 14:38 ` Fries, Justus
2022-06-19 15:32 [Rpm] " Dave Taht
2022-06-19 15:46 ` [Rpm] [Bloat] " Sebastian Moeller
2022-06-19 19:39 ` 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/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='CAA93jw7qjvyxVeSpYVatNJxUf7NPpwYujyXC_=3tOEv=0GwcFA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=justus.fries@tum.de \
--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