An Inter-domain SDN Testbed and its Fine-grained Routing Application Demonstration

(1)

An Inter-domain SDN Testbed

and its Fine-grained Routing

Application Demonstration

Jun Bi

Tsinghua University/CERNET

Presenting on behalf of CANS Future Internet WG (FIWG)

CANS2014, New York 2014.09.15

(2)

}  Tsinghua Univ./CERNET

–  Prof. Jun Bi

–  Dr. Yangyang Wang

(application)

–  Anmin Xu (coding)

–  Yikai Lin (coding)

–  Ze Chen (coding)

–  Pingping Lin

–  Prof. Jilong Wang /

Zhonghui Li/Zhiyan Zheng (infrastructure)

Contributors

}  CSTNET –  Dr. Yulei Wu –  Dr. Yuepeng E (configuration) }  BUPT –  Prof. Yan Ma –  Prof. Xiaohong Huang –  Chunbing Zhang (configuration) } 

Interent2

–  Steve Wolff –  John Hicks (configuration) –  Edward Moynihan –  Di Lu } 

SURFnet

–  Ronald van der Pol (configuration)

(3)

• Inter-domain SDN: Motivations

• Inter-domain SDN: Mechanism - WE-Bridge

• Inter-domain SDN Testbed and Applications

(with live demo)

• Conclusions and Future Work

Content

(4)

Inter-domain SDN:

Motivations

(5)

• Software defined networking (SDN) is one of the hot

research topics in networking area

• Openness

–  decouples the tightly coupled network architecture, and

opens up the control plane and the associated protocol

• Agility

–  SDN enables more flexible network control and

management

–  SDN promotes the rapid innovation on networking

technologies by programing the network

• SDN is considered as a promising way to enhance

the networks.

(6)

SDN Architecture

East-west Boundary North Boundary South Boundary Inter-domain SDN APPs

Inter-domain control mechanism WE-Bridge

Inter-domain Infrastructure

(7)

• Inter-domain

(Shall we provide real topo., full control to others ?)

–  The Internet are managed by owners of different domains, which makes the centralized control doesn’t work for inter-domain

• Scalability

–  Centralized control could not scale to a very large network (may work for a data center or a campus, but not Internet scale)

• Use cases

–  To improve the feasibility in real world

• Other Challenges

–  Data plan

–  Security

–  …

(8)

• Inter-domain

–  The Internet are managed by owners of different domains, which make the centralized control doesn’t work for inter-domain

• Scalability

–  Centralized control could not scale to a very large network (work for data center, campus, but not Internet scale)

• Use cases

–  To improve the feasibility in real world

• Other Challenges

–  Data plan –  Security –  …

SDN Research Challenges

Covered by WE-Bridge

(9)

•  Inter-domain

–  Change centralized resource control by global network view

negotiation on inter-domain resource by exchanging domain views

•  Scalability

–  Change logical or physical centralized control　

　distributed mechanism for the Internet scale

•  Use cases

–  We developed Three example use cases and demos

•  Other Challenges

–  Data plain

–  Security

–  …

(10)

•  We proposed a Four-layer FINE (Future Internet iNnovation

Environment) Architecture _{in China’s 863 High-tech R&D project}

WE-Bridge proposed in

FINE

DPA1 Open Devices Local View API Global Physical View API Logical View API AS-1 (Doman 1) DPA2 DPAn

APP-1 APP-2 APP-n

DPA1

AS-2 (Domain 2)

DPA2 DPAn

APP-1 APP-2 APP-n

IDN IDN IDN IDN Open Devices NOS-1 NOS-2 VCP-1 VCP-2 WE-Bridge

(11)

• Google’s B4 (SDN for private WAN)

–

 

is still under one single administrator.

•  Two-level hierarchical centralized control based solution

(12)

• SDX: Software Defined Internet Exchange Center

–  Specific goal: using SDN to connecting traditional BGP

domains

(13)

Inter-domain SDN:

(14)

West-East Bridge for SDN Peering

•  Each NOS gathers local

network view, then

exchange domain view

among heterogeneous　 NOSes by WE-Bridge •  An APP requires resource in other domains by WE-Bridge NB-API

•  APPs in other domains

may accept or deny the request (Negotiation details will be

(15)

WE-Bridge: West-East Bridge in SDN

Network view storage Network view virtualization Network view exchange format Network view distribution North bound API for network view

Network view learning NOS Inter-domain Innovation 1 Inter-domain Innovation 2 Inter-domain Innovation N WE-Bridge West-East Interface

(16)

Physical view to virtual view (PP: Physical Path; VP: Virtual Path; OF: OpenFlow; S: Switch; bd: bandwidth; t: time; bps: bits per second)

Domain View Abstraction: Virtualization

(17)

Domain View Abstraction: Storage

Key Columns

Node_ID (physical/virtual)

is_ virtual (first column)

IP_addresses, OF_version, port_numbers, is_edge_node, Vendor_name, MTU

Device_type, Device_function Link_ID

(physical/virtual)

Node_ID_src, Port_ID_src, Node_ID_dst, Port_ID_dst, Bandwidth, is_interdomain_link

Port_ID (physical/virtual)

Node_ID, Port_MAC, is_active, is_edge_port, VLAN_ID, throughput

Node_capbility protocol_name, version, port Reachability IP_prefixes, length

Node_table_ID (Flow entity)

Columns names are the same as the fields defined in the flowtable in OpenFlow specification

Link_Utilities Link_ID, Link utilities Flow_path

(Node_ID_src_ Node_ID_dst)

Port_ID (in), Node_ID_src, Port_ID (out), Node Series with ingress and egress ports, Port_ID (in), Node_ID_dst, Port_ID (out)

(18)

• We suggest

JSON

as a basic implementation, and the

XML, YANG, YAML as alternatives.

• Those languages have the ability to enable

WE-Bridge with the following advantages:

–  vendor and application-independent, thus the network view

transfer format is independent with the storage systems;

–  allow explicit definition of the inherent structure according

to the requirements; such features make the network view message format flexible and easy to extend;

–  they are files and not a data packet format, containing rich

content.

(19)

•  Enable WE-Bridge in all kinds of NOSes by adding three modules:

–  Network Virtualization, East-West Bridge, and LLDP Extension

(20)

Inter-domain SDN Testbed

and Applications

(21)

CANS13/SuperComputing13/INFOCOM14

Demos for CANS inter-domain SDN testbed

(22)

Global SDN Federal Testbed: Internet2, CERNET (China educa>on and research network), CSTNET (China science and technology network), and SURFNET (the na>onal research and educa>on

network of Netherlands)

CANS13/SuperComputing13/INFOCOM14

Demos on Inter-domain SDN APPs

(23)

(24)

Application demo:

Fine-Grained Inter-domain Diff-Serv Routing

• Traditional differ-serv

defines

fixed differ-serv

bit

, and the service action is also fixed

• In SDN, we can program the networking routing

with flexibility:

fine granularity

inter-domain

diff-serv

can be achieved by flexiblely defining

VIP

service by any field in packet header

(e.g IP

address & UDP port)

• Installing

flow table entries with different service

levels

(routing actions): when link failure

(25)

Demo Introduction

Video chat ﬂow selects another path

Src =101.6.30.103 Dst =207.75.165.202 Udp port =101

VIP Video Conference Addr &UDP Port 5004

VOD Server Addr & UDP Port 1234

VOD Cient 207.75.165.202

VIP Video Conference 207.75.165.202 Link failure Link Recover Ann Arbor NYU Video forwarding