Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: dan <dandenson@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] qos is still more popular than qoe
Date: Thu, 3 Nov 2022 10:10:57 -0600	[thread overview]
Message-ID: <CAA_JP8UtSxO5Z5AWfa0XtVt6hZu85ypP1UAfPJWXgQL355gQog@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5ei5Mr5UXe5149o_8WH9QWDs+T60bbO5RGbptmk75HXA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

QoE is definitely an industry term and it belongs there.  It really isn't a
fit for the customer jargon because customers have a 'service' not an
'experience'.  They wouldn't call up their ISP and say 'my experience
sucks', they say 'my service sucks'.  So QoS naturally fits in there.

From a business side, 'Experience' is a better fit.  If you're doing
metrics on customer 'support' lines, the customer 'experience' is often in
that language.  We're trying to drive loyalty and value home by giving a
customer a better experience on their service.


On Thu, Nov 3, 2022 at 8:45 AM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:

> https://trends.google.com/trends/explore?q=qoe,qos,bufferbloat
>
>
> --
> This song goes out to all the folk that thought Stadia would work:
>
> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>

[-- Attachment #2: Type: text/html, Size: 1900 bytes --]

      reply	other threads:[~2022-11-03 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 14:45 Dave Taht
2022-11-03 16:10 ` dan [this message]

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/libreqos.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAA_JP8UtSxO5Z5AWfa0XtVt6hZu85ypP1UAfPJWXgQL355gQog@mail.gmail.com \
    --to=dandenson@gmail.com \
    --cc=dave.taht@gmail.com \
    --cc=libreqos@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