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: "Livingood, Jason" <jason_livingood@comcast.com>
Cc: Mike Conlow via Nnagain <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] 2015 flashback
Date: Mon, 30 Oct 2023 08:58:09 -0700	[thread overview]
Message-ID: <2b1fb8f6-84f4-4d5b-8082-4d68d9b5dc92@rjmcmahon.com> (raw)
In-Reply-To: <617093D3-0AF2-416D-BD6A-F489BB2EEBFE@comcast.com>

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

It may be a lack of awareness as well as a statement on home networks that are woefully underfunded. Security vulnerability scanning, audits and reporting seem like an obvious need, likely even more than low latency - though both are needed. Our smoke detectors beep incessantly when the sensors expire or the battery is low. There really is no consumer signal to upgrade per vulnerabilities, though that's  all that's needed 80+% of the time.

I recently replaced all my circuit breakers with AFCI to prevent electrical fires. That's a recent innovation to our home electrical networks. We need even more innovation for home comm networks.

Maybe the government helps educate homeowners on their vulnerabilities? Then, market participants sell services to help?

Also, it seems good idea to remove the general purpose CPUs running full-blown multi user systems and replace them with signal processing and L2 forwarding/transit, a la FiWi. But at our current rate of home networking innovation, that may take as long as AFCIs. I hope not as this should help significantly with the pernicious security issues found all throughout networking where no silver bullet that resolves all, rather continuous innovation is required.

Bob

On Oct 30, 2023, 7:20 AM, at 7:20 AM, "Livingood, Jason" <jason_livingood@comcast.com> wrote:
>On home routers / gateways, many ISPs will lease a device to users and
>that covers the cost of ongoing feature & security & performance
>updates and so on. The retail channel is mostly (except at the high
>end) a 1-time purchase with no ongoing revenue for the device maker or
>incentive for shipping reasonably current software. But with the FCC's
>upcoming cybersecurity certification program under consideration, I do
>wonder if that will improve the situation for consumers by pushing
>device makers to improve their software & ongoing support (such as for
>bugs/vulns)?
>
>Jason
>
>On 10/29/23, 15:29, "Nnagain on behalf of rjmcmahon via Nnagain"
><nnagain-bounces@lists.bufferbloat.net
><mailto:nnagain-bounces@lists.bufferbloat.net> on behalf of
>nnagain@lists.bufferbloat.net <mailto:nnagain@lists.bufferbloat.net>>
>wrote:
>
>
>My thoughts are those that want to innovate in network devices should
>do
>the innovative work and sell their innovations to the market, then find
>
>out if the market wants those innovations by asking for payments. I
>find
>if people are unwilling to pay for something it many times means that
>that something isn't seen as desired. Market signals are a way in a
>capitalistic system to allocate resources including human resources.
>
>
>Asking government to step in and expropriate decades of intellectual
>property development or the outside plants via "type II regulation" is
>typically not effective and likely not even legal. Few want to do the
>work and have their work taken away by the State. Systems that allow
>this will cause investment into these activities to cease, and more
>importantly, it is a form of State coercion parading itself as "doing
>good." Nobody wants to go back to the days of Ma Bell and State
>controlled communications.
>
>
>There are existence proofs of many new Wifi & AP companies since 2015.
>One may look there to see how these groups were able to innovate so
>their products had monetary value and how device mfg became partners.
>
>
>Bob
>> We had many notables have key and prophetic things to say about the
>> internet's problems and future... back in 2015,
>> when we were fighting to keep home routers open enough to fix them.
>>
>>
>https://urldefense.com/v3/__https://docs.google.com/document/d/1HT2NjsHR1bGQM0PeawYuF60B_m3Hisa3_Q1MB2aVNs4/edit?usp=sharing__;!!CQl3mcHX2A!BCaF1xaItJ-TpDmrKGG4HLKkne8v8RFk8VPtvJvbGCPzppWvm-WhX1qVDgb5iDYDWv9Sfr7Gc55XSVXOywt-cZ6qpyBapjnz$
><https://urldefense.com/v3/__https://docs.google.com/document/d/1HT2NjsHR1bGQM0PeawYuF60B_m3Hisa3_Q1MB2aVNs4/edit?usp=sharing__;!!CQl3mcHX2A!BCaF1xaItJ-TpDmrKGG4HLKkne8v8RFk8VPtvJvbGCPzppWvm-WhX1qVDgb5iDYDWv9Sfr7Gc55XSVXOywt-cZ6qpyBapjnz$>
>
>>
>> I do not think any of the contributors to this document have changed
>> their opinions much since then, and while I think the situation less
>> dire, the overall scope of these problems outlined above, wider.
>_______________________________________________
>Nnagain mailing list
>Nnagain@lists.bufferbloat.net <mailto:Nnagain@lists.bufferbloat.net>
>https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/nnagain__;!!CQl3mcHX2A!BCaF1xaItJ-TpDmrKGG4HLKkne8v8RFk8VPtvJvbGCPzppWvm-WhX1qVDgb5iDYDWv9Sfr7Gc55XSVXOywt-cZ6qpzc2Z5hA$
><https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/nnagain__;!!CQl3mcHX2A!BCaF1xaItJ-TpDmrKGG4HLKkne8v8RFk8VPtvJvbGCPzppWvm-WhX1qVDgb5iDYDWv9Sfr7Gc55XSVXOywt-cZ6qpzc2Z5hA$>
>

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

      reply	other threads:[~2023-10-30 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-29  6:18 Dave Taht
2023-10-29 19:28 ` rjmcmahon
2023-10-30 14:20   ` Livingood, Jason
2023-10-30 15:58     ` Robert McMahon [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=2b1fb8f6-84f4-4d5b-8082-4d68d9b5dc92@rjmcmahon.com \
    --to=rjmcmahon@rjmcmahon.com \
    --cc=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