[c-nsp] [External] SDx open standard?

Mark Tinka mark.tinka at seacom.mu
Sun Mar 15 15:18:26 EDT 2020



On 15/Mar/20 20:04, Alex K. wrote:
> That's what I'm asking about.
>
> While the thread Mark referenced, deals (in my humble opinion) primarily
> with automation side of things, my question is how the whole SDN thing
> became vendor-specific-closed-protocol?

So the thread I shared is little to do with automation, and all to do
with how the industry has spent the past 10 years distracting itself
with finding reasons to standardize what has, for a long time, been
either in-house, custom-designed network operation tools and systems, or
disparate systems working in silos to give operators a consolidated view
of the network.

Several operators have had some SDN-like thing and/or some
automation-like thing for decades. What we've been struggling with since
2010 was how we standardize this, for some reason or other. This is how
and why you are ending up with (not proprietary, but) competing
solutions and ideas, which then manifest as, well, proprietary.

Meanwhile, a ton of network operators continue to run their networks
with their customer SDN- and automation-like thingies, paying minimal or
no attention to all the confusion going on in the industry that has cost
us 10 years.

Personally, what the last decade taught me is to sniff out all the snake
oil, and not waste my time on things that are trying to reinvent some of
the basics that, despite the ubiquity of the Internet, we cannot simply
give up to "greater intelligence and optimization" because, well, that's
just unnecessary overhead beyond what we can already build and play with
nicely today.

You can tell how much I love SDN, SD-WAN, IoT, Big Data and 5G :-).

Now because of "Cory", WFH is about to be touted as "a technology" :-\...

#TheIndustrysAddictionToBuzzWords

Mark.



More information about the cisco-nsp mailing list