From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Michael Richardson <mcr@sandelman.ca>,
"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: [Starlink] Re: SCONE, bandwidth indeterminacy and network to host signals (was Re: Re: Starlink Digest, Vol 53, Issue 14)
Date: Tue, 30 Sep 2025 14:39:25 +0000 [thread overview]
Message-ID: <MW4PR11MB71043CD9D8DE9A8EB449EA9CC71AA@MW4PR11MB7104.namprd11.prod.outlook.com> (raw)
In-Reply-To: <13785.1759100270@obiwan.sandelman.ca>
> The point of SCONE is allow end ("terminals") to better select (video)
bandwidths that are going to be more sustainable. It's definitely driven by
3GPP (LTE) operators so far. I give it a 40% chance of getting usefully
deployed before the need is overtaken by other events.
The promise is that 3GPP operators won't have to do expensive DPI anymore.
I am not a MNO but I think, given pervasive encryption, at this point it is less deep packet inspection and just header inspection. Probably the rule is something like, if dest IP/FQDN = YouTube, then assign RAN priority X and max bitrate Y.
JL
next prev parent reply other threads:[~2025-09-30 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <175909736500.1555.17525399538686390446@gauss>
2025-09-28 22:57 ` [Starlink] " Michael Richardson
2025-09-29 6:04 ` [Starlink] " Sebastian Moeller
2025-09-30 14:39 ` Livingood, Jason [this message]
[not found] <175912611110.1561.4051032455939480932@gauss>
2025-09-29 7:37 ` David Fernández
2025-09-29 8:00 ` Sebastian Moeller
2025-09-30 14:42 ` Livingood, Jason
2025-09-30 15:18 ` Sebastian Moeller
2025-09-30 20:39 ` David Fernández
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=MW4PR11MB71043CD9D8DE9A8EB449EA9CC71AA@MW4PR11MB7104.namprd11.prod.outlook.com \
--to=jason_livingood@comcast.com \
--cc=mcr@sandelman.ca \
--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