From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Make-wifi-fast] marketing wifi and broadband in the c-suite
Date: Mon, 22 Aug 2022 12:30:08 -0700 [thread overview]
Message-ID: <CAHb6Lvo91CX9fVoTOrRf=j++J5BLOwEiLTNNOgF87CSRGrOSmg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7+c5DUSWT+6y8=k+gEJAG6NJKtJoM4AhurH9sRSXud2g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2360 bytes --]
Thanks for sharing this. It's interesting that the focus is still on speed
and not so much on latency/responsiveness.
*In addition to navigating the competitive landscape, BSPs must also
continually hone theirmarketing messages to attract and recruit new
subscribers. As Figure 10 illustrates, basedon “top priority” responses,
the C-levels are following a pragmatic marketing messagestrategy centered
on faster speeds (54%),This is judicious given that many of their
competitors are also focusing on network speed to enhance the quality of
experience. *
On Mon, Aug 22, 2022 at 10:23 AM Dave Taht via Make-wifi-fast <
make-wifi-fast@lists.bufferbloat.net> wrote:
>
> https://www.calix.com/content/dam/calix/marketing-documents/public/reports/report_marketer-bb-provider.pdf
>
> Very different world, but it stood out to me, that "managed wifi" was
> a number #1 priority. Having wifi that actually worked right out the
> box has always been mine....
>
> 'C-level "top priority” marketing use cases include managed Wi-Fi (46%),
> home
> network cybersecurity and device security (both 45%), and professional home
> monitored security (42%). Rounding out the top five is social media
> monitoring
> (39%)"'
>
> --
> FQ World Domination pending:
> https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> 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: 3234 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]
next prev parent reply other threads:[~2022-08-22 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 17:23 [Bloat] " Dave Taht
2022-08-22 19:30 ` Bob McMahon [this message]
2022-08-23 10:56 ` [Bloat] [Make-wifi-fast] " Dave Collier-Brown
2022-08-23 11:59 ` Sebastian Moeller
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHb6Lvo91CX9fVoTOrRf=j++J5BLOwEiLTNNOgF87CSRGrOSmg@mail.gmail.com' \
--to=bob.mcmahon@broadcom.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--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