SDN and NFV value in Business Services. 

Innovations in Network Monetization and Optimization.

* Mazen.Khaddam@cox.com, Loukas@cisco.com

Network Architecture Groups

M. Khaddam*, L. Paraschis

SDN & NFV

SDN = Control Plane Programmability

NFV = Data Plane Programmability

Service Plane Programmability?

Current State of Network Plumbing

3

Cox Packet Layer Network The current state of network technology is:

Expensive • Traffic will continue to increase &

network will experience failures • All service providers network is 2x –

3x overprovisioned to handle failures• The Backbone experiences on

average 3 fiber cuts per month

Inflexible • It is hard to change the number of

logical paths and their speeds dynamically based on services

• It is difficult to delete logical paths when not needed

• Lack of programmability

Complex • Network complexity is increasing• The maintenance of the network is

complicated by using different network operating systems

• Lack of coordination between network layers & services

Layers in an IP/Transport Network

4

IP Traffic Flows

Layer-2 Links (Ethernet, DS1/DS3, etc.)

Layer-2/3 VPN and Carrier Ethernet Services

IP Routing Topology (OSPF,etc.)

MPLS/Virtual Link/Tunnel Layer

VPN A

VPN B

VPN A

VPN B

Transport LayersDigital Channels

(SONET/SDH/OTN)

Source: Designing Multi-Layer Carrier Networks for Capacity and Survivability, OPNET Technologies, Inc., OPNETWORK 2012.

Layer 0

< Data Plane abstractions Only -- where are the control plane abstractions?>

Layer 1

SDN Defined Source: ONF

According to ONF SDN is a network in which the control plane is physically separate from forwarding plane. The SDN architecture must open, programmable & standard.

SDN Proposition value– Network automation– Optimization– Flexibility & efficiency

The Benefits of SDN – Provides more control – Enable programing – Better Guarantees

SDN as defined by Open Network Foundation

Traditional

controlcontrol

control

control control

coordination primitivesprotocols

Source: Bruce Davie , Principle Engineer VMware , ONS 2013

SDN

NFV based on ETSI: Separate network function from Hardware : Source ETSI

• Move functions from hardware to software• Leverage COTS • Reduced equipment costs and reduced

power consumption• Increased speed of Time to Market• Scale up/down dynamically

• Purpose hardware to support defined functions

• Difficult to scale to handle unscheduled events

• Expensive

NFV ArchitectureSource: ETSI

8

Hydrogen Release: OpneDaylightt Source: SDN Hub

Base Network Service Functions

Management GUI/CLI

Controller Platform

Southbound Interfaces& Protocol Plugins

OpenDaylight APIs (REST)

DOVE Mgr

Data Plane Elements(Virtual Switches,Physical Device

Interfaces)

Service Abstraction Layer (SAL)(plug-in mgr., capability abstractions, flow programming, inventory, …)

OpenFlow

1.0 1.3LISP

Topology Mgr

Stats Mgr

Switch Mgr

Host Tracker

Shortest Path

Forwarding

VTN Coordinator

Affinity Service

Network Applications Orchestration & ServicesOpenStack

Neutron

OpenFlow Enabled Devices

VTN Manager

VTN: Virtual Tenant NetworkDOVE: Distributed Overlay Virtual EthernetDDoS: Distributed Denial Of ServiceLISP: Locator/Identifier Separation ProtocolOVSDB: Open vSwitch DataBase ProtocolBGP: Border Gateway ProtocolPCEP: Path Computation Element Communication ProtocolSNMP: Simple Network Management Protocol

LISP Service

NETCONF BGP-LS

Additional Virtual & Physical Devices

SNMP

DDoS Protection

Open vSwitches

OVSDB PCEP

OpenStack Service

NetworkConfig

Main difference from other OpenFlow-centric controller platforms

Core

Long Haul DWDM

Service Provider SDN use cases Data CentreMetro and AccessCPE

Metro DWDM

Data Centre

Virtualized n/w

Virtual 2 virtual n/w interconnect

Service chaining appliances

Analytics collection

Core Infrastructure

Bandwidth calendaring

Demand engineering / PCE

Single/multi layer optimization

Analytics collection

Agg and access Infrastructure

Automated set-up

Analytics collections

Service definition

Optimization

CPE

NFV

Services

provisioning

Analytics

Edge

Edge

NFV

Services

Provisioning

Analytics

Control Program/Manager A

Control Program/Manager B

Example: Network Virtualization

Virtualization Associated SDN/Network Function Virtualization

OF-Agent

App App App

Example: Open Flow - centricController & Agent

Flow based SDN

Example: Path Computation

PCC PCC PCC

PCEP

Applicability to market segment

Metros BBData Centre

Applicability to market segmentApplicability to market segment

Infrastructure Controller based SDN

SDN and NFVCategorizing current SDN/NFV ModelsSDN & NFV Use Cases

OF Agent OF Agent

Network Plumbing: Infrastructure Controller

Topology ConfigBGP

v4/v6

Optimization / Analytics Algorithms

Infrastructure ControllerUtilization

Packet Network

Traffic Matrix

Optical Network

Device Level APIsOpenFlow, I2RS, SNMP, Netconf, CLI ,PCEP

Application and Sub-Systems

Application API

Google B4, SDN Global WAN

SDN Optimization & Automation with PCEGoogle B4, SDN Global WAN

Microsoft SWAN: Software-defined networkingSource: Stanford University networking Seminar – Tested-Based Evolution

Hong Kong

Seoul

Seattle

Los Angeles

New York

Miami

Dublin

Barcelona

WAN

Network Agent

Service broker

Traffic demand

BW allocation Network, Config

Topology, traffic

Rate limiting

Cox Case Study: SDN – PCE vs Distributed path Compution

1 7 13 19 25 31 37 43 49 55 61 67 73 79 85 91 97 103 109 115 121 127 133 139 145 151 157 163 169 175 181 187 193 199 205 211 217 223 229 2350.00%

10.00%20.00%30.00%40.00%50.00%60.00%70.00%80.00%90.00%

100.00%

Path Compuation Model

Online PCE

Links

Link

Util

izati

on

WAN Controller - Use-Case example Bandwidth Scheduling (On-Demand)

16

Controller

NB API

WAN

R1

R2

R3

1

4

Data Center #1 Data Center #2

① Network conditions reported tocollector

② Cust requests DC #1 – DC #2 bandwidth asap

③ Demand admission request:<R1-R3, B/W, NOW!!>

④ SDN WAN returns option andcust confirms

⑤ R1-R3 LSP Tunnel Programmedvia PCEP

2

Web Portal

Congested!!

3

PCEP

5

Collector & modelling

Programming

NFV use cases - vPE to VPN mapping

SP WAN

SP Data CenterWAN Controller

Collector Programming

Cloud Controller

DC WAN Gateway DC

Fabric

Server

ServerTenant 1 VM

Tenant 2 VM

Tenant 1 VM

Tenant 1 VM

vPEF

VRF1

vPEF

VRF2

VRF1VRF1

VRF2VRF1

VRF2

VRF3

Server

Tenant 2 VM

Tenant 3 VM

vPEF

VRF3

VRF2

VRF3

BGP MPLS VPNs extended into the DC

17

SDN “southbound” Automation of Service & Network Programmability – YANG/NETCONF