Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: Bob McMahon <bob.mcmahon@broadcom.com>
Cc: iPerf User Group <iperf-users@lists.sourceforge.net>,
	Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] comments on renaming iperf 2 to iperf next generation
Date: Tue, 16 Aug 2022 22:04:12 +0200	[thread overview]
Message-ID: <8495AC2A-C001-43F4-9AD9-E07A98B704C0@gmx.de> (raw)
In-Reply-To: <CAHb6LvpB6tUozmugf7Lx+WghkXETVwR7ht2JLQ9L=k+Hq8E_Lw@mail.gmail.com>

Ho Bob,

+1 for renaming; the iperf2 iperf3 things is really confusing for mere end users.

However "next generation/NG" is a relative moniker, in a few years NG is going to be the new normal and hence the name misleading again.

While somewhat lame, maybe "iperformance" might be better in side stepping the-bigger-is-better issue when including numbers in the name, or obviously the correct answer go directly to iperf42 ;)

Regards
	Sebastian


> On Aug 16, 2022, at 20:54, Bob McMahon via Make-wifi-fast <make-wifi-fast@lists.bufferbloat.net> wrote:
> 
> 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. 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._______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast


  reply	other threads:[~2022-08-16 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 18:54 Bob McMahon
2022-08-16 20:04 ` Sebastian Moeller [this message]
2022-08-16 20:30   ` Bob McMahon
     [not found] <mailman.590.1660681819.1281.make-wifi-fast@lists.bufferbloat.net>
2022-08-16 20:54 ` Rich Brown
2022-08-16 21:10   ` Bob McMahon

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/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8495AC2A-C001-43F4-9AD9-E07A98B704C0@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bob.mcmahon@broadcom.com \
    --cc=iperf-users@lists.sourceforge.net \
    --cc=make-wifi-fast@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