From: Spencer Sevilla <spencer.builds.networks@gmail.com>
To: "Network Neutrality is back! Let´s make the technical aspects
heard this time!" <nnagain@lists.bufferbloat.net>
Cc: bloat <bloat@lists.bufferbloat.net>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [NNagain] cloud gaming on a comeback?
Date: Wed, 10 Jan 2024 13:11:59 -0800 [thread overview]
Message-ID: <644FD1D6-E0B9-40A6-82E4-F3BDF3E1A0F8@gmail.com> (raw)
In-Reply-To: <CAA93jw4cHgFFqeBbrCgsOghL41G9iqrKoqv7xstP6w6G0ktVuA@mail.gmail.com>
I’ve thought about this exact point for years. Game network programming often uses some complexity to split low-bandwidth low-latency traffic (e.g. location updates) from bigger amounts of data transfer. Similarly, the LTE/5G stack provides amazing primitives to segregate and prioritize different traffic streams at a low level throughout the entire network. You’d think they were a natural fit for each other, but the semantic differences (and IMO the telco architecture’s need to control *everything* and breakout traffic by content type) are pretty large and hard to get around. To make the point clear I’ve sometimes idly considered a joke of a solution wherein a gaming app opens up a phone call to one of their servers and uses that channel for low-bandwidth-low-latency traffic encoded using an audio codec, and sends everything else over as generic data.
I am deeply interested in best of both worlds solutions, or specifically a more content-blind/neutral way for ISPs/Telcos to prioritize certain low-bandwidth-low-latency traffic streams. I’ve seen that topic discussed a fair amount on this listserv and have sincerely appreciated the nuanced points raised :-)
Spencer
> On Jan 10, 2024, at 08:33, Dave Taht via Nnagain <nnagain@lists.bufferbloat.net> wrote:
>
> This does a pretty good job of summarizing the benefits, and issues,
> behind making gaming a for-pay at the isp service, among other things.
>
> https://www.lightreading.com/cloud/telcos-should-offer-dedicated-gaming-internet-packages-ericsson
>
> In the case of LTE/5G if they could merely deliver a solid home gaming
> experience, it would be a win... and they still can´t.
>
> --
> 40 years of net history, a couple songs:
> https://www.youtube.com/watch?v=D9RGX6QFm5E
> Dave Täht CSO, LibreQos
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
prev parent reply other threads:[~2024-01-10 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 16:33 Dave Taht
2024-01-10 18:47 ` Dick Roy
2024-01-10 21:11 ` Spencer Sevilla [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/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=644FD1D6-E0B9-40A6-82E4-F3BDF3E1A0F8@gmail.com \
--to=spencer.builds.networks@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=nnagain@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