Ethernet & SDN Expo

ESDN: AT&T Calls for SDN APIs Now

NEW YORK — Ethernet & SDN Expo — AT&T is developing application programming interface (API) specifications for software defined networking (SDN), and network functions virtualization (NFV) that will use a common language, but won't necessarily be open, Margaret Chiosi, distinguished network architecture and NFV Forum representative told the Ethernet and SDN Expo keynote crowd today.

At the same time, AT&T Inc. (NYSE: T) is pursuing open-source APIs, realizing these may be available in advance of any industry standards, she said. Because SDN and NFV are considered the key technologies to build a truly next-generation network, AT&T will adopt whichever approach enables APIs as soon as possible.

"We need APIs today that are common," Chiosi added. "If standards are taking too long, maybe the open-source community is the way to go. So, both will be pursued."

Chiosi Chat
Margaret Chiosi, distinguished network architect at AT&T and Network Functions Virtualization Forum representative, talks SDN and NFV to the ESDN crowd.
Margaret Chiosi, distinguished network architect at AT&T and Network Functions Virtualization Forum representative, talks SDN and NFV to the ESDN crowd.

AT&T's API specifications will enable an SDN architecture that is not necessarily open, but that uses a common language, and is programmable, centralized, agile, and cost effective. In fact, the reason AT&T is so keen on SDN at all is that it enables the carrier to make money faster. "We don’t try new technologies for the sake of new technologies," Chiosi quipped.

Chiosi said AT&T also needs APIs related to both service abstractions and network abstractions, for SDN controllers, both northbound and southbound, and for the all-important MANO [management and organization] layer for NFV.

Right now, there are too many standards, Chiosi said. AT&T's goal is to be common, rather than open or commoditized, but to be able to differentiate. "You need a common language to define an information data model," she explained.

Chiosi also addressed the Ethernet Expo crowd at last year's show, so she used Wednesday's presentation to check up on her assertions from last year. While AT&T's priorities remain the same, there is a lot more urgency to element SDN sooner rather than later, but, she said, the industry is still a long ways from having a clear view of what the equipment and interfaces for SDN will look like. (See AT&T Has High Hopes for SDN.)

"It's too early," Chiosi admitted. "We are all over the place. There's lots of good debate and ideas, but no convergence yet."

— Sarah Reedy, Senior Editor, Light Reading

dwx 10/2/2013 | 11:22:05 PM
Re: An OpenStack shoe-in? OpenStack has nothing to do with SDN and NFV other than providing a virtual compute platform with some hooks into which SDN can operate. The behind the scenes plugins for OpenStack are pretty much hacks and I don't think those interfaces are well developed.
Atlantis-dude 10/2/2013 | 8:02:55 PM
Common but not open That sounds like ONF. But the only information model they have is for OF. Is that good enough to define all the abstractions for NFV ?
Dredgie 10/2/2013 | 5:16:24 PM
An OpenStack shoe-in? Is this a signal to stop messing around and (at a minimum) select Nova and Neutron as the reference interface between VNF manager and VNF/EMS and the VI Manager and VI, respectively, as the CloudNFV gang are suggesting?
Sign In