Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: rjmcmahon <rjmcmahon@rjmcmahon.com>
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 10:16:46 -0800	[thread overview]
Message-ID: <db5abc0ae3741ada059c80008f15a085@rjmcmahon.com> (raw)
In-Reply-To: <b77671a9-c9af-4395-944f-174057d376c3@3kitty.org>

It's frustrating to me that even experts here don't measure latency as a 
first priority. The tooling has been available for years to do this. And 
it's only getting better and more feature rich, e.g. bounce-back.

--bounceback[=n]
run a TCP bounceback or rps test with optional number writes in a burst 
per value of n. The default is ten writes every period and the default 
period is one second (Note: set size with --bounceback-request). See 
NOTES on clock unsynchronized detections.
--bounceback-hold n
request the server to insert a delay of n milliseconds between its read 
and write (default is no delay)
--bounceback-no-quickack
request the server not set the TCP_QUICKACK socket option (disabling TCP 
ACK delays) during a bounceback test (see NOTES)
--bounceback-period[=n]
request the client schedule its send(s) every n seconds (default is one 
second, use zero value for immediate or continuous back to back)
--bounceback-request n
set the bounceback request size in units bytes. Default value is 100 
bytes.
--bounceback-reply n
set the bounceback reply size in units bytes. This supports asymmetric 
message sizes between the request and the reply. Default value is zero, 
which uses the value of --bounceback-request.
--bounceback-txdelay n
request the client to delay n seconds between the start of the working 
load and the bounceback traffic (default is no delay)

https://iperf2.sourceforge.io/iperf-manpage.html

Bob
> If video conferencing worked well enough, they would not have to all
> get together in one place and would instead hold IETF meetings online
> ...?
> 
> Did anyone measure latency?   Does anyone measure throughput of
> "useful" traffic - e.g., excluding video/audio data that didn't arrive
> in time to be actually used on the screen or speaker?
> 
> Jack Haverty
> 
> On 11/14/23 09:25, Vint Cerf via Nnagain wrote:
> 
>> if they had not been all together they would have been consuming
>> tons of video capacity doing video conference calls....
>> 
>> :-))
>> v
>> 
>> 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 [1] 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):
>>> 
>>> _______________________________________________
>>> Nnagain mailing list
>>> Nnagain@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/nnagain
>> 
>> --
>> 
>> Please send any postal/overnight deliveries to:
>> 
>> Vint Cerf
>> Google, LLC
>> 1900 Reston Metro Plaza, 16th Floor
>> Reston, VA 20190
>> +1 (571) 213 1346
>> 
>> until further notice
>> 
>> _______________________________________________
>> Nnagain mailing list
>> Nnagain@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/nnagain
> 
> 
> 
> Links:
> ------
> [1] https://www.ietf.org/how/meetings/118/
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain

  parent reply	other threads:[~2023-11-14 18:16 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 [this message]
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=db5abc0ae3741ada059c80008f15a085@rjmcmahon.com \
    --to=rjmcmahon@rjmcmahon.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