1. Multi-layer Multi-domain Inter-op Test based on ACTN Architecture
SDN RG, IETF 97th, Seoul, Korea
Haomian Zheng
Young
Daniele Ceccarelli
Jong Yoon Shin
Yunbin
Yunbo
Yan
Boyuan

2. ACTN Goal Abstraction and Control of Traffic-Engineering Networks
Considered as “SDN Architecture & Solution” in IETF
Compatible in supporting legacy heterogeneous transport network control/management technologies (e.g., GMPLS/ASON, PCE, NMS/EMS).
SDN controllers’ hierarchy and roles
Customer network controllers (CNC)
Multi-domain service coordinators (MDSC)
Physical network controllers (PNC)
Multi-domain service coordination based on abstraction/virtualization.
Distributed data centers dispersed over different domains including wireless backhaul transport, metro and core packet/optical networks.

3. ACTN Architecture： Customer Layer CMI Coordination Layer MPI
Customer Network Controller
PNC (Transport)
PNC
(Access)
PNC (IP)
CNC
MDSC
Customer Layer
MDSC
CMI
Allow Recursion
Multi-domain Service Coordinator
Coordination Layer
MPI
Physical Network Controller
Network Control Layer
SBI
Physical Layer

4. Inter-op introduction
MDSC
Choice 1: RESTConf+YANG
Choice 2: PCEP
MPI
PNC
IP/MPLS
PNC
Transport
PNC
Transport
PNC
IP/MPLS
Based on Emulators;
Inter-op focused on ACTN MPI:
Operators are welcomed to discuss or develop their own MDSC;
Vendors are expected to have PNC and device emulators with corresponding solution on Southbound Interface
Multi-layer, multi-domain and multi-protocol is supported;

5. Related IETF work ACTN: Applicability: Yang model (with RESTconf)
draft-ietf-teas-actn-requirements
draft-ietf-teas-actn-framework
Applicability:
draft-zhang-teas-actn-yang
draft-dhody-pce-applicability-actn
Yang model (with RESTconf)
For Topology: Based on draft-ietf-teas-yang-te-topo-04
For Services: Based on draft-zhang-teas-transport-service-model-00
PCEP:
For Topology: draft-dhodylee-pce-pcep-ls-04
For Services: draft-ietf-pce-pce-initiated-lsp-05/draft-dhodylee-pce-stateful-hpce

6. ACTN Test Case (1) – Topology Abstraction
PNC (IP)
PNC (T)
MDSC
MPI
Topology Abstraction Steps:
Preparation (respective TED & Abstraction Algorithm as per PNC):
Each PNC report abstracted topology to MDSC; MDSC create its TED;
RESTconf: Get message with topo model for initial topo, with notification on changes;
PCEP-LS: LSRpt message for both initial topology and changes;
MDSC need to detect the cross-domain link, and stitching to get full topology;

7. ACTN Test Case(2) – E2E Service Provision
Service Provisioning Steps:
MDSC initiate a service provisioning request;
RESTconf: POST message with Service YANG model;
Use Hierarchical PCInitiate for PCEP;
Each PNC compute intra-domain path, and establish it respectively;
Process is domain-specific, report to MDSC via standard HTTP message;
MDSC should have DELETE operation;

8. ACTN Test Case(3) – Bandwidth Adjustment
Service A
DC2 A1 A2 B1 B2 C1 C2
DC1
Service B A3 A4 B3 B4 C3 C4
DC3
Bandwidth adjustment Steps:
Set up two ‘existing’ LSPs, say 30G and 10G respectively;
Update the bandwidth for two LSPs:
RESTconf: PUT message with Service model;
PCEP: PCUpd and PCRpt message;
Looks like a ‘DC load balance’;

9. ACTN Test Case(4) – Inter-domain Restoration
DC2
DC3
DC1
PNC (IP)
PNC (T)
MDSC
MPI
Inter-domain Restoration Steps
Create one service between DC1 and DC2;
Detect a ‘failure’ in transport domain, and assume there is not enough resources to do intra-domain restoration; need to report to MDSC;
MDSC create backup inter-layer paths based on failure notification;

10. Future work Future Work: Suggest to IETF&SDN RG:
Continue our job on inter-op test;
Result will be published in ACTN wiki after IETF: ;
We are willing to see interests and partners to work together.
Suggest to IETF&SDN RG:
Would be nice to see official inter-op test events

11. Thank You! BnB Demo Available on Thursday Night!