Light Reading

Lifting the Cloud Over SDN

Sunil Khandekar
7/21/2014
50%
50%

Software-defined networking (SDN) must be magic. Why else would researchers, educators, vendors, customers -- practically everyone and anyone connected to the networking industry -- be so high on SDN?

The answer, of course, lies in the promise of SDN. After all, isn't it supposed to completely transform networking? Isn't it the innovation that has finally rescued the networking industry after a decade-long drought? And, most importantly, isn't the SDN market forecast to generate tens of billions of dollars -- an estimate being raised every month? (See Defining SDN & NFV.)

The cloud over SDN
Interestingly, everyone has their own definition of SDN and their own take on how it will reshape the networking industry. That's not entirely surprising. The term is broad enough to allow everyone's convenient interpretation to stand. The industry has made progress in moving beyond hype, and customers are now asking how SDN will help them, rather than what SDN is. Nevertheless, there is still a fair amount of confusion, which causes doubt and constricts the real progress that SDN stands to deliver. It is time to lift the cloud over SDN.

Goal
The ultimate goal of an SDN solution is to massively simplify network operations, increase agility, and accelerate deployment of new services without sacrificing security and control.

Definition
The four key tenets of an SDN solution are abstraction, automation, control, and visibility.

SDN bridges the gap between applications and networks to enable the rapid consumption of network services such as bandwidth, QoS, security, firewall, and load balancing by providing visibility and control to the applications. It is about providing abstraction of network capabilities, and it is about the automation of network provisioning. It is about separating what applications need from how the network implements its capabilities.

In order to lift the cloud over SDN, we need to understand how various implementations of "SDN" currently promoted across our industry measure up against these defining characteristics of SDN.

1. Does SDN = OpenFlow?
Discussion of separating the control and data planes took off when the Open Networking Foundation introduced the OpenFlow protocol version 1.1 circa 2011. Normally, the control and forwarding planes are part of the same network switch or router. But the ONF advocated separating and logically centralizing the control plane from the forwarding plane. The forwarding plane would remain part of the network element -- in other words, the switch or router. The ONF introduced OpenFlow as the southbound protocol used by the control plane to program reachability information in the forwarding elements.

Separating the control plane and the forwarding plane was not new. It had been done a decade ago in routers, though both functions still resided in the same physical device. The idea of physically separating the two planes and logically centralizing the control plane is not new, either. It had been already proposed in prior work, such as IETF ForCES initiative. But the industry took note of the revived efforts this time around, and the idea opened up interesting possibilities. Benefits included the ability to conduct control plane upgrades that did not disrupt network forwarding, centralizing the control plane to enable traffic optimizations based on a network-wide view (vs. network-element views), and removing the burden of processor-intensive distributed control protocols from lightweight network elements: virtual switches, CPEs, etc.

However, the overt focus on the separation of the control and forwarding planes and the shiny new OpenFlow protocol diverted attention away from SDN. The separation of the control and forwarding planes created the notion that all forwarding elements could be made simpler and cheaper. It is absolutely true that the networking requirements in campus and data center networks have traditionally not been nearly as stringent as required in the WAN. As a result, the premium attached to these devices have not been justified. The "white-box" discussion that ensued in the industry and drove down the cost of networking devices commensurate with networking requirements has been great for customers. This change has been long overdue. It was tempting for some to apply the same broad brush everywhere and suggest that all networking elements, including WAN core and edge routers, could also be simplified. This caused some confusion in the industry, which has largely settled now.

To be clear, this approach -- separating the control and forwarding planes -- falls short when measured against the four tenets of SDN discussed before. Though it provides control over forwarding elements under the OF controller domain, it does not deliver against the other three tenets: visibility into applications, abstraction of networking capabilities, and network automation.

However, the long-overdue change that caused pricing structures to change in the networking industry is nothing but goodness, and the ONF deservedly gets the credit for this.

2. Does SDN = traffic engineering?
The often-cited case study of Google's SDN implementation for the purpose of traffic engineering the network is certainly interesting. The Google implementation is about computing optimal paths for the network using an offline compute tool and then programming these paths in network elements using OpenFlow. This approach affords Google full control and visibility over the network infrastructure. But it is not the first such implementation, nor is it new by any means.

The (former) MCI network team members must get a chuckle out of this, because they did exactly the same thing 14 years ago. The one difference? They did not use OpenFlow as the southbound protocol. Instead, they used MPLS labels for traffic engineered paths computed with an offline traffic engineering (TE) engine, now called a path computation element (PCE) server, which were programmed using SNMP in their network elements. Yes, this was back in Y2K.

Next: A new approach

(5)  | 
Comment  | 
Print  | 
Newest First  |  Oldest First  |  Threaded View        ADD A COMMENT
tdwivedi
50%
50%
tdwivedi,
User Rank: Light Beer
7/22/2014 | 8:45:09 PM
SDN
Thanks Sunil for distilling the buzzword into clear capabilities and characteristics.

I think the network is following the demands of the server and storage virtulization in the data center/enterprise and is responding to the economy of scale from the cloud computing.

I liked how you net the final goal of the network to be the "application delivery" with the abstraction of what from how, provisoning the network based on the application characteristics, and the visibility and control of the (App) delivery.

I see the similarities on OpenFlow with the other standards (and initiatives) and its possible fate (example SMI-S by SNIA from storage side of the world), as I see ONF has added conformance testing and vendor extenstions which reminds me of how fragmented the storage industry was in adopting the standards and the high expectation from customers and sysemintegrators. 

For reference http://snia.org/ I can't even find the SMi-S links now on the site. I wonder how is OpenFlow different from the other standards to lead a better outcome.

 

 

 

 
SunilKhandekar
50%
50%
SunilKhandekar,
User Rank: Blogger
7/22/2014 | 12:08:32 PM
Re: Let's not forget the business angle..
Thanks Steve.  

Couldn't agree more on the business benefits.  Indeed, massively simplying operations translates to OPEX savings, increasing agility and quicker TTM translates to capitalizing on opportunity, flexibility in the network infrastructure translates to CAPEX savings. 

Yes, my focus in the article is on the network and how to it is made consumable by SDN for applications running on top.  The applications running on top certainly are important on how they are architected for deployment and deliver efficiency and automation at that layer.
SunilKhandekar
50%
50%
SunilKhandekar,
User Rank: Blogger
7/22/2014 | 11:56:45 AM
Re: Bit quick to dismiss multi-vendor OSS
Definitely Ray - to the extent multi-vendor EMS helps right now to manage the existing mult-vendor networks, this is only goodness.  Was simply keeping focus on what SDN ultimately stands to deliver.
Steve Hateley
50%
50%
Steve Hateley,
User Rank: Light Beer
7/22/2014 | 9:28:26 AM
Let's not forget the business angle..
Great article Sunil.

From the Nuage position, your observations are good and well captured however I sense that there is still understandably an air of hardware vendor, "from the network up" perspective. But if the aim is to give an unbiased view on what SDN means to the industry across the board we should be throwing in the all-important business perspective. 

"The ultimate goal of an SDN solution is to massively simplify network operations, increase agility, and accelerate deployment of new services without sacrificing security and control."

Increasing agility (to build, configure and create new market-facing services) and accelerating deployment (shortening the time from lead-to-activate) are two goals that translate well into the concept of simplifying business automation. This requires a holistic ability to not only understand virtual networks and virtualised services, but to properly orchestrate their delivery from the sales process right through to the VNF manager and virtual machines. In many cases this sales automation is now driven from SaaS/Cloud based applications.

New startups with lightweight provisioning tools are a small part of the fully automated process, and provisioning is only one capability of the traditional EMS. In fact comprehensive orchestration needs to encompass technical catalog abstraction of available resources and logical services. In turn this is dependant upon a federated inventory perspective that reigns in not only the virtual resources but also logical and physical connectivity necessary to "connect" the cloud. Then of course there is "provisioning" but we mustn't forget the logical ordering of the necessary processes to activate requested services. So provisioning is just a cog in a larger machine.

SDN certainly brings an evolutionary change that impacts network vendors, CSPs, ISVs and customers all in one go - something that previous service and infrastructure enhancements have never fully done. Importantly though it's not just a network vendor play. To make it a success, NEMs, ISVs and CSPs need to find common ground and make it work. 

Best regards, Steve

 

 

 
Ray@LR
100%
0%
Ray@LR,
User Rank: Blogger
7/22/2014 | 3:32:52 AM
Bit quick to dismiss multi-vendor OSS
Good article Sunil, though I have to point out a slight tension in your argument.

 

You state early on that:

'The industry has made progress in moving beyond hype, and customers are now asking how SDN will help them...'

Indeed -- network operators want to know how SDN, and indeed ANY technology or strategy, will help them perform better, provide a better service and make (more/any) money.

 

Then later, when discussing 'next-generation element management systems', you rightly allude to the fact that a next-gen EMS does not equal SDN (and I think we all know who you're referring to here...) you state:

'Does [a multi-vendor EMS] provide business agility? Not really. At best, it enhances the present mode of operations, to an extent.'

I think there's a good argument that any multi-vendor EMS that works NOW and is also relevant to future network evolutionaryy developments is providing operational and business agility -- after all, the operators want to know HOW any technology can help them, and for most telcos SDN is something they are looking at for the future, whereas a multi-vendor EMS is something that can help them right now.

A multi-vendor EMS does not = SDN, but it can sure make a difference to companies struggling to maximize efficiencies and meet customer demands, something that an SDN implementation cannot do for them with such immediate impact.

So - I am not saying an EMS = SDN, or that SDN isn't going to transform networking, I'm just highlighting that you've maybe been a bit quick to dismiss something that COULD provide great value AND act as a stepping stone towards a virtualization strategy just because it doesn't tick your SDN boxes.  

 
More Blogs from Column
The industry is at an inflection point, and one of the looming disruptors is 5G.
Network architects aiming to upgrade their networks to support agile, open, virtualized services in the 21st century need to consider new criteria when choosing between technology suppliers.
Cable companies still dominate the scene at INTX, the event formerly known as The Cable Show.
What is the best way to support both layer 2 and layer 3 services at the edge of the network that incorporates virtual network functions?
How fast is too fast in terms of communication? Unless our lives and actions start being measured in seconds, do we really need a 43 Tbps connection to fulfill our everyday tasks?
Flash Poll
From The Founder
Last week I dropped in on "Hotlanta," Georgia to moderate Light Reading's inaugural DroneComm conference – a unique colloquium investigating the potential for drone communications to disrupt the world's telecom ecosystem. As you will see, it was a day of exploration and epiphany...
LRTV Documentaries
Cable Eyeing SDN for Headend, Home Uses

5|26|15   |   05:57   |   (1) comment


CableLabs is looking at virtualizing CMTS and CCAP devices in the headend, as well as in-home devices, says CableLabs' Karthik Sundaresan.
LRTV Documentaries
Verizon's Emmons: SDN Key to Cost-Effective Scaling

5|22|15   |   03:53   |   (0) comments


For Verizon and other network operators to ramp up available bandwidth cost effectively, they need to move to SDN and agree on how to do that.
LRTV Documentaries
Lack of Universal SDN a Challenge

5|21|15   |   04:51   |   (3) comments


Heavy Reading Analyst Sterling Perrin talks about how uncertainty about SDN standards and approaches may be slowing deployment.
LRTV Custom TV
Steve Vogelsang Interview: Carrier SDN

5|20|15   |   05:02   |   (0) comments


Sterling Perrin speaks to Steve Vogelsang, Alcatel-Lucent CTO for IP Routing & Transport business, about the new Carrier SDN-enabling Network Services Platform and the operator challenges it solves.
LRTV Custom TV
Carrier SDN: On-Demand Networks for an On-Demand World

5|20|15   |   20:52   |   (0) comments


Steve Vogelsang, Alcatel-Lucent CTO for IP Routing & Transport business, talks about requirements and benefits of Carrier SDN during the keynote address at the Light Reading Carrier SDN event May 2015.
LRTV Documentaries
The Security Challenge of SDN

5|19|15   |   02:52   |   (0) comments


CenturyLink VP James Feger discusses concerns that virtualization could create new vulnerabilities unless network operators build in safeguards.
LRTV Custom TV
NFV Elasticity – Highly Available VNF Scale-Out Architectures for the Mobile Edge

5|18|15   |   5:50   |   (0) comments


Peter Marek and Paul Stevens from Advantech Networks and Communications Group talk about their NFV Elasticity initiative and the company's latest platforms for deploying virtual network functions at the edge of the network. Packetarium XL and the new Versatile Server Module: 'designed to reach parts of the network that other servers cannot reach.'
LRTV Huawei Video Resource Center
Bay Area Spark Meetup 2015

5|14|15   |   3:54   |   (0) comments


Developed in 2009, Apache Spark is a powerful open source processing engine built around speed, ease of use and sophisticated analytics. This spring, Huawei hosted a meetup for Spark developers and data scientists in Santa Clara, California. Light Reading spoke with organizers and attendees about Huawei's code contributions and long-term commitment to Spark.
LRTV Custom TV
The Transport SDN Buzz

5|12|15   |   06:01   |   (1) comment


Sterling Perrin, senior analyst at Heavy Reading, speaks with Peter Ashwood-Smith of Huawei and Guru Parulkar of ON.Lab about the evolution of transport SDN and the integration of technologies.
LRTV Custom TV
Next-Generation CCAP: Cisco cBR-8 Evolved CCAP

5|5|15   |   04:49   |   (0) comments


John Chapman, Cisco's CTO of Cable Access Business Unit and Cisco Fellow, explained the innovation design of Cisco's cBR-8, the industry's first Evolved CCAP, including DOCSIS 3.1 design from ground-up, distributed CCAP with Remote PHY and path to virtualization. Cisco's cBR-8 Evolved CCAP is the platform that will last through the transitions.
LRTV Custom TV
Meeting the Demands of Bandwidth & Service Group Growth

5|1|15   |   5:35   |   (0) comments


Jorge Salinger, Comcast's Vice President of Access Architecture, explains how DOCSIS 3.1 and multi-service CCAP can meet the demands of the bandwidth and service group growth.
LRTV Custom TV
DOCSIS 3.1: Transforming Cable From Hardware-Defined Network to Software-Defined Network

4|29|15   |   03:48   |   (0) comments


John Chapman, Cisco's CTO of Cable Access Business Unit and Cisco Fellow, explains how DOCSIS 3.1 can transform cable HFC network to a more agile software-defined network.
Upcoming Live Events
June 8, 2015, Chicago, IL
June 9, 2015, Chicago, IL
June 9-10, 2015, Chicago, IL
June 10, 2015, Chicago, IL
September 29-30, 2015, The Westin Grand Müchen, Munich, Germany
October 6, 2015, The Westin Peachtree Plaza, Atlanta, GA
October 6, 2015, Westin Peachtree Plaza, Atlanta, GA
All Upcoming Live Events
Infographics
Procera has gathered facts, stats and customer experience feedback from a survey of 540 users from across the globe.
Hot Topics
10 Alternate Uses for Tablets
Eryn Leavens, Copy Desk Editor, 5/22/2015
Bidding War for TWC Looks Likelier
Alan Breznick, Cable/Video Practice Leader, 5/22/2015
Comcast Targets 6 New Gigabit Markets
Mari Silbey, Senior Editor, Cable/Video, 5/21/2015
Chattanooga Charts Killer Gigabit Apps
Mari Silbey, Senior Editor, Cable/Video, 5/20/2015
Potholes Lurk in Indian Smart City Project
Gagandeep Kaur, Contributing Editor, 5/22/2015
Like Us on Facebook
Twitter Feed
Webinar Archive
BETWEEN THE CEOs - Executive Interviews
With 200 customers in 60 countries, Stockholm-based Net Insight has carved out a solid leadership position in one of the hottest vertical markets going in comms right now: helping service providers and broadcasters deliver video and other multimedia traffic over IP networks. How has Net Insight managed to achieve this success in the face of immense competition from the industry giants?
My ongoing interview tour of the leading minds of the telecom industry recently took me to Richardson, Texas, where I met with Rod Naphan, CTO and SVP, Solutions, ...
I recently popped down to Texas to chat with CEO Eric L. Pratt about his company, Taqua.
Cats with Phones
Too Fluffy to Talk Click Here
Elmer found that his bountiful fur got in the way of meaningful conversation.