draft-klee-actn-connectivity-multi-vendor-domains-01 July 24, 2014 IETF ‘90 - Toronto

1. ACTN Use-case for On-demand E2E Connectivity Services in Multiple Vendor Domain Transport Networks draft-klee-actn-connectivity-multi-vendor-domains-01 July 24, 2014 IETF ‘90 - Toronto

2. Transport SDN Strategy • Transport SDN (PTN/OTN) • Centralized Control (TCO reduction) • E2E On-Demand Provisioning (New Business) Transport SDN controller Converged packet-optical core domain CE Access Domain Access Domain CE End-to-End connection

3. Problem of Current Transport Network • Vendor’s EMS/NMS only provides topology management and path provisioning within its own domain. • How to establish E2E connection across multiple vendor domains? End-to-End Connection EVC EVC EVC CE CE Access Domain(Vendor A) Core Domain (Vendor B) Access Domain (Vendor C) CE CE

4. Information Flow Requirements • ACTN Use-case Information Flow Requirements • ACTN can solve the interoperability problems between multiple vendor domain transport networks Customer On-Demand Network Service Abstracted Global View Single Integrated E2E Network View Immediate Need for Standard Solution Domain A Control Domain B Control

5. High-level Requirements • Single Integrated E2E Network View • collect domain-level data such as topology and capability. • compute paths and provision the end-to-end paths that traverse multiple vendor domains. • coordinate a signaling flow for end-to-end connections to each domain involved. • Domain border information • discovery of inter-connection information such as domain border nodes and links between each domain. • should recognize interoperability method between each domain.

6. High-level Requirements • Programmable API • Need to common API for on-demand connectivity service • Following items are required: • Abstraction of network resource (e.g. topology, inter-domain gateway) • Physical network constraints (e.g. SRLG, link types) • Domain preference and local policy (e.g. operator’s policy) • Domain network capability (e.g. support of push/pull model)

7. Virtual Network Operation for Multiple Domain in a Single Operator Networkdraft-lopez-actn-vno-multidomains-00.txt Diego Lopez, Telefonica Oscar deDios Gonzales, Telefonica

8. Overview • We have a similar use-case with KT, but with different contexts/scenarios. • We have global network operations in different continents dealing with different transport domains (internal/trusted) for end-to-end connectivity.

9. Global Network Operation Transport Network Domain C DC 3 Transport Network Domain A DC 1 DC 4 DC 2 Transport Network Domain B • Heterogeneous domains: • Transport Technology (MPLS-TE/TP, OTN, WSON, etc.) • Domain Control (SDN for DCN, GMPLS/PCE for some transport • domains and EMS-based for other transport domains) • Vendor Domain • Administration Domain (A, B, C belong to different admin under Telefonica) • Dynamic Reconfiguration Requirement • End-to-end coordination, End-to-end resource view, domain-boundary • info EP 1 DCN Domain 2 EP 2 DCN Domain 1

10. Our Goal • The creation of a virtualized environment allowing operators to view the abstraction of the underlying multi-admin, multi-vendor, multi-technology networks • The operation and control/management of these multiple networks as if it is a single virtualized network.

11. How can we get there • We need a control hierarchy • A central global control interfacing domain controls • We need a common resource abstraction model from each heterogeneous domain control • We need a common control mechanism that support: • End-to-end Path computation • End-to-end Connection with dynamicity requirements • End-to-end Connection Life Cycle Management • End-to-end Path Rerouting

12. Thank You!