1 / 7

Framework for Abstraction and Control of Transport Networks

Framework for Abstraction and Control of Transport Networks. draft-ceccarelli-actn-framework-04 November 10, 2014 IETF 91 - Honolulu. Drivers of ACTN.

amena-mayer
Download Presentation

Framework for Abstraction and Control of 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. Framework for Abstraction and Control of Transport Networks draft-ceccarelli-actn-framework-04 November 10, 2014 IETF 91 - Honolulu

  2. Driversof ACTN • Operators want to build on top of what they have deployed while pursuing new green field. One of the drivers for ACTN is an horizontal integration based on multi-domain coordination function to enable legacy control/management domains while allowing new domain control like ONF SDN controller. • Separating “virtualizer” level from (physical) network control/management (with minor add-on on these). By doing so, the operational simplification for operators can achieved, helping the introduction of new services/applications that are not tied with specific data plane technologies. • What are the added values of ACTN reference model with respect the ONF architecture ? IETF 91, Honolulu

  3. Controller RoleHierachy NW Mobile customer ISP on-demand NW service customer VPN customer Customer B Control Customer C Control Customer A Control Multi domain coordinationfunction Virtualizerfunction VNC Customermappingfunction PNC GMPLS trigger PNC SDNcontroller PNC SDNcontroller PCE NMS IETF 91, Honolulu

  4. Controller RoleRecursivness Customer D Control VNC Customer C Control Customer B Control VNC relatedto service B Customer A Control VNC VNC relatedto service A PNC GMPLS trigger PNC SDNcontroller PCE NMS Multi domain coordinationfunction Virtualizerfunction IETF 91, Honolulu Customermappingfunction

  5. Interfaces Customer C Control Customer B Control Customer A Control CVI VNC VPI PNC ? GMPLS trigger PNC OF controller PCE NMS Multi domain coordinationfunction Virtualizerfunction IETF 91, Honolulu Customermappingfunction

  6. Interfacesdefinitons CNC (Customer Network Control) -VNC Interface (CVI): • To allow programmability to create, modify and delete virtual network service instances . • Shouldsupportopen standard information models and protocol-specific interface data schema able to carry abstracted topology • Itcould report potential network topologyavailability (availablepath in tunnel or graph) ifqueriedfrom CNC • Topermitrequestofconfigurationofvirtual network resourcesexposedto CNC byvirtualizationfunction at the VNC level. VNC-PNC Interface (VPI): • To allow programmability to service provider(s) (through VNCs) to facilitate path computation, provisioning, and restoration • To communicate creation request of new conncetivity in the physical network (including OAM, layers mapping, performances) • Sincephysical NW mayitselfbevirtual, seamlessmapping and translationbetweenphysical and virtualresources . CVI and VPI intersection: should we make a single i/f ? • Special case for interfaces not fitting the recursive model (e.g. GMPLS) PNC-PNC or VNC-VNC : which interface for recursivness? IETF 91, Honolulu

  7. Controller functions Multi-domain coordination function: • What is a domain? Everything that is under the control of the same controller. • to overcome specifities of the different domain building a single abstracted end-to-end network topology . Virtualizer function: • to provide an abstracted view of the underlying network resources towards client (i.e. customer/higher level controller PNC/VNC) • is present with different scope but same target, at any of the 3-tier level of ACTN Reference Model. • In the PNC to provide mapping between the abstracted CP model of VNC and the specifics of the controlled domain • in the VNC to provide allocation of abstract resources for the specific customer or application. Customer mapping function: • in charge of mapping  VN setup commands into network provisioning requests to the PNC accordingly to business OSS/NMS provisioned static or dynamic policy . IETF 91, Honolulu

More Related