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>,
	"Dave Taht via Nnagain" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] FCC NOI due dec 1 on broadband speed standards
Date: Tue, 14 Nov 2023 11:33:22 -0500	[thread overview]
Message-ID: <9FEDA717-E55F-4D7B-AB22-E8DF3BA4DA88@gmx.de> (raw)
In-Reply-To: <CAA93jw7XRGKJ6uMFO6xuDhUmj8rCMHAUv4-FKjRBHiuHNNpW7g@mail.gmail.com>

Hi Dave,

On 14 November 2023 11:06:54 GMT-05:00, Dave Taht via Nnagain <nnagain@lists.bufferbloat.net> wrote:
>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.
>
>The 83% of people (experts!!!) that were wrong is ... mindboggling.


[SM] The optimist in me reads this as only 27% were really off... I also note the options had an odd scaling, neither liner, nor logarithmic, making it hard to make inferences.

>
>PS What wifi standard was at ietf? Is this still the old ciscos? The
>headline bandwidths claimed for any version of wifi drop dramatically at
>distance and with multiple users present.  So it might have taken a couple
>laptops out of the thousand there to move the stats in a perverse
>direction, now that I think about it.
>
>Thank you for doing this experiment! While there are certainly also cases
>were mass groupings of people totally saturate the underlying mac (more
>than the perceived bandwidth - I have seen congestion collapse and a sea of
>retransmits even in small wifi gatherings), the only number that seems a
>bit off  in your test from a typical residential/small office is the
>roughly 3.5x1 ratio between down and up. I am willing (for now) to put that
>down to engineers doing actual work, rather than netflix.

[SM] +1; the typical high down/up ratio for home users is partly a result of offering mostly heavily asymmetric links, users inherently learn what they can use a link for...

Regards
        Sebastian



>
>I would so love to see more measurements like this at other wifi
>concentration points, in offices and coffee shops. Packet captures too!!!!
>
>On Tue, Nov 14, 2023 at 10: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 <https://www.ietf.org/how/meetings/118/> 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
>>
>>
>>
>> From my pre-meeting Twitter poll (
>> https://twitter.com/jlivingood/status/1720060429311901873):
>>
>> [image: A screenshot of a chat Description automatically generated]
>> _______________________________________________
>> Nnagain mailing list
>> Nnagain@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/nnagain
>>
>
>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  parent reply	other threads:[~2023-11-14 16:33 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     ` Sebastian Moeller [this message]
2023-11-14 16:14   ` [NNagain] " 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=9FEDA717-E55F-4D7B-AB22-E8DF3BA4DA88@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