1. Application-oriented Stateful PCE Architecture and Use-cases for Transport Networks Young Lee, Xian Zhang, Haomian Zhang, Dhruv Dhody (Huawei), Guoying Zhang (CATR), Oscar Gonzalez de Dios (Telefonica) PCE WG IETF 88 Vancouver

2. Can PCE support open programmable interfaces that it might support SDN network virtualization for transport networks? Currently, it is out of scope. Related work: – CSO: http://datatracker.ietf.org/doc/draft-dhody-pce- cso-enabled-path-computation/http://datatracker.ietf.org/doc/draft-dhody-pce- cso-enabled-path-computation/ – ABNO: http://datatracker.ietf.org/doc/draft-farrkingel- pce-abno-architecture/http://datatracker.ietf.org/doc/draft-farrkingel- pce-abno-architecture/ – NCFV: http://www.ietf.org/id/draft-lee-network- control-function-virtualization-01.txthttp://www.ietf.org/id/draft-lee-network- control-function-virtualization-01.txt IETF 88, Vancouver2 Background & Motivation

3. SDN concept has been applied for transport networks. – Separation of control plane functions from data planes by GMPLS/ASON control plane technology Link Discovery (LMP) Dissemination of Link/Resource Information (OSPF-TE) Connection/Provisioning (RSVP-TE) – Global view of a network TEDB, LSDB give the global domain view of a network – Logically centralized control PCE for path computation; Stateful PCE for initiation of path provisioning (in cooperation with GMPLS signaling) Can PCE architecture support network virtualization? Transport Network Control 3IETF 88, Vancouver

4. Client Control CC NE CCI GMPLS PCE Client End Point Client End Point Client End Point Client End Point Client Controller Applications Supports various applications via various NB APIs (e.g., OpenStack, etc.) Various types of client to network – Data Center Operators – Virtual Network Providers – Contents Providers – Carriers of carrier Primary source for application service/connectivity requirements and location information (client end points). Network Control But current GMPLS/PCE architecture does not support programmable interfaces for network virtualization 4IETF 88, Vancouver

5. Virtual Network Control Layer CC NE CCI GMPLS Client End Point Client End Point Client End Point Client End Point Client Controller Applications Virtual Network Control Layer Network Control Virtual Network Control separated from Physical network control – Open interfaces creation – Third party developer can develop VNC layer Virtual Network Control Layer provides virtual network control functions: – Virtual Service Creation – Virtual Path Computation – Virtual Topology Database Creation – Virtual Network Discovery – Topology Abstraction for Virtual Service – Virtual connection setup 5IETF 88, Vancouver

6. 6 Application-oriented Stateful PCE Architecture ------------------------------------------ | Application Stratum | ------------------------------------------ /|\ /|\ /|\ | | \|/ North Bound API | | --------------- | \|/ | Client | | -------------- Control | \|/ | Client |-------- -------------- Control | /|\ | Client |------- | | Control | /|\ | -------------- | | /|\ | | Client-VNC Interface | | | (CVI) \|/ \|/ \|/ ---------------------------------- / | Virtual Network Control (VNC) | Transport | ---------------------------------- Network | /|\ Controller | | VNC-PCE Interface (VPI) (TNC) | \|/ | ---------------------------------- \ | Transport Stateful PCE | ---------------------------------- /|\ | PCEP \|/ Physical Network Infrastructure

7. Use-case A: application-specific topology abstraction and virtual control Client B Controller VNC Client C Controller Client A Controller 4 1 2 5 6 5 1 2 5 6 1 1 2 3 4 56 34 34 78 A.1 A.2 A.3 B.1 B.2 B.3 C.2 C.3 2 1 2 3 4 56 3 1 2 3 4 56 PCE Creates abstraction topology per application/client need 4 1 6 5 2 1 13 6 4 3 8 A.1 A.2 A.3 2 1 4 5 3 2 3 6 5 1 1 13 6 8 3 13 5 B.1 B.2 B.3 1 8 3 C.1 C.2 C.3 network topology

8. Use-case: Dynamic DCI in multi-domain network (Topology Request) DC Controller VNC PCE 1 PCE 2 PCE 3 DC1 DC2 DC3DC4 DC5 DC6 Network 1 Network 3 Network 2 1. Topology Request: Endpoints list 2. Topology Request: Endpoints list, peering point 3. Abstracted Topology 4. E2E Abstracted Topology 8IETF 88, Vancouver

9. Use-case: Dynamic DCI in multi-domain network (Connection Request) DC Controller VNC PNC 1 PNC 2 PNC 3 DC1 DC2 DC3DC4 DC5 DC6 Network 1 Network 3 Network 2 1. Connect Request:1-6 3. Connect 2. V_Path Compute 9IETF 88, Vancouver

10. PCE IETF 88, Vancouver10 Implementation Alternatives Client B Controller VNC Client C Controller Client A Controller PCE Client B Controller VNC Client C Controller Client A Controller Focus of PCE protocol extensions Focus of PCE protocol extensions Option A: PCE interacts with VNC Option B: PCE interacts with Client/APP directly

11. Extend the charter if WG thinks this is a viable PCE direction. Explore a new WG formation if WG thinks this is out of scope. IETF 88, Vancouver Next Steps 11