jain sdn tutorial

8/11/2019 Jain Sdn Tutorial

http://slidepdf.com/reader/full/jain-sdn-tutorial 1/90

1http://www.cse.wustl.edu/~jain/tutorials/icc14.htmWashing ton University in St. Louis

OpenFlow, Software DefinedOpenFlow, Software DefinedNetworking (SDN) and NetworkNetworking (SDN) and Network

Function Virtualization (NFV)Function Virtualization (NFV)

Raj Jain Washington University in Saint Lou

Saint Louis, MO [email protected]

These slides and audio/video recordings of this tuhttp://www.cse.wustl.edu/~jain/tutorials/icc

SDN = Separati

Data

SDN=OpenFlow

SDN = CentralizSDN=Standard Southbound API

http://icc2014.ieee-icc.org/2014/private/programTutorials.htm

http://icc2014.ieee-icc.org/2014/private/programTutorials.html






2http://www.cse.wustl.edu/~jain/tutorials/icc14.htmWashington University in St. Louis

OverviewOverview

1. OpenFlow and Tools

2.

Software Defined Networking (SDN)

3.

Network Function Virtualization (NFV)




3

http://www.cse.wustl.edu/~jain/tutorials/icc14.htmWashing ton University in St. Louis

Part I: OpenFlow and ToolsPart I: OpenFlow and Tools

Planes of Networking

OpenFlow

OpenFlow Switches including Open vSwitch

OpenFlow Evolution

OpenFlow Configuration Protocol (OF-Config)

OpenFlow Notification Framework

OpenFlow Controllers








4


Part II: Software Defined NetworkingPart II: Software Defined Networking

What is SDN?

Alternative APIs: XMPP, PCE, ForCES, ALTO

OpenDaylight SDN Controller Platform and Tool








5


Part III: Network Function VirtualizationPart III: Network Function Virtualization

What is NFV?

NFV and SDN Relationship

ETSI NFV ISG Specifications

Concepts, Architecture, Requirements, Use cases

Proof-of-Concepts and Timeline








6


Part I: OpenFlow and ToolsPart I: OpenFlow and Tools

Planes of Networking

OpenFlow

OpenFlow Operation

OpenFlow Evolution

OpenFlow Configuration Protocol (OF-Config)

OpenFlow Notification Framework

OpenFlow Controllers








7


Planes of NetworkingPlanes of Networking

Data Plane : All activities involving as well asresulting from data packets sent by the end user, e

Forwarding

Fragmentation and reassembly

Replication for multicasting

Control Plane : All activities that are necessary plane activities but do not involve end-user data p

Making routing tables

Setting packet handling policies (e.g., security

Base station beacons announcing availability o

Ref: Open Data Center Alliance Usage Model: Software Defined Networking Rev 1.0,”

http://www.opendatacenteralliance.org/docs/Software_Defined_Networking_Master_Usage_Model_Re





http://www.opendatacenteralliance.org/docs/Software_Defined_Networking_Master_Usage_Model_Rev1.0.pdf



http://www.opendatacenteralliance.org/docs/Software_Defined_Networking_Master_Usage_Model_Rev1.0.pdf



8

http://www.cse.wustl.edu/~jain/tutorials/icc14.htmWashington University in St. Louis

Planes of Networking (Cont)Planes of Networking (Cont)

Management Plane : All activities related to provisioning and monitoring of the networks

Fault, Configuration, Accounting, Performanc(FCAPS ).

Instantiate new devices and protocols (Turn de

Optiona l May be handled manually for sm

Services Plane : Middlebox services to improve security, e.g.,

Load Balancers, Proxy Service, Intrusion DeteFirewalls, SSL Off-loaders

Optional Not required for small networks



9


Data vs. Control LogicData vs. Control Logic

Data plane runs at line rate,e.g., 100 Gbps for 100 Gbps Ethernet Fast P

Typically implemented using special hardwaree.g., Ternary Content Addressable Memories (TC

Some exceptional data plane activities are handle

in the switch Slow path e.g., Broadcast, Unknown, and Multicast (BUM)

All control activities are generally handled by CP

Control Logic

Data Logic



10


OpenFlow: Key IdeasOpenFlow: Key Ideas

1.

Separation of control and data planes2.

Centralization of control3.

Flow based control

Ref: N. McKeown, et al., ``OpenFlow: Enabling Innovation in Campus Networks," ACMVol. 38, No. 2, April 2008, pp. 69-74.



11


History of OpenFlowHistory of OpenFlow

2006: Martin Casado, a PhD student at Stanford and team

propose a clean-slate security architecture (SANE) whiccentralized control of security (in stead of at the edge as Ethane generalizes it to all access policies.

April 2008: OpenFlow paper in ACM SIGCOMM CCR

2009: Stanford publishes OpenFlow V1.0.0 specs

June 2009: Martin Casado co-founds Nicira

March 2010: Guido Appenzeller, head of clean slate labfounds Big Switch Networks

March 2011: Open Networking Foundation is formed

Oct 2011: First Open Networking Summit.Juniper, Cisco announce plans to incorporate.

July 2012: VMware buys Nicira for $1.26B

Nov 6, 2013: Cisco buys Insieme for $838MRef: ONF, “The OpenFlow Timeline, ”

http://openflownetworks.com/of_timeline.php







Separation of Control and Data PlaneSeparation of Control and Data Plane

Control logic is moved to a controller

Switches only have forwarding elements

One expensive controller with a lot of cheap sw

OpenFlow is the protocol to send/receive forwafrom controller to switches

Control

DataSwitch

ForwardingElement

ForwardingElement

ForwardingElement

ForwardingElement

OpenFlow




OpenFlow V1.0OpenFlow V1.0

On packet arrival, match the header fields with flotable, if any entry matches, update the counters inentry and perform indicated actions

Ref : http://archive.openflow.org/documents/openflow-spec-v1.0.0.pdf

Header Fields Counters Actions

Ingress

PortEther

SourceEther

DestVLAN

IDVLAN

PriorityIP

SrcIP

DstIPProto



… … …

Flow Table:

http://archive.openflow.org/documents/openflow-spec-v1.0.0.pdf






* * 0A:C8:* * * * * * * * *

* * * * * * * 192.168.*.* * * * * * * * * * * * * * 21* * * * * * * * 0x806 * * * * * * * * * * 0x1* * *

Flow Table ExampleFlow Table Example

Ref: S. Azodolmolky, "Software Defined Networking with OpenFlow," Packt Publishing, October 2013,ISBN:978-1-84969-872-6 (Safari Book)

P or t S r c MA

C

D s t MA

C

E t h e r T y p e

VL A

NI D

P r i or i t y

S r c I P

D s t I P

I P P r o t o

I P T

o S

S r c L4 P or t

I C MP T

y p e

Idle timeout: Remove entry if no packets received

Hard timeout: Remove entry after this time

If both are set, the entry is removed if either one e




MatchingMatchingSet Input Port

Ether SrcEther DstEther TypeSet all others to zero

Set VLAN IDSet VLAN PriorityUse EtherType in VLAN tagfor next EtherType Check

Set IP Src, IP DstIP Proto, IP ToS

from within ARP

EtherType

=0x8100?

Set IP Src, IP DstIP Proto, IP ToS

IP Proto=6 or 17

Not IPFragment?

IP Proto=1?

EtherType

=0x0806?

EtherType

=0x0800?

Packet lookupusing assignedheader fields

Y

Y

Y Y

N

N

N N N

N

MatchTable 0

MatchTable n

N

N

Tagged

ARP

IP

IC

TU




CountersCounters

Per Table Per Flow Per Port Per QuActive Entries Received Packets Received Packets TraPacket Lookups Received Bytes Transmitted Packets TranPacket Matches Duration (Secs) Received Bytes Tra

Duration (nanosecs) Transmitted Bytes

Receive DropsTransmit DropsReceive ErrorsTransmit ErrorsReceive FrameAlignment Errors

Receive OverrunerorrsReceive CRCErrorsCollisions



17


ActionsActions

Forward to Physical Port i

or to Virtual Port :

All : to all interfaces except

incoming interfa

Controller : encapsulate and send to controlle

Local : send to its local networking stack

Table : Perform actions in the flow table

In_port : Send back to input port

Normal : Forward using traditional Ethernet

Flood : Send along minimum spanning tree exincoming interface

Enqueue: To a particular queue in the port

Drop

Modify Field: E.g., add/remove VLAN tags, ToS TTL



18


Actions (Cont)Actions (Cont)

Masking allows matching only selected fields,

e.g., Dest. IP, Dest. MAC, etc.

If header matches an entry, corresponding actions aand counters are updated

If no header match, the packet is queued andthe header is sent to the controller, which sends a neSubsequent packets of the flow are handled by this

Secure Channel: Between controller and the switch

Modern switches already implement flow tables, tyTernary Content Addressable Memories (TCAMs)

Controller can change the forwarding rules if a clie

Packets for mobile clients are forwarded correc

Controller can send flow table entries beforehand (Send on demand ( Reactive ). OpenFlow allows bo



19


Hardware OpenFlow SwitchesHardware OpenFlow Switches

Arista 7050

Brocade MLXe, Brocade CER, Brocade CES

Extreme Summit x440, x460, x670

Huawei openflow-capable router platforms

HP 3500, 3500yl, 5400zl, 6200yl, 6600, and 8200style L3 hardware match platform)

HP V2 line cards in the 5400zl and 8200zl (the nehardware match platform)

IBM 8264

Juniper (MX, EX)

NEC IP8800, NEC PF5240, NEC PF5820

NetGear 7328SO, NetGear 7352SO

Pronto (3290, 3295, 3780) -

runs the shipping p

Switch Light platform



20


Software OpenFlow SwitchesSoftware OpenFlow Switches

Indigo : Open source implementation that runs on physical switches and uses features of the ASICs to ru

LINC : Open source implementation that runs on LinuWindows, MacOS, and FreeBSD

Pantou : Turns a commercial wireless router/access pOpenFlow enabled switch. OpenFlow runs on OpenW

generic Broadcom and some models of LinkSys and T points with Broadcom and Atheros chipsets.

Of13softswitch : User-space software switch based oTrafficLab 1.1 softswitch

XORPlus : Open source switching software to drive h

ASICs. Supports STP/RSTP/MSTP, LCAP, QoS, VLAOSPF/ECMP, RIP, IGMP, IPv6, PIM-SM

Open vSwitchRef : http://www.openvswitch.org/ , http://www.projectfloodlight.org/indigo/ , http://flowforwardinhttp://github.com/CPqD/openflow-openwr t, http://cpqd.github.io/ofsoftswitch13/ , http://sourcefor

http://www.openvswitch.org/



http://www.projectfloodlight.org/indigo/



http://flowforwarding.github.io/LINC-Switch/

http://github.com/CPqD/openflow-openwrt

http://cpqd.github.io/ofsoftswitch13/




http://sourceforge.net/projects/xorplus




http://github.com/CPqD/openflow-openwrt

http://flowforwarding.github.io/LINC-Switch/





21


Open vSwitchOpen vSwitch

Open Source Virtual Switch

Nicira Concept

Can Run as a stand alone hypervisor switch or as switch across multiple physical servers

Default switch in XenServer 6.0, Xen Cloud Platfsupports Proxmox VE, VirtualBox, Xen KVM

Integrated into many cloud management systems OpenStack, openQRM, OpenNebula, and oVirt

Distributed with Ubuntu, Debian, Fedora Linux. A

Intel has an accelerated version of Open vSwitch Data Plane Development Kit (DPDK)

Ref : http://openvswitch.org/

http://openvswitch.org/





22


Open vSwitch FeaturesOpen vSwitch Features

Inter-VM communication monitoring via:

NetFlow : Cisco protocol for sampling and costatistics (RFC 3954)

sFlow : Similar to NetFlow by sflow.org (RFC

Jflow : Juniper’s version of NetFlow

NetStream : Huawei’s version of NetFlow

IPFIX : IP Flow Information Export Protocol IETF standard for NetFlow

SPAN, RSPAN : Remote Switch Port Analyzmirroring by sending a copy of all packets to a

GRE-tunneled mirrors : Monitoring deviceconnected to the switch via a GRE tunnel



23


Open vSwitch Features (Cont)Open vSwitch Features (Cont)

Link Aggregation Control Protocol (LACP)

IEEE 802.1Q VLAN

IEEE 802.1ag Connectivity Fault Management (C

Bidirectional Forwarding Detection (BFD) to dete(RFC 5880)

IEEE 802.1D-1998 Spanning Tree Protocol (STP

Per-VM traffic policing

OpenFlow

Multi-table forwarding pipeline

IPv6

GRE, VXLAN, IPSec tunneling

Kernel and user-space forwarding engine options



24


OVSDBOVSDB

Open vSwitch Database Management Protocol (O

Monitoring capability using publish-subscribe me

Stores both provisioning and operational state

Java Script Object Notation (JSON) used for scheand for JSON-RPC over TCP for wire protocol (R

<database-schema>“name”: <id>“version”: <version>“tables”: {<id>: <table-schema>,…}

RPC Methods: List databases, Get Schema, Upda

Open vSwitch project includes open source OVSDserver implementations

Ref: B. Pfaff and B. Davie, “The Open vSwitch Database Management Protocol,”

IETF draft, Oct http://tools.ietf.org/html/draft-pfaff-ovsdb-proto-04

C

OVSD

OV

http://tools.ietf.org/html/draft-pfaff-ovsdb-proto-04

http://tools.ietf.org/html/draft-pfaff-ovsdb-proto-04





V1: Perform action on a match. Ethernet/IP only. Did not cover MPLS, Q-in-Q, ECMP, and efficien

V1.1 Introduced Table chaining,

Group Tables, MPLS Label

and MPLS traffic class

to match f

Table Chaining : On a match, instruction may b

Immediate actions: modify packet,update match fields and/or

Update action set, and/or

Send match data and action set to Table n,

Go to Group Table

entry n

Table 1 Table 2 Table 3 Table nAction Set = {} Action Set = {1}



26


OpenFlow V1.1 (Cont)OpenFlow V1.1 (Cont)

On a miss, the instruction may be to send packet t

or continue processing with the sequentially next

Group Tables: each entry has a variable number o

All : Execute each bucket. Used for Broadcast

Select : Execute one switch selected

bucket.mirroring. Selection may be done by hashing

Indirect : Execute one predefined

bucket.

Fast Failover : Execute the first live bucket

New Features supported:

Multipath : A flow can be sent over one of se

MPLS : multiple labels, traffic class, TTL, pu

Q-in-Q : Multiple VLAN tags, push/pop VLA

Tunnels : via virtual portsRef : http://archive.openflow.org/documents/openflow-spec-v1.1.0.pdf






27



1.

IPv6 Support : Matching fields include IPv6 sodestination address, protocol number, traffic clastype, ICMPv6 code, IPv6 neighbor discovery heand IPv6 flow labels.

2.

Extensible Matches : Type-Length-Value (TLV

Previously the order and length of match fields w3.

Experimenter extensions

through dedicated f points assigned by ONF

Ref : https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openf

https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-spec-v1.2.pdf





28


OpenFlow 1.3OpenFlow 1.3

IPv6 extension headers : Can check if Hop-by-

Fragmentation, Destination options, AuthenticatioSecurity Payload (ESP), unknown extension head present

MPLS Bottom-of-Stack bit

matching

MAC-in-MAC

encapsulation

Tunnel ID meta data : Support for tunnels (VxL

Per-Connection Event Filtering : Better filtericonnections to multiple controllers

Many auxiliary connections

to the controller a parallelism

Better capability negotiation : Requests can spmessages

More general experimenter capabilities

allow

A separate flow entry for table miss actionsRef : https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openf

https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-spec-v1.3.0.pdf







29



Cookies : A cookie field is added to messages co packets sent to the controller. This helps controllemessages faster than if it had to search its entire d

Duration : Duration field has been added to mostcompute rates.

Per-flow counters can be disabled to improve perf

Per Flow Meters and meter bands

Meter : Switch element that can measure and con packets/bytes.

Meter Band : If the packet/byte rate exceeds threshold the meter has triggered the band

A meter may have multiple bands





If on triggering a band the meter drops the paccalled rate limiter.

Other QoS and policing mechanisms can be dthese meters

Meters are attached to a flow entry not to a qu

Multiple flow entries can all point to the same

Match Fields Priority Counters Instructions Timeouts Time

Meter ID Meter Bands Counters

Band Type Rate Counters Type Specific Argume

1. Drop

2. Remark DSCPkb/s

Burst

New Instruction: Meter Meter_ID



31



Optical ports : Configure and monitor transmit afrequencies of lasers and their power

Improved Extensibility : Type-Length-Value (Tat most places Easy to add new features in fu

Extended Experimenter Extension API : Can

ports, tables, queues, instructions, actions, etc.

More information when a packet is sent to contromatch, invalid TTL, matching group bucket, matc

Controllers can select a subset of flow tables for m

Switches can evict

entries of lower importance i

Switches can notify controller if table is getting fu

Atomic execution of a bundle

of instructions

Ref : https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openf









OpenFlow Evolution SummarOpenFlow Evolution Summar

Dec 2009V1.0

Feb 2011V1.1

Dec 2011

V1.2Apr 2012

V1.3Jun 2012V1.3.1

Sep 20V1.3

Single Flow Table

Ethernet/IPv4

IPv6 TLV matching

Multiple controllers Bug Fix

MPLS, Q-in-QEfficient multicastECMP

Multiple Tables

MAC-in-MACMultiple channels

between switchand controller



33

http://www.cse.wustl.edu/~ja in/tutorials/icc14.hWashington University in St. Louis

BootstrappingBootstrapping

Switches require initial configuration: Switch IP aController IP address, Default gateway

Switches connect to the controller

Switch provides configuration information about

Controller installs a rule to forward LLDP packetand then sends, one by one, LLDP packets to be si (i=1, 2, …, n) which are forwarded to respectiveThe neighbors send the packets back to controller

Controller determines the topology from LLDP p

LLDP is a one-way protocol to advertise the capafixed intervals.

Ref: S. Sharma, et al., “Automatic Bootstrapping of OpenFlow Networks,”

19 th

IEEE Workshop onhttp://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6528283

(Available t o subscribers only

http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6528283










OpenFlow Configuration ProtocolOpenFlow Configuration Protocol(OF(OF --ConfigConfig ))

OpenFlow Control Point : Entity that configurswitches

OF-Config : Protocol used for configuration and of OpenFlow Switches.

Assignment of OF

controllers so that switches cconnections to them:

IP address of controller

Port number at the controller

Transport protocol:TLS or TCP

Configuration of queues

(min/max rates) and ports

Enable/disable receive/forwardspeed, media on ports

OpenFlowConfiguratio

Point

OF-Config

Operational Con

Ref: Cisco, “An Introduction to OpenFlow,”

Feb 2013,http://www.cisco.com/web/solutions/trends/open_network_environment/docs/cisco_one_webcastan_introduction_to_openfl

http://www.cisco.com/web/solutions/trends/open_network_environment/docs/cisco_one_webcastan_introduction_to_openflowfebruary142013.pdf

http://www.cisco.com/web/solutions/trends/open_network_environment/docs/cisco_one_webcastan_introduction_to_openflowfebruary142013.pdf




OFOF --ConfigConfig

(Cont)(Cont)

A physical switch = one or more logical

switcheach controlled by an OF Controller

OF-Config

allows configuration of logical switch

OF Logical

Switch

OF-Config OpenFlowProtocol

OF Capable Switch

OF Logical

Switch

OpenFlow

Configuration

Point

OpenFlow

Controller

…

Ref: ONF, “OpenFlow Management and Configuration Protocol (OF-Config

1.1.1),”

March 23, 20https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow-c

https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow-config/of-config-1-1-1.pdf




36


OFOF --ConfigConfig

ConceptsConcepts

OF Capable Switch : Physical OF switch.Can contain one or more OF logical switches.

OpenFlow Configuration Point : configuration

OF Controller : Controls logical switch via OF p

Operational Context : OF logical switch

OF Queue : Queues of packets waiting for forwa

OF Port : forwarding interface. May be physical

OF Resource : ports, queues, certificates, flow taresources of OF

capable switches assigned to a

Datapath

ID : 64-ID of the switch. Lower 48-bitMAC address, Upper 16-bit assigned by the opera



37


OFOF --ConfigConfig

EvolutionEvolution

V1.0 (Jan 2012): Based on OpenFlow V1.2

Assign controllers to logical switches

Retrieve logical switch configurations

Configure ports and queues

V1.1 (May 2012): Based on OpenFlow V1.3

Configuration of certificates

Capability Discovery: Retrieve logical switch

Configure logical tunnels (VXLAN, NVGRE,

V1.1.1 (Jan 2013): Bug Fix. Versioning support

V1.2: Based on OpenFlow V1.4

Simple topology Detection

Assigning resources to logical switchesRef : https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow-confighttps://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow-config/of-cohttps://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow-config/of-c

https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow-config/of-config-1.1.pdf



https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow-config/of-config1dot0-final.pdf









38


OpenFlow Notification Framework OpenFlow Notification Framework

Notification : Event triggered messages, e.g., link

Publish/subscribe model : Switch = publisher. controller or OpenFlow config

points, and othe

They will be notified about the events they subscr

Use ITU-T M.3702

Notifications: Attribute valCommunication alarm, Environmental alarm, Equalarm, QoS alarm, Processing error alarm, Securitchange, Object creation and deletion

Pre-existing Notifications : Do not fit in the frawill be recognized.

OpenFlow: Packet-in, Flow removed, Port StaHello, Echo request, Echo reply, Experimente

OpenFlow Config: OpenFlow logical switch iOpenFlow capability switch capability changeOpenFLow session establishment, Failed Opeestablishment, Port failure or recovery

Ref : https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow-config

https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow-config/of-notifications-framework-1.0.pdf







Implementation IssuesImplementation Issues

40+ matching fields in a flow

Multiple tables, each with a large number of flow

Instructions and actions for each table

Need VXLAN, NVGRE, etc. support

For a large network, flow level programming cantime

Ref: R. Oshana and S. Addepalli, “Networking Trends-

Software Defined Networking, Network Virtualization and ClouOct 2012 , https://www.power.org/wp-content/uploads/2012/10/13.-FSL-SDN-Openflow-and-Cloud-computing-UPD_Rob-O

Port Management VxLAN NVGRE

Logical Ports

Table 0 Table 1 Table n Group Table

Physical Ports

…

https://www.power.org/wp-content/uploads/2012/10/13.-FSL-SDN-Openflow-and-Cloud-computing-UPD_Rob-Oshana.pdf





40


OpenFlow: Future Work ItemsOpenFlow: Future Work Items

Each controller has its own way to program. Need a common standard “Northbound API” (

No standard API for communication between conoverlapping domain Need an East-West API

Ability to continue operation when the controller

Many other packet formats (non-IP, non-Ethernet

Flow Decide once, use many times Perfo

But does not help non-flow based request/resp

Need API to encrypt data plane packets, to inject to instantiate a service, such as a firewall, IDS, on

Need to program an abstract view, e.g., source to without knowing the physical network

Ref: T. Nadeau and K. Gray, “SDN,”

O’Reilly, 2013, 384 pp, ISBN:978-1-449-34230-2Ref : http://onrc.stanford.edu/research_modern_sdn_stack.html

http://onrc.stanford.edu/research_modern_sdn_stack.html





41


OpenFlow ControllersOpenFlow Controllers

1. NOX2.

POX3.

SNAC

4.

Beacon

5.

Trema6.

Maestro

7.

Floodlight8.

ONIX

9.

ONOS

Many more…This is not a complete list.




ONOSONOS

Open Network Operating System:Distributed OpenFlow OS for a large WAN

8-10 instances in a cluster.Each Instance responsible for a part of a network

Ref : http://tools.onlab.us/onos-learn-more.html

Distributed Network Graph/State (Cassandra in mem

Distributed Registry (Zookeeper)

OpenFlow

ControllerOpenFlowController

Control Application Contr

ForwardingElements

Control Application

Instances

(Floodlight)

http://tools.onlab.us/onos-learn-more.html






OpenVirteXOpenVirteX

(OVX)(OVX)

Transparent Proxy between OpenFlow switches aOpenFlow Controllers. Slices defined by header f

Creates network slices that can be managed by dicontrollers Isolates slices from each other

All control traffic goes through OVX Slight

OF Controller

POXOF Contr

BEACOOF Controller

Floodlight

OpenVirteX

App App App App App A

SwitchSwitch Switch Switch Swi

…

Ref : http://tools.onlab.us/ovx.html

http://tools.onlab.us/ovx.html





44


MininetMininet

Widely used open source network emulation envi

Can simulate a number of end-hosts, switches, roua Linux

Used for rapid prototyping of software define netw

Built-in Open vSwitch, and a OpenFlow capable

Command line launcher and Python API for creatof varying sizes, e.g., mn –topo tree,depth=2,fan

Useful diagnositc commands like iperf, ping, andcommands in a host, e.g., mininet> h11 ifconfig

Mininet code for several popular commercial swiavailable.

Ref : https://github.com/mininet/mininet

https://github.com/mininet/mininet





45


Summary of Part ISummary of Part I

1.

Four planes of Networking: Data, Control, ManaService

2.

OpenFlow separates control plane and moves it to

controller Simplifies the forwarding element3.

Switches match incoming packets with flow entriand handle it as instructed. The controller supplietables and other instructions.

4.

OpenFlow has been extended to IPv4, MPLS, IPvOptical Network. But more work ahead.

5.

ONOS controller, OVX virtualization, Mininet fo



46


Part II: Software Defined NetworkingPart II: Software Defined Networking(SDN)(SDN)

What is SDN?

Alternative APIs: XMPP, PCE, ForCES, ALTO

OpenDaylight SDN Controller Platform and Tool




Origins of SDNOrigins of SDN

SDN originated from OpenFlow

Centralized Controller

Easy to program Change routing policies on the fly

Software Defined Network (SDN)

Initially, SDN=

Separation of Control and DataPlane

Centralization of Control

OpenFlow to talk to the data plane

Now the definition has changedsignificantly.

Applic

N

Switch

O

SouthbAPI




ONF Definition of SDNONF Definition of SDN

“ What is SDN?The physical separation of the network control plane from the fo

plane, and where a control plane controls several devices1.

Directly programmable2.

Agile: Abstracting control from forwarding 3.

Centrally managed4.

Programmatically configured5.

Open standards-based vendor neutralThe above definition includes How .

Now many different opinions about How .

SDN has become more general. Need to define by What ?

Ref : https://www.opennetworking.org/index.php?option=com_content&view=article&id=686&Itemid=

https://www.opennetworking.org/index.php?option=com_content&view=article&id=686&Itemid=272&lang=en





50


What do We need SDN for?What do We need SDN for?1. Virtualization : Use network resource without

worrying about where it is physically located,how much it is, how it is organized, etc.

2. Orchestration : Manage thousands of devices3. Programmable : Should be able to change behav4. Dynamic Scaling : Should be able to change size5. Automation : Lower OpEx6. Visibility : Monitor resources, connectivity7. Performance : Optimize network device utilizati8. Multi-tenancy : Sharing expensive infrastructure

9. Service Integration10. Openness : Full choice of Modular plug-ins11.

Unified management

of computing, networkin




SDN 2.0: OpenDaylight Style SDNSDN 2.0: OpenDaylight Style SDN

NO-OpenFlow

(Not Only

OpenFlow) Multi-Protocol

New work in IETF

XMPP, ALTO, I2RS, PCEP, ….

Linux Foundation

RESTful API OSGi F

Network Service Functions Network OrchestrationFunctionSlicing

Manager Topology

Manager

Host

Tracker

Service Abstraction Layer (SAL)

SouthboundProtocols

PCEP SMTP XMPP BGP OpFlex OpenFlowV1.0

Network Element Network Element Network Ele

Controller API (Java, REST)

Network

Elements

Overlay Tunnels (VxLAN, NVGRE, …)

…

Protocol

Plug-ins

NorthboundAPIs

Controller 1Controller

Controller 2 …



53


Current SDN Debate: What vs. How?Current SDN Debate: What vs. How?

SDN is easy if control plane is centralized but not necessaryDistributed solutions may be required for legacy equipmentoperation.

Complete removal of control plane may be harmful.Exact division of control plane between centralized controldistributed forwarders is yet to be worked out

SDN is easy with a standard southbound protocol like Open

protocol may not work/scale in all cases

Diversity of protocols is a fact of life.

There are no standard operating systems, processors, roswitches.

If industry finds an easier way to solve the same problems bmethod, that method may win. E.g., ATM vs. MPLS.



55


XMPPXMPP

Extensible Messaging and Presence Protocol

Extensible

Using XML

Similar to SMTP email protocol but for near real-communication

Each client has an ID, e.g. , [email protected]/momobile phone)

Client sets up a connection with the server

Presence : Server maintains contact addresses ancontacts know that this client is now on-line

Messaging : When a client sends a “chat”

messclients, it is forwarded to these other clients

Messages are “ pushed ” ( real-time) as oppose

in SMTP/POP emails.Server

Client Client…

Server

Client Cli…Ref: P. Saint-Andre, et al., “XMPP: The Definitive Guide,”

O’Reilly, 2009, 320 pp., ISBN:9780596

mailto:[email protected]/mobile





56


XMPP (Cont)XMPP (Cont)

XMPP is IETF standardization of Jabber protocol

RFC 6121 defines XMPP using TCP connectionsBut HTTP is often used as transport to navigate fi

All messages are XML encoded Not efficient for binary file transfers

Out-of-band binary channels are often used wi

A number of open-source implementations are av

Variations of it are widely used in most instant me programs including Google, Skype, Facebook, …

Used in IoT and data centers for management. Nehave XMPP clients that respond to XMPP messag

CLI management requests You can manage using any other XMPP client, e.g., your mobile ph

Arista switches can be managed by XMPP, Junipeas a southbound protocol for SDN

Ref : http://en.wikipedia.org/wiki/XMPP

http://en.wikipedia.org/wiki/XMPP







XMPP in Data CentersXMPP in Data Centers

Everything is an XMPP entity.It has its own contact list and authorizations.

Ref : https://github.com/ArchipelProject/Archipel/wiki/Architecture-%26-Concepts

VM

Hypervisor

vSwitch

User

Controller

pSwitch

XMPPServer

Data Center

pM

https://github.com/ArchipelProject/Archipel/wiki/Architecture-%26-Concepts





58


Path Computation Element (PCE)Path Computation Element (PCE)

MPLS and GMPLS require originating routersto find paths that satisfy multiple constraints incluusing any backup routers and having a given band

This may require more computer power or netwothan a router may have.

IETF PCE working group has developed a set of pallow a Path computation client (PCC), i.e., route path from path computation element (PCE)

PCE may be centralized or may be distributed in mrouter.

What is the 1 Gbps routeto New York not going

through Boston?

Path ComputationElement (PCE)

Path Computation

Client (PCC)



59


PCE (Cont)PCE (Cont)

PCE separates the route computation function froforwarding function.

Both functions may be resident in the same box o boxes.

25+ RFCs documenting protocols for:

PCE-to-PCC communication

PCE-to-PCE communication (Multiple PCEs)

PCE discovery

Ref : http://en.wikipedia.org/wiki/Path_computation_elementRef : http://datatracker.ietf.org/wg/pce/

http://en.wikipedia.org/wiki/Path_computation_element


http://datatracker.ietf.org/wg/pce/







Forwarding and Control ElementForwarding and Control ElementSeparationSeparation

(ForCES)(ForCES)

IETF working group since July 2001

Control Elements (CEs) prepare the routing table forwarding elements (FEs).

Each CE may interact with one or more FEs

There may be many CEs and FEs managed by a C

and a FE manager

Forwarding

Element (FE)

Control

Element (CE)

FE Manager

CE Manager

….

….



61


ForCES (Cont)ForCES (Cont)

Idea of control and data plane separation was userouting sockets

in early 1990s. It allowed routing

controlled by a simple command line or by a rout

ForCES protocol supports exchange of:

Port type, link speed, IP address

IPv4/IPv6 unicast/multicast forwarding

QoS including metering, policing, shaping, an

Packet classification

High-touch functions, e.g., Network Address T(NAT), Application-level Gateways (ALG)

Encryptions to be applied to packets

Measurement and reporting of per-flow traffic

Ref : http://datatracker.ietf.org/doc/rfc3654/?include_text=1

http://datatracker.ietf.org/doc/rfc3654/?include_text=1







Sample ForCES ExchangesSample ForCES Exchanges

CE Manager CE

Security exchangeCE ID, attributes

FE ID

FESecurity ex

FE ID, attInitial ConfiAdd these ne

Give meStat

Port x d New forward

Security exchangeList of CEs and their attributesList of FEs and their attributes

FE Manager CE Manager FE Manager

Security exchFE ID, attrib

CE ID

Ref : http://datatracker.ietf.org/doc/rfc3746/?include_text=1






63


Application Layer Traffic OptimizationApplication Layer Traffic Optimization(ALTO)(ALTO)

IETF working group to optimize P2P trafficBetter to get files from nearby peers

Provide guidance in peer selection

ALTO Server: Has knowledge of distributed resou

ALTO Client: Requests information from servers appropriate peers

Ratio Criteria: Topological distance, traffic charge

ALTO Server could get information from providenodes about their characteristics, e.g., flat-rate or charging

A client may get the list of potential peers and senserver, which can return a ordered list

Also need a protocol for ALTO server discovery

Ref: Y. Lee, et al., “ALTO Extensions for collecting Data Center Resource Information,”

http://datatracker.ietf.org/doc/draft-lee-alto-ext-dc-resource/?include_text=1

Ref: J. Seedorf and E. Berger, “ALTO Problem Statement, ”

http://datatracker.ietf.org/doc/rfc5693/?








64


ALTO ExtensionALTO Extension

Now being extended to locate resources in data ce

Need to be able to express

resource (memory, storage, CPU, network) av

Cost of these resources

Constraints on resources, e.g., bandwidth

Constraints on structure, e.g., Power consump

ALTO client gets the info from various providers

Issue of privacy of resource and cost info for the p

Data Center 1 Data Center 1 Data Center 1

ALTO Client

Application Orchestrator



65


Summary of Part IISummary of Part II

1.

SDN is the framework to automatically manage large number of network devices and services inenvironment

2.

OpenFlow originated SDN but now many differesouthbound and northbound APIs, intermediate stools are being discussed and implemented by the.g., XMPP, ForCES, PCE, ALTO

3.

OpenDaylight SDN Controller platform is the lesource SDN controller project under Linux Foun

4.

It uses REST APIs and OSGI framework for mo



66


Part III: Network Function Virtualization (NFVPart III: Network Function Virtualization (NFV

What is NFV?

NFV and SDN Relationship

ETSI NFV ISG Specifications

Concepts, Architecture, Requirements, Use cases

Proof-of-Concepts and Timeline




Four Innovations of NFVFour Innovations of NFV

4. Standard API’s between Mod

3. Implementation in Virtual Machine

2. Network Function Modules

1. Software implementation of network




Network Function Virtualization (NFV)Network Function Virtualization (NFV)

1.

Fast standard hardware Software based DevicRouters, Firewalls, Broadband Remote Access Se

A.k.a. white box

implementation2.

Function Modules (Both data plane and contro

DHCP (Dynamic Host control Protocol), NA

Address Translation), Rate Limiting,

Ref: ETSI, “NFV –

Update White Paper,”

Oct 2013 , http://www.tid.es/es/Documents/NFV_White_P

ResideGatewa

vBase

Stations

3G 2GLTE

Hardware

CDNDNS DHCP

Hardware

http://www.tid.es/es/Documents/NFV_White_PaperV2.pdf







69


NFV (Cont)NFV (Cont)3.

Virtual Machine implementation

Virtual appliancesAll advantages of virtualization (quick pro

scalability, mobility, Reduced CapEx, Reduced

4.

Standard APIs : New ISG (Industry SpecificETSI (European Telecom Standards Institute)

November 2012

Hypervisor

VM VM VM



70


Why We need NFV?Why We need NFV?1. Virtualization : Use network resource without

worrying about where it is physically located,how much it is, how it is organized, etc.

2. Orchestration : Manage thousands of devices3. Programmable : Should be able to change behav4. Dynamic Scaling : Should be able to change size5. Automation6. Visibility : Monitor resources, connectivity7. Performance : Optimize network device utilizati

8. Multi-tenancy9. Service Integration10. Openness : Full choice of Modular plug-ins

Note: These are exactly the same reasons why we ne



71


NFV and SDN RelationshipNFV and SDN Relationship

Concept of NFV originated from SDN

First ETSI white paper showed overlapping

It was removed in the second version of the

NFV and SDN are complementary.One does not depend upon the other.

You can do SDN only, NFV only, or SDN and N

Both have similar goals but approaches are ver

SDN needs new interfaces, control modules, app NFV requires moving network applications fromhardware to virtual containers on commercial-o(COTS) hardware

NFV is present. SDN is the future.

Virtualization alone provides many of the requir

Not much debate about NFV.



72


Mobile Network FunctionsMobile Network Functions

Switches, e.g., Open vSwitch

Routers, e.g., Click

Home Location Register (HLR),

Serving GPRS Support Node (SGSN),

Gateway GPRS Support Node (GGSN),

Combined GPRS Support Node (CGSN),

Radio Network Controller (RNC),

Serving Gateway (SGW),

Packet Data Network Gateway (PGW),

Residential Gateway (RGW),

Broadband Remote Access Server (BRAS),

Carrier Grade Network Address Translator (CGNAT),

Deep Packet Inspection (DPI),

Provider Edge (PE) Router,

Mobility Management Entity (MME),

Element Management System (EMS)



73


Industry Specification Group (ISG)’s

goal is to

requirements.

Four Working Groups:

INF : Architecture for the virtualization Infras

MANO : Management and orchestration

SWA : Software architecture

REL : Reliability and Availability, resilience atolerance

ETSI NFV ISGETSI NFV ISG

Ref: M. Cohn, “NFV, An Insider’s Perspective: Part 1: Goals, History, and Promise,”

Sep 2013,http://www.sdncentral.com/education/nfv-insiders-perspective-part-1-goals-history-promise/2013/09/

ETSI NFV ISG Network Ope

Technical Steering Committee

INF WG MANO WG SWA WG REL WG Security EG

http://www.sdncentral.com/education/nfv-insiders-perspective-part-1-goals-history-promise/2013/09/

http://www.sdncentral.com/education/nfv-insiders-perspective-part-1-goals-history-promise/2013/09/



74


ETSI NFV ISG (Cont)ETSI NFV ISG (Cont)

Two Expert Groups:

Security

Expert Group: Security

Performance and Portability Expert Grouefficiency, and performance VNFs relative to dedicated hardware



75


NFV SpecificationsNFV Specifications

1.

NFV Use cases (GS NFV 001)2.

NFV Architectural Framework (GS NFV 002)3.

Terminology for Main Concepts in NFV (GS NF4.

NFV Virtualization Requirements (GS NFV 004

5.

NFV Proof of Concepts Framework (GS NFV-P

Ref: ETSI, “Network Function Virtualization, ”

http://www.etsi.org/technologies-clusters/technologie

http://www.etsi.org/technologies-clusters/technologies/nfv






Network Forwarding GraphNetwork Forwarding Graph

An end-to-end service may include nested forwar

Ref: ETSI, “Architectural Framework,”

Oct 2013,http://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.01.01_60/gs_NFV002v010101p.pdf

End

PointVNF 1

VNF 2A

VNF 2B

VNF 2CV

Virtualization Layer

Hardware

http://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.01.01_60/gs_NFV002v010101p.pdf





NFV ArchitectureNFV Architecture

Ref: ETSI, “Architectural Framework,”

Oct 2013,http://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.01.01_60/gs_NFV002v010101p.pdf

NFV

Computing Hardware Storage Hardware Network Hardware

Virtualization Layer

Virtual Computing Virtual Storage Virtual Network

VNF 1 VNF 2 VNF 3

EMS 1 EMS 2 EMS 3

OSS/BSS

Service VNF andInfrastructureDescription

Execution Reference Points Main NFV Reference Points Other N

Os-Ma

Se-Ma

Ve-Vnfm

Nf-Vi

VI-Ha

Vn-Nf NFVI





79


NFV Reference PointsNFV Reference PointsReference Point: Points for inter-module specificatio

1.

Virtualization Layer-Hardware Resources ( V2.

VNF –

NFVI ( Vn-Nf )3.

Orchestrator –

VNF Manager ( Or-Vnfm )4.

Virtualized Infrastructure Manager –

VNF Ma5.

Orchestrator –

Virtualized Infrastructure Manag

6.

NFVI-Virtualized Infrastructure Manager ( Nf

7.

Operation Support System (OSS)/Business Supp(BSS) –

NFV Management and Orchestration (

8.

VNF/ Element Management System (EMS) – (Ve-Vnfm )

9.

Service, VNF and Infrastructure Description – Management and Orchestration ( Se-Ma ): VNtemplate, VNF Forwarding Graph, service-relate

NFV infrastructure informationRef: ETSI, “Architectural Framework,”

Oct 2013 , http://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.0






80


NFV Framework RequirementsNFV Framework Requirements

1.

General : Partial or full Virtualization, Predictab2.

Portability : Decoupled from underlying infrastr3.

Performance : as described and facilities to mon

4.

Elasticity : Scalable to meet SLAs. Movable to o

5. Resiliency : Be able to recreate after failure.Specified packet loss rate, calls drops, time to rec6.

Security : Role-based authorization, authenticatio

7.

Service Continuity : Seamless or non-seamless failures or migration

Ref: ETSI, “NFV Virtualization Requirements,”, Oct 2013, 17 pp.,http://www.etsi.org/deliver/etsi_gs/NFV/001_099/004/01.01.01_60/gs_NFV004v010101p.pdf





81


NFV Framework Requirements (Cont)NFV Framework Requirements (Cont)

8.

Service Assurance: Time stamp and forward c packets for Fault detection

9.

Energy Efficiency Requirements : Should bea subset of VNF in a power conserving sleep sta

10.

Transition: Coexistence with Legacy and Interamong multi-vendor implementations

11.

Service Models : Operators may use NFV infraoperated by other operators



82


NFV Use CasesNFV Use Cases

Cloud :1.

NFV infrastructure as a service (NFVIaaS) li2.

Virtual Network Functions (VNFs) as a servilike SaaS

3.

VNF forwarding graphs (Service Chains)4.

Virtual Network Platform as a Service (VNPa

Mobile :5.

Virtualization of the Mobile Core Network an6.

Virtualization of Mobile Base Station

Data Center :7.

Virtualization of CDNs

Access/Residential :8.

Virtualization of the Home environment9.

Fixed Access NFVRef: ETSI, “NFV Use Cases, ”

http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_Ref: M. Cohn, “NFV Insider’ s Perspective, Part 2: There’s a Network in NFV –

The Business Casehttp://www.sdncentral.com/education/nfv-insiders-perspective-part-2-theres-network-nfv-business-case-


http://www.sdncentral.com/education/nfv-insiders-perspective-part-2-theres-network-nfv-business-case-sdn/2013/09/











83


NFV Proof of Concepts (NFV Proof of Concepts ( PoCsPoCs ))ETSI has formed and NFV ISG PoC

Forum.

Following modules have been demoed:1.

Virtual Broadband Remote Access Server (BRASTelecom

2.

Virtual IP Multimedia System (IMS) by Deutsche

3. Virtual Evolved Packet Core (vEPC) by Orange S

4.

Carrier-Grade Network Address Translator (CGNDeep Packet Inspection (DPI), Home Gateway by

5.

Perimeta

Session Border Controller (SBC) from 6.

Deep packet inspection from ProceraMost of these are based on Cloud technologies, e.g.,

Ref: M. Cohn, “NFV Group Flocks to Proof-of-Concept Demos,”

Aug 2013,http://www.sdncentral.com/technology/nfv-group-flocks-to-proof-of-concept-models/2013/08/

http://www.sdncentral.com/technology/nfv-group-flocks-to-proof-of-concept-models/2013/08/

http://www.sdncentral.com/technology/nfv-group-flocks-to-proof-of-concept-models/2013/08/



84


Summary of Part IIISummary of Part III

1.

NFV aims to reduce OpEx by automation and sca provided by implementing network functions as vappliances

2.

NFV allows all benefits of virtualization and clouincluding orchestration, scaling, automation, hardindependence, pay-per-use, fault-tolerance, …

3.

NFV and SDN are independent and complementado either or both.

4.

NFV requires standardization of reference pointsto be able to mix and match VNFs from different5.

NFV can be done now. Several of virtual functionalready been demonstrated by carriers.



85


Overall SummaryOverall Summary

1.

Four planes of Networking: Data, Control, Mgm2.

OpenFlow separates control plane and moves it tcontroller Simplifies the forwarding element

3.

SDN is the framework to automatically manage

large number of multi-tenant network devices an4.

OpenFlow originated SDN but now many differesouthbound and northbound APIs, intermediate stools are being discussed and implemented by th

5.

OpenDaylight SDN Controller platform is the lesource SDN controller project under Linux Foun

6.

NFV reduces OpEx by automation and scalabilitimplementing network functions as virtual applia



R R eef f eerr eenn cceess Part I: OpenFlow

Pfaff and B. Davie, “The Open vSwitch Database Management Protocol,” IETF draft,Oct 2013, http://tools.ietf.org/html/draft-pfaff-ovsdb-proto-04

T. Koponen, et al., “Onix: A distributed Control Platform for Large Scale Production

Networks,” OSDI 2010,http://static.usenix.org/events/osdi10/tech/full_papers/Koponen.pdf http://www.noxrepo.org/forum/ http://www.noxrepo.org/pox/about-pox/ http://www.openflowhub.org/display/Snac/SNAC+Home https://openflow.stanford.edu/display/Beacon/Home http://github.com/trema/ http://trema.github.com/trema/ http://www.projectfloodlight.org/floodlight/ https://code.google.com/p/maestro-platform/ https://github.com/mininet/mininet

https://github.com/OPENNETWORKINGLAB/flowvisor/wiki ? http://osrg.github.io/ryu/ https://sites.google.com/site/routeflow/home http://en.wikipedia.org/wiki/Bird_Internet_routing_daemon https://github.com/travelping/flower https://github.com/Sovietaced/Avior http://archive.openflow.org/wk/index.php/Oflops http://www.es.net/services/virtual-circuits-oscars http://github.com/Luxoft/Twister http://www.openflowsec.org/OpenFlow_Security/Home.html N. McKeown, et al., ``OpenFlow: Enabling Innovation in Campus Networks," ACM

SIGCOMM CCR, Vol. 38, No. 2, April 2008, pp. 69-74. ONF, “The OpenFlow Timeline,” http://openflownetworks.com/of_timeline.php Open Data Center Alliance Usage Model: Software Defined Networking Rev 1.0,”

http://www.opendatacenteralliance.org/docs/Software_Defined_Networking_Master_ Usage_Model_Rev1.0.pdf

R. Oshana and S. Addepalli, “Networking Trends- Software Defined Networking, Network Virtualization and Cloud Orchestration,” Asia Power Arch. Conf, Oct 2012,https://www.power.org/wp-content/uploads/2012/10/13.-FSL-SDN-Openflow-and-Cloud-computing-UPD_Rob-Oshana.pdf

ONF, "OpenFlow Specifications V1.0.0,"http://archive.openflow.org/documents/openflow-spec-v1.0.0.pdf

ONF, "OpenFlow Specifications V1.1.0,"http://archive.openflow.org/documents/openflow-spec-v1.1.0.pdf

ONF, "OpenFlow Specifications V1.2.0,"https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-spec-v1.2.pdf

ONF, "OpenFlow Specifications V1.3.0,"https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-spec-v1.3.0.pdf



ONF, "OpenFlow Specifications V1.4.0,"https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-spec-v1.4.0.pdfhttp://openvswitch.org/

http://www.openvswitch.org/ http://www.projectfloodlight.org/indigo/

http://flowforwarding.github.io/LINC-Switch/ http://github.com/CPqD/openflow-openwrt http://cpqd.github.io/ofsoftswitch13/ http://sourceforge.net/projects/xorplus http://en.wikipedia.org/wiki/OpenFlow http://en.wikipedia.org/wiki/Software-defined_networking http://en.wikipedia.org/wiki/Network_Functions_Virtualization http://en.wikipedia.org/wiki/Forwarding_plane http://en.wikipedia.org/wiki/NetFlow http://en.wikipedia.org/wiki/IP_Flow_Information_Export http://en.wikipedia.org/wiki/SFlow http://en.wikipedia.org/wiki/Northbound_interface http://en.wikipedia.org/wiki/Big_Switch_Networks

http://en.wikipedia.org/wiki/Open_Data_Center_Alliance http://en.wikipedia.org/wiki/Virtual_Extensible_LAN http://en.wikipedia.org/wiki/Optical_Transport_Network http://en.wikipedia.org/wiki/Automatically_switched_optical_network http://en.wikipedia.org/wiki/Wavelength-division_multiplexing http://en.wikipedia.org/wiki/IEEE_802.1ad http://en.wikipedia.org/wiki/Transport_Layer_Security http://en.wikipedia.org/wiki/OpenStack http://en.wikipedia.org/wiki/IPv6_packet http://en.wikipedia.org/wiki/ICMPv6

Part II: Software Defined Networking: S. Azodolmolky, "Software Defined Networking with OpenFlow," Packt Publishing,October 2013, 152 pp., ISBN:978-1-84969-872-6 (Safari Book)

T. Nadeau and K. Gray, “SDN,” O’Reilly, 2013, 384 pp, ISBN:978-1-449-34230-2B(Safari Book)

V. Josyula, M. Orr, and G. Page, “Cloud Computing: Automating the Virtualized DataCenter,” Cisco Press, 2012, 392 pp., ISBN: 1587204347 (Safari Book).

J. Seedorf and E. Berger, “ALTO Problem Statement,”http://datatracker.ietf.org/doc/rfc5693/?include_text=1

Y. Lee, et al., “ALTO Extensions for collecting Data Center Resource Information,”http://datatracker.ietf.org/doc/draft-lee-alto-ext-dc-resource/?include_text=1

B. Martinussen (Cisco), “Introduction to Software Defined Networks (SDN),” April2013, http://www.cisco.com/web/europe/ciscoconnect2013/pdf/DC_3_SDN.pdf

http://www.osgi.org/Technology/WhatIsOSGi http://www.sdncentral.com/sdn-use-cases / https://wiki.opendaylight.org/view/OpenDaylight_SDN_Controller_Platform_%28OS

CP%29:Proposal



http://datatracker.ietf.org/wg/pce/ https://wiki.opendaylight.org/view/Main_Page P. Saint-Andre, et al., “XMPP: The Definitive Guide,” O’Reilly, 2009, 320 pp.,

ISBN:9780596521264 (Safari Book) OpenDaylight Components and Tools:

https://wiki.opendaylight.org/view/Open_DOVE:Proposal https://wiki.opendaylight.org/view/OpenDaylight_Network_Virtualization_%28O NV%29:Main

https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Overview https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_%28V

TN%29:Overview https://wiki.opendaylight.org/view/Openflow_Protocol_Library:Main https://wiki.opendaylight.org/view/OVSDB_Integration:Design https://wiki.opendaylight.org/view/Project_Proposals:Affinity_Metadata_Service https://wiki.opendaylight.org/view/Project_Proposals:BGP_and_PCEP https://wiki.opendaylight.org/view/Project_Proposals:Defense4All

https://wiki.opendaylight.org/view/Project_Proposals:Dlux https://wiki.opendaylight.org/view/Project_Proposals:LispMappingService https://wiki.opendaylight.org/view/Project_Proposals:SNMP4SDN https://wiki.opendaylight.org/view/YANG_Tools:Main


Open Data Center Alliance Usage Model: Software Defined Networking Rev 1.0,”http://www.opendatacenteralliance.org/docs/Software_Defined_Networking_Master_ Usage_Model_Rev1.0.pdf

http://en.wikipedia.org/wiki/Multiprotocol_Label_Switching http://en.wikipedia.org/wiki/Software-defined_networking http://en.wikipedia.org/wiki/Representational_state_transfer http://en.wikipedia.org/wiki/OSGI http://en.wikipedia.org/wiki/XMPP http://en.wikipedia.org/wiki/Path_computation_element

Part III: Network Function Virtualization: ETSI, “NFV - Update White Paper,” Oct 2013,

http://portal.etsi.org/NFV/NFV_White_Paper2.pdf (must read) ETSI, “Network Function Virtualization,”

http://www.etsi.org/technologies-clusters/technologies/nfv ETSI, “Architectural Framework,” Oct 2013,


ETSI, “NFV Terminology for Main Concepts in NFV,” Oct 2013,http://www.etsi.org/deliver/etsi_gs/NFV/001_099/003/01.01.01_60/gs_NFV003v010101p.pdf

ETSI, “NFV Use Cases,”http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01.01_60/gs_NFV001v010101p.pdf



ETSI, “NFV Virtualization Requirements,”, Oct 2013, 17 pp.,http://www.etsi.org/deliver/etsi_gs/NFV/001_099/004/01.01.01_60/gs_NFV004v010101p.pdf

M. Cohn, “NFV, An Insider’s Perspective: Part 1: Goals, History, and Promise,” Sep2013,

http://www.sdncentral.com/education/nfv-insiders-perspective-part-1-goals-history-pr omise/2013/09/



AA ccrr oonn yymm ss

ACI Application Policy Infrastructure ACL Access Control List AEX Application Information Exposure ALG Application Level Gateway

ALTO Application Layer Traffic Optimization ANDSF Access Network Discovery and Selection Function API Application Programming Interface APIC Application Policy Infrastructure Controller ARP Address REsolution Protocol ASICs Application Specific Integrated Circuit ATIS Association for Telecom Industry Solutions ATM Asynchronous Transfer Mode AVNP Active Virtual Network Management Protocol

BFD Bidirectional Forwarding DetectionBGP Border Gateway ProtocolBIRD Bird Internet Routing DaemonBNC Big Switch Network ControllerBRAS Broadband Remote Access ServerBSD Berkeley Software DistributionBSS Business Support SystemsBUM Broadcast, Unknown, and MulticastCapEx Capital ExpenditureCDN Content Distribution NetworkCDNI Content Distribution Network InterconnectionCE Control ElementCFM Connectivity Fault ManagementCGNAT Carrier-Grade Network Address TranslatorCGSN Combined GPRS Support NodeCLI Command Line InterfaceCMS Content Management SystemCOTS Commercial-off-the-shelf

CPU Central Processing UnitCRUD Create, Read, Update, DeleteCSP Cloud Service ProviderDDIO Data Direct I/O TechnologyDFCA Dynamic Frequency Channel AllocationDHCP Dynamic Host Control ProtocolDNS Domain Name SystemDOVE Distributed Overlay Virtual EthernetDPI Deep Packet InspectionDSCP Differentiated Service Control PointDVS Distributed Virtual SwitchECMP Equal Cost MultipathEID Endpoint IdentifierEMS Element Management SystemESP Encrytec Security PayloadETSI European Telecom Standards InstituteETSI European Telecommunications Standards InstituteFCAPS Faults, configuration, accounting, performance , and securityFE Forwarding ElementFIB Forwarding information baseForCES Forwarding and Control Element SeparationGGSN Gateway GPRS Support NodeGMPLS Generalized Multi-Protocol Label Switching



GPRSGRE Generic Routing EncapsulationGUI Graphical User InterfaceHLR Home Location RegisterHTML Hypertext Markup LanguageHTTP Hypertext Tranfer ProtocolI2AEX Infrastructure to Application Information ExposureIaaS Infrastructure as a ServiceICMP Internet Control Message ProtocolICSI International Computer Science InstituteID IdentifierIDS Intrusion Detection SystemIEEE Institution of Electrical and Electronic EngineersIETF Internet Engineering Task ForceIGMP Internet Group Multicast ProtocolIGP Interior Gateway ProtocolIMS IP Multimedia SystemINF Architecture for the virtualization InfrastructureIoT Internet of ThingsIP Internet Protocol

IPFIX IP Flow Information Export ProtocolIPSec IP SecurityIPv4 Internet Protocol version 4IPv6 Internet Protocol version 6IRTF Internet Research TaskforceIS-IS Intermediate System to Intermediate SystemISG Industry Specification GroupISO International Standards OrganizationJSON Java Script Object NotationJVM Java Virtual MachineKVM Kernel-based Virtual MachineLACP Link Aggregation Control ProtocolLAN Local Area NetworkLISP Locator-ID Separation ProtocolLLDP Link Layer Discovery ProtocolLS Link StateLSP Label Switched PathMAC Media Access ControlMAN Metropolitan Area NetworkMANO Management and orchestrationMME Mobility Management EntityMPLS Multiprotocol Label SwitchingNAT Network Address TranslationNF Network FunctionNFV Network Function VirtualizationNFVI Network Function Virtualization InfrastructureNFVIaaS NFVI as a Service

NIB Network Information BaseNIC Network Interface CardNSF National Science FoundationNTP Network Time ProtocolNTT Nippon Telegraph and TelephoneNVGRE Network Virtualization using Generic Routing EncapsulationNVO3 Network Virtualization over L3NVP Network Virtualization PlatformOF OpenFlowOFlops OpenFlow Operations Per Second



OLSR Optimized Link State RoutingON.LAB Open Networking Lab at StanfordOnePK Open Network Environment Platform KitONF Open Networking FoundationONV OpenDaylight Network VirtualizationopenQRM Open Qlusters Resource ManagerOpenWRT Open WRT54G (Linksys product name) softwareOpEx Operational ExpencesOpEx Operational ExpencesOS Operating SystemOSCP OpenDaylight SDN Controller PlatformOSGi Open Services Gateway InitiativeOSPF Open Shortest Path FirstOSS Operation Support SystemOTN Optical Transport NetworkOVS Open Virtual SwitchOVSDB Open vSwitch DatabasePaaS Platform as a ServicePCC Path Computation ClientPCE Path Computation Element

PCEP Path Computation Element ProtocolPE Provider EdgePGW Packet Data Network GatewayPIM-SM Protocol Independent Multicast - Sparse ModePIM Protocol Independent MulticastPoC Proof-of-ConceptPOP Post Office ProtocolPSTN Public Switched Telephone NetworkPWE3 Pseudowire Emulation Edge to EdgeQoS Quality of ServiceRAN Radio area networksREL Reliability, Availability, resilience and fault tolerance groupREST Representational State TransferRFC Request for CommentsRGW Residential GatewayRIB Routing Information BaseRIP Routing Information ProtocolRLOC Routing LocatorRNC Radio Network ControllerRPC Remote Procedure CallRS Routing SystemRSPAN Remote Switch Port AnalyzerSaaS Software as a ServiceSAL Service Abstraction LayerSBC Session Border ControllerSDN Software Defined NetworkingSGSN

SGW Serving GatewaySIP Session Initiation ProtocolSLA Service Level AggrementSMTP Simple Mail Transfer ProtocolSNACSNMP Simple Network Management ProtocolSPAN Switch Port AnalyzerSSH Secure Socket HostSSL Secure Socket LayerSTP Spanning Tree Protocol



STT Stateless TCP-like TransportSWA Software architectureTAS Telephony Application ServerTCAM Ternary Content Addressable MemoryTCL Tool Command LanguageTCP Transmission Control ProtocolTE Traffic EngineeringTIA Telecom Industry AssociationTLS Transport Level SecurityTLV Type-Length-ValueTMF ForumToS Type of ServiceTRILL Transparent Interconnection of Lots of LinksTTL Time to LiveTTP Table Typing PatternsUC University of CaliforniaUDP User Datagram ProtocolURI Uniform Resource IdentifiervBridge Virtual BridgevEPC

VIRL Virtual Internet Routing LabVLAN Virtual Local Area NetworkVM Virtual MachineVNF Virtual Network FunctionVNFaaS VNF as a ServiceVNS Virtual Network SegementVPN Virtual Private NetworkvSwitch Virtual SwitchVT-d Virtualization Technology for Direct IOVT-x Virtualization TechnologyvTep Virtual Tunnel End PointVTN Virtual Tenant NetworkVxLAN Virtual Extensible Local Area NetworkWAN Wide Area NetworkWG Working GroupXML Extensible Markup LanguageXMPP Extensible Messaging and Presence ProtocolXORP eXensible Open Router Platform