Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: "David Fernández" <davidfdzp@gmail.com>,
	"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Researchers Seeking Probe Volunteers in USA
Date: Mon, 9 Jan 2023 14:50:37 +0000	[thread overview]
Message-ID: <D64420C2-C6AE-4554-9F1D-C4F366E10D48@cable.comcast.com> (raw)
In-Reply-To: <CAC=tZ0r_FQVth5tmt3hsBhqQ+6Zr94y6nDCx=wfZZmDrm8+_Aw@mail.gmail.com>

> AFAIK, quality of service (QoS) refers to network characteristics you
can measure quantitatively without human opinion being involved, i.e.:
throughput, latency and packet losses, also availability (MTBF/(MTBF +
MTTR)). Then, quality of experience (QoE) refers to what the users
experience, it is subjective, it must be done using subjects that are
not engineers or telecom technicians, and it is defined by the ITU as
the MOS (Mean Opinion Score), in Recommendation ITU-T P.800.1.

ISTM that everyone has a different view of QoS & QoE. My view is that QoS refers to DSCP marking and such (so best effort, priority, less than best effort, etc.) and/or some metric that the *network* is configured to deliver. But...these are all proxies for end user QoE, which used to be difficult to measure individually but is now easy/affordable to do at scale. IMO all that really matters is the end user experience, and that can be quantitatively measured (link capacity at peak hour, responsiveness/working latency, uptime) and qualitatively measured.  After all, the end user does not care about what the network is in theory configured to delivery but only their actual experience using the Internet. __ 


  reply	other threads:[~2023-01-09 14:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 10:07 David Fernández
2023-01-09 14:50 ` Livingood, Jason [this message]
2023-01-09 15:45   ` Doc Searls
2023-01-09 17:11     ` Sebastian Moeller
     [not found] <mailman.2651.1672779463.1281.starlink@lists.bufferbloat.net>
2023-01-03 22:58 ` David P. Reed
2023-01-09 14:44   ` Livingood, Jason
2023-01-09 15:26     ` Dave Taht
2023-01-09 17:00       ` Sebastian Moeller
  -- strict thread matches above, loose matches on Subject: below --
2023-01-03 20:53 Livingood, Jason
2023-01-03 20:57 ` Vint Cerf
2023-01-03 21:23 ` Eric

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

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

  git send-email \
    --in-reply-to=D64420C2-C6AE-4554-9F1D-C4F366E10D48@cable.comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=davidfdzp@gmail.com \
    --cc=starlink@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