Open Transport Switch:

Transcription

1 Open Transport : Supporting SDN in Transport Networks Ping Pan [email protected] Wes Doonan [email protected] Lyndon Ong [email protected] Geoffrey Mattson [email protected] Meral Shirazipour [email protected] Young Lee [email protected] Thomas Nadeau [email protected] Saurav Das [email protected] Piotr Myslinski [email protected] October 2012

2 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

3 Problems in Transport Networks 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) For Open Discussion 3

4 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

5 Overlay Why SDN? 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

6 SDN for Transport Networks is not hard This is where SDN services are defined and offered SDN App SDN App SDN App Overlay topology This is where SDN API s need to be defined to support configuration, monitoring and provisioning Transport Infrastructure Transport Infrastructure Transport Infrastructure For Open Discussion 6

7 How to Build an Overlay? Service & App #1 Service & App #2 Service &App #N SDN Controller Access Devices Open Transport Overlay Network Open Transport Open Transport Access Devices E2E Connections Transport Infrastructure A virtual switch built on top of transport equipment for overlay interfacing For Open Discussion 7

8 Open Transport : A light-weight virtual switch in transport equipment SDN Controller XMPP/others JSON /others OpenFlow+ OTS-Management Agent OTS-Control Agent OTS-Data Agent Control Plane Internal Communication Data Forwarding Plane Transport Platform N Physical Interfaces For Open Discussion 8

9 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

10 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

11 Operation Example #1: Explicit Provisioning F L1 A L2 B L3 C L4 D L5 SDN Controller E G H Topology report: L1: 10GE L2: to B, 100GE Provisioning (e.g., OpenFlow): L2-L3 :: map VLAN-200 packets to VIF X VLAN 100 OTS VLAN OTS Wave X OTS VLAN OTS Ethernet Ethernet / DWDM Ethernet / DWDM Ethernet A B C D VLAN 400 For Open Discussion 11

12 Operation Example #2: Implicit Provisioning A B C D E F SDN Controller Provisioning: Setup A-B with BW X Provisioning: Setup C-D with BW X Map data to C-D LSR OTS OTS OTS LSR MPLS LSR POTN A LSR B C POTN OTN (GMPLS) POTN OTS OTS ENET POTN ENET L2 Ethernet OTS ENET D E ENET F Data Data Label Data Data ODU Data Data VLAN Data For Open Discussion 12

13 The existing OpenFlow needs work Functions Example Problem Possible Solution Connection setup F1 (ODU1) F2 (ODU1) Interface 1 Interface 2 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-1 (pkt) Flow-2 (pkt) Flow-3 (e.g. wave) Flow modification message is to add flows to an Ethernet port, not to another flow Introduce the concept of virtual port for nonpacket flows QoS and CAC Flow-1 (7G) Flow-3 (10G) QoS is not in v1.0 Largely solved in v1.3. But need to include latency requirements Flow-2 (3G) Implicit provisioning F1 F2 F3 F4 How can we make flow id s unique? MPLS Label? Push this to OTS-Control to handle For Open Discussion 13

14 Example: Multi-Layer Integration Multiple-Layer Integration Application SDN Controller Topology information Traffic aggregation instruction Access Domain A Domain B Domain Access C 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 For Open Discussion 14

15 Work Items Architecture and framework OpenFlow enhancement discussion, modification and prototyping Protocol extensions for control and management For Open Discussion 15

16 Final Words SDN can speed up service deployment in transport network through network overlay and virtualization Open Transport 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 together For Open Discussion 16