1 / 11

Application-oriented Stateful PCE Architecture and Use-cases for Transport Networks

Application-oriented Stateful PCE Architecture and Use-cases for Transport Networks. <draft-lee-pce-app-oriented-arch-00.txt>. Young Lee, Xian Zhang, Haomian Zhang, Dhruv Dhody (Huawei), Guoying Zhang (CATR), Oscar Gonzalez de Dios ( Telefonica ). PCE WG IETF 88 Vancouver.

xandy
Download Presentation

Application-oriented Stateful PCE Architecture and Use-cases for Transport Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Application-oriented Stateful PCE Architecture and Use-cases for Transport Networks <draft-lee-pce-app-oriented-arch-00.txt> Young Lee, Xian Zhang, HaomianZhang, Dhruv Dhody (Huawei), Guoying Zhang (CATR), Oscar Gonzalez de Dios (Telefonica) PCE WG IETF 88 Vancouver

  2. Background & Motivation • 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/ • ABNO: http://datatracker.ietf.org/doc/draft-farrkingel-pce-abno-architecture/ • NCFV: http://www.ietf.org/id/draft-lee-network-control-function-virtualization-01.txt IETF 88, Vancouver

  3. Transport Network Control • 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? IETF 88, Vancouver

  4. CC CC CC CC CC NE NE NE NE NE Client Control 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). Client Controller Network Control PCE GMPLS CCI Client End Point Client End Point Client End Point Client End Point But current GMPLS/PCE architecture does not support programmable interfaces for network virtualization IETF 88, Vancouver

  5. CC CC CC CC CC NE NE NE NE NE Virtual Network Control Layer Applications • 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 Client Controller Virtual Network Control Layer Network Control GMPLS CCI Client End Point Client End Point Client End Point Client End Point IETF 88, Vancouver

  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 IETF 88, Vancouver

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

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

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

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

  11. Next Steps • 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

More Related