Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
	libreqos <libreqos@lists.bufferbloat.net>,
	Rpm <rpm@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Starlink] [Bloat] [LibreQoS] [Rpm] net neutrality back in the news
Date: Fri, 29 Sep 2023 13:16:55 +0000	[thread overview]
Message-ID: <4C8F178A-BDC9-4D7E-84BD-DFE7231E8740@cable.comcast.com> (raw)

On 9/29/23, 00:54, "Jonathan Morton" <chromatix99@gmail.com <mailto:chromatix99@gmail.com>> wrote:
> Some ISPs began to actively degrade Netflix traffic, in particular by refusing to provision adequate peering capacity at the nodes through which Netflix traffic predominated

That is not true and really not worth re-litigating here. 

> NN regulations forced ISPs to carry Netflix traffic with reasonable levels of service, even though they didn't want to for purely selfish and greedy commercial reasons. 

NN regulations played no role whatsoever in the resolution of that conflict - a business arrangement was reached, just as it was in the SK Telecom example recently: https://about.netflix.com/en/news/sk-telecom-sk-broadband-and-netflix-establish-strategic-partnership-to 

> ISPs behind L4S actively do not want a technology that works end-to-end over the general Internet. 

That's simply not true. As someone running an L4S field trial right now - we want the technology to get the widest possible deployment and be fully end-to-end. Why else would there be so much effort to ensure that ECN and DSCP marks can traverse network domain boundaries for example? Why else would there be strong app developer interest? What evidence do you have to show that anyone working on L4S want to create a walled garden? If anything, it seems the opposite of 5G network slicing, which seems to me personally to be another 3GPP run at walled garden stuff (like IMS). Ultimately it is like a lot of other IETF work -- it is an interesting technology and we'll have to see whether it gets good adoption - the 'market' will decide. 

> They want something that can provide a domination service within their own walled gardens. 

Also not correct. And last time I checked the balance sheets of companies in these sectors - video streaming services were losing money while provision of internet services were financially healthy. 

JL




             reply	other threads:[~2023-09-29 13:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 13:16 Livingood, Jason [this message]
2023-09-29 15:53 ` [Starlink] [LibreQoS] [Bloat] " dan
2023-09-30 11:41   ` [Starlink] [Rpm] [LibreQoS] [Bloat] " Frantisek Borsik
  -- strict thread matches above, loose matches on Subject: below --
2023-09-27 18:21 [Starlink] " Dave Taht
2023-09-28  6:25 ` [Starlink] [Rpm] " Sebastian Moeller
2023-09-28 16:38   ` Dave Taht
2023-09-28 19:31     ` Sebastian Moeller
2023-09-28 19:39       ` Dave Taht
2023-09-28 20:08         ` [Starlink] [LibreQoS] " dan
2023-09-28 20:36           ` Jeremy Austin
2023-09-28 20:54             ` [Starlink] [Bloat] " Livingood, Jason
2023-09-28 20:48           ` [Starlink] " Livingood, Jason
2023-09-28 22:19             ` [Starlink] [Bloat] " David Lang
2023-09-29  4:54               ` Jonathan Morton
2023-09-28 22:25           ` David Lang

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=4C8F178A-BDC9-4D7E-84BD-DFE7231E8740@cable.comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    --cc=rpm@lists.bufferbloat.net \
    --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