From: "David Fernández" <davidfdzp@gmail.com>
To: "Livingood, Jason" <Jason_Livingood@comcast.com>
Cc: Sebastian Moeller <moeller0@gmx.de>,
starlink <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 22:39:00 +0200 [thread overview]
Message-ID: <CAC=tZ0onqBtP056jSgzqzC7f=TpgwHPnWdRB24nJXdT77KJD9w@mail.gmail.com> (raw)
In-Reply-To: <MW4PR11MB7104657600822882CD98BE16C71AA@MW4PR11MB7104.namprd11.prod.outlook.com>
Ok, yes, now I remember, this, here:
https://www.adslzone.net/noticias/operadores/telefonica-meta-limitar-consumo-datos-videos-cortos
Telefónica and Meta collaborating so that Telefónica tells Meta by an API
(to be standardized by IETF SCONEPRO), that it should reduce the
resolution, or not to push so many videos in advance in the infinite
scrolls of users of Instagram that are located in congested base stations,
e.g. serving a lot of users or to users with poor coverage.
The GSMA calls it Open Gateway (and it uses CAMARA APIs) and I think it can
do the same. The network operators offer an API to developers of websites
and applications to get info from the network.
Vodafone and Broadcom have also been doing similar experiments,
implementing an API that informs major short video websites (YouTube, Meta,
TikTok...) of network conditions, so the operators provide info
preventively, on request.
https://www.diariosigloxxi.com/texto-ep/mostrar/20240227134501/vodafone-broadcom-desarrollan-tecnologia-reducir-red-proveedores-contenido
IMHO, this is an automation of what happened when COVID started, that
streamers stopped pushing 4K video, just HD, to avoid a possible collapse
while everybody stayed at home confined.
Now that Starlink is evolving also into a kind of MNO, we may see them also
implementing this. Well, any operator of a network may implement this, if
it helps to save money and to keep the network more stable, which seems to
be the objective.
Regards,
David
On Tue, 30 Sept 2025 at 16:42, Livingood, Jason <Jason_Livingood@comcast.com>
wrote:
> >> AFAIK, the objective of SCONE is " improve slow-start in general", not
> only
> >> for video, but I must confess I am not following it closely.
>
> > Not seeing that objective clearly in the SCONE group/working group or
> ID, but I might have overlooked that.
>
> IIRC one of the initial presentations was from Google on “Plan Aware
> Streaming” – see
> https://datatracker.ietf.org/meeting/119/materials/slides-119-sconepro-youtube-plan-aware-streaming-01.pdf.
>
>
> JL
>
next prev parent reply other threads:[~2025-09-30 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[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
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='CAC=tZ0onqBtP056jSgzqzC7f=TpgwHPnWdRB24nJXdT77KJD9w@mail.gmail.com' \
--to=davidfdzp@gmail.com \
--cc=Jason_Livingood@comcast.com \
--cc=moeller0@gmx.de \
--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