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] A quick report from the WISPA conference
Date: Fri, 17 Nov 2023 14:56:29 -0800	[thread overview]
Message-ID: <59331e1632a26aae505e8231881a80db@rjmcmahon.com> (raw)
In-Reply-To: <647406f6-9895-4b53-8cad-2e3183e8d723@3kitty.org>

The WiFi Alliance does certification for WiFi products.

https://www.wi-fi.org/

They've adopted iperf 2 for latency tests.

Bob
> On 11/17/23 11:27, Dave Taht via Nnagain wrote:
> 
>> one of the things we really wished existed was a standardized way to
>> 
>> test latency and throughput to routers. It would be super helpful if
>> 
>> there was a standard in consumer routers that allowed users to both
>> ping
>> and fetch 0kB fils from their routers, and also run download/upload
>> 
>> tests.
> 
> Back when I was involved in operating a network, we tried to track
> latency and throughput by standard ping and related tests.  We
> discovered that, in addition to the network conditions, the results
> were often dependent on the particular equipment and software involved
> at the time.   Some companies treated ping traffic (e.g., anything
> directed to the "echo" port) as low priority since it was obviously
> (to them) less important than any other traffic.   Others treated such
> traffic as high priority - it made their results in review articles
> look better.
> 
> In another case we discovered one brand of desktop computer was
> achieved much higher throughputs over the net than similar products
> from other manufacturers.  It took some serious technical
> investigation but we eventually discovered that the high throughput
> was achieved by violating the Ethernet specification.   The offending
> vendor didn't follow the rules about timing.  But their test results
> looked much better than the competition.
> 
> IMHO the root of the problem is that you can not assume much about
> what any software and hardware are doing.  There are lots of specs,
> standards, and mandates in RFCs or even governmental rules and
> regulations.  But lacking any kind of testing or certification, it's
> difficult to tell if those "standards" are actually being followed.
> If someone, technical organization or government regulator, declares
> or legislates some protocol, algorithm, or behavior to be a required
> "standard", it should be accompanied by mechanisms and processes for
> testing to verify that the standard is implemented correctly and is
> actually used, and certification so that purchasers are informed.
> 
> Jack Haverty
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain

  reply	other threads:[~2023-11-17 22:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA93jw77h=ztEOzyADriH2PnswUDQiyNvBdsuFi+K5EexpoxUQ@mail.gmail.com>
     [not found] ` <938D9D45-DADA-4291-BD8A-84E4257CEE49@apple.com>
     [not found]   ` <CAA93jw4KOkgdfT2LunCtPYPjXL+=OtTrouJgPjM7U1bHKtErnw@mail.gmail.com>
     [not found]     ` <CACTgmGpgDjWF4d_+Kga4CL4vxb-YQ91Lu1U6Zt5vca0EGSwQ2w@mail.gmail.com>
     [not found]       ` <CAA93jw4f701R+4B538jF1+qAW=cUgP35EmWy8VZG-1h=w8woOA@mail.gmail.com>
     [not found]         ` <l9egkfsn.61659de8-7256-4ec0-938c-38be1dcb1e4c@we.are.superhuman.com>
2023-11-17 19:27           ` Dave Taht
2023-11-17 20:31             ` Jack Haverty
2023-11-17 22:56               ` rjmcmahon [this message]
2023-11-19 11:04               ` le berger des photons
2023-11-19 16:57                 ` Robert McMahon
2023-11-17 21:19             ` Dick Roy
2023-11-18 16:34             ` Sina Khanifar

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=59331e1632a26aae505e8231881a80db@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