Starting off with a novel idea from a group of researchers at Stanford motivated by the hope for greater network programmability and flexibility, to the relentless hype generated by vendors (and non-operational researchers), the community has been overwhelmed with different interpretations of what software defined networking is, and what actual problems it can solve.
Given the endless list of proposed frameworks, each serving someone’s agenda, which of these can we implement and up to what extent? Are these ideas and proposals that talk about “what we would like to have” in line with “what is actually feasible and practical” given present day technologies and challenges? Do the new ideas require undoing what the industry has worked on for the last 2-3 decades? Do the ideas attempt to solve actual problems? Or is there a need to find a practical compromise between what we would like and what is actually doable?
This tutorial is a high-level attempt at trying to answer a few of the above questions taking into account the reality of closed proprietary vendor implementations, and our hope for an open, programmable and agile network infrastructure. It is an attempt at distinguishing the hype from reality.
This tutorial will be delivered at APAN 45 – please visit the APAN website for full details and to register https://apan45.singaren.net/
Network Engineers and/or Researchers who want to understand more about SDN (Software Defined Network) from a vendor-neutral point of view.
- Emergence and evolution of SDN
- Architectural frameworks for SDN
- SDN controller Northbound interfaces
- SDN use cases
- OpenFlow Versions
- Workings of OpenFlow
Maximum number of attendees