Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: "Livingood, Jason" <jason_livingood@comcast.com>
To: "Dave Taht" <dave.taht@gmail.com>,
	"Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] [EXTERNAL] Re: FCC NOI due dec 1 on broadband speed standards
Date: Tue, 14 Nov 2023 16:26:23 +0000	[thread overview]
Message-ID: <F5DE0970-DDBB-4472-83FD-19D321F82640@comcast.com> (raw)
In-Reply-To: <CAA93jw7XRGKJ6uMFO6xuDhUmj8rCMHAUv4-FKjRBHiuHNNpW7g@mail.gmail.com>

> As I noted also on the twitter thread for this, were I there, and dishonest, (particularly were gobs of money on the table) I could easily have permuted the bandwidth on both tests hugely upwards from a single laptop by running continuous speedtests. But speedtests are not what we do day in or out, and reflect normal usage not at all.

Exactly so. And certainly many speed tests were run I am sure. But in terms of everyday usage, I find it very interesting that this number of people used that amount of capacity. I have no doubt people were using P2P and doing large downloads, watching streaming video, and of course many peope on video conferences since everyone on site tended to also be running Meetecho from WG sessions. 

> PS What wifi standard was at ietf? Is this still the old ciscos? 

Cisco APs. Both 5 GHz and 2.4 GHz and this meeting they started the shift to WPA3. 

My broader objective is - like you - to help the world shift its mindset from 'bandwidth is the only solution' to 'bandwidth is important, but so is working latency'. Along these lines I'd like to see folks start to recognize that the single biggest way to improve end user QoE is probably less about bandwidth and more about working latency. 

Jason 


  parent reply	other threads:[~2023-11-14 16:26 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-11 16:32 [NNagain] " Dave Taht
2023-11-11 18:24 ` rjmcmahon
2023-11-14 15:46 ` Livingood, Jason
2023-11-14 16:06   ` Dave Taht
2023-11-14 16:14     ` Frantisek Borsik
2023-11-14 16:15     ` Dave Taht
2023-11-14 16:26     ` Livingood, Jason [this message]
2023-11-14 16:33     ` Sebastian Moeller
2023-11-14 16:14   ` Sebastian Moeller
2023-11-14 16:37     ` Livingood, Jason
2023-11-14 17:00       ` Sebastian Moeller
2023-11-14 17:25   ` Vint Cerf
2023-11-14 17:43     ` Dave Taht
2023-11-14 18:10       ` rjmcmahon
2023-11-14 18:02     ` Jack Haverty
2023-11-14 18:10       ` Sebastian Moeller
2023-11-14 19:27         ` Jack Haverty
2023-11-14 19:40           ` rjmcmahon
2023-11-14 21:01             ` Dave Taht
2023-11-14 21:45               ` rjmcmahon
2023-11-16  3:41                 ` [NNagain] Metrics for Network Managers (was FCC NOI due dec 1 on broadband speed standards) Jack Haverty
2023-11-16  6:57                   ` rjmcmahon
2023-11-14 19:53           ` [NNagain] FCC NOI due dec 1 on broadband speed standards Sebastian Moeller
2023-11-14 20:01             ` David Lang
2023-11-14 20:37               ` Dick Roy
     [not found]                 ` <CA+aeVP8dT-ynmHxNCmZq1OWdw3VBMMJTH0zsL6dGASvfKVpDMQ@mail.gmail.com>
     [not found]                   ` <CA+aeVP9XyNd1rL_7S7U4OdvOwtVR8Sae8QvtiQLX0HMyzE57Xw@mail.gmail.com>
2023-11-14 20:55                     ` [NNagain] Virtual mtgs and conferences vs. in-person ones (was) " David Bray, PhD
2023-11-15  0:58                       ` Jack Haverty
2023-11-14 20:52             ` [NNagain] " Livingood, Jason
2023-11-16  0:27               ` Jack Haverty
2023-11-16  2:31                 ` Robert McMahon
2023-11-14 18:16       ` rjmcmahon
2023-11-14 18:30         ` rjmcmahon
2023-11-14 17:58   ` Jeremy Austin
2023-11-14 18:08     ` Sebastian Moeller
2023-11-14 18:34     ` [NNagain] [EXTERNAL] " Livingood, Jason

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=F5DE0970-DDBB-4472-83FD-19D321F82640@comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=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