From: Jonathan Foulkes <jf@jonathanfoulkes.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] NTIA filing
Date: Fri, 4 Feb 2022 16:33:02 -0500 [thread overview]
Message-ID: <A2094BAB-1F73-497E-A746-73255C17DD5C@jonathanfoulkes.com> (raw)
In-Reply-To: <CAA93jw6FmpiOscJZWqYyr1CkEv+D5m+M9vuUjUzYvH73RO9svg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]
Thanks for all your efforts Dave.
BTW- Same router that produced the quoted RPM test, but now connected to a 300Mbps DOCSIS 3.0 line:
networkQuality -s -v
==== SUMMARY ====
Upload capacity: 22.249 Mbps
Download capacity: 267.126 Mbps
Upload flows: 16
Download flows: 12
Upload Responsiveness: High (1931 RPM)
Download Responsiveness: High (1618 RPM)
Base RTT: 29
Start: 2/4/22, 3:43:26 PM
End: 2/4/22, 3:43:49 PM
OS Version: Version 12.2 (Build 21D49)
Download responsiveness somewhat impacted by the fact my ISP thinks it’s fine to have an arp storm at a rate of >5K / minute.
Jonathan
> On Feb 4, 2022, at 3:56 PM, Dave Taht via Rpm <rpm@lists.bufferbloat.net> wrote:
>
> against: https://www.wiley.law/alert-NTIA-Issues-Request-for-Comment-on-Broadband-Programs-Authorized-by-the-Infrastructure-Investment-and-Jobs-Act-Worth-Over-46-Billion
>
> I leveraged a rpm test in the appendix...
>
> https://docs.google.com/document/d/1FjRo9MNnVOLh733SNPNyqaR1IFee7Q5qbMrmW1PlPr8/edit#heading=h.tlg9hjfsdlnr
>
> And I copped stuart cheshires wonderful line that a "busy network
> doesn't have to be a bad network", without attribution. Next time.
>
> What encourages me about having filed this is there were only 133
> comments so perhaps, perhaps, this will be read.
>
> I have to admit I've almost had enough with politics this year. I am
> setting aside time, on a beach, with fizzy boat drinks, to
> write some code, or fiction, or maybe, just play guitar.
>
> --
> 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
> _______________________________________________
> Rpm mailing list
> Rpm@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/rpm
[-- Attachment #2: Type: text/html, Size: 5390 bytes --]
next prev parent reply other threads:[~2022-02-04 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 20:56 Dave Taht
2022-02-04 21:33 ` Jonathan Foulkes [this message]
2022-02-05 12:58 ` Rich 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/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=A2094BAB-1F73-497E-A746-73255C17DD5C@jonathanfoulkes.com \
--to=jf@jonathanfoulkes.com \
--cc=dave.taht@gmail.com \
--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