From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id DDF943B29D for ; Tue, 16 Aug 2022 16:04:14 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1660680253; bh=EB+fhOYz6/hv6mnCuF/jsyk1qFRl7+h4zPmS6gQUPbU=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=G22pMp7LI6vKT64rSqeb4SbwqJ3vidgrI7L4iF127QmefV7yut0OJUQXU6zzDZhPS Iif8l89TqDfzCf0kNvsTH0l8AULDQDRKojne/bh8ZxFIuQdL0DJllaZ7nXbL3RAvgP 5CMvbb8GSuC8iQJJUi0vYt0Lk8Aub500V3Y74wLQ= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from smtpclient.apple ([77.1.208.90]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MzyuS-1nTBJT02Jq-00x31z; Tue, 16 Aug 2022 22:04:13 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) From: Sebastian Moeller In-Reply-To: Date: Tue, 16 Aug 2022 22:04:12 +0200 Cc: iPerf User Group , Make-Wifi-fast Content-Transfer-Encoding: quoted-printable Message-Id: <8495AC2A-C001-43F4-9AD9-E07A98B704C0@gmx.de> References: To: Bob McMahon X-Mailer: Apple Mail (2.3696.120.41.1.1) X-Provags-ID: V03:K1:mRg2QAzQ9RYwhHqJRbtd3X0pFyZgZG4L8E7ekbstSljZc3sqbZw JTnaN0Mu/93wCZ4Ac0Q3mbo8woLdTDX4rotHbysObWTDYWzPphqlV5rsxK6OjWKjh72N+T8 kmSaGGNcuIJH1cwnR46kGgxtdfji/Mw848FqRoEB3AGmcN6eNTQaXtPK2ugJPfkuyieTeQJ 3NdStu/OpVRI4cbAwAOxw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:RSPL2zFzBgo=:Oq/bQrDjYl+81ZRBx5FeDi ruHL3/bF1il9mJFr7T2NrDbYJqynD//KE2WMJd//aLCE63Js1o0r1low8ITREDzfzLNRt9S5K QDJ28wHD6GREGAvDar3BWL4hzkTyWOYSrUrMO0gTepnnAbWBwX7IhcEjj+bY3teiVe1G2jt1c tN/owqZpCl6WVCzMNMW/hEIxpBaelym/rq/n3JNvHuTfFyOhaZU8Z3BV1SihHHLQ3r1vRtiKb TmdAdA6HOy9NJe1pw1O094BNdptR4YvKo+aSMyqeKyLD0tT1T60S2nA27+4/T1oHL6RcZWIq/ h8qfpvm9izWpxDFIrzEKnSYApy6wY2nByHOdee140jfjp4IjG0G0eTTdjLjCU5k7sYFHY2fuM t6YWkGb7KasPvvS9O3BWK+HW+Vo5dJ6hNZJCXTh07BMW6pMxc9Av3UxG4IJTMNdSTsByDH34Q v1oBZzWXAGNZv8VYIPNhmtwgqZ9M6qc3VFubLX3VpicM+4izOtSQo3gCRwvdsPM+UX3kq0+Iu hVrK8gE+SnaJphSs4JJUp6uhd3KM8PoWfZQSexXo8qm++RluKpzzh9iUfH7QcF+xSN3J6j2wi LLputy+HgDuntrbTbshMOaXFqJZmIQuW3ckXPOhV5LXuOMGLifMKmPe26OKZvntUSWi2eEZWq 2kwt/5Ah+1c8vQdlKXnVQ7/jjJaw/QZjz1puiRgEKpvQ7whXsOMNkaWJhs5In2uxEy63c+CZz 1cReZR01m7V5ehRfQprMfVOb1dEJVws/6UBEO5ISUB16gdRsZfNeWr75cqpROgRMzowgj6kNB YUqLc3U2b9pZmsjcDKEFKhQlsrjiz/ukF+y+eAHbaf4eZ1d5rGwnD3beuxeLQXu1J+cwZh57R hT7xuTotNPMvDnaMtiHMp4tR9qCmgm/7daNHfq0jvndLmQBODyXUVvrLTet35jcLIzLFOhzk+ UjVodfHuytnywNHwDBZm4LD8skskdhaLdQWvH4Ne2Cjcl2w3bEt16aDQ6V6xjb2c0wZrX5p5d mXo5speb+6R8QRN+WICpzEFNA2FA05H8sI6AdSY59UXqW0XZ9pFrg2skkXvnQQBTLiH4vBx4/ mkjUGZEaKBF3A+CVtoZ/aJs3bYP8ZUR91sgv+qo3oze6YcseotHkxCKpg== Subject: Re: [Make-wifi-fast] comments on renaming iperf 2 to iperf next generation X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2022 20:04:15 -0000 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 = wrote: >=20 > Hi All, >=20 > 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. >=20 > 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. >=20 > 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. >=20 > 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. >=20 > Comments? > Bob=20 >=20 > 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