SDN architectures

Verizon Builds Key Vendors Into SDN Strategy

Verizon today unveiled its corporate-wide strategy for moving to SDN, naming five key vendors that are its current partners in the effort and promising "meaningful" deployments across a converged wireless-wireline network by 2016. (See Verizon Outlines SDN Strategy.)

Citing scalability and flexibility for the Internet of Things world and speed to market of new services as its two big drivers, Verizon Communications Inc. (NYSE: VZ) VP-Network Planning Brian Higgins admitted his company's strategy is different from those announced to date because Verizon is working directly with Alcatel-Lucent (NYSE: ALU), Cisco Systems Inc. (Nasdaq: CSCO), Ericsson AB (Nasdaq: ERIC), Juniper Networks Inc. (NYSE: JNPR) and Nokia Networks in developing software-based solutions and strategies.

Companies such as AT&T Inc. (NYSE: T) and NTT Communications Corp. (NYSE: NTT) that have already been aggressively pushing SDN strategies have leaned heavily on their own internal development. (See Ethernet Expo 2012: SDN Is Nothing New at NTT, NTT Reaping Opex Rewards of SDN, AT&T Puts SDN/NFV in Driver's Seat and AT&T Working on Home-Grown SDN Controller for Later in 2014 .)

That doesn't mean the networking giant will be dependent on its partners' traditional hardware, however -- quite the opposite. Higgins says Verizon is coming forward now to make the industry aware of its strategy and vendor plan and is focusing on software from these key partners with a plan to also incorporate commodity hardware and many non-traditional vendors in the effort as well. Verizon is already working with "well north of 20" such non-traditional players, either smaller vendors or those not traditionally part of the telecom mix, he said.

"What we are doing right now and have been doing for some time is working on decomposing all of what we have loosely categorized as the monolithic hardware and software offerings -- deconstructing those and figuring out how we get into software as a primary delivery mechanism," he says. Verizon will not be using any end-to-end vendor ecosystems, he adds.

Verizon's SDN strategy is significant in how it will unify the company's diverse networks, built from a combination of local telco operations, Verizon Wireless and the long-distance network that was once MCI, notes Brian Washburn, service director, Global Business Network and IT Services at Current Analysis .

"This is a really huge announcement giving Verizon's entire roadmap, couched in a fairly innocuous press release," Washburn noted. "Verizon has finally got a strategy to tie together all of its networks. The company finally has a way to pull together its separate wireline, wireless, private IP, Internet and FiOS networks. That means a whole lot of streamlining for Verizon but this gets them to the final place where they can offer truly converged services."

Verizon was considered a pioneer in the early days of SDN discussion but has been relatively quiet in recent years as other companies including AT&T, NTT, Deutsche Telekom AG (NYSE: DT) and others seem to be moving ahead. One possibility, Washburn says, is that the company has simply been less visible in its efforts. Two of its better known public faces in the virtualization space, Stu Elby and Prodip Sen, left the company for vendor jobs, reducing its public profile further. (See Verizon's Elby to Head Infinera's Cloud Team and HP Looks to Conquer Carriers With NFV.)

Want to know more about AT&T's plans for SDN and NFV? Hear Andre Fuetsch, senior vice president, Architecture & Design, deliver a keynote address at Light Reading's second Big Telecom Event on June 9-10 in Chicago. Get yourself registered today or get left behind!

Higgins says today's announcement has been in the works for some time. Verizon is operating three labs, in San Jose, Tampa and Waltham, Mass., and multiple commercial data centers on both coasts. It has numerous proofs of concept in process, working with its five key vendors and the non-traditional partners.

"With this announcement, they have laid out the architecture and reference documents and said they are talking to a bunch of vendors and they're all going to come to a basic agreement," Washburn notes. "But they are doing a whole bunch of things behind that. This is one piece of the roadmap but it's still a roadmap."

Higgins says Verizon is moving some existing services onto the SDN platform now and will be adding new services as well, to be announced later this year and into 2016. The service migration is being made systematically based on the "needs of the network and of the customer," he adds.

"We'll create architecture documents, API documents, just like you would expect, to help our vendor partners understand how they can bring new services into the network and drive that process based upon need" after considering things like capital intensity, reliability and customer expectations.

Verizon is facing the same challenges as other major telecom carriers both in transitioning its existing operations system and in preparing its workforce for the new skills needed in a more IT-intensive world. On the operations front, the company is looking at its BSS/OSS and working through individual transitions "on a network function and service-by-service basis," Higgins says, to map what is in place today to a cloud orchestration and management system for the future.

"None of it has been officially decided," he says.

The Verizon exec says there will be significant announcements to come, including more partners and transitions and peeks at the company's roadmap, which will include significant contributions from Open Source. Verizon hasn't yet chosen specific components such as an OpenStack approach or SDN controller, however.

Washburn sees Verizon's SDN effort as part of a major transition for the entire company that includes a mindset as well as new ways of working. "This isn't just about the technology," he notes. "It's a new way of doing business. Better to get started sooner rather than later."

— Carol Wilson, Editor-at-Large, Light Reading

Page 1 / 2   >   >>
ClientSo14801 5/8/2015 | 12:39:57 PM
It's not just the software... SDN deployment for a provider would have to be a nightmare if the carrier has tons of older equipment patched together in their old legacy infrastructure. Also for customers to realize the true benefits (especially on a global level) the provider must have adequate free bandwidth to allow clients SDN control of their service on the fly without experiencing any quality of serivice issues. Integrating and deploying the SDN software is one thing, transforming your old legacy infrastructure is another.
ajwdctSBU 5/2/2015 | 8:08:25 PM
What version/model of SDN is Verizon implementing? There are atleast 4 viable SDN architecture models:

Overlay-based/ network virtualization- led by VMWare's NSX

ONF Classical Model: strict separation of Control & Data planes, centralized controller, OpenFlow as "Southbound API" between Control & Data plane with OpenFlow controllers/switches

Evolution: Augment existing ndustry-standard protocols (BGP, OSPF, IS-IS) with newer protocols (ECMP, XMPP, VxLAN, etc) and APIs (northbound and southbound)

Bare metal switch with "Open" Network OS: from Cumulus or Big Switch Networks.  The Network OS product also offers many different protocols, including routing (L3), network virtualization, and various L2 features (including VxLAN).   


Does Verizon's SDN conform to any of the above?  It's probably the Augmentation/Evolution model (if any) as VZ is using well known vendor box products.


Note that AT&Ts "SDN" offerings (NetBond and On-Demand Virtual Private LAN) don't relate to any of the above models.

AT&T's "SDN-WAN" as the Network to Access & Deliver Cloud Services

AT&T Taps SDN for New 'Network on Demand' Service


dwx 4/28/2015 | 9:26:27 PM
Re: let's vote Uhh there are NO white boxes currently (or on the horizon) which come close to the scale operators like Verizon need in routers in their networks.  The current white boxes are low buffer Ethernet switches, not routers and they don't make a lot of sense in many parts of the network.  There are ways to scale horizontally but only to a certain extent before it becomes unmanageable, SDN or not.   The highest capacity and lower power NPUs come from Juniper, Cisco, and ALU.  

The reality is the majority of large operator networks still run on large Cisco, Juniper, and ALU routers running OSPF, IS-IS, and MPLS/RSVP-TE and will continue to do so for some time.  

It will be augmented by SDN but I would expect SDN to play a larger role on the service provisioning and network optimization and orchestration side.   
Kenton 4/28/2015 | 2:01:57 PM
Impact on VAR Channel? I'm curious how people think this will impact vendor's indirect pipeline through partners? Clearly direct revenue from major carriers is a primary source of revenue for hardware vendors, but the aggregate of revenue from the channel is also significant, and significantly impacted by cloud migration. While VZ has the resources to build their own end-to-end solutions and relegate vendors to commodity status, is there a substantial enough opportunity for vendors to build solutions that enable VARs on a less commoditized basis? Or is solution-enablement for VARs too complex a proposition to be managed effectively across a constellation of industries?
Mitch Wagner 4/28/2015 | 12:00:41 PM
Re: let's vote Carol - "Cisco, like every other vendor that has depended on hardware for revenue, is going to have to create new business models around its software. That includes new pricing and licensing strategies. But that's not just to get Verizon's business, that's to serve the entire telecom industry."

And Cisco has been doing just that -- unbundling hardware from software for a disaggregaton strategy, and focusing on security, communications, and services. It seems to be a good story, but we shall see how that translates into execution. 
Mitch Wagner 4/28/2015 | 11:58:57 AM
Re: let's vote Vendors can continue to thrive selling boxes -- but there needs to be something terrifically special about the boxes. Juniper is clear that it is specializing in selling high-performance equipment. Could work, if there is sufficient demand for that kind of performance.
brooks7 4/28/2015 | 11:33:45 AM
Re: let's vote I think Cisco has been dealing with this for over 5 years given their exposure to the Enterprise Space.


cnwedit 4/28/2015 | 10:52:33 AM
Re: let's vote Very well said, Ray. 
[email protected] 4/28/2015 | 10:51:16 AM
Re: let's vote Here's the thing - if you used to sell boxes and you still try to sell boxes then you are cooked.

If you used to sell boxes but are on the path to selling software plus professional services that support the deployment of white box elements and still are able to provide some key boxes through what will be a very length migration process, then you stand a chance of surviving the transformation.


So it's no longer business as usual for Cisco, Juniper and lots of other vendors but it can be the start of a new business era for those that can make the change. Revenues and profits may not be what they were but that's one of the great unknowns, right?
cnwedit 4/28/2015 | 10:36:36 AM
Re: let's vote Cisco, like every other vendor that has depended on hardware for revenue, is going to have to create new business models around its software. That includes new pricing and licensing strategies. But that's not just to get Verizon's business, that's to serve the entire telecom industry.

But being at the table for the software discussion is the first step. This isn't necessarily good for bad for Cisco, they still have to execute on the strategy and win their share of the business going forward in teh software era. 

Page 1 / 2   >   >>
Sign In