General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Collier-Brown <dave.collier-Brown@indexexchange.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Rpm] An 8 years perspective on broadband in the usa - fcc data
Date: Mon, 20 Jun 2022 17:49:18 -0400	[thread overview]
Message-ID: <8c05cadb-7cbc-89c6-d6e4-4a2bc4b642ac@indexexchange.com> (raw)
In-Reply-To: <a793341b359a4f159708b1f19c04e4a6@tum.de>

[-- Attachment #1: Type: text/plain, Size: 2667 bytes --]

It may well* be more diagnostic than downstream latency, it's

* commonly the requests that you want to get through, so you ca get downstream flows, and

* enthusiastically avoided by the vendors as a metric (;-))


--dave c-b

[* polite Canadian for "very much"]




On 6/20/22 10:38, Fries, Justus via Bloat wrote:

No, we do not have that data aggregated.

________________________________
From: Dave Taht <dave.taht@gmail.com><mailto: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



_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net<mailto:Bloat@lists.bufferbloat.net>
https://lists.bufferbloat.net/listinfo/bloat


--
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
dave.collier-brown@indexexchange.com<mailto:dave.collier-brown@indexexchange.com> |              -- Mark Twain


CONFIDENTIALITY NOTICE AND DISCLAIMER : This telecommunication, including any and all attachments, contains confidential information intended only for the person(s) to whom it is addressed. Any dissemination, distribution, copying or disclosure is strictly prohibited and is not a waiver of confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and delete the message from your inbox and deleted items folders. This telecommunication does not constitute an express or implied agreement to conduct transactions by electronic means, nor does it constitute a contract offer, a contract amendment or an acceptance of a contract offer. Contract terms contained in this telecommunication are subject to legal review and the completion of formal documentation and are not binding until same is confirmed in writing and has been signed by an authorized signatory.

[-- Attachment #2: Type: text/html, Size: 5345 bytes --]

  reply	other threads:[~2022-06-20 21:49 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
2022-06-20 21:49     ` Dave Collier-Brown [this message]
  -- 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=8c05cadb-7cbc-89c6-d6e4-4a2bc4b642ac@indexexchange.com \
    --to=dave.collier-brown@indexexchange.com \
    --cc=bloat@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