You can have SDN without NFV, but you can't have NFV without SDN – not if you want greater service agility and new revenue streams, said the head of the Open Networking Foundation.
Speaking at the SDN & Openflow Asia-Pacific Congress in Hong Kong Wednesday, ONF executive director Dan Pitt said that while the foundation is committed to working with the ETSI NFV ISG to help develop NFV, he warned operators that NFV is only a partial solution to the overall problem of virtualizing telecom networks to make them more agile and programmable.
“There are complaints from so many operators that they have so many appliances – as many as they have switches and routers – so they want to get rid of those,” Pitts said. “But it’s only a partial solution to take an appliance out of the network and replace it with a bare-metal server running Linux, because they still require separate management and because they’re out in the field, it’s a whole maintenance question.”
Pitt said that NFV will help operators dramatically reduce capex, but not opex, and it doesn’t really enable service agility and new revenue streams the way SDN does.
Pitt also argued that NFV has a limited shelf life on its own because certain network functions will eventually become obsolete as networks become primarily software-driven.
“I think we’re going to get a lot of mileage out of NFV for about ten years, and after that we’re going to realize that we’re just virtualizing artifacts of the old hardware-defined networking days, and we don’t need to perpetuate those any longer,” he said. “We’re going to have applications that need certain kinds of connectivity – that’s what the network does – and we’ll eliminate all the intermediate artifacts.”