Network Working Group Diego Lopez (Ed.) Telefonica Internet Draft Intended status: Informational May 25, 2014 ACTN Use-case for Virtual Network Operation for Multiple Domains in a Single Operator Network draft-lopez-actn-vno-multidomains-00.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on November 25, 2014. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of Lopez Expires November 25, 2014 [Page 1] Internet-Draft Multi-domain Virtual Network Operation March 2014 publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Abstract This document provides a use-case that addresses the need for facilitating the application of virtual network abstractions to network operation. These abstractions shall create a virtualized environment supporting operators in viewing and controlling different domains (at any dimension: applied technology, administrative zones, or vendor-specific technology islands) as a single virtualized network. Such an approach will facilitate the deployment of NFV (Network Function Virtualization) mechanisms, and accelerate rapid service deployment of new services, including more dynamic and elastic services, and improve overall network operations and scaling of existing services. This use-case considers the application of these abstractions within the network of a single operator. Table of Contents 1. Introduction..................................................2 2. Operational Issues in Multi-domain Networks....................3 3. Virtual Network Operations for Multi-domain Networks...........6 3.1. Responsibilities of Domain Control/Management Entities....7 3.2. Responsibilities of the VNO Coordinator...................7 3.3. Virtual Network Operations Interface (VNO-I)..............8 4. References.....................................................8 Author's Addresses................................................9 Intellectual Property Statement...................................9 Disclaimer of Validity............................................9 1. Introduction Network operators build and operate their network using multiple domains in different dimensions. Domains may be defined by a collection of links and nodes (each of a different technology), administrative zones under the concern of a particular business entity, or vendor-specific "islands" where specific control mechanisms have to be applied. Establishing end-to-end connections spanning several of these domains is a perpetual problem for operators, which need to address both interoperability and operational concerns at the control and data planes. The introduction of new services, often requiring connections that traverse multiple domains, needs significant planning, and several Lopez Expires September 25, 2014 [Page 2] Internet-Draft Multi-domain Virtual Network Operation March 2014 manual operations to interface different administrative zones, vendor equipment and technology. This is problem becomes more relevant as the consolidation of virtualization technologies like Network Functions Virtualization (NFV) calls for a more elastic behavior of the transport network, able to support their requirements on dynamic infrastructure reconfiguration [NFV-UC]. This document provides a use-case that addresses the aforementioned need within a single operator network. This use-case is a part of the overarching work, called Abstraction and Control of Transport Networks (ACTN). The goal of ACTN is to facilitate virtual network operation by: . The creation of a virtualized environment allowing operators to view the abstraction of the underlying multi-admin, multi- vendor, multi-technology networks and . The operation and control/management of these multiple networks as a single virtualized network. This will accelerate rapid service deployment of new services, including more dynamic and elastic services, and improve overall network operations and scaling of existing services. Related documents are the ACTN-framework [ACTN-Frame] and the problem statement [ACTN-PS]. 2. Operational Issues in Multi-domain Networks As an illustrative example, let's consider a multi-domain network consisting of four administration zones: three Data Center Network zones, A, B and C; and one core Transport Network (TN) zone to which Data Center Network zones A, B and C are inter-connected. These zones are under a single operator's administration, but there are organizational boundaries amongst them (being under the concern of different business units, for example). Figure 1 shows this example multi-domain network. Lopez Expires September 25, 2014 [Page 3] Internet-Draft Multi-domain Virtual Network Operation March 2014 +----------------------+ | +---+ DC Domain B | | |EP6| | | +---+ | | | | | |-------- | | /// \\\ | +----------------+ | // \\ | | TN Domain | || | | +------------------------+ | ---- -|--|| Data Center B | | | DC Domain A | | //- -\\ | | || | | | --------- | | / \| | | \\ // | | /// \\\ | | / \ | | \\\ /// | | // \\ | || || | --------- | | | | | || Transport || +----------------------+ | | Data Center A |-|-|| Network || +----------------------+ | | | | || || | --------- | | \\ // | | \ / | | /// \\\ | | \\\ /// | | \ /| | | // \\ | | | --------- | | | \\- -// | | || | | | | | | | ---- | | || Data Center C | | | +---+ +---+ | | | -|--|| | | | |EP1| |EP2| | | | | | \\ // | | +---+ +---+ | | +---+ | | \\\ /// | +------------------------+ | |EP3| | | |--------- | | | +---+ | | | | | | | | +---+ +---+ | +----------------+ | |EP4| |EP5| | | +---+ +---+ | | DC Domain C | +----------------------+ Figure 1. Multi-domain Network Although the figure depicts a single operator's network, there can be several partitions into sub-domains in which some connections may have to traverse several sub-domains to connect End Points (EPs). EPs are customer end-points such as enterprise gateway locations, some of which are directly homed on transport networks, while some Lopez Expires September 25, 2014 [Page 4] Internet-Draft Multi-domain Virtual Network Operation March 2014 others are part of data center networks. EPs can also host physical or virtual network functions (PNFs/VNFs) or virtual machines (VMs). Connections between EPs in many cases have to traverse multiple technology and/or administrative domains. For instance, in Figure 1 if EP1 were to be connected to EP4, then the data path for this connection would have to traverse DC Domain A, TN Domain and DC Domain C where the destination of this connection resides. Another example of a multi-domain connection would be from EP3 in TN Domain to EP 6 in DC Domain B. There are also intra-domain connections; for instance, a connection from EP4 to EP5 would only constitute an intra-domain connection within DC Domain C. We can assume there are domain control entities of various types (e.g., SDN-controller, NMS/EMS, Control Plane, or a combination of these entities, etc.) responsible for domain-specific network operations such as connection operation and management (including creation/deletion of a connection, path computation and protections, etc.), and other functions related to operations such as configuration, monitor, fault management, etc. As different technologies have emerged in different times, there is a plethora of diverse domain control systems with their respective interfaces and protocols. To maximize capital investments, operators tend to keep the current legacy operation and management technology and to continue to offer network services from the technology deployed in their networks. Due to these domain boundaries, facilitating connections that traverse multi-domains is not readily achieved. Each domain control establishing other domain control in a peer to peer level creates permutation issues for the end-to-end control. Besides, these domain controls are optimized for its local operation and in most cases not suited for controlling the end-to-end connectivity services. For instance, the discovery of the EPs that belong to other domains is hard to achieve partly because of the lack of the common API and its information model and control mechanisms thereof to disseminate the relevant information. Moreover, the path computation for any end-to-end connection would need abstraction of network resources and ways to find an optimal path that meets the connection's service requirements. This would require knowledge of the inter-domain peering relationships and the local domain policy. From a connection provisioning perspective, in order to facilitate a fast and reliable end-to-end signaling, each domain operation and management elements should ideally speak the same control protocols to its neighboring domains. Lopez Expires September 25, 2014 [Page 5] Internet-Draft Multi-domain Virtual Network Operation March 2014 From a network connectivity management perspective, it would require a mechanism to disseminate any connectivity issues from the local domain to the other domains whenever the local domain cannot resolve a connectivity issues. 3. Virtual Network Operations for Multi-domain Networks Based on the issues discussed in the previous section in regard to the operations for multi-domain networks, we propose the definition of a virtual network operations (VNO) infrastructure that helps operators to establish end-to-end connections spanning multiple domains and its related operation and management issues. The VNO Coordinator facilitates virtual network operation, the creation of a virtualized environment allowing operators to view the underlying multi-admin, multi-vendor, multi-technology networks and their operation and management as a single, virtualized network. The basic premise of VNO is to create a hierarchy of operations in which to separate virtual network operations from physical network operations. This helps operators build virtual network operations infrastructure on top of physical network operations. Figure 2 shows a hierarchical structure of operations. +----------------------+ | VNO Coordinator | +----------------------+ | | VNO-I .-----------------------------------------. | | | | +----------+ +----------+ +----------+ +----------+ | DCN | | DCN | | DCN | | | | Domain A | | Domain B | | Domain C | | TN Domain| | Control | | Control | | Control | | Control | | | | | | | | | +----------+ +----------+ +----------+ +----------+ | | | | /----\ /----\ /----\ /----\ // \\ // \\ // \\ // \\ | DC A | | DC B | | DC C | | Transport| \\ // \\ // \\ // \\Network/ \----/ \----/ \----/ \----/ Figure 2. Operations Hierarchy Lopez Expires September 25, 2014 [Page 6] Internet-Draft Multi-domain Virtual Network Operation March 2014 Figure 2 shows operations hierarchy based on Figure 1. The two main ideas are: 1. Domain control/management entities (e.g., DCN Domain Control A, B, C and TN Domain Control) are kept intact to continue its domain operations with its technology choice and policy, etc. As discussed before domain control/management entities can be a form of various types (e.g., SDN-controller, NMS/EMS, Control Plane, or a combination of these entities, etc.) that is responsible for domain-specific network operations. 2. The VNO Coordinator establishes a standard-based API (which is termed as the Virtual Network Operations Interface (VNO-I) in Figure 2) with each of the domain control/management entities. The VNO coordination takes place via the VNO-I's. 3.1. Responsibilities of Domain Control/Management Entities . Creation of domain-level abstraction of network topology It is the responsibility of domain control/management entity to create an abstraction of its network topology. The level of abstraction varies from one domain to another, subject to local domain policy. All EPs and gateway nodes to other domains need to be represented at a minimum. The level of internal nodes and links may be abstracted according to its domain policy. . Dissemination of abstraction of network topology to the VNO Coordinator (both Push and Pull models) . VNO interface support (e.g., protocol, messages, etc.) . Domain-level connection control/management that includes creation/deletion of a connection . Domain-level path computation . Domain-level protection and reroute . Other functions related to operations such as monitor, fault management, etc. 3.2. Responsibilities of the VNO Coordinator . Creation of a global abstraction of network topology. Lopez Expires September 25, 2014 [Page 7] Internet-Draft Multi-domain Virtual Network Operation March 2014 The VNO Coordinator assembles each domain level abstraction of network topology into a global abstraction of the end-to-end network. . VNO interface support (e.g., protocol, messages, etc.) . End-to-end connection lifecycle management . Invocation of path provisioning request to each domain . Invocation of path protection/reroute to the affected domain(s) . End-to-end network monitoring and fault management . OSS/BSS interface support for service management 3.3. Virtual Network Operations Interface (VNO-I) [Editor's Note: the details of the supported functions of the VNO-I as well as the discussions pertaining to the info/data model requirements of the VNO-I will be supplied in the revision] 4. References [ACTN-Frame] D. Ceccarelli, L. Fang, Y. Lee and D. Lopez, "Framework for Abstraction and Control of Transport Networks," draft- ceccarelli-actn-framework, work in progress. [ACTN-PS] Y. Lee, D. King, M. Boucadair, and R. Jing, "Problem Statement for the Abstraction and Control of Transport Networks," draft-leeking-actn-problem-statement, work in progress. [NFV-UC] NFV ETSI Industry Specification Group (ISG), "Network Functions Virtualisation (NFV); Use Cases", http://www.etsi.org/deliver/etsi_gs/NFV/001_099/001/01.01. 01_60/gs_NFV001v010101p.pdf Lopez Expires September 25, 2014 [Page 8] Internet-Draft Multi-domain Virtual Network Operation March 2014 Author's Addresses Diego Lopez (Editor) diego@tid.es Young Lee leeyoung@huawei.com Intellectual Property Statement The IETF Trust takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in any IETF Document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Copies of Intellectual Property disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement any standard or specification contained in an IETF Document. Please address the information to the IETF at ietf-ipr@ietf.org. Disclaimer of Validity All IETF Documents and the information contained therein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Lopez Expires September 25, 2014 [Page 9] Internet-Draft Multi-domain Virtual Network Operation March 2014 Lopez Expires September 25, 2014 [Page 10]