--- 1/draft-ietf-teas-actn-requirements-00.txt 2015-10-01 14:15:11.538406060 -0700 +++ 2/draft-ietf-teas-actn-requirements-01.txt 2015-10-01 14:15:11.578406991 -0700 @@ -1,33 +1,33 @@ Network Working Group Young Lee (Editor) Dhruv Dhody Internet Draft Huawei Intended status: Informational Sergio Belotti Alcatel-Lucent -Expires: January 2016 +Expires: April 2016 Khuzema Pithewan Infinera Daniele Ceccarelli Ericsson October 1, 2015 Requirements for Abstraction and Control of TE Networks - draft-ietf-teas-actn-requirements-00.txt + draft-ietf-teas-actn-requirements-01.txt Abstract This draft provides a set of requirements for abstraction and - control of transport networks. + control of TE networks. 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. @@ -55,38 +55,82 @@ publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction...................................................2 - 2. High-level ACTN requirements...................................3 - 3. ACTN Use-Cases.................................................7 - 3.1. Two categories of requirements...........................10 - 4. ACTN interfaces requirements..................................14 - 4.1. CMI Interface Requirements...............................15 - 4.2. MPI (MDSC-PNC Interface).................................17 - 5. References....................................................20 - 5.1. Informative References...................................20 - 6. Contributors..................................................21 - Contributors' Addresses..........................................21 - Authors' Addresses...............................................21 + 2. High-level ACTN requirements...................................4 + 3. ACTN Use-Cases.................................................8 + 3.1. Two categories of requirements...........................11 + 4. ACTN interfaces requirements..................................15 + 4.1. CMI Interface Requirements...............................16 + 4.2. MPI (MDSC-PNC Interface).................................18 + 5. References....................................................21 + 5.1. Informative References...................................21 + 6. Contributors..................................................22 + Contributors' Addresses..........................................22 + Authors' Addresses...............................................22 1. Introduction - This draft provides a set of requirements for ACTN identified in - various use-cases of ACTN. [ACTN-frame] defines the base reference - architecture and terminology. [ACTN-PS] provides problem statement - and gap analysis. + This draft provides a set of requirements for Abstraction and + Control of TE Networks (ACTN) identified in various use-cases of + ACTN. [ACTN-frame] defines the base reference architecture and + terminology. [ACTN-PS] provides problem statement and gap analysis. + + ACTN refers to the set of virtual network operations needed to + orchestrate, control and manage large-scale multi-domain TE networks + so as to facilitate network programmability, automation, efficient + resource sharing, and end-to-end virtual service aware connectivity + and network function virtualization services. + + These operations are summarized as follows: + + - Abstraction and coordination of underlying network resources + to higher-layer applications and customers, independent of how + these resources are managed or controlled, so that these + higher-layer entities can dynamically control virtual + networks. Where control includes creating, modifying, + monitoring, and deleting virtual networks. + + - Multi-domain and multi-tenant virtual network operations via + hierarchical abstraction of TE domains that facilitates + multi-administration, multi-vendor, and multi-technology + networks as a single virtualized network. This is achieved by + presenting the network domain as an abstracted topology to the + customers via open and programmable interfaces. Which allows + for the recursion of controllers in a customer-provider + relationship. + + - Orchestration of end-to-end virtual network services and + applications via allocation of network resources to meet + specific service, application and customer requirements. + + - Adaptation of customer requests (made on virtual resources) to + the physical network resources performing the necessary + mapping, translation, isolation and, policy that allows + conveying, managing and enforcing customer policies with + respect to the services by the network to said customer. + + - Provision of a computation scheme and virtual control + capability via a data model to customers who request virtual + network services. Note that these customers could, themselves, + be service providers. + + ACTN solutions will build on, and extend, existing TE constructs and + TE mechanisms wherever possible and appropriate. Support for + controller-based approaches is specifically included in the possible + solution set. Section 2 provides high-level ACTN requirements. Sections 3-5 provide the list of ACTN use-cases and the detailed requirement analysis of these use-cases. 2. High-level ACTN requirements 1. Requirement 1: Single Virtualized Network Topology Ability to build virtual network operation infrastructure based