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

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

[Rich Brown]

I don't necessarily like or endorse any of these... Just some random neurons firing.

- If you're going to change the (full) name, would you also change the name on the command line?
- If you did, it might be to something like "iperfnext", which is long
- Or perhaps "iperfx" but that's hard to type that final X (my ring finger doesn't get down there as easily)
- "iperfx" is an anagram for "prefix"
- What about "iperfect"? :-)
- "xperf" is easier to type, is short. And there's a program called "Xperf" Dang.
- Maybe there's a way to work "responsiveness" and "performance" into the name "res-perf"? "resperf"

I dunno. 

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

[Bob McMahon]

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

Yeah, I got some input to just leave things as is so you're not alone in
your "random neurons firing."

My goal is to minimize confusion. Changing the binary name from iperf to
something else is something I'd like to avoid.

Changing the name and description in sourceforge may only cause more
confusion.  Hence the pseudo polling here to see what others think.

Bob


On Tue, Aug 16, 2022 at 1:54 PM Rich Brown via Make-wifi-fast <
make-wifi-fast@lists.bufferbloat.net> wrote:

>
> I don't necessarily like or endorse any of these... Just some random
> neurons firing.
>
> - If you're going to change the (full) name, would you also change the
> name on the command line?
> - If you did, it might be to something like "iperfnext", which is long
> - Or perhaps "iperfx" but that's hard to type that final X (my ring finger
> doesn't get down there as easily)
> - "iperfx" is an anagram for "prefix"
> - What about "iperfect"? :-)
> - "xperf" is easier to type, is short. And there's a program called
> "Xperf" Dang.
> - Maybe there's a way to work "responsiveness" and "performance" into the
> name "res-perf"? "resperf"
>
> I dunno.
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast

-- 
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: 2853 bytes --]

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

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

[Bob McMahon]

[-- 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 --]

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

[Sebastian Moeller]

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

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

[Bob McMahon]

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

How about something like 'Iperf Next Evolution 2022 (iperf2)
<https://sourceforge.net/projects/iperf2/>'

I'm very open to better suggestions.

Thanks,
Bob

On Tue, Aug 16, 2022 at 1:04 PM Sebastian Moeller <moeller0@gmx.de> wrote:

> 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
>
>

-- 
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: 4489 bytes --]

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