[Make-wifi-fast] comments on renaming iperf 2 to iperf next generation

[Bob McMahon <bob.mcmahon@broadcom.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1807 bytes --]

Hi All,

It's unfortunate that numbers have been used in iperf naming. Many think
iperf3 is the next version of iperf (or iperf2.)  The number in the name
isn't a version number as iperf 2 and iperf 3 are different code bases,
different developers, have different goals, and don't interoperate.

I'm thinking it's a good time to break this number as part of the name and
only use -v for version numbers. In that context, I'm thinking about
renaming iperf 2 to iperf next generation. The "next generation" implies
that are lots of new features around responsiveness and latency.

This proposed name will be used in web sites, etc. The "iperf2" binary will
still just be iperf. I'm also hoping to get an IANA service as 'iperf' that
way any device that supports the iperf 2.1.8 can also advertise
responsiveness support.

Here is an example and proposed updates to sourceforge.
<https://sourceforge.net/projects/iperf2/> My hope is that this will help
clear up the confusion between the two different tools.

Comments?
Bob

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

[-- Attachment #1.2: Type: text/html, Size: 2022 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]