Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
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: Fri, 8 Mar 2024 23:30:02 +0000	[thread overview]
Message-ID: <MN2PR11MB370920B6842F45A66A7A8625C7272@MN2PR11MB3709.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAEf-zrg2xL88B_Nb--BK6pgBWMRUEqDfKoKVae1hWU+Tz-hPZQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1760 bytes --]

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.
________________________________
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<https://urldefense.com/v3/__https://www.lightreading.com/regulatory-politics/verizon-t-mobile-nokia-get-noisy-on-network-slicing-and-net-neutrality__;!!CQl3mcHX2A!Cco-2y5APq2qA34gWl-3semjgX4nCU2MUxcXbp31NDgbY6cNJ7Kes3JaTaDZZ6SZwjyiYAKjrN0PgpNlR_efbRPRcra8VvVw$>
via
https://twitter.com/mikeddano/status/1766207009106669682<https://urldefense.com/v3/__https://twitter.com/mikeddano/status/1766207009106669682__;!!CQl3mcHX2A!Cco-2y5APq2qA34gWl-3semjgX4nCU2MUxcXbp31NDgbY6cNJ7Kes3JaTaDZZ6SZwjyiYAKjrN0PgpNlR_efbRPRcq3TfLy0$>

--
Geoff.Goodfellow@iconia.com<mailto:Geoff.Goodfellow@iconia.com>
living as The Truth is True


[-- Attachment #2: Type: text/html, Size: 3340 bytes --]

  reply	other threads:[~2024-03-08 23:30 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 [this message]
2024-03-09  9:16   ` Sebastian Moeller
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=MN2PR11MB370920B6842F45A66A7A8625C7272@MN2PR11MB3709.namprd11.prod.outlook.com \
    --to=jason_livingood@comcast.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