transport sdn overview and standards update: industry perspectives
TRANSCRIPT
I N D U S T R Y P E R S P E C T I V E S
TRANSPORT SDN OVERVIEW & STANDARDS UPDATE
Chris Liou, Infinera
Jun 4 2013 – 2nd PLENARY
THE EVOLVING CORE LANDSCAPE
• 100Gb coherent technology
• Optical Super-channels & FlexGrid emerging
• Bandwidth service needs vary broadlyFiber Capacity
• Integrated WDM + OTN + Packet transport
• Intelligent traffic management, switching & shared protection
• Carriers interested in router offload & bypass
Transport Convergence
• Dynamic traffic patterns & profiles
• Demand for adaptive and agile transport
• Integration of Network & IT
Data Center
Networking
IP/MPLS
SONET
SDH
OTN
DWDM
IP
MPLS
IP
CONVERGENCE IN CORE NETWORKS
Phase 1Status Quo Phase 2
Integrated
MPLS/OTN/DWDM
(future)
PIC
Enabled
Integrated OTN/DWDM
PIC
Enabled
• Restoring bandwidth quickly and cost effectively
• Minimize impact from both single & multiple simultaneous failure scenarios
• Milliseconds matter (user conversion rates, customer retention)
• Intelligence in the network to optimize latency for particular application
• Priorities for different classes of cloud services
• Avoid application-
level timeouts
• Capacity for unpredictable, unplanned & one-time events
• Rapid scale of on-demand cloud services (up & down) in minutes
ResiliencyRapid Bandwidth
DeliveryLow Latency
CORE NETWORK REQUIREMENTS FOR CLOUD
TRANSPORT NETWORK PROGRAMMABILITY
Packet World
• Connectionless
• Enterprise origins
• Dynamic flows
• Innate control plane (EMS/NMS independent)
• Numerous distributed CP solutions
• Monolithic, closed systems
Transport World
• Connection (circuit) oriented
• Service provider origins
• Static pipes
• EMS/NMS + Cross-connect paradigm
• Nascent CP (GMPLS)
• Open, programmable systems
T R A N S P O R T P A R A D I G M I S D I F F E R E N T
Historically, transport networks have been programmable.
EXTENDING SDN TO TRANSPORT
• Dynamic network & service
programmability
• Different abstractions key
for simplifying network representation
• Transport SDN offers unified
CP over multi-layer, multi-
vendor network
• Benefits:• Rapid & Flexible Bandwidth
• Simplify/Automate Operations
• Global resource optimization
• Speed New Service
Deployment
O P E N & P R O G R A M M A B L E N E T W O R K I N G
Cloud Applications
Transport SDN
Control Layer
Network/
Service
Abstractions
Discover,
Monitor,
Control
• Multi-layer
• Multi-vendor
• Multi-domain
Packet, OTN, Optics
Transport Network
Control API
NB API
Control +
Net Apps
Virtualization
APPLICATIONS FOR TRANSPORT SDN
• Networking-as-a-Service (NaaS)• Layer 1 Virtual Networks (network slicing for multi-tenancy)
• Virtual transport switches & virtual bandwidth links
• Useful as both Internal partitioning & external service capability
• Optimized Data Center Interconnect• Right-sized transport capacity (tunnels) for A-Z flow set
• Multi-layer topology integration & resiliency
• Multi-layer orchestration & optimization• Simplified orchestration through uniform API
• Optimize traffic flows through multi-layer network
• E.g., minimize packet processing for Big Data at intermediate sites
• Globalized optimization for lowest-cost & highest network utilization
D Y N A M I C C I R C U I T S & V I R T U A L W A V E S
K E Y E L E M E N T S
• Integrated WDM/OTN infrastructure• Dynamic, switched real-time circuits
• Bandwidth Virtualization for abstracting optical infrastructure
• Open Transport Switch (OTS)• Infinera’s open Virtual transport switch
• OpenFlow 1.0 protocol extensions
• Transport BW src, dst, size, latency, abstraction level, etc.
• Interworking with GMPLS technologies demonstrated• Key capabilities well suited for SDN framework
• Topology discovery
• Robust signaling
• Route computation can still be centralized!
• SDN Controller & App• OSCARS, OpenFlowJ
TRANSPORT SDN COLLABORATION DEMO
EthernetSwitch
OTN/MPLS/ DWDM
EthernetSwitch
OTN/MPLS/ DWDM
Ethernet Optical
OTS OTS OTS OTS
SDN Controller
Explicit Path Set Up (provision every node)
POTN
POTN
POTN
POTN
OTSOTS
SDN
Controller
GMPLSLSR
LSR
LSR
LSRENET
ENET
ENET
ENET
OTS OTSOTS
OTSMPLSEthernet
DEMONSTRATING COMPATIBILITY WITH DISTRIBUTED CONTROL PLANES
Implicit Path Set Up(provision edge nodes only,
leverage existing control plane)
OpenFlow
OpenFlow
Ethernet Ethernet Ethernet
SDN DEMO CONFIGURATION
• SDN Controller communicating with OTS via OpenFlow 1.0 extensions• Bandwidth on Demand application for Big Data RDMA transport• 3 physical transport path options (with varying latencies)• Implicit & explicit provisioning of 10GbE/40GbE services demonstrated
bnl-tb-wdm-3 bnl-tb-wdm-4
40G
100G
20G 20G
20G L1 Tunnel
Topology Monitoring BW on Demand
ESnet SDN Controller
Mellanox Mellanox
Path #1
Path #2
Path #3
OTS
ESnet LIMAN Production Network
Brookhaven National Laboratory
Testbed
OTS
ONF OTWG CHARTER
• SDN/OpenFlow extensions for optical transport networks will
address technologies such as Layer 0 and Layer 1 optical and digital circuit switching and packet-optical integration (POI)
• Identification of use cases, definition of a target reference
architecture for control of optical transport networks
incorporating OpenFlow, identification and creation of OpenFlow protocol extensions, and adaptation to, or integration
with, existing efforts within the ONF scope.
• Both direct control of optical transport network elements and
control operating on an abstracted view of the transport network will be explored. This work will include definition of L0/L1 circuit
switch and L2 packet switch abstractions for OpenFlow and their
interactions with incoming/outgoing packet flows
A P P R O V E D Q 1 2 0 1 3
OTWG USE CASES - SUMMARY
• Use case 1 – private enterprise cloud/optical networks
• Direct programmability of components/devices comprising an
all optical networks
• Eg., transponders, WSS, VGA , OXC, VOA, etc.
• Use case 2 – data center interconnect
• Shared SP infrastructure
• Orchestration between data center + provider network
• Use case 3 – packet optical integration
• Multi-layer optimization & traffic engineering
• All work still in-progress & subject to change
Client … ……
…
Client
Client
Client
EPS
EPS
EPS
EPS
Electronic Packet Switch
SDN
Controller
Aps… …Aps
Aps
Aps
……
USE CASE 1 – PRIVATE OPTICAL NETWORKS
O P T I C A L C I R C U I T S W I T C H I N G B Y W S S
14
Client … …Client EPSEPS
SDN
Controller
Client …EPS …Client EPS Aps…
Aps…
Tuning Tx l
…Aps
…Aps
USE CASE 1 – PRIVATE OPTICAL NETWORKS
O P T I C A L C I R C U I T S W I T C H I N G B Y T U N I N G
15
USE CASE 2 - SP DC INTERCONNECTION
• Current DCI Architecture
• Static WAN optical pipe pre-allocated between DC sites
• Limited peak rate plus underutilized capacity due to
fluctuating traffic demands
• OF-based Transport SDN
• Dynamic WAN optical pipe establishment including DC
selection
• Optical tunnels reconfigured within virtual network slice
• DC packet net forwards selectively into tunnels on command
• Security (e.g., inter-controller authentication and encryption
options) and policy control
16
USE CASE 2 - BASE ARCHITECTURAL CONTEXT
17
ProviderNetwork
Controller
CVNI (Control
Virtual Network
Interface)
CDPI (Control Data
Plane Interface)
1
2
56
43
78
Client Controller A
Client Controller B
Client Controller N
Transport Network
ClientEnd
Point
ClientEnd
Point
ClientEnd
Point
ClientEnd
Point
Virtualizer/Mediation Function
isolation, policy enforcement,
network resource slicing, virtual/physical
to physical/virtual control/management ,
etc.
USE CASE 2 - SP DCI ARCHITECTURAL CONTEXT
18
ProviderNetwork
Controller
12
56
43
78
DCController
Transport Network
Server
Racks DC A
AS
DC
End
Point
Server
RacksDC C
AS
DC
End
Point
Server
RacksDC D
AS
DC
End
Point
Server
Racks DC B
AS
DC
End
Point
USE CASE 2 – DCI ORCHESTRATION
Orchestration between DC Control & Provider Network Control
• DC Controller• Has resource knowledge of DCs under its control and the workload
requirement that requires inter-DC data transport.
• Instantiates Virtual Network Service for each application
• Views the Virtual Network Topology provided from PNC
• Controls the allocated network resources on a virtual level
• Provider Network Controller• Has resource knowledge of transport network under its control
• Creates virtual view for each client/application
• Applies authentication and policy control
• Instantiates Network Provisioning
• Joint Optimization • Efficiency at a cost of complexity
• Some research work (Cross Stratum Optimization) to address this issue.
19
USE CASE 3 – PACKET OPTICAL INTEGRATION
• Optical transport systems rapidly converging multiple
layers (L0 – L2.5)
• Flexibility creates opportunities for multi-layer optimization
• Use case characteristics• Packet traffic is transported over optical server network, involving
multiple layer networks
• Goal is for packet and optical topologies to be jointly optimized for
greater network efficiencies
• Two sub-cases• service provider’s packet services network routers are interconnected
via service provider’s transport network
• 3rd party packet services network routers are interconnected via
service provider’s transport network
20
USE CASE 3 - CURRENT ARCHITECTURE
• Current architecture• Optical transport operates independently of packet
• In particular, traffic engineering/path computation is done in packet
without knowledge of or taking advantage of optical network
• Both may be dynamic but without integration of control
• Often dynamism in the optical layer is considered a problem in the packet
layer because of routing topology changes
• Separate organizations & separate network layers
leads to local optimization, not global optimization
21
USE CASE 3 - MULTI-LAYER TRANSPORT SDN
• With OpenFlow-based Transport SDN• Network operator sees both transport and packet network topologies
• Optimization done across multiple layers
• Integrated packet/optical OF controls mapping from packet to optical
• Packet and optical topologies can be adjusted to fit demand
• If separate, the packet/services network controller is connected to
the transport network controller via a Control Virtual Network
Interface (CVNI) over which OF-wire/config messages will be
exchanged wrt a virtual network topology
• Information is provided in the virtual topology to identify, e.g., fate-sharing,
latency, cost, etc. to support efficient traffic engineering
• If combined, packet/optical network controller controls forwarding at
both layers with knowledge of multilayer topology
• Config protocol populates controller with multilayer topology
22