SDN NFV Days @ ITB
SDN is merely set of abstractions for control plane: Not a specific set of mechanisms; OpenFlow is only an implementation of the SBI in SDN concept. SDN involves computing a function, NOS handles distribution of state. SDN involves computing a function on an abstract network, services can ignore actual physical infrastructure. Network virtualization is the 'killer app' for SDN.
SDN NFV Days @ ITB (2016):
What Should I Remember About SDN?
SDN is merely set of abstractions for control plane
- Not a specific set of mechanisms
- OpenFlow is only an implementation of the SBI in SDN concept
SDN involves computing a function
- NOS handles distribution of state
SDN involves computing a function on an abstract network
- Can ignore actual physical infrastructure
Network virtualization is the “killer app”
- Already virtualized compute, storage; network is next
Key points to remember
Networks have changed a lot in the last two decades, and we can only expect the evolution to continue as our world becomes more connected. And SDN is no longer just a buzzword for things to come. It is real and happening as we speak.
Many organizations all over the globe and of all sizes are deploying SDN. Why? The simple answer is - because they have to.
In order for companies to meet their customers' changing needs and deliver new services, they must have strong networks that work at the speed of today’s business.
Internet of Things (IoT)
Networks are facing a tipping point with the growth of mobile data and the need to simultaneously operate over multiple transmission technologies, especially wireless. The rise of IoT means that networks will inevitably be handling an influx in big data and an increase in network traffic.
5G Connectivity
With 5G networks, the needs of a wide variety of devices and applications will be met so that IoT service providers or enterprises will not need to worry about the details of the network or radio technologies involved. The variety of these devices and applications requires a highly flexible infrastructure, with its behavior dynamically programmed by software (hence SDN).
Case AT&T
AT&T is aiming to have 30% of its network virtualized this year (2016) and 70% by 2020. That’s quite the timeline. “Why so aggressive?”
“Survival,” was Donovan’s immediate answer, noting that it isn’t just advantageous to be pursuing a virtualization strategy seemingly so quickly – it’s “absolutely necessary,” he added.
“Let me remind you that’s just the WAN.. In our traditional IT environment, which we don’t have any more, in our target architecture there, we are already 60% in the cloud and at the end of the year we will be at 80%. So we are marching into the cloud in every dimension in everything we do, as quickly as we can.”
“.. putting more HW at the network, just isn’t the answer, you can’t scale quickly & cost-effectively. It’s simply not sustainable..”
“Because there is no army that can hold back an economic principle whose time has come”
AT&T Networks on Demand:
- 6 Months from Idea to Trials
- Business as Usual -> Low Automation -> Weeks for Provisioning
- High Automation -> Minutes for Provisioning
References
- Scott Shenker, The Future of Networking and the Past of Protocols
- Nick McKeown, Stanford University, Many Talks/Articles
- Jennifer Rexford, COS 597E, Princeton University
- Guido Appenzeller, Network Virtualization in Multi-tenant Datacenters, VMware
- SDN Today for Tomorrow’s Network
- Telco Transformation