Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] FCC NOI due dec 1 on broadband speed standards
Date: Tue, 14 Nov 2023 13:08:56 -0500	[thread overview]
Message-ID: <19251772-BCFE-40D8-9CB6-E91A1B3FA1C8@gmx.de> (raw)
In-Reply-To: <CACw=56KRvQK4t6dKUKYKH-+FgYErdB4YcMWAN=e34Fi2dvtVfw@mail.gmail.com>

Hi Jeremy,


> On Nov 14, 2023, at 12:58, Jeremy Austin via Nnagain <nnagain@lists.bufferbloat.net> wrote:
> 
> 
> 
> On Tue, Nov 14, 2023 at 6:46 AM Livingood, Jason via Nnagain <nnagain@lists.bufferbloat.net> wrote:
> On the subject of how much bandwidth does one household need, here's a fun stat for you.
> 
>  
> 
> At the IETF’s 118th meeting last week (Nov 4 – 10, 2023), there were over 1,000 engineers in attendance. At peak there were 870 devices connected to the WiFi network. Peak bandwidth usage:
> 
> 	• Downstream peak ~750 Mbps
> 	• Upstream ~250 Mbps
> 
> How was this calculated? That's an unusually high ratio of up to down, so my suspicion is that they aren't time correlated; they're also not /normal/ or /evening/ peaks, I'm expecting.

	[SM] Given that this is from a conference network, I think it is expected that the pattern does not match typical end-user traffic, no?


> 
> There's a big difference between individual peaks of upload and aggregate peaks of upload; most people aren't streaming high symmetric bandwidth simultaneously.

	[SM] Which is good, at current rates of over-subscription (or under-provisioning for the glass half empty folks) such a shift in usage behavior likely would not result in happiness all around?


> Consequently a peak busy hour online load, I'm finding, is still much more like 8:1 over all users (idle and active), in Preseem's data set.

	[SM] But this is end users that have been trained over decades to operate on heavily asymmetric links and that adjusted their usage patterns to match the "possible" while we might expect the network experts at IETF to have different expectations? (Then again these folks likely also are users of normal home internet links).


> 
> In addition to speed tests being, like democracy, the worst form of government except for all the others that have been tried, it would be instructive both for end users and ISPs to choose, agree on and understand specific percentiles of expected performance at idle and at peak busy hour.

	[SM] That will not be easy to achieve.


> Has anyone solved the math problem of distinguishing (from outside) a constraint in supply from a reduction in demand?

	[SM] Keep in mind that the former can cause the latter, if connectivity/responsiveness is too bad, people might shift to do other things there y reducing the measurable load, but not the conceptual demand (as they might prefer a workable internet access).

Regards
	Sebastian


> 
> Jeremy
> 
> 
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain


  reply	other threads:[~2023-11-14 18:09 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-11 16:32 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     ` [NNagain] [EXTERNAL] " Livingood, Jason
2023-11-14 16:33     ` [NNagain] " 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 [this message]
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=19251772-BCFE-40D8-9CB6-E91A1B3FA1C8@gmx.de \
    --to=moeller0@gmx.de \
    --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