Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] Verizon, T-Mobile, Nokia get noisy on network slicing and net neutrality (LightReading)
Date: Sat, 9 Mar 2024 10:16:17 +0100	[thread overview]
Message-ID: <C4ACA21F-BF1E-48B2-B4F7-C3A7D6B49790@gmx.de> (raw)
In-Reply-To: <MN2PR11MB370920B6842F45A66A7A8625C7272@MN2PR11MB3709.namprd11.prod.outlook.com>

Hi Jason.

> On 9. Mar 2024, at 00:30, Livingood, Jason via Nnagain <nnagain@lists.bufferbloat.net> wrote:
> 
> I find it difficult to imagine a lot of consumer use cases for this (and find it another rather complex 3GPP spec). I can see some enterprise, industrial, and event (e.g. sports venue) use cases - but those seem like simple give X devices priority over Y devices sorts of scenarios. 

[SM] Looking at the wikipedia article on slicing I see:
"Network slicing emerges as an essential technique in 5G networks to accommodate such different and possibly contrasting quality of service (QoS) requirements exploiting a single physical network infrastructure.[1][13]
[...]
Impact and applications
In commercial terms, network slicing allows a mobile operator to create specific virtual networks that cater to particular clients and use cases. Certain applications - such as mobile broadband, machine-to-machine communications (e.g. in manufacturing or logistics), or smart cars - will benefit from leveraging different aspects of 5G technology. One might require higher speeds, another low latency, and yet another access to edge computingresources. By creating separate slices that prioritise specific resources a 5G operator can offer tailored solutions to particular industries.[14][15]: 3  Some sources insist this will revolutionise industries like marketing, augmented reality, or mobile gaming,[16][17] while others are more cautious, pointing to unevenness in network coverage and poor reach of advantages beyond increased speed.[18][19]"

As expected this technique is designed to allow exactly what NN was designed to prohibit (treating packets differentially in the internet based on economic considerations*)... this is IMHO why instead of calling a spade a spade mobile carriers avoid describing this in a useful way, as it is exactly about prioritisation... IMHO that will back fire, and a better avenue would be to be open about what it enables and propose a method to restrict the potential issues. E.g. (I am making this up on the fly, so it will likely not hold up to any degree of scrutiny) by self limiting to never commit more than X% of a cell's capacity to slicing, IFF the cell is used for normal end user service at all. So admit that there is some trade-off here, limit the fall-out, and then describe why we as a society should embrace that trade-off. I am a bit sceptical about the whole car 2 car communication thing (that is cars talk to cars, not people n cars talk to people on cars ;) ), but if a Carrier believes there is value in that for e.g. accident avoidance, then tell how this requires the stricter network guarantees that (only?) slicing can deliver.

Personally I still think this is not an attractive proposition, but I am not the audience for that anyway; the relevant regulatory agency and the legislative is.

Regards
	Sebastian

*) This is a (too) short condensation of the rationale of the EU for stepping into the NN debate.

> From: Nnagain <nnagain-bounces@lists.bufferbloat.net> on behalf of the keyboard of geoff goodfellow via Nnagain <nnagain@lists.bufferbloat.net>
> Sent: Friday, March 8, 2024 5:08:28 PM
> To: Network Neutrality is back! Let´s make the technical aspects heard this time! <nnagain@lists.bufferbloat.net>
> Cc: the keyboard of geoff goodfellow <geoff@iconia.com>
> Subject: [NNagain] Verizon, T-Mobile, Nokia get noisy on network slicing and net neutrality (LightReading)   'Placing unnecessary restrictions on this technology could stifle it in its infancy,' Verizon wrote of network slicing, in a widening debate involving the FCC's net neutrality proceeding and new wireless technologies...
> [...]
> https://www.lightreading.com/regulatory-politics/verizon-t-mobile-nokia-get-noisy-on-network-slicing-and-net-neutrality
> via
> https://twitter.com/mikeddano/status/1766207009106669682
> 
> -- 
> Geoff.Goodfellow@iconia.com
> living as The Truth is True
> 
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain


  reply	other threads:[~2024-03-09  9:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 22:08 the keyboard of geoff goodfellow
2024-03-08 23:30 ` Livingood, Jason
2024-03-09  9:16   ` Sebastian Moeller [this message]
2024-03-09 20:42     ` Dick Roy
2024-03-09 20:57       ` Robert McMahon
2024-03-09 22:26         ` Dick Roy
2024-03-09 23:02           ` Vint Cerf
2024-03-10  2:08             ` Dick Roy

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=C4ACA21F-BF1E-48B2-B4F7-C3A7D6B49790@gmx.de \
    --to=moeller0@gmx.de \
    --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