Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: [NNagain] drafty FCC NOI response on raising the broadband standard speeds
Date: Mon, 27 Nov 2023 04:42:57 -0500	[thread overview]
Message-ID: <CAA93jw6qA=1=q-ZhrTxDT4HzWDrXJCvzV50Xc46k5ribhN5Wpw@mail.gmail.com> (raw)

This is so drafty that normally I would not be distributing it this
early, but family matters have intruded overmuch (in a good way, I
hope everyone had a great thanksgiving!!) and the Dec 1 deadline is
looming..

Co-authors (and commentors) desired! I primarily wanted to hit
latency, latency under load, bufferbloat, as usual, as well as MTBF
and MTTR as well as how complex networks are, . Just three pages, +
repeatable experiments in the appendix, so at least those are in the
public record. Cite the bitag latency report, and this cloudflare
piece, especially:

https://blog.cloudflare.com/making-home-internet-faster/

Anyway the far too drafty draft is here:

https://docs.google.com/document/d/19ADByjakzQXCj9Re_pUvrb5Qe5OK-QmhlYRLMBY4vH4/edit?usp=sharing

In terms of things not flowing for me the concept of equating the need
for more bandwidth as a solution to everything... to the "chewbacca
defense" is entertaining but possibly not useful. People are already
telling me the conclusion is too strong, and it's 4:30 AM, and I am
going back to bed.

Please comment there, and not here. Thanks for any spare brain cells
you might have! gnight.

-- 
:( My old R&D campus is up for sale: https://tinyurl.com/yurtlab
Dave Täht CSO, LibreQos

             reply	other threads:[~2023-11-27  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27  9:42 Dave Taht [this message]
2023-11-28 23:32 ` [NNagain] massively less " Dave Taht
2023-11-29  1:24   ` rjmcmahon
2023-11-29  1:33     ` Dave Taht
2023-11-29  1:47       ` rjmcmahon

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/nnagain.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw6qA=1=q-ZhrTxDT4HzWDrXJCvzV50Xc46k5ribhN5Wpw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=nnagain@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