From: Dave Taht <dave.taht@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Anything but "AQM"
Date: Fri, 20 Dec 2013 18:55:42 -0800 [thread overview]
Message-ID: <CAA93jw5G+UmOTo9sPqWZidW5HeOXNTcNvD=tj73cL0v0gvb=Hg@mail.gmail.com> (raw)
In-Reply-To: <8CF86926-CA6D-40BA-B554-61BF54C53BBB@gmail.com>
Given that StreamBoost(tm) consists of fq_codel + bigfoots packet
classification technology and service which gives prioritization to
gamer packets + some kind of automatic rate finder (better than
gargoyle's ACC I'm told). I am increasingly irked by how the roles
these technologies' interplay are being sold by the people selling it.
(the prioritization bit is thoroughly oversold, fq_codel is never
mentioned)
I AM happy it's being sold, winning things like best in show at SCTE
for example. there is clearly demand for debloating technologies!
I liked the idea of BroadBandEQ(tm) last year. Still do. Being that at
the time I was nominally working for the cable industry I wasn't in a
position to go around trademarking things. Now I'm not. I can't
remember if Bill followed up on the trademark or not.
I'm not sure if what I have in mind for this code is "competitive"
with StreamBoost or Pie, I think I was trying merely to go for a term
(like SQM) that covered more stuff than "AQM", rather than a "brand",
like BroadBandEQ.
I do like things like the Dolby brand to ensure quality for the final
product (and make a little money). CeroWrt doesn't exactly roll off
the tongue.
There are billions of devices that need fixing, and perhaps creating a
trusted brand, and trusted tests, would help? I've long thought about
setting up a 501c6 for bufferbloat.net, maybe that would work?
Aside from the name and branding discussion here:
Next years effort is going to be "make-wifi-fast", which will apply a
lot of things we've discussed here to some new hardware. It's a lot
easier to talk to people about the goal of making wifi fast, than it
is to describe bufferbloat, or ipv6.
On Fri, Dec 20, 2013 at 4:47 PM, Rich Brown <richb.hanover@gmail.com> wrote:
> Folks,
>
> I just remembered that about a year ago, Bill McGonigle offered a “marketing name” for CeroWrt - BroadbandEQ. He wrote:
>
>> From: Bill McGonigle <bill@bfccomputing.com>
>> Subject: Re: Dang, I forgot...
>> Date: December 10, 2012 11:13:55 PM EST
>> To: Richard Brown
>>
>> Rationale: Not a precise technical name, but in the vein of "WiFi" it's
>> something that people can make a prior association with. Hi-Fi's and equalizers, right?
>> To backcronym it, "Broadband Enhanced Queueing" which ain't such a bad description.
>> I know that "broadband" is technically wrong on many topologies, but it seems to
>> have achieved popular usage for "high speed Internet". I realize that Co-Del will be
>> also useful on non-last-mile links and such, but the intent is to have something on a
>> label on a SOHO router box at the warehouse club for people to recognize, right?
>> Getting it in use is more important than being technically pedantic anyway, and a catchy
>> marketing name seems to have worked for WiFi, err, I mean "802.11[b,g,a,n] wireless
>> ethernet and associated standards."
>>
>> It would be fairly simple to create a logo involving the word and slider knobs
>> or something. If there's interest I could whip up a Rev. A. logo. And, besides,
>> it looks like it's not in use: https://www.google.com/search?q=“broadbandeq"
>
> The name continues to grow on me…
>
> Rich
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
next prev parent reply other threads:[~2013-12-21 2:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 20:07 Dave Taht
2013-12-20 20:52 ` Rich Brown
2013-12-20 21:22 ` dpreed
2013-12-20 21:29 ` Rich Brown
2013-12-20 21:36 ` Sebastian Moeller
2013-12-21 0:47 ` Rich Brown
2013-12-21 2:55 ` Dave Taht [this message]
2013-12-20 21:58 ` Dave Taht
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw5G+UmOTo9sPqWZidW5HeOXNTcNvD=tj73cL0v0gvb=Hg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
/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