From: Sam Crawford <sam@samknows.com>
To: Matt Mathis <matt.mathis@gmail.com>
Cc: "Dave Täht" <dave.taht@gmail.com>,
"Dave Taht via Bloat" <bloat@lists.bufferbloat.net>,
Rpm <rpm@lists.bufferbloat.net>,
"Sebastian Moeller" <moeller0@gmx.de>
Subject: Re: [Bloat] [Rpm] An 8 years perspective on broadband in the usa - fcc data
Date: Sun, 19 Jun 2022 19:51:32 -0000 [thread overview]
Message-ID: <CAH5X0xmxKEv7R31LoKJHw2W=mqP+zmeZwe7hsxZzfXPvXuFJ8A@mail.gmail.com> (raw)
In-Reply-To: <CA+s1KQGG7ZB4kposGajsHcUxh38CTdNvChkG1Sx7w8XDfBJ+Og@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3351 bytes --]
Thanks for the heads up.
Downstream throughput and upstream throughput are measured in indepdent
tests, they aren't mixed as the question suggests might be the case. So,
latency under downstream load is measured independently from latency under
upstream load. The raw data for both is published for the FCC project.
I've not read the paper to understand which one they are using. But I'll
take a look tomorrow.
Thanks
Sam
On Sun, 19 Jun 2022, 20:39 Matt Mathis, <matt.mathis@gmail.com> wrote:
> Sam, see the question below about your methodology, from your FCC report.
>
> Thanks,
> --MM--
> Evil is defined by mortals who think they know "The Truth" and use force
> to apply it to others.
> -------------------------------------------
> Matt Mathis (Email is best)
> Home & mobile: 412-654-7529 please leave a message if you must call.
>
>
>
> On Sun, Jun 19, 2022 at 8:46 AM Sebastian Moeller via Rpm <
> rpm@lists.bufferbloat.net> wrote:
>
>> Hi Dave,
>>
>> > On Jun 19, 2022, at 17:32, Dave Taht via Bloat <
>> bloat@lists.bufferbloat.net> wrote:
>> >
>> > It's not clear if they are only measuring downloads in fig 4. ?
>> >
>> >
>> https://vaibhavbajpai.com/documents/papers/proceedings/fcc-networking-2022.pdf
>>
>> indeed:
>>
>> "The SamKnows probes measure a variety of broadband met- rics [22] over
>> IPv4. The tests [22] covered in this paper include: multi-threaded download
>> speed, UDP latency, UDP latency un- der load, and UDP packet loss. The
>> tests connect to the closest measurement servers (based on round-trip
>> time); measurement servers are hosted both off-net (outside of ISP
>> boundary) and on-net (within ISP boundary). The off-net measurement points
>> were hosted by Measurement Lab (M-Lab) [23] and changed to Level 3
>> Communications (CenturyLink) across ten cities in the US, while the on-net
>> measurement targets are hosted by the ISPs themselves. The FCC publishes
>> the raw data for each month [24], along with annual reports on major
>> findings [25]. For controllability reasons, the annual MBA reports only
>> cover measurements to the off-net locations, i.e., latency results might be
>> inflated due to geographical distance. Thus, we also consider the on-net
>> measurements in our analysis."
>>
>> reference 22 points to
>> https://www.fcc.gov/general/measuring-broadband-america-open-methodology
>> "Latency under load Average round trip time for a series of regularly
>> spaced UDP packets sent during downstream/upstream sustained tests"
>>
>> this seems to imply that it would be mixed upload/download saturation?
>>
>>
>> But I agree that this is unclear... maybe Sam (Crawford) knows (pun
>> intended), I do not have his email, but maybe he is on-list or someone else
>> can relay that question?
>>
>> Regards
>> Sebastian
>>
>>
>> >
>> >
>> > --
>> > FQ World Domination pending:
>> https://blog.cerowrt.org/post/state_of_fq_codel/
>> > Dave Täht CEO, TekLibre, LLC
>> > _______________________________________________
>> > Bloat mailing list
>> > Bloat@lists.bufferbloat.net
>> > https://lists.bufferbloat.net/listinfo/bloat
>>
>> _______________________________________________
>> Rpm mailing list
>> Rpm@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/rpm
>>
>
[-- Attachment #2: Type: text/html, Size: 5329 bytes --]
next prev parent reply other threads:[~2022-06-19 19:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2022-06-19 21:18 ` Sebastian Moeller
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
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='CAH5X0xmxKEv7R31LoKJHw2W=mqP+zmeZwe7hsxZzfXPvXuFJ8A@mail.gmail.com' \
--to=sam@samknows.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=matt.mathis@gmail.com \
--cc=moeller0@gmx.de \
--cc=rpm@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