Network Working Group Young Lee Internet Draft Huawei Intended status: Informational Sergio Belotti Alcatel-Lucent Expires: October 2015 Khuzema Pithewan Infinera Daniele Ceccarelli Ericsson April 6, 2015 Requirements for Abstraction and Control of Transport Networks draft-actn-requirement-02.txt Abstract This draft provides a set of requirements for abstraction and control of transport 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. 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. Lee, et. al. Expires October 6, 2015 [Page 1] Internet-Draft ACTN Requirement April 2015 This Internet-Draft will expire on October 6, 2015. Copyright Notice Copyright (c) 2015 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 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.................................................6 3.1. Two categories of requirements............................9 4. Mapping of requirements into generalized scenarios............13 4.1. Coordination of Multi-destination Service Requirement/Policy ..............................................................15 4.2. Application Service Policy-aware Network Operation.......17 4.3. Dynamic Service Control Policy Enforcement for Performance and Fault Management..........................................18 4.4. E2E VN Survivability and Multi-Layer (Packet-Optical) Coordination for Protection/Restoration.......................19 5. ACTN interfaces requirements..................................20 5.1. CMI Interface Requirements...............................21 5.2. MPI (MDSC-PNC Interface).................................24 6. References....................................................28 6.1. Informative References...................................28 7. Contributors..................................................29 Contributors' Addresses..........................................29 Authors' Addresses...............................................29 1. Introduction This draft provides a set of requirements for ACTN identified in various use-cases of ACTN. Lee, et, al. Expires October 6, 2015 [Page 2] Internet-Draft ACTN Requirement April 2015 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. The terminology and the base architecture are based on [ACTN-frame]. 2. High-level ACTN requirements 1. Requirement 1: Single Virtualized Network Topology Ability to build virtual network operation infrastructure based on multi-layer, multi-domain topology abstracted from multiple physical network controllers (e.g., GMPLS, OpenFlow, PCE, NMS, etc.) 2. Requirement 2: Policy Enforcement Ability to provide service requirement/policy (Between Customer and Network) and mechanism to enforce service level agreement. - Endpoint selection policy, routing policy, time-related policy, etc. 3. Requirement 3: VN Query Ability to request/respond VN Query (Can you give me VN(s)?) - Request Input: - VN end-points (CE end) - VN Topology Service-specific Multi-Cost Objective Function - VN Topology diversity (e.g., VN1 and VN2 must be disjoint) - VN Topology type: path, graph - Response includes VN topology Lee, et, al. Expires October 6, 2015 [Page 3] Internet-Draft ACTN Requirement April 2015 - Exact - Potential 4. Requirement 4: VN Instantiate Ability to request/confirm VN Instantiation - VN instance ID - VN end-points - VN constraints requirement - Latency only, B/W guarantee, Latency and B/W guarantee together - VN diversity - Node/Link disjoint from other VNs - VN level diversity (e.g., VN1 and VN2 must be disjoint) - VN type - Path (tunnel), Node/Links (graph) - VN instance ID per service (unique id to identify VNs) 5. Requirement 5: Dynamic VN Control Dynamic/On-demand VN Modification/Confirmation with feedback loop to the customer - Traffic monitoring and control policies sent to the network - Network states based traffic optimization policies - Utilization Monitoring (Frequency of report) - Abstraction of Resource Topology reflecting these service- related parameters Lee, et, al. Expires October 6, 2015 [Page 4] Internet-Draft ACTN Requirement April 2015 6. Requirement 6: VN Lifecycle M&O VN lifecycle management/operation - Instantiate - Delete - Modify - Update (VN level OAM Monitoring) under policy agreement 7. Requirement 7: VN Service Operation Ability to setup and manage end-2-end service on the VN involving multi-domain, multi-layer, meeting constraints based on SLAs 8. Requirement 8: Multi-destination Coordination Coordination of multi-destination service requirement/policy to support dynamic applications such as VM migration, disaster recovery, load balancing, etc. - Service-policy primitives and its parameters 9. Requirement 9: Multi-domain & Multi-layer Coordination Ability to Coordinate multi-domain and multi-layer path computation and setup operation (network) - Computes E2E path across multi-domain (based on abstract topology from each domain) - Determines the domain sequence - Request path signaling to each domain controller - Find alternative path if any of the domain controllers cannot find its domain path Lee, et, al. Expires October 6, 2015 [Page 5] Internet-Draft ACTN Requirement April 2015 10. Requirement 10: E2E Path Restoration Ability to perform E2E Path Restoration Operation - Intra-domain recovery - Cross-domain recovery 11. Requirement 11: Dynamicity of network control operations The ACTN interfaces should support dynamicity nature of network control operations. This includes but not limited to the following: - Real-time VN control (e.g., a fast recovery/reroute upon network failure). - Fast convergence of abstracted topologies upon changes due to failure or reconfiguration across the network domain view, the multi-domain network view and the customer view. - Large-scale VN operation (e.g., ability to query tens of thousands of nodes and connectivity) for time-sensitive applications. 3. ACTN Use-Cases Listed below is a set of high-level requirements identified by each of the ACTN use-cases: - draft-cheng-actn-ptn-requirements-00 (ACTN Use-cases for Packet Transport Networks in Mobile Backhaul Networks) o Faster End-to-End Enterprise Services Provisioning o Multi-layer coordination in L2/L3 Packet Transport Networks o Optimizing the network resources utilization (supporting various performances monitoring matrix, such as traffic flow statistics, packet delay, delay variation, throughput and packet-loss rate) o Virtual Networks Operations for multi-domain Packet Transport Networks - draft-dhody-actn-poi-use-case-03 (Packet Optical Integration (POI) Use Cases for Abstraction and Control of Transport Networks (ACTN)) Lee, et, al. Expires October 6, 2015 [Page 6] Internet-Draft ACTN Requirement April 2015 o Packet Optical Integration to support Traffic Planning, performance Monitoring, automated congestion management and Automatic Network Adjustments o Protection and Restoration Synergy in Packet Optical Multi- layer network. o Service Awareness and Coordination between Multiple Network Domains - draft-fang-actn-multidomain-dci-01 (ACTN Use Case for Multi- domain Data Center Interconnect) o Multi-domain Data Center Interconnection to support VM Migration, Global Load Balancing, Disaster Recovery, On- demand Virtual Connection/Circuit Services o The interfaces between the Data Center Operation and each transport network domain SHOULD support standards-based abstraction with a common information/data model to support the following: . Network Query (Pull Model) from the Data Center Operation to each transport network domain to collect potential resource availability (e.g., BW availability, latency range, etc.) between a few data center locations. . Network Path Computation Request from the Data Center Operation to each transport network domain to estimate the path availability. . Network Virtual Connections/Circuits Request from the Data Center Operation to each transport domain to establish end-to-end virtual connections/circuits (with type, concurrency, duration, SLA.QoS parameters, protection.reroute policy options, policy constraints such as peering preference, etc.). . Network Virtual Connections/Circuits Modification Request - draft-klee-actn-connectivity-multi-vendor-domains-03 (ACTN Use- case for On-demand E2E Connectivity Services in Multiple Vendor Domain Transport Networks) o Two-stage path computation capability in a hierarchical control architecture (MDSC-PNC) and a hierarchical composition of integrated network views o Coordination of signal flow for E2E connections. o Abstraction of: Lee, et, al. Expires October 6, 2015 [Page 7] Internet-Draft ACTN Requirement April 2015 . Inter-connection data between domains . Customer Endpoint data . The multiple levels/granularities of the abstraction of network resource (which is subject to policy and service need). . Any physical network constraints (such as SRLG, link distance, etc.) should be reflected in abstraction. . Domain preference and local policy (such as preferred peering point(s), preferred route, etc.), Domain network capability (e.g., support of push/pull model). - draft-kumaki-actn-multitenant-vno-00 (ACTN : Use case for Multi Tenant VNO) o On-demand Virtual Network Service Creation o Domain Control Plane/Routing Layer Separation o Independent service Operation for Virtual Services from control of other domains o Multiple service level support for each VN (e.g., bandwidth and latency for each VN service). o VN diversity/survivability should be met in physical network mapping. o VN confidentiality and sharing constraint should be supported. - draft-lopez-actn-vno-multidomains-01 (ACTN Use-case for Virtual Network Operation for Multiple Domains in a Single Operator Network) o Creation of a global abstraction of network topology: The VNO Coordinator assembles each domain level abstraction of network topology into a global abstraction of the end-to- endnetwork. o End-to-end connection lifecycle management o Invocation of path provisioning request to each domain (including optimization requests) o Invocation of path protection/reroute to the affected domain(s) o End-to-end network monitoring and fault management. This could imply potential KPIs and alarm correlation capabilities. o End-to-end accounting and generation of detailed records for resource usage o End-to-end policy enforcement Lee, et, al. Expires October 6, 2015 [Page 8] Internet-Draft ACTN Requirement April 2015 - draft-shin-actn-mvno-multi-domain-00 (ACTN Use-case for Mobile Virtual Network Operation for Multiple Domains in a Single Operator Network) o Resource abstraction: operational mechanisms in mobile backhaul network to give the current network usage information for dynamic and elastic applications be provisioned dynamically with QoS guarantee. o Load balancing or for recovery, the selection of core DC location from edge constitutes a data center selection problem. o Multi-layer routing and optimization, coordination between these two layers. - draft-xu-actn-perf-dynamic-service-control-02 (Use Cases and Requirements of Dynamic Service Control based on Performance Monitoring in ACTN Architecture) o Dynamic Service Control Policy enforcement and Traffic/SLA Monitoring: . Customer service performance monitoring strategy, including the traffic monitoring object (the service need to be monitored) . monitoring parameters (e.g., transmitted and received bytes per unit time), . traffic monitoring cycle (e.g., 15 minutes, 24 hours), . threshold of traffic monitoring (e.g., high and low threshold), etc. 3.1. Two categories of requirements This section provides a summary of use-cases in terms of two categories: (i) service-specific requirements; (ii) network-related requirements. Service-specific requirements listed below are uniquely applied to the work scope of ACTN. Service-specific requirements are related to virtual service coordination function defined in Section 3. These requirements are related to customer's VNs in terms of service policy associated with VNs such as service performance objectives, VN endpoint location information for certain required service- Lee, et, al. Expires October 6, 2015 [Page 9] Internet-Draft ACTN Requirement April 2015 specific functions (e.g., security and others), VN survivability requirement, or dynamic service control policy, etc. Network-related requirements are related to virtual network operation function defined in Section 3. These requirements are related to multi-domain and multi-layer signaling, routing, protection/restoration and synergy, re-optimization/re-grooming, etc. These requirements are not inherently unique for the scope of ACTN but some of these requirements are in scope of ACTN, especially for coherent/seamless operation aspect of multiple controller hierarchy. The following table gives an overview of service-specific requirements and network-related requirements respectively for each ACTN use-case and identifies the work in scope of ACTN. Lee, et, al. Expires October 6, 2015 [Page 10] Internet-Draft ACTN Requirement April 2015 Use- Service- Network-related ACTN Work case specific Requirements Scope Requirements ------- -------------- --------------- -------------- Cheng - E2E service - Multi-layer - Dynamic provisioning (L2/L2.5) multi-layer - Performance coordination coordination monitoring - VNO for multi- based on - Resource domain transport utilization is utilization networks in scope of abstraction ACTN - YANG for utilization abstraction ------- -------------- ---------------- -------------- Dhody - Service - POI - Performance awareness/ Performance related data coordination monitoring model may be between P/O. - Protection/ in scope of Restoration ACTN synergy - Customer's VN survivability policy enforcement for protection/res toration is unique to ACTN. ------- -------------- ---------------- -------------- Fang - Dynamic VM - On-demand - Multi- migration virtual circuit destination (service), request service Global load - Network Path selection balancing Connection policy (utilization request enforcement efficiency), and its Disaster related recovery primitives/inf - Service- ormation are aware network unique to query ACTN. Lee, et, al. Expires October 6, 2015 [Page 11] Internet-Draft ACTN Requirement April 2015 - Service - Service- Policy aware network Enforcement query and its data model can be extended by ACTN. ------- -------------- ---------------- -------------- Klee - Two stage path - Multi-domain computation service policy E2E signaling coordination coordination to network primitives is - Abstraction of in scope of inter-domain ACTN info - Enforcement of network policy (peering, domain preference) - Network capability exchange (pull/push, abstraction level, etc.) ------- -------------- ---------------- -------------- Kumaki - On-demand VN - All of the creation service- - Multi- specific lists service level in the left for VN column is - VN unique to survivability ACTN. /diversity/con fidentiality ------- -------------- ---------------- -------------- Lopez - E2E - E2E connection - Escalation accounting and management, path of performance resource usage provisioning and fault data - E2E network management Lee, et, al. Expires October 6, 2015 [Page 12] Internet-Draft ACTN Requirement April 2015 - E2E service monitoring and data to CNC policy fault management and the policy enforcement enforcement for this area is unique to ACTN. ------- -------------- ---------------- -------------- Shin - Current - LB for - Multi-layer network recovery routing and resource - Multi-layer optimization abstraction routing and are related to Endpoint/DC optimization VN's dynamic dynamic coordination endpoint selection (for selection VM migration) policy. ------- -------------- ---------------- -------------- Xu - Dynamic - Traffic - Dynamic service monitoring service control policy - SLA monitoring control policy enforcement enforcement - Dynamic and its service control control primitives are in scope of ACTN - Data model to support traffic monitoring data is an extension of YANG model ACTN can extend. 4. Mapping of requirements into generalized scenarios The subsequent sections provide the mapping of requirements into a number of generalized scenarios. - Coordination of Multi-destination Service Requirement/Policy (Section 2.1) - Application Service Policy-aware Network Operation (section 2.2) - Dynamic Service Control Policy Enforcement for Performance/Fault Management (Section 2.3) Lee, et, al. Expires October 6, 2015 [Page 13] Internet-Draft ACTN Requirement April 2015 - E2E VN Survivability and Multi-Layer (Packet-Optical) Coordination for Protection/Restoration (Section 2.4) Lee, et, al. Expires October 6, 2015 [Page 14] Internet-Draft ACTN Requirement April 2015 4.1. Coordination of Multi-destination Service Requirement/Policy +----------------+ | CNC | | (Global DC | | Operation | | Control) | +--------+-------+ | | Service Requirement/Policy: | | - Endpoint/DC location info | | - Endpoint/DC dynamic | | selection policy | | (for VM migration, DR, LB) | v +---------+--------+ | Multi-domain | Service policy-driven |Service Controller| dynamic DC selection +-----+---+---+----+ | | | | | | +----------------+ | +----------------+ | | | +-----+-----+ +-----+------+ +------+-----+ | PNC for | | PNC for | | PNC for | | Transport | | Transport | | Transport | | Network A | | Network B | | network C | +-----------+ +------------+ +------------+ | | | +---+ ------ ------ ------ +---+ |DC1|--//// \\\\ //// \\\\ //// \\\\---+DC4| +---+ | | | | | | +---+ | TN A +-----+ TN B +----+ TN C | / | | | | | / \\\\ //// / \\\\ //// \\\\ //// +---+ ------ / ------ \ ------ \ |DC2| / \ \+---+ +---+ / \ |DC6| +---+ \ +---+ +---+ |DC3| \|DC4| +---+ +---+ DR: Disaster Recovery LB: Load Balancing Figure 1: Service Policy-driven Data Center Selection Lee, et, al. Expires October 6, 2015 [Page 15] Internet-Draft ACTN Requirement April 2015 Figure 1 shows how VN service policies from the CNC are incorporated by the MDSC to support multi-destination applications. Multi- destination applications refer to applications in which the selection of the destination of a network path for a given source needs to be decided dynamically to support such applications. Data Center selection problems arise for VM mobility, disaster recovery and load balancing cases. VN's service policy plays an important role for virtual network operation. Service policy can be static or dynamic. Dynamic service policy for data center selection may be placed as a result of utilization of data center resources supporting VNs. The MSDC would then incorporate this information to meet the service objective of this application. Lee, et, al. Expires October 6, 2015 [Page 16] Internet-Draft ACTN Requirement April 2015 4.2. Application Service Policy-aware Network Operation +----------------+ | CNC | | (Global DC | | Operation | | Control) | +--------+-------+ | | Application Service Policy | | - VNF requirement (e.g. | | security function, etc.) | | - Location profile for each VNF | v +---------+--------+ | Multi-domain | Dynamically select the |Service Controller| network destination to +-----+---+---+----+ meet VNF requirement. | | | | | | +---------------+ | +----------------+ | | | +------+-----+ +-----+------+ +------+-----+ | PNC for | | PNC for | | PNC for | | Transport | | Transport | | Transport | | Network A | | Network B | | network C | | | | | | | +------------+ +------------+ +------------+ | | | {VNF b} | | | {VNF b,c} +---+ ------ ------ ------ +---+ |DC1|--//// \\\\ //// \\\\ //// \\\\-|DC4| +---+ | | | | | |+---+ | TN A +---+ TN B +--+ TN C | / | | | | | / \\\\ //// / \\\\ //// \\\\ //// +---+ ------ / ------ \ ------ \ |DC2| / \ \\+---+ +---+ / \ |DC6| {VNF a} +---+ +---+ +---+ |DC3| |DC4| {VNF a,b,c} +---+ +---+ {VNF a, b} {VNF a, c} Figure 2: Application Service Policy-aware Network Operation Lee, et, al. Expires October 6, 2015 [Page 17] Internet-Draft ACTN Requirement April 2015 This scenario is similar to the previous case in that the VN service policy for the application can be met by a set of multiple destinations that provide the required virtual network functions (VNF). Virtual network functions can be, for example, security functions required by the VN application. The VN service policy by the CNC would indicate the locations of a certain VNF that can be fulfilled. This policy information is critical in finding the optimal network path subject to this constraint. As VNFs can be dynamically moved across different DCs, this policy should be dynamically enforced from the CNC to the MDSC and the PNCs. 4.3. Dynamic Service Control Policy Enforcement for Performance and Fault Management +------------------------------------------------+ | Customer Network Controller | +------------------------------------------------+ 1.Traffic| /|\4.Traffic | /|\ Monitor& | | Monitor | | 8.Traffic Optimize | | Result 5.Service | | modify & Policy | | modify& | | optimize \|/ | optimize Req.\|/ | result +------------------------------------------------+ | Mult-domain Service Controller | +------------------------------------------------+ 2. Path | /|\3.Traffic | | Monitor | | Monitor | |7.Path Request | | Result 6.Path | | modify & | | modify& | | optimize \|/ | optimize Req.\|/ | result +------------------------------------------------+ | Physical Network Controller | +------------------------------------------------+ Figure 3: Dynamic Service Control for Performance and Fault Management Figure 3 shows the flow of dynamic service control policy enforcement for performance and fault management initiated by customer per their VN. The feedback loop and filtering mechanism tailored for VNs performed by the MDSC differentiates this ACTN scope from traditional network management paradigm. VN level dynamic OAM data model is a building block to support this capability. Lee, et, al. Expires October 6, 2015 [Page 18] Internet-Draft ACTN Requirement April 2015 4.4. E2E VN Survivability and Multi-Layer (Packet-Optical) Coordination for Protection/Restoration +----------------+ | Customer | | Network | | Controller | +--------*-------+ * | E2E VN Survivability Req. * | - VN Protection/Restoration * v - 1+1, Restoration, etc. +----=-*----+ - End Point (EP) info. | | | MDSC | MDSC enforces VN survivability | | requirement, determining the | | optimal combination of Packet/ +---==-*-----+ Opticalprotection/restoration, * Optical bypass, etc. * * ********************************************** * * * * +----*-----+ +----*----+ +----*-----+ +----*----+ |PNC for | |PNC for | |PNC for | |PNC for | |Access N. | |Packet C.| |Optical C.| |Access N.| +----*-----+ +----*----+ +----*-----+ +---*-----+ * --*--- * * * /// \\\ * * --*--- | Packet | * ----*- /// \\\ | Core +------+------/// \\\ | Access +----\\ /// * | Access | | Network | ---+-- * | Network | +---+ |\\\ /// | * \\\ ///---+EP6| | +---+- | | -----* -+---+ +---+ +-+-+ | | +----/// \\\ | | |EP1| | +--------------+ Optical | | | +---+ +---+ | | Core +------+ +--+EP5| +-+-+ \\\ /// +---+ |EP2| ------ | +---+ | | +--++ ++--+ |EP3| |EP4| +---+ +---+ Figure 4: E2E VN Survivability and Multi-layer Coordination for Protection and Restoration Lee, et, al. Expires October 6, 2015 [Page 19] Internet-Draft ACTN Requirement April 2015 Figure 4 shows the need for E2E protection/restoration control coordination that involves CNC, MDSC and PNCs to meet the VN survivability requirement. VN survivability requirement and its policy need to be translated into multi-domain and multi-layer network protection and restoration scenarios across different controller types. After an E2E path is setup successfully, the MSDC has a unique role to enforce policy-based flexible VN survivability requirement by coordinating all PNC domains. As seen in Figure 4, multi-layer (i.e., packet/optical) coordination is a subset of this E2E protection/restoration control operation. The MDSC has a role to play in determining an optimal protection/restoration level based on the customer's VN survivability requirement. For instance, the MDSC needs to interface the PNC for packet core as well as the PNC for optical core and enforce protection/restoration policy as part of the E2E protection/restoration. Neither the PNC for packet core nor the PNC for optical core is in a position to be aware of the E2E path and its protection/restoration situation. This role of the MSDC is unique for this reason. In some cases, the MDSC will have to determine and enforce optical bypass to find a feasible reroute path upon packet core network failure which cannot be resolved the packet core network itself. To coordinate this operation, the PNCs will need to update its domain level abstract topology upon resource changes due to a network failure or other factors. The MSDC will incorporate all these update to determine if an alternate E2E reroute path is necessary or not based on the changes reported from the PNCs. It will need to update the E2E abstract topology and the affected CN's VN topology in real-time. This refers to dynamic synchronization of topology from Physical topology to abstract topology to VN topology. MDSC will also need to perform the path restoration signaling to the affected PNCs whenever necessary. 5. ACTN interfaces requirements This section provides ACTN interface requirements for the two interfaces that are within the ACTN scope. . CMI: CNC-MDSC Interface (Section 3.1) . MPI: MDSC-PNC Interface (Section 3.2) For each requirement, it also identifies the following categories: Lee, et, al. Expires October 6, 2015 [Page 20] Internet-Draft ACTN Requirement April 2015 1. Applicable: Existing components are applicable to ACTN architecture 2. Extensible: Existing components can be extended to ACTN architecture 3. New: The components are new work to ACTN architecture 5.1. CMI Interface Requirements Lee, et, al. Expires October 6, 2015 [Page 21] Internet-Draft ACTN Requirement April 2015 Requirement Notes 1. Security/Policy Negotiation - Some new element for (Who are you?) (Between CNC controller-controller and MDSC) (CNC-MDSC) - Configured vs. Discovered security/policy - Trust domain verification negotiation aspect. (External Entity vs. Internal - It is not entirely Service Department) clear if there is - Push/Pull support (for existing work that can policy) be extended to support all requirements 2. VN Topology Query (Can you - New for some primitives give me VN?) (From CNC to and IEs (e.g., VN MDSC) Topology Query, VN - VN end-points (CE end) Topo. Negotiation, VN - VN Topology Service-specific end-points) Multi-Cost Objective Function o Latency Map - Extensible for some o Available B/W Map IE/Objects from PCEP o Latency Map and (e.g., Objective Available B/W Map function, etc.) together o Other types - VN Topology diversity o Node/Link disjoint from other VNs o VN Topology level diversity (e.g., VN1 and VN2 must be disjoint) - VN Topology type o Path vector (tunnel) o Node/Links (graph) 3. VN Topology Query Response - Similar comment to #2. (From MDSC to CNC: Here's the VN Topology that can be given to you if you accept) - For VN Topology, o This is what can be reserved for you o This is what is available beyond what is given to you (potential) 4. VN Topology Abstraction - Applicable (Generic TE Model (generic network model) YANG model) 5. VN Topology Abstraction - Extensible from generic Model (Service-specific model TE Abstraction Model Lee, et, al. Expires October 6, 2015 [Page 22] Internet-Draft ACTN Requirement April 2015 that include customer (TEAS WG) to include endpoints) service-related parameters and end- point abstraction 6. Basic VN Instantiation - It is not completely Request/Confirmation clear if existing (Between CNC and MDSC: I need components can be VN for my service, please extended or if these instantiate my VN) require new - VN instance ID protocol/primitives/IEs - VN end-points . - VN service requirement - It appears that there o Latency only is no existing proper o B/W guarantee protocol that supports o Latency and B/W all required guarantee together primitives/IEs, but - VN diversity this is subject to o Node/Link disjoint further analysis. from other VNs - VN level diversity (e.g., VN1 and VN2 must be disjoint) - VN type o Path vector (tunnel) o Node/Links (graph) - VN instance ID per service (unique id to identify VNs) - If failed to instantiate the requested VN, say why 7. Dynamic/On-demand VN - New: dynamic policy Instantiation/Modification enforcement seems to be and Confirmation with new while abstraction feedback loop (This is to be of service-aware differentiated from Basic VN abstraction model can Instantiation) be extended from basic - Performance/Fault Monitoring TE YANG model. - Utilization Monitoring - Note: Feedback loop (Frequency of report) requires very frequent - Abstraction of Resource updates of abstracted Topology reflecting these topology real-time. service-related parameters - Current management - Dynamic Policy enforcement interface may not be appropriate to support this feedback loop and the real-time operation. Lee, et, al. Expires October 6, 2015 [Page 23] Internet-Draft ACTN Requirement April 2015 This is related to Section 3.3. 8. VN lifecycle management/operation - Create (same as VN instantiate Request) - Delete - Modify - Update (VN level OAM Monitoring) under policy agreement 9. Coordination of multi- - This is from Section destination service 4.2.1 and Requirement 7 requirement/policy to support (above) but there are dynamic applications such as unique requirements. VM migration, disaster - New: Primitives that recovery, load balancing, allow integrated etc. network operation and - Service-policy primitives service operation and its parameters - See also the corresponding MPI requirement. 5.2. MPI (MDSC-PNC Interface) Lee, et, al. Expires October 6, 2015 [Page 24] Internet-Draft ACTN Requirement April 2015 Requirement Notes 1. Security/Policy negotiation - Extensible from (who are you?) PCEP/YANG - Exchange of key, etc. - End-point mobility for - Domain preference + local multi-destination policy exchange policy is new element - Push/Pull support in primitives and Data - Preferred peering points Model - Preferred route - Reroute policy - End-point mobility (for multi-destination) 2. Topology Query /Response - Pull Model with (Pull Model from MDSC to PNC: Customer's VN Please give me your domain requirement can be topology) extended from existing - TED Abstraction level components. negotiation - Abstraction negotiation - Abstract topology (per primitive seems to be policy) new ACTN work. o Node/Link metrics o Node/Link Type (Border/Gateway, etc.) o All TE metrics (SRLG, etc.) o Topology Metrics (latency, B/W available, etc.) 3. Topology Update (Push Model - Push/Subscription can from PNC to MDSC) be extended from - Under policy agreement, existing components topology changes to be pushed (YANG) to MDSC from PNC 4. VN Path Computation Request - Extensible from PCEP (From MDSC to PNC: Please give me a path in your domain) - VN Instance ID (Note: this is passed from CNC to MDSC) - End-point information - CE ends - Border points (if applicable) - All other PCE request info Lee, et, al. Expires October 6, 2015 [Page 25] Internet-Draft ACTN Requirement April 2015 (PCEP) 5. VN Path Computation Reply - Extensible from PCEP (here's the path info per your request) - Path level abstraction - LSP DB - LSP ID ?? - VN ID 6. Coordination of multi-domain - New element on Centralized Signaling (MSDC centralized signaling operation) Path Setup operation for MSDC as Operation well as control-control - MSDC computes E2E path primitives (different across multi-domain (based on from NE-NE signaling abstract topology from each primitives) although PNC) RSVP-TE can be extended - MDSC determines the domain to support some sequence functions defined here - MDSC request path signaling if not all. to each PNC (domain) - MDSC finds alternative path if any of the PNCs cannot find its domain path o PNC will crankback to MDSC if it cannot find its domain path o PNC will confirm to MDSC if it finds its domain path 7. Path Restoration Operation - New for MDSC's central (after an E2E path is setup path restoration successfully, some domain had primitives and a failure that cannot be interaction with each restored by the PNC domain) PNC to coordinate this - The problem PNC will send real-time operation. this notification with changed abstract topology Related to Section 3.4. (computed after resource changes due to failure/other factors) - MDSC will find an alternate E2E path based on the changes reported from PNC. It will need to update the E2E Lee, et, al. Expires October 6, 2015 [Page 26] Internet-Draft ACTN Requirement April 2015 abstract topology and the affected CN's VN topology in real-time (This refers to dynamic synchronization of topology from Physical topology to abstract topology to VN topology) - MDSC will perform the path restoration signaling to the affected PNCs. 8. Coordination of Multi- - Related to Section 3.1. destination service - New for ACTN in restoration operation (CNC determining the optimal have, for example, multiple destination on the fly endpoints where the source given customer policy endpoint can send its data to and network condition either one of the endpoints) and its related real- - When PNC reports domain time network operation problem that cannot be procedures. resolved at MDSC level because of there is no network restoration path to a given destination. - Then MDSC has Customers' profile in which to find the customer has "multi- destination" application. - Under policy A, MDSC will be allowed to reroute the customer traffic to one of the pre-negotiated destinations and proceed with restoration of this particular customer's traffic. - Under policy B, CNC may reroute on its VN topology level and push this to MDSC and MDSC maps this into its abstract topology and proceed with restoration of this customer's traffic. - In either case, the MDSC will proceed its restoration operation (as explained in Req. 6) to the corresponding Lee, et, al. Expires October 6, 2015 [Page 27] Internet-Draft ACTN Requirement April 2015 PNCs. 9. MDSC-PNC policy negotiation - This seems to be new to is also needed as to how ACTN. restoration is done across MDSC and PNCs. 10. Generic Abstract Topology - Current Generic TE YANG Update per changes due to new model applicable. path setup/connection However, the real-time failure/degradation/restorati nature of these models on with frequent update and synchronization check is new for ACTN. 11. Service-specific Abstract - Extensible from generic Topology Update per changes TE Abstraction Model due to new path (TEAS WG) to include setup/connection service-related failure/degradation/restorati parameters and end- on point abstraction 12. Abstraction model of - Extensible from generic technology-specific topology TE Abstraction Model element (TEAS WG) to include abstraction of technology-specific element. 6. References 6.1. Informative References [ACTN-Frame] D. Ceccarelli, et al., "Framework for Abstraction and Control of Transport Networks", draft-ceccarelli-actn- framework, work in progress. Lee, et, al. Expires October 6, 2015 [Page 28] Internet-Draft ACTN Requirement April 2015 7. Contributors Contributors' Addresses Authors' Addresses Young Lee Huawei Technologies 5340 Legacy Drive Plano, TX 75023, USA Phone: (469)277-5838 Email: leeyoung@huawei.com Sergio Belotti Alcatel Lucent Via Trento, 30 Vimercate, Italy Email: sergio.belotti@alcatel-lucent.com Khuzema Pithewan Infinera Email: kpithewan@infinera.com Daniele Ceccarelli Ericsson Torshamnsgatan,48 Stockholm, Sweden Email: daniele.ceccarelli@ericsson.com Dhruv Dhoddy Email: dhruv.ietf@gmail.com Lee, et, al. Expires October 6, 2015 [Page 29]