From: Robert McMahon <rjmcmahon@rjmcmahon.com>
To: dickroy@alum.mit.edu,Dick Roy via Nnagain
<nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] Verizon, T-Mobile, Nokia get noisy on network slicing and net neutrality (LightReading)
Date: Sat, 09 Mar 2024 12:57:58 -0800 [thread overview]
Message-ID: <03cb3495-5f60-4a13-ae75-60bb92a5b867@rjmcmahon.com> (raw)
In-Reply-To: <6BE25389766648E5AA898A86F4937D34@SRA6>
[-- Attachment #1: Type: text/plain, Size: 2713 bytes --]
What is DSRC?
DSRC (Dedicated Short-Range Communications) is a wireless communication technology that enables vehicles to communicate with each other and other road users directly, without involving cellular or other infrastructure. DSRC is based on WiFi technology
https://auto-talks.com/technology/dsrc-technology/#:~:text=What%20is%20DSRC%3F,involving%20cellular%20or%20other%20infrastructure.
On Mar 9, 2024, 12:42 PM, at 12:42 PM, Dick Roy via Nnagain <nnagain@lists.bufferbloat.net> wrote:
>
>
>
>
>
>
>
>
>
>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.
>
>[RR] V2X communications for saving lives will NEVER go through ANY
>carriers
>network in spite of what you hear. There is simply no way anyone is
>going
>to pay to have BSMs broadcast 10 times a second to prevent accidents,
>and NO
>CARRIER is going to give that capacity away for free, even if they had
>enough to carry the traffic, which they do not by many orders of
>magnitude!!! More importantly, the information being exchanged does
>NOT
>require a network to get where it needs to go! The 5G hype you hear
>from
>various carriers and equipment suppliers related to V2X communications
>is
>all powerpoint BS (to make shareholders happy). And there is a ton of
>it out
>there! :-):-)
>
>
>
>RR
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Nnagain mailing list
>Nnagain@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/nnagain
[-- Attachment #2: Type: text/html, Size: 5903 bytes --]
next prev parent reply other threads:[~2024-03-09 20:58 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
2024-03-09 20:42 ` Dick Roy
2024-03-09 20:57 ` Robert McMahon [this message]
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=03cb3495-5f60-4a13-ae75-60bb92a5b867@rjmcmahon.com \
--to=rjmcmahon@rjmcmahon.com \
--cc=dickroy@alum.mit.edu \
--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