Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: Robert McMahon <rjmcmahon@rjmcmahon.com>
To: "Network Neutrality is back! Let´s make the technical aspects
	heard this time!" <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] benton broadband futures post-election
Date: Fri, 11 Oct 2024 13:30:24 -0700	[thread overview]
Message-ID: <CAEBrVk6MnnOX5mQo-mmXY9BvmD5KP_DVAWMj6b7owB-tftjRXg@mail.gmail.com> (raw)
In-Reply-To: <CAHxHggcArz6MQnPJZzfN9Ft15U6w4XpwF=V7jwPOv-D2RXxmwQ@mail.gmail.com>

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

Matching the OSP to the end users is the tricky part. Cadence matching is
critical. It's analogous to pelotons in cycling. An ASIC is a 24-36 month
cycle.

The market dynamic that works the best is consumer purchases where no
financial analysis is done rather people buy tech for a purpose or for use
case(s).

The next missing piece is Fi-Wi. That will make home networks phenomenal
and as simple as a whole home fire alarm system. When this occurs,
consumers will push back on service providers to upgrade their OSP faster
because they are not being limited by the mobile phone as the primary user
device. Life support use cases, redundancy and quarantining of bad acting
devices will be standard practice (as are circuit breakers, AFCI an GCF in
our electric panels)

Universal service is a must here too, even within a building. Life support
is not only for the wealthy. (And those going to Mars won't get such either
- no escaping reality)

I get the broadband focus (and that Elon Muisk is a disaster in the
making,) but "Wi-Fi only inside" is not sufficient at all and there really
is nothing stopping us from addressing this that I can see. Fix the homes
with fronthaul and wireless to the last meters using the only two mediums
that matter, fiber and RF over spacetime. Most everything else will follow.

Bob

On Thu, Oct 10, 2024 at 6:20 PM Vint Cerf via Nnagain <
nnagain@lists.bufferbloat.net> wrote:

> good analysis
>
> v
>
> On Thu, Oct 10, 2024 at 11:19 PM Dave Taht via Nnagain <
> nnagain@lists.bufferbloat.net> wrote:
>
>>
>> https://www.benton.org/blog/impact-election-broadband-sector
>>
>>
>> --
>> Dave Täht CSO, LibreQos
>> _______________________________________________
>> Nnagain mailing list
>> Nnagain@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/nnagain
>>
>
>
> --
> Please send any postal/overnight deliveries to:
> Vint Cerf
> Google, LLC
> 1900 Reston Metro Plaza, 16th Floor
> Reston, VA 20190
> +1 (571) 213 1346
>
>
> until further notice
>
>
>
> _______________________________________________
> Nnagain mailing list
> Nnagain@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/nnagain
>

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

  reply	other threads:[~2024-10-11 20:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 22:19 Dave Taht
2024-10-11  1:20 ` Vint Cerf
2024-10-11 20:30   ` Robert McMahon [this message]
2024-10-12 14:19     ` David Bray, PhD

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=CAEBrVk6MnnOX5mQo-mmXY9BvmD5KP_DVAWMj6b7owB-tftjRXg@mail.gmail.com \
    --to=rjmcmahon@rjmcmahon.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