This team presentation was part of "Advance Networking" course in my postgraduate studies, and its about SDN technology in the WAN domain. "Applying Software-Defined Networking to the Telecom Domain" paper was our main source of information. This paper authors are Georg Hampel, Moritz Steiner and Tian Bu Bell Labs – Alcatel-Lucent , Murray Hill, from New Jersey-USA

1. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Advanced Computer Networks
ECE 540
Team
Husain Al Yusuf
Alejandro Flores
Mustafa Al Mashhadani
Applying Software-Defined
Networking to the Telecom Domain

2. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
What is SDN
?
What is SDN
Magic ?!

3. Wikipedia
• …. decoupling the
system that makes
decisions about where
traffic is sent (control
plane) from the
underlying systems that
forwards traffic to the
selected destination
(data plane)….
NetworkWorld
• … focuses somewhat
less on decoupling and
more on providing
programmatic interfaces
into network
equipment, whether or
not there is a separation
of the control and
forwarding planes
CISCO
• Simplified Operation
• Enhanced Agility
• New Business
Opportunity
UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
SDN Definition

4. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering

5. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
What is SDN
Magic ?!

6. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
SDN Components
• Programmable approach to network
multi-tenancy within the datacenter
Network
Virtualization
• Software that makes policy decisions
within the network. (Control Plane)Controller
• Programing interfaces between
‘applications’ and Controller.
Application API
(Northband API)
• Programming interfaces between
Controller and physical or virtual
network device (OpenFlow)
Data Plan API
(Southband API)

7. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering

8. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Virtualization
Controller
Forwarding

9. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Applying SDN to the Telecom Domain
• Objective
• Apply SDN on telecommunication domain
• Main Challenges
• Legacy infrastructure constrains
• Others…
• How to Implement SDN
• “ SDN - Vertical Forwarding “
• Definition: extend the concept of SDN to controller-programmed
en-/de-capsulation operations on top of IP

10. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering

11. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Gateway-based
Architecture
-vs-
SDN-based Architecture

12. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Gateway-based Architecture
Control
Plane
Data
Plane

13. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Limitations of the
Gateway-based
Architecture?

14. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Gateway-based Architecture Limitations
Complexity
Complexity that leads to stasis: any change must be done
everywhere. (ACLs, QOS, FW … )
• Scalability
Inability to scale; causing new investment! Must upgrade
hardware to get new features.
• Proprietary
Vendor dependence (i.e. proprietary) or lack of openness.

15. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Gateway-based Architecture Limitations
Slow failure recovery time.

16. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Gateway-based Architecture
Limitations
Inflexible and hard to upgrades (takes time)

17. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
What is the
alternative?

18. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Alternative to Gateway-based Architecture
SERVER
STORAGE
Separation of functions:

19. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
SDN-based Architecture
Separate functionality into two:
• Control Plane - Makes the forwarding decisions
(brain)
• Data Plane – Does the actual forwarding
(workhorse)
Control
Plane
Data
Plane
FE
CE

20. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
SDN-based Architecture
• Optimized for high throughput
• Control function can be virtualized
• Ease of upgrading the control plane
without affecting the FE’s.
• Omits all inter-gateway signaling
protocols
• Reduces routing update and
network status traffic
Why SDN?

21. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Gateway-based Architecture
Faster failure recovery time
Controller

22. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
SDN-based Architecture
Offers the option to distribute the controller function over
multiple nodes.

23. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
How do we fade
out the old
technology?

24. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
SDN and Gateway-based Architecture
Can interoperates with legacy gateways and allows
incremental deployment.

25. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
What is
OpenFlow?

26. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
OpenFlow
What is OpenFlow?
• It defines the open communications protocol in SDNs
that enables the Controller to interact with the
forwarding plane and make adjustments to the
network.

27. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
OpenFlow
•Basic Idea: Separate Control from Data path
The switch and controller communicate via
OpenFlow protocol.

28. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
OpenFlow
•Does all routers and switches support
OpenFlow?
OpenFlow is option that you can add to
switch or router
Most of today routers and switches
support OpenFlow

29. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
OpenFlow With Vertical SDN
•Do we need to make changes to OpenFlow in
order to support Vertical SDN ?
•Header
Additional flow match types
With the corresponding flow match
fields on encapsulation headers.

30. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
•Do we need to make changes to OpenFlow
in order to support Vertical SDN ?
•Protocol
Extensions to enable en- and
decapsulation operations.
Represented as actions after flow
matching.

31. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
•Push and POP operations
When pushing or popping ESP and AH,
information about the flow’s security policies
and security associations have to be provided.
Some of this information is already supplied by
OpenFlow
•Do we need to make changes to OpenFlow
in order to support Vertical SDN ?

32. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
•Integrate Distributed routing protocols into
openflow’s controller operation.
•Do we need to make changes to OpenFlow
in order to support Vertical SDN ?

33. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Use Cases
•Does the vertical SDN applicable only with telecom
domain?
•We can benefit from this architecture in other
applications:
I. IETF Mobility protocol
II. 3GPP UMTS & SAE
III. Wireline Broadband networks
IV. Virtual Private Networks and Secure Links
V. IP protocol transition

34. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
VPN
•VPN’s are used to interconnect individual hosts
with a security gateway (Tunnel).

35. `
UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
VPN
•Using SDN architecture:
The signaling protocol falls into the realm of
the controller
The keys will not be exchanged over the
network.

36. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Final Thoughts on SDN

37. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Implications of
Change
Final Thoughts on SDN

38. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
$$ Marketing $$
Final Thoughts on SDN

39. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Vulnerability
Final Thoughts on SDN

40. UNM Electrical and Computer Engineering DepartmentUNM Electrical and Computer Engineering
Final Thoughts on SDN