Open Transport Switch - SDxCentral · Open Transport Switch: Supporting SDN in Transport Networks...

Open Transport Switch:

Supporting SDN in Transport Networks

Ping Pan ppan@infinera.com Wes Doonan WDoonan@advaoptical.com

Lyndon Ong Lyong@Ciena.com Geoffrey Mattson gmattson@juniper.net

Meral Shirazipour meral.shirazipour@ericsson.com Young Lee leeyoung@huawei.com

Thomas Nadeau tnadeau@juniper.net Saurav Das saurav.das@bigswitch.com

Piotr Myslinski pmyslinski@vellosystems.com

October 2012

Acknowledgments and Other Contributors

• Inder Monga (Esnet)

• Martin Swany (Indiana University)

• Matthew Davy (Internet2 / Indiana University)

• Guy Roberts (DANTE)

• Richard Hughes-Jones (DANTE)

• Lars Fischer (NORDUnet)

• Jerry Sobieski (NORDUnet)

• David McDysan (Verizon)

For Open Discussion 2

1. Typically, transport equipment cannot talk to each other outside one network domain

2. Network operation over multiple layers (including ROADM, OTN, Ethernet and MPLS) is very expensive

3. Service deployment is very slow (due to technology, operational practice and politics)

Problems in Transport Networks

For Open Discussion 3

SDN Means Different Things to Different People

• Application Providers: business incentives – Faster service deployment

– Simpler network connection provisioning

– Better network resource utilization

• Network Providers: reality check – Control the distribution of network interior information

– Need to integrate multi-layer/multi-regional networks

– Continue the use of dynamic protocols for provisioning and protection in some parts of the network

We need to take the above into consideration to enable fast adaption, development and deployment in transport networks

For Open Discussion 4

Why SDN?

• Overlay

• Deploy services on top of network infrastructure

• Operate over multiple networks, over multiple layers

• Technology-agnostic

• Virtualization

• Enable the control of relevant nodes and links

• Enable the optimization of network resources

• Provide needed security and isolation

For Open Discussion 5

SDN for Transport Networks is not hard

For Open Discussion 6

Overlay topology

SDN App

SDN App

SDN App

Transport Infrastructure

Transport Infrastructure Transport Infrastructure

This is where SDN services are defined

and offered This is where SDN API’s need to be defined to support configuration,

monitoring and provisioning

How to Build an Overlay?

Overlay Network

Service & App #1

Service & App #2

Service &App #N

SDN Controller

Transport Infrastructure

Open Transport

Switch

Open Transport

Switch

Open Transport

Switch

Access Devices

Access Devices

E2E Connections

A virtual switch built on top of transport equipment for overlay

interfacing

For Open Discussion 7

Open Transport Switch: A light-weight virtual switch in transport equipment

OTS-Management Agent

OTS-Control Agent OTS-Data Agent

Control Plane

XMPP/others JSON /others

OpenFlow+

SDN Controller

Data Forwarding Plane

Physical Interfaces

N

Internal Communication

Transport Switch

Platform

For Open Discussion 8

Key Functions

• OTS Data Agent – Responsible for setting up data-plane connections, such as

cross-connects

– Use OpenFlow and additional extensions (see later)

• OTS Control Agent – Responsible for switch configuration (Controller OTS)

– Responsible for exporting network topology (OTS Controller)

– Protocol Choice • JSON is one solution, based on our experience in ALTO and OVS

• Other protocols (e.g. XMPP) would also work

For Open Discussion 9

Key Functions (cont.)

• OTS Management Agent – Responsible for real-time event data (e.g. alarm)

exchange (OTS Controller) – Responsible for service negotiation and discovery at

boot-up time (OTS Controller) – Protocol Choice

• XMPP is a simple and reliable way for event messaging • DNS may be used for service discovery and negotiation

• OTS representation – A single node: such as an optical switch – A couple of nodes: such as an optical switch + a router

For Open Discussion 10

Operation Example #1: Explicit Provisioning

Ethernet Switch

Ethernet / DWDM

Ethernet Switch

A B C D

Ethernet / DWDM

VLAN 100

VLAN 200

VLAN 300

VLAN 400

Wave X

OTS OTS OTS OTS

SDN Controller

Topology report: • L1: 10GE • L2: to B, 100GE

A D

H E

L2 L4 B C

G

F

L3 L1 L5

Provisioning (e.g., OpenFlow): L2-L3 :: map VLAN-200 packets to VIF X

For Open Discussion 11

Operation Example #2: Implicit Provisioning

LSR

LSR

LSR

LSR POTN

POTN

POTN

POTN ENET

ENET

ENET

ENET

OTS OTS OTS OTS OTS

OTS

A B C D E F

SDN Controller

Data Data

Label

Data Data

ODU

Data Data

VLAN

Data

A D B C F E

MPLS OTN (GMPLS) L2 Ethernet

Provisioning: • Setup A-B with BW X Provisioning:

• Setup C-D with BW X • Map data to C-D

For Open Discussion 12

The existing OpenFlow needs work…

Functions Example Problem Possible Solution

Connection setup

What if the flows are non-packet (e.g. waves); it’s not defined in OpenFlow

Introduce the concept of flow-id into

OpenFlow

Flow Aggregation

Flow modification message is to add flows to an Ethernet port, not to another flow

Introduce the concept of virtual port for non-

packet flows

QoS and CAC

QoS is not in v1.0 Largely solved in v1.3. But need to include

latency requirements

Implicit provisioning

How can we make flow id’s unique?

MPLS Label? Push this to OTS-Control

to handle

F1 (ODU1) F2 (ODU1)

Interface 1 Interface 2

Flow-1 (pkt) Flow-3 (e.g. wave)

Flow-2 (pkt)

Flow-1 (7G) Flow-3 (10G)

Flow-2 (3G)

F1 F2 F3 F4

For Open Discussion 13

Example: Multi-Layer Integration

Domain C

Domain A

Domain B

Switch Access

SDN Controller

Topology information Traffic aggregation instruction

Switch Switch Access Switch Switch Switch

• Operators may perform TE using the topology information gathered from the network

• Use simple tunneling mechanism for traffic aggregation

• Transport equipment is responsible for interworking at data-plane

Multiple-Layer Integration Application

For Open Discussion 14

Work Items

• Architecture and framework

• OpenFlow enhancement discussion, modification and prototyping

• Protocol extensions for control and management

For Open Discussion 15

• SDN can speed up service deployment in transport network through network overlay and virtualization

• Open Transport Switch is a virtual switch installed on transport equipment for SDN Controller to discover, monitor and provision user flows

• We’d like to work with the community to define and develop Open Transport Switch together

Final Words

For Open Discussion 16