The benefits of SDN are hard to grasp because they're so big. But NFV provides a nice, finite-value proposition.

Mitch Wagner, Executive Editor, Light Reading

July 18, 2014

4 Min Read
How NFV Gets a Foot in the Door for SDN

A recent blog post by veteran industry analyst Tom Nolle points up where SDN is a tough sell to carriers: It's too ambitious, and the benefit is difficult to quantify.

Tom, who's a friend of Light Reading, starts with a reminder of my past as an English literature major. No, he doesn't ask if you want fries with that... he quotes the poet John Milton.

Then Tom gets into the meat of the thing:

When SDN got started, it quickly became identified with a kind of network-buyer "throw the bums out" vision where hordes of white-box revolutionaries were carried on the shoulders of the crowd as they trampled incumbents. In reality, there is no indication that SDN is really revolutionizing much at this point, and if you believe the latest Wall Street analysis of buyer sentiment, we're going to see an uptick in traditional network spending. Why is all of this happening?

Read Tom's whole post here: SDN is a Spectator Sport. (Also, see 3 Barriers to SDN Adoption.)

Tom then describes why SDN is having a tough time: "The barrier to SDN revolution is incrementalism. You can't readily value SDN by replacing one router at a time. You have to displace a bunch of stuff to create a value in networking, and to do that you need significant benefits -- new things."

Of course the big benefit of SDN, proponents say, is agility. You can configure networks faster, increase customer self-service and satisfaction, and innovate new kinds of service. But that kind of thing is difficult to describe in detail and quantify. And it's hard to explain exactly how SDN fits in, Tom says.

And as for innovation: The nature of innovation is you can't describe it in advance. The only way you know if something is innovative is in retrospect. Indeed, innovation often looks stupid when first proposed (and even stupidity is no reliable dowsing rod for finding innovation, because you know what else looks stupid when proposed? Stupid things.)

Reading Tom's post, it strikes me that NFV dodges the tough selling proposition of SDN precisely because it's less ambitious. NFV is about using software for network functions that currently require dedicated hardware appliances, such as firewalls and load balancers and such. That's easy to understand. And the benefits are easy to understand too -- the carrier doesn't have to roll a truck to install hardware on customer premises. (See Wind River Launches NFV 'App Store', Overture Adds Hardware to Its NFV Pitch, NFV-Enabled Ethernet for Generating New Revenues , and Cyan Debuts Planet Orchestrate to Manage Physical & Virtual Network Resources.)

There are other benefits too, but the CEO and CFO don't have to worry about those.

Like Tom, I'm reminded of the PC and Internet revolutions. A fundamental characteristic of those revolutions is they started small. PCs came into the office when accountants wanted to run spreadsheets without having to get the blessing of IT every time. The Internet at first just involved installing a web browser on employees' PCs, and putting up some company literature on the web, maybe sell a couple of products. Evangelists could build on small success and iterate until, soon enough, they'd upended the entire world economy.

But how do you get off to a small start with SDN? As Tom points out, it's hard.

NFV isn't so difficult. You can do a small NFV pilot, achieve a small but tangible benefit, and use that benefit to justify a bigger investment.

That's how revolutions are made.

So is SDN a loser? No. Operators at our recent Big Telecom Event said they need SDN to get the full benefits of NFV. With a single or a few virtualized functions, you gain some flexibility and economy locally, but SDN helps to deliver all the efficiencies and agility that NFV can, in theory, deliver across a broad network.

In that respect, the SDN and NFV revolution is like the PC and Internet revolutions that came before: You start out making small changes around the edges -- putting a few PCs on desktops to run spreadsheets, or putting your company's catalog and brochures on the Internet -- build on those benefits, until before long you're rebuilding the entire network infrastructure around the new technology. (See NFV 'Irrelevant' in Long Term, ONF Reckons.)

For more on some of the developments around NFV, see Exclusive: Leaked 'Inception' Document Fleshes Out Open-Source NFV Plans and NFV 'Inception' Meeting Highlights Tectonic Shift in Telecom.

— Mitch Wagner, Circle me on Google+ Follow me on TwitterVisit my LinkedIn profileFollow me on Facebook, West Coast Bureau Chief, Light Reading. Got a tip about SDN or NFV? Send it to [email protected].

About the Author(s)

Mitch Wagner

Executive Editor, Light Reading

San Diego-based Mitch Wagner is many things. As well as being "our guy" on the West Coast (of the US, not Scotland, or anywhere else with indifferent meteorological conditions), he's a husband (to his wife), dissatisfied Democrat, American (so he could be President some day), nonobservant Jew, and science fiction fan. Not necessarily in that order.

He's also one half of a special duo, along with Minnie, who is the co-habitor of the West Coast Bureau and Light Reading's primary chewer of sticks, though she is not the only one on the team who regularly munches on bark.

Wagner, whose previous positions include Editor-in-Chief at Internet Evolution and Executive Editor at InformationWeek, will be responsible for tracking and reporting on developments in Silicon Valley and other US West Coast hotspots of communications technology innovation.

Beats: Software-defined networking (SDN), network functions virtualization (NFV), IP networking, and colored foods (such as 'green rice').

Subscribe and receive the latest news from the industry.
Join 62,000+ members. Yes it's completely free.

You May Also Like