Network Neutrality is back! Let´s make the technical aspects heard this time!
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Richard Roy via Nnagain <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] FCC - delete, delete, delete
Date: Fri, 14 Mar 2025 14:09:03 -0700 (PDT)	[thread overview]
Message-ID: <o6n142q5-0302-87qp-2696-n4p8pq2157sn@ynat.uz> (raw)
In-Reply-To: <CY8PR12MB77325D7F80414965843A0A738AD22@CY8PR12MB7732.namprd12.prod.outlook.com>

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

it's also impossible to fix bugs when you prevent updates.

show me any product deployed at large scale that has not had bugs.

David Lang

On Fri, 14 Mar 2025, Richard Roy via Nnagain wrote:

> Date: Fri, 14 Mar 2025 19:05:18 +0000
> From: Richard Roy via Nnagain <nnagain@lists.bufferbloat.net>
> To: Network Neutrality is back! Let´s make the technical aspects heard this
>     time! <nnagain@lists.bufferbloat.net>, Tara Stella <tara@tara.sh>
> Cc: Richard Roy <dickroy@alum.mit.edu>
> Subject: Re: [NNagain] FCC - delete, delete, delete
> 
> Bob,
>
>
>
> You are certainly correct.  Complexity of implementation always leads to the potential for more attack surfaces.  As importantly, security as an add-on is really no security at all.  If security is not designed in at the outset, optimal security can rarely if ever be achieved.  First and foremost at the core of security is "credential material" that MUST be protected IN TAMPER-PROOF/EVIDENT HARDWARE (e.g. FIPS 140-x).  It is nearly impossible to secure a system without this capability, and not all of the systems out there today are so "equipped" making system-wide trust nearly impossible. ☹☹☹
>
>
>
> Cheers,
>
> RR
>
>
>
> -----Original Message-----
> From: Nnagain <nnagain-bounces@lists.bufferbloat.net> On Behalf Of Robert McMahon via Nnagain
> Sent: Friday, March 14, 2025 11:53 AM
> To: Tara Stella <tara@tara.sh>
> Cc: Robert McMahon <rjmcmahon@rjmcmahon.com>; Network Neutrality is back! Let´s make the technical aspects heard this time! <nnagain@lists.bufferbloat.net>
> Subject: Re: [NNagain] FCC - delete, delete, delete
>
>
>
>> I'm not an expert, but I wonder if the complexity has increased the potential attacking surface.
>
>
>
> I'm not an expert here either - but I do think complexity does increase the attack service. Breaking up the control and data planes seems like a good idea to me.
>
>
>
> Also, devices like CPUs that run programmable logic are a target because their logic flows can be hijacked. Hardware solutions for simple functions like forwarding packets cannot be reprogrammed at the data plane level, minimizing their attack service.
>
>
>
> Moving the control plane(s) into a management domain where security experts do their work everyday seems a must to me. Pushing this into consumer premises and adding more and more seems like a disaster in the making.
>
>
>
> https://www.splunk.com/en_us/blog/learn/control-plane-vs-data-plane.html
>
>
>
> Bob
>
>
>
> On Fri, Mar 14, 2025 at 1:16 AM Tara Stella <tara@tara.sh<mailto:tara@tara.sh>> wrote:
>
>>
>
>> On Thu, 2025-03-13 at 22:24 -0400, David Bray, PhD via Nnagain wrote:
>
>>
>
>> Indeed. Yet here on ground SS7 remains vulnerable and exploitable too?
>
>>
>
>>
>
>> I'm working for a big telco in Europe, and I'm just marginally involved in the telco network.
>
>> AFAIK, in our infrastructure, SS7 is a niche in some very old equipment sitting somewhere.
>
>> On fixed broadband, we migrated everything over IP, voice is SIP, including VAS services, that are somehow fading away as well (IMS still in place for voicemail).
>
>> On 5G Standalone, everything is HTTP on the control plane and GTP encapsulation on the user plane.
>
>>
>
>> I'm not an expert, but I wonder if the complexity has increased the potential attacking surface.
>
>> Cheers,
>
>> Tara
>
>>
>
> _______________________________________________
>
> Nnagain mailing list
>
> Nnagain@lists.bufferbloat.net<mailto:Nnagain@lists.bufferbloat.net>
>
> https://lists.bufferbloat.net/listinfo/nnagain
>

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

_______________________________________________
Nnagain mailing list
Nnagain@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/nnagain

  reply	other threads:[~2025-03-14 21:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 17:39 Dave Taht
2025-03-13  0:00 ` Richard Roy
2025-03-13 16:33   ` Robert McMahon
2025-03-13 17:00     ` Frantisek Borsik
2025-03-13 18:36       ` Robert McMahon
2025-03-13 23:59         ` David Lang
2025-03-14  1:12           ` Robert McMahon
2025-03-14  1:38         ` David Bray, PhD
2025-03-14  2:17           ` Robert McMahon
2025-03-14  2:20             ` Robert McMahon
2025-03-14  2:24             ` David Bray, PhD
2025-03-14  8:16               ` Tara Stella
2025-03-14 18:53                 ` Robert McMahon
2025-03-14 19:05                   ` Richard Roy
2025-03-14 21:09                     ` David Lang [this message]
2025-03-14 21:20                       ` Dick Roy
2025-03-14 21:48                         ` David Lang
2025-03-15 18:16                           ` Robert McMahon
2025-03-15 18:49                             ` Daniel Ezell
2025-03-16 17:50                               ` Robert McMahon
2025-03-15 18:50                             ` Robert McMahon

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=o6n142q5-0302-87qp-2696-n4p8pq2157sn@ynat.uz \
    --to=david@lang.hm \
    --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