idnits 2.17.1 draft-ietf-teas-actn-requirements-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 3, 2017) is 2670 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'ACTN-frame' is mentioned on line 87, but not defined Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Young Lee (Editor) 2 Dhruv Dhody 3 Internet Draft Huawei 5 Intended status: Informational Sergio Belotti 6 Alcatel-Lucent 7 Expires: July 2017 8 Khuzema Pithewan 9 Infinera 11 Daniele Ceccarelli 12 Ericsson 14 January 3, 2017 16 Requirements for Abstraction and Control of TE Networks 18 draft-ietf-teas-actn-requirements-04.txt 20 Abstract 22 This document provides a set of requirements for abstraction and 23 control of Traffic Engineering networks to facilitate virtual 24 network operation via the creation of a single virtualized network 25 or a seamless service. This supports operators in viewing and 26 controlling different domains (at any dimension: applied technology, 27 administrative zones, or vendor-specific technology islands) as a 28 single virtualized network. 30 Status of this Memo 32 This Internet-Draft is submitted to IETF in full conformance with 33 the provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF), its areas, and its working groups. Note that 37 other groups may also distribute working documents as Internet- 38 Drafts. 40 Internet-Drafts are draft documents valid for a maximum of six 41 months and may be updated, replaced, or obsoleted by other documents 42 at any time. It is inappropriate to use Internet-Drafts as 43 reference material or to cite them other than as "work in progress." 45 The list of current Internet-Drafts can be accessed at 46 http://www.ietf.org/ietf/1id-abstracts.txt 48 The list of Internet-Draft Shadow Directories can be accessed at 49 http://www.ietf.org/shadow.html. 51 This Internet-Draft will expire on July 3, 2017. 53 Copyright Notice 55 Copyright (c) 2016 IETF Trust and the persons identified as the 56 document authors. All rights reserved. 58 This document is subject to BCP 78 and the IETF Trust's Legal 59 Provisions Relating to IETF Documents 60 (http://trustee.ietf.org/license-info) in effect on the date of 61 publication of this document. Please review these documents 62 carefully, as they describe your rights and restrictions with 63 respect to this document. Code Components extracted from this 64 document must include Simplified BSD License text as described in 65 Section 4.e of the Trust Legal Provisions and are provided without 66 warranty as described in the Simplified BSD License. 68 Table of Contents 70 1. Introduction...................................................3 71 2. High-level ACTN requirements...................................4 72 2.1. Service-Specific Requirements.............................4 73 2.2. Network-Related Requirements..............................7 74 3. ACTN Interfaces Requirements...................................8 75 3.1. CMI Requirements..........................................9 76 3.2. MPI Requirements.........................................11 77 4. References....................................................13 78 4.1. Normative References.....................................13 79 4.2. Informative References...................................14 80 5. Contributors..................................................15 81 Authors' Addresses...............................................15 83 1. Introduction 85 This document provides a set of requirements for Abstraction and 86 Control of Traffic Engineering (TE) Networks (ACTN) identified in 87 various use-cases. [ACTN-frame] defines the base reference 88 architecture and terminology. 90 ACTN refers to the set of virtual network operations needed to 91 orchestrate, control and manage large-scale multi-domain TE networks 92 so as to facilitate network programmability, automation, efficient 93 resource sharing, and end-to-end virtual service aware connectivity 94 and network function virtualization services. 96 These operations are summarized as follows: 98 - Abstraction and coordination of underlying network resources 99 independent of how these resources are managed or controlled, 100 so that higher-layer entities can dynamically control virtual 101 networks based on those resources. Control includes creating, 102 modifying, monitoring, and deleting virtual networks. 104 - Collation of the resources from multiple TE networks (multiple 105 technologies, equipment from multiple vendors, under the 106 control of multiple administrations) through a process of 107 hierarchical abstraction to present a customer with a single 108 virtual network. This is chieved by presenting the network 109 domain as an abstracted topology to the customer via open and 110 programmable interfaces. Hierarchical abstraction allows for 111 the recursion of controllers in a customer-provider 112 relationship. 114 - Orchestration of end-to-end virtual network services and 115 applications via allocation of network resources to meet 116 specific service, application and customer requirements. 118 - Adaptation of customer requests (to control virtual resources) 119 to the physical network resources performing the necessary 120 mapping, translation, isolation and, policy that allows 121 conveying, managing and enforcing customer policies with 122 respect to the services and the network of the customer. 124 - Provision via a data model of a computation scheme and virtual 125 control capability to customers who request virtual network 126 services. Note that these customers could, themselves, be 127 service providers. 129 ACTN solutions will build on, and extend, existing TE constructs and 130 TE mechanisms wherever possible and appropriate. Support for 131 controller-based approaches is specifically included in the possible 132 solution set. 134 Section 2 provides high-level ACTN requirements. Section 3 provides 135 ACTN interface requirements. 137 2. High-level ACTN requirements 139 This section provides a summary of use-cases in terms of two 140 categories: (i) service-specific requirements; (ii) network-related 141 requirements. 143 Service-specific requirements listed below are uniquely applied to 144 the work scope of ACTN. Service-specific requirements are related to 145 the virtual service coordination function. These requirements are 146 related to customer's VNs in terms of service policy associated with 147 VNs such as service performance objectives, VN endpoint location 148 information for certain required service specific functions (e.g., 149 security and others), VN survivability requirement, or dynamic 150 service control policy, etc. 152 Network-related requirements are related to the virtual network 153 operation function. These requirements are related to multi-domain 154 and multi-layer signaling, routing, protection/restoration and 155 synergy, re-optimization/re-grooming, etc. These requirements are 156 not inherently unique for the scope of ACTN but some of these 157 requirements are in scope of ACTN, especially for coherent/seamless 158 operation aspect of multiple controller hierarchy. 160 2.1. Service-Specific Requirements 162 1. Requirement 1: Policy Enforcement 164 Ability to provide service requirement/policy (between Customer 165 and Network) and mechanism to enforce Service Level Agreements 166 (SLA). 168 - Endpoint selection policy, routing policy, time-related 169 policy, etc. 171 Reference: [KLEE], [LOPEZ], [SHIN], [DHODY], [FANG]. 173 2. Requirement 2: Virtual Network (VN) Query 175 Ability to request/respond VN Query ("Can you give me these 176 VN(s)?") 178 Request Input: 180 - VN end-points (Customer Edge equipment) 181 - VN Topology Service-specific Multi-Cost Objective Function 182 - VN constraints requirement 183 o Latency only, bandwidth guarantee, joint latency and 184 bandwidth guarantee 185 - VN Topology diversity (e.g., VN1 and VN2 must be disjoint; 186 Node/link disjoint from other VNs) 187 - VN Topology type: path, graph 189 Response includes VN topology: 191 - Exact 192 - Potential 194 Reference: [KUMAKI], [FANG], [CHENG]. 196 3. Requirement 3: VN Instantiation ("Please create a VN for me") 198 Ability to request/confirm VN Instantiation 200 Request Input: 202 - VN instance ID 203 - VN end-points (Customer Edge equipment) 204 - VN Topology Service-specific Multi-Cost Objective Function 205 - VN constraints requirement 206 o Latency only, bandwidth guarantee, joint latency and 207 bandwidth guarantee 208 - VN Topology diversity (e.g., VN1 and VN2 must be disjoint; 209 Node/link disjoint from other VNs) 210 - VN Topology type: path, graph 212 Response includes VN topology: 214 - Exact 215 - Potential 217 Reference: [KUMAKI], [FANG], [CHENG]. 219 4. Requirement 4: VN Lifecycle Management & Operation (M&O) 221 Ability to do the following VN operations: 223 - Delete 224 - Modify 225 - Update (VN level Operations, Administration and Management 226 (OAM) Monitoring) under policy agreement 228 Reference: [FANG], [KUMAKI], [LOPEZ]. 230 5. Requirement 5: VN Service Operation 232 Ability to set up and manage end-to-end services on the VN 233 involving multi-domain and multi-layer operations of the 234 underlying network while meeting constraints based on SLAs. 236 Reference: [LOPEZ], [KUMAKI], [CHENG], [DHODY], [FANG], [KLEE]. 238 6. Requirement 6: VN Confidentiality/Security 240 - A VN customer must not be able to control another customer's 241 virtual network 242 - A VN customer must not see any routing information (e.g. IGP 243 database, TE database) relating to another customer's 244 virtual network 246 Reference: [KUMAKI], [FANG], [LOPEZ] 248 7. Requirement 7: Multi-Destination Coordination 249 Coordination of multi-destination service requirement/policy to 250 support dynamic applications such as VM migration, disaster 251 recovery, load balancing, etc. 253 - Service-policy primitives and their parameters 255 Reference: [FANG], [LOPEZ], [SHIN]. 257 2.2. Network-Related Requirements 259 1. Requirement 1: Single Virtualized Network Topology 261 Ability to build virtual network operation infrastructure based 262 on multi-layer, multi-domain topology abstracted from multiple 263 physical network control mechanisms (e.g., GMPLS, OpenFlow, PCE, 264 NMS, etc.) 266 Reference: [KLEE], [LOPEZ], [DHODY], [CHENG]. 268 2. Requirement 2: Multi-Domain & Multi-layer Coordination 270 Ability to coordinate multi-domain and multi-layer path 271 computation and path setup operation 273 - End-to-end path computation across multi-domain networks 274 (based on abstract topology from each domain) 275 - Domain sequence determination 276 - Request for path signaling to each domain controller 277 - Alternative path computation if any of the domain 278 controllers cannot find its domain path 280 Reference: [CHENG], [DHODY], [KLEE], [LOPEZ], [SHIN], [SUZUKI]. 282 3. Requirement 3: End-to-End Path Restoration 284 Ability to perform end-to-end Path Restoration Operations 286 - Intra-domain recovery 287 - Cross-domain recovery 289 Reference: [CHENG], [KLEE], [DHODY], [LOPEZ], [SHIN]. 291 4. Requirement 4: Dynamicity of network control operations 293 The ACTN interfaces should support dynamic network control 294 operations. This includes, but is not limited to, the following: 296 - Real-time VN control (e.g., fast recovery/reroute upon 297 network failure). 298 - Fast convergence of abstracted topologies upon changes due 299 to failure or reconfiguration across the network domain 300 view, the multi-domain network view and the customer view. 301 - Large-scale VN operation (e.g., the ability to query tens of 302 thousands of nodes, and to examine tens of thousands of 303 connectivity requests) for time-sensitive applications. 305 Reference: [SHIN], [XU], [XU2], [KLEE], [KUMAKI], [SUZUKI]. 307 5. Requirement 5: Dynamic VN Control 309 Dynamic/On-demand VN Modification/Confirmation with feedback loop 310 to the customer 312 - Traffic monitoring and control policies sent to the network 313 - Network states based traffic optimization policies 314 - Utilization Monitoring (including frequency of reporting) 315 - Abstraction of Resource Topology reflecting service-related 316 parameters 318 Reference: [XU], [XU2], [DHODY], [CHENG] 320 3. ACTN Interfaces Requirements 322 This section provides detailed ACTN interface requirements for the 323 two interfaces that are within the ACTN scope based on [ACTN-Frame] 324 and the use-cases referenced in this document. 326 The ACTN architecture described in [ACTN-Frame] comprises three 327 functional components: 329 - CNC: Customer Network Controller 330 - MDSC: Multi Domain Service Coordinator 331 - PNC: Physical Network Controller 333 The architecture gives rise to two interfaces between components: 335 - CMI: CNC-MDSC Interface 336 - MPI: MDSC-PNC Interface 338 3.1. CMI Requirements 340 1. Security/Policy Negotiation ("Who are you?") between CNC and 341 MDSC 343 - Trust domain verification (External Entity versus Internal 344 Service Department) 345 - Push/Pull support (for policy) 347 2. VN Topology Query ("Can you give me VN?") from CNC to MDSC 349 - VN end-points (CE end) 350 - VN Topology Service-specific Multi-Cost Objective Function 351 o Latency Map 352 o Available Bandwidth Map 353 o Latency Map and Available Bandwidth Map together 354 o Other types 355 - VN Topology diversity 356 o Node/Link disjoint from other VNs 357 o VN Topology level diversity (e.g., VN1 and VN2 must be 358 disjoint) 359 - VN Topology type 360 o Path vector (tunnel) 361 o Node/Links (graph) 363 3. VN Topology Query Response from MDSC to CNC: "Here's the VN 364 Topology that can be given to you if you request it" 366 - For VN Topology, 367 o This is what can be reserved for you 368 o This is what is available beyond what you asked for 369 (potential) 371 4. Basic VN Instantiation Request/Confirmation between CNC and 372 MDSC: "I need a VN for my service, please instantiate my VN" 373 - VN instance ID 374 - VN end-points 375 - VN service requirement 376 o Latency only 377 o B/W guarantee 378 o Latency and B/W guarantee together 379 - VN diversity 380 o Node/Link disjoint from other VNs 381 - VN level diversity (e.g., VN1 and VN2 must be disjoint) 382 - VN type 383 o Path vector (tunnel) 384 o Node/Links (graph) 385 - VN instance ID per service (unique id to identify VNs) 386 - If failed to instantiate the requested VN, say why 388 5. Dynamic/On-demand VN Instantiation/Modification and 389 Confirmation with feedback loop (This is to be differentiated 390 from Basic VN Instantiation) 392 - Performance/Fault Monitoring 393 - Utilization Monitoring (Frequency of report) 394 - Abstraction of Resource Topology reflecting these service- 395 related parameters 396 - Dynamic Policy enforcement 398 6. VN lifecycle management/operation 400 - Create (same as VN instantiate Request) 401 - Delete 402 - Modify 403 - Update (VN level OAM Monitoring) under policy agreement 405 7. Coordination of multi-destination service requirement/policy 406 to support dynamic applications such as VM migration, 407 disaster recovery, load balancing, etc. 409 - Service-policy primitives and its parameters 411 3.2. MPI Requirements 413 1. Security/Policy negotiation ("Who are you?") 415 - Exchange of key, etc. 416 - Domain preference + local policy exchange 417 - Push/Pull support 418 - Preferred peering points 419 - Preferred route 420 - Reroute policy 421 - End-point mobility (for multi-destination) 423 2. Topology Query /Response (Pull Model from MDSC to PNC: "Please 424 give me your domain topology") 426 - TED Abstraction level negotiation 427 - Abstract topology (per policy) 428 o Node/Link metrics 429 o Node/Link Type (Border/Gateway, etc.) 430 o All TE metrics (SRLG, etc.) 431 o Topology Metrics (latency, B/W available, etc.) 433 3. Topology Update (Push Model from PNC to MDSC: "The topology 434 has been updated") 436 - Under policy agreement, topology changes to be pushed to 437 MDSC from PNC 439 4. VN Path Computation Request (From MDSC to PNC: "Please give me 440 a path in your domain") 442 - VN Instance ID (Note: this is passed from CNC to MDSC) 443 - End-point information 444 - CE ends 445 - Border points (if applicable) 446 - All other PCE request info (PCEP) 448 5. VN Path Computation Reply ("Here's the path info per your 449 Request") 450 - Path level abstraction 451 - LSP DB 452 - LSP ID 453 - VN ID 455 6. Coordination of multi-domain Centralized Signaling Path Setup 456 Operation (From MDSC to PNC: "Please give me your domain path 457 if you can; otherwise, let me know if that is not possible." 459 - MSDC computes E2E path across multi-domain (based on abstract 460 topology from each PNC) 461 - MDSC determines the domain sequence 462 - MDSC request path signaling to each PNC (domain) 463 - MDSC finds alternative path if any of the PNCs cannot find 464 its domain path 465 o PNC will crankback to MDSC if it cannot find its domain 466 path 467 o PNC will confirm to MDSC if it finds its domain path 469 7. Path Restoration Operation after an E2E path is setup 470 successfully, some domain had a failure that cannot be restored 471 by the PNC domain (From PNC to MDSC: "My domain path failed and 472 I cannot restore it."; From MDSC to PNC: "OK. Please set up a 473 new domain path with this ingress/egress nodes." 475 - The problem PNC will send this notification with changed 476 abstract topology (computed after resource changes due to 477 failure/other factors) 478 - MDSC will find an alternate E2E path based on the changes 479 reported from PNC. It will need to update the E2E abstract 480 topology and the affected CN's VN topology in real-time (This 481 refers to dynamic synchronization of topology from Physical 482 topology to abstract topology to VN topology) 483 - MDSC will perform the path restoration signaling to the 484 affected PNCs. 486 8. Coordination of Multi-destination service restoration 487 operation: the CNC may have, for example, multiple endpoints 488 where the source can send its data to either one of the 489 endpoints. (From PNC to MDSC, "I lost my connectivity to the 490 endpoint. Please help to find alternative endpoint."; From MDSC 491 to PNC, "Please use this alternative endpoint.") 493 - When PNC reports domain problem that cannot be resolved at 494 PNC level because of there is no network restoration path to 495 a given destination, then MDSC has customers' profile in 496 which to find the customer has "multi-destination" 497 application. 498 - Under policy A, MDSC will be allowed to reroute the customer 499 traffic to one of the pre-negotiated destinations and 500 proceed with restoration of this particular customer's 501 traffic. 502 - Under policy B, CNC may reroute on its VN topology level and 503 push this to MDSC and MDSC maps this into its abstract 504 topology and proceed with restoration of this customer's 505 traffic. 506 - In either case, the MDSC will proceed its restoration 507 operation (as explained in Req. 7) to the corresponding 508 PNCs. 510 9. MDSC-PNC policy negotiation is also needed as to how 511 restoration is done across MDSC and PNCs. (From MDSC to PNC: 512 "Please resolve at your domain for restoration of LSP." 514 10. Generic Abstract Topology Update per changes due to new path 515 setup/connection failure/degradation/restoration (From PNC to 516 MDSC: "Here's an updated topology") 518 11. Service-specific Abstract Topology Update per changes due 519 to new path setup/connection failure/degradation/restoration 520 (From PNC to MDSC: "Here's an updated service-specific 521 topology") 523 4. References 525 4.1. Normative References 527 [ACTN-Frame] D. Ceccarelli, et al., "Framework for Abstraction and 528 Control of Transport Networks", draft-ietf-teas-actn- 529 framework, work in progress. 531 4.2. Informative References 533 [CHENG] W. Cheng, et. al., "ACTN Use-cases for Packet Transport 534 Networks in Mobile Backhaul Networks", draft-cheng-actn- 535 ptn-requirements, work in progress. 537 [DHODY] D. Dhody, et. al., "Packet Optical Integration (POI) Use 538 Cases for Abstraction and Control of Transport Networks 539 (ACTN)", draft-dhody-actn-poi-use-case, work in progress. 541 [FANG] L. Fang, "ACTN Use Case for Multi-domain Data Center 542 Interconnect", draft-fang-actn-multidomain-dci, work in 543 progress. 545 [KLEE] K. Lee, H. Lee, R. Vilata, V. Lopez, "ACTN Use-case for E2E 546 Network Services in Multiple Vendor Domain Transport 547 Networks", draft-klee-teas-actn-connectivity-multi-domain, 548 work-in-progress. 550 [KUMAKI] K. Kumaki, T. Miyasaka, "ACTN : Use case for Multi Tenant 551 VNO", draft-kumaki-teas-actn-multitenant-vno, work in 552 progress. 554 [LOPEZ] D. Lopez (Ed), "ACTN Use-case for Virtual Network Operation 555 for Multiple Domains in a Single Operator Network", draft- 556 lopez-actn-vno-multidomains, work in progress. 558 [SHIN] J. Shin, R. Hwang, J. Lee, "ACTN Use-case for Mobile Virtual 559 Network Operation for Multiple Domains in a Single 560 Operator Network", draft-shin-actn-mvno-multi-domain, work 561 in progress. 563 [XU] Y. Xu, et. al., "Use Cases and Requirements of Dynamic Service 564 Control based on Performance Monitoring in ACTN 565 Architecture", draft-xu-actn-perf-dynamic-service-control, 566 work in progress. 568 [XU2] Y. Xu, et. al., "Requirements of Abstract Alarm Report in ACTN 569 architecture", draft-xu-teas-actn-abstract-alarm-report, 570 work-in-progress. 572 [SUZUKI] T. Suzuki, et. al., "Use-case and Requirements for Multi- 573 domain Operation Plane Change", draft-suzuki-teas-actn- 574 multidomain-opc, work-in-progress. 576 5. Contributors 578 Kwangkook Lee 579 KT 580 Email: kwangkooglee@gmail.com 582 Takuya Miyasaka 583 KDDI 584 Email: ta-miyasaka@kddi.com 586 Yunbin Xu 587 CATR 588 Email: xuyunbin@mail.ritt.com.cn 590 Toshiaki Suzuki 591 Hitachi 592 Email: toshiaki.suzuki.cs@hitachi.com 594 Authors' Addresses 596 Young Lee (Editor) 597 Huawei Technologies 598 5340 Legacy Drive 599 Plano, TX 75023, USA 600 Phone: (469)277-5838 601 Email: leeyoung@huawei.com 603 Dhruv Dhody 604 Huawei Technologies 605 Email: dhruv.ietf@gmail.com 607 Sergio Belotti 608 Nokia 609 Via Trento, 30 610 Vimercate, Italy 611 Email: sergio.belotti@nokia.com 613 Khuzema Pithewan 614 Infinera 615 Email: kpithewan@infinera.com 617 Daniele Ceccarelli 618 Ericsson 619 Torshamnsgatan,48 620 Stockholm, Sweden 621 Email: daniele.ceccarelli@ericsson.com